Wilc3000 on SAMA5D2 custom board

we have designed a custom board based on sama5D21. we have interfaced wilc3000 to the flexcom spi of the sama device. the device initially boots up and wifi works properly in access point mode.after some time spi transfers stalls and the device needs to be rebooted. the following is the error message that is shown.

[  226.829181] WILC_SPI spi1.0: Failed data response read, c3 0 0
[  226.834963] WILC_SPI spi1.0: Failed block data write...
[  226.857047] WILC_SPI spi1.0: Reset and retry 10 0 40960
[  226.935952] WILC_SPI spi1.0: Failed data response read, 0 0 0
[  226.941779] WILC_SPI spi1.0: Failed block data write...
[  226.956723] WILC_SPI spi1.0: Failed cmd response, cmd (cf), resp (00)
[  226.963107] WILC_SPI spi1.0: Failed cmd reset
[  226.967538] WILC_SPI spi1.0: Reset and retry 9 0 40960
[  226.995842] WILC_SPI spi1.0: Failed cmd response, cmd (c7), resp (00)
[  227.002233] WILC_SPI spi1.0: Failed cmd, write block (00000000)...
[  227.024047] WILC_SPI spi1.0: Failed cmd response, cmd (cf), resp (00)
[  227.030561] WILC_SPI spi1.0: Failed cmd reset

i am using openwrt ver kernel 5.4.41,openwrt version.
linux-github_com_linux4sam_linux_at91_git-linux4sam_2020_04
wilc driver driver-wilc_linux_15_3_1

please advice on the same.

Thanks
Akhilesh

is this some vendor SDK ?

what does ubus call system board say ?

{
        "kernel": "5.4.41-linux4sam-2020.04",
        "hostname": "WiZNG2EL",
        "system": "ARMv7 Processor rev 1 (v7l)",
        "model": "Atmel SAMA5D2 Xplained",
        "board_name": "sama5d2_xplained",
        "release": {
                "distribution": "Openwrt",
                "version": "19.07.2",
                "revision": "r10947-65030d81f3",
                "target": "at91/sama5",
                "description": "Openwrt 19.07.2 linux4sam-2020.04"
        }
}

This is vendor specific release, if you have issues with it, ask them for support.

Openwrt 19.07 never used any v5 kernel.


It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

  1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
  2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
  3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.