WILC1000 not working in SAM5D2_Xplained Board

Moderator: nferre

freaky_geek234
Posts: 9
Joined: Sat May 13, 2017 12:06 pm

WILC1000 not working in SAM5D2_Xplained Board

Fri Oct 20, 2017 12:11 pm

Hi,
Iam trying to port WILC1000 to linux (Atmel SAMA5D2_Xplained board). I have enabled WILC1000 SPI driver in staging drivers as a module (option <M>)

I have copied wilc1000_spi.ko and wilc1000.ko to /lib/modules/${Kernel_version}/kernel/drivers/staging/wilc/

and copied wilc1003_firmware.bin (which i got from some github) to /lib/firmware/atmel (atmel folder created by me) and also checked copying to lib/firmware, /atmel/ , /lib/modules/${Kernel_version}/kernel/drivers/staging/wilc/ also

I have made entry for wilc1000_spi in dts file as below:

spi1: spi@fc000000 {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_spi1_default>;
status = "okay";

wilc_spi@0 {
compatible = "atmel,wilc_spi";
spi-max-frequency = <6000000>;
reg = <0>;
status = "okay";
};




};


but after doing all these things, wilc1000 is not being detected.

if i run ifconfig: wlan0 is not appearing.

in the document when insmod is bein run. then it is initializing wilc1000 and firmware also being initialized and updated. debug messages are being displayed.

but when iam running insmod, no messages are being displayed. if i run modinfo -F firmware wilc1000 or modinfo -F firmware wilc1000_spi then also iam not getting any firmware required info.

am i missing anything. how firmware is being updated or initialized by insmod command.

is there any way to debug this problem????
blue_z
Location: USA
Posts: 1767
Joined: Thu Apr 19, 2007 10:15 pm

Re: WILC1000 not working in SAM5D2_Xplained Board

Tue Oct 24, 2017 2:17 am

freaky_geek234 wrote:I have made entry for wilc1000_spi in dts file as below:
What kernel version?
What "dts file"?
What you present doesn't look complete. You reference a pinctrl_spi1_default; where is that defined?

freaky_geek234 wrote:is there any way to debug this problem????
You could enable debug-message capability in selected subsystems. Start with pin-control, and then spi.

Regards
freaky_geek234
Posts: 9
Joined: Sat May 13, 2017 12:06 pm

Re: WILC1000 not working in SAM5D2_Xplained Board

Wed Oct 25, 2017 3:32 pm

forgot to post pinctrl_spi1_default: spi1_default which is defined in my dts (at91-sama5d2_xplained_common.dtsi) file as follows:





pinctrl_spi1_default: spi1_default {
pinmux = <PIN_PC1__SPI1_SPCK>,
<PIN_PC2__SPI1_MOSI>,
<PIN_PC3__SPI1_MISO>,
<PIN_PC4__SPI1_NPCS0>;
bias-disable;
};
roberto2018
Posts: 5
Joined: Wed Apr 18, 2018 3:13 pm

Re: WILC1000 not working in SAM5D2_Xplained Board

Wed Apr 18, 2018 4:24 pm

I have a similar problem.
I use a SAMA5D2 board called RoadRunner made by Acmesystems.
I'm trying to connect the SAMA5D27 core to ATWILC1000 through the SPI1 port.
The board runs a 4.9.40 kernel Linux.
I have configured a ATWILC1000-SD module to operate over SPI signals.
I have connect the SPI_SS, SPI_RXD, SPI_CLK, SPI_TXD and IRQ pins, and pull up the CHIP_EN, RESET_N ones.
The SPI1 lines of the SAMA5D27 are:
PC1: SPI_CLK; PC2: SPI_TXD; PC3: SPI_RXD; PC4: SPI_CS0; PC5: IRQ request.
I have done modifications to "menuconfig" kernel and .DTB files.
I have successful compiled the WILC module (wilc.ko and wilc-spi.ko).
I have conveniently copied the firmware file wilc1000_wifi_firmware.bin to the /lib/firmware.
After boot and login I manually start the driver typing:
insmod wilc.ko and insmod wilc-spi.ko
The system first respond:
"WILC_SPI spi32766.0: WILC SPI probe success"
then shows a list of problems, but it seems it right reads the MAC address (as the last ifconfig shows in the log).
At the end the ATWILC1000 dosn't work.
Now the .DTB is configurated to operate at 500KHz, but the frequency is irrilevant, the result is the same from 5Mhz
down to 500Khz.
If someone can help me, I attach the modifications made to "menuconfig", the DTS file and the log.
Thanks in advance.

"menuconfig" **************

Device Drivers --->
[*] SPI support --->
<*> Atmel SPI Controller
<*> User mode SPI device driver support


WILC1000 SPI WiFi
Device Drivers
-- Staging Drivers
-- -- Atmel WILC1000 SPI

"Boot" ****************

Debian GNU/Linux 8 roadrunner ttyS0

roadrunner login: root
Password:
Last login: Mon Jan 9 01:59:13 CET 2012 on ttyS0
Linux roadrunner 4.9.40 #7 Tue Mar 13 15:00:16 CET 2018 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@roadrunner:~# ifconfig
can0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOrandom: crng init done
ARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:37

eth0 Link encap:Ethernet HWaddr 00:04:25:12:34:56
inet addr:192.168.1.208 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::204:25ff:fe12:3456/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:99 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15300 (14.9 KiB) TX bytes:1270 (1.2 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

root@roadrunner:~# cd /mnt/SDStorage
root@roadrunner:/mnt/SDStorage# insmod wilc.ko
wilc: module is from the staging directory, the quality is unknown, you have been warned.
root@roadrunner:/mnt/SDStorage# insmod wilc-spi.ko
wilc_spi: module is from the staging directory, the quality is unknown, you have been warned.
WILC_SPI spi32766.0: WILC SPI probe success
root@roadrunner:/mnt/SDStorage# ------------[ cut here ]------------
WARNING: CPU: 0 PID: 1539 at drivers/spi/spi-atmel.c:1347 atmel_spi_transfer_one_message+0x6c4/0xb0c
Modules linked in: wilc_spi(C) wilc(C)
CPU: 0 PID: 1539 Comm: wpa_supplicant Tainted: G C 4.9.40 #7
Hardware name: Atmel SAMA5
[<c010cd1c>] (unwind_backtrace) from [<c010a77c>] (show_stack+0x10/0x14)
[<c010a77c>] (show_stack) from [<c0115e70>] (__warn+0xe4/0xfc)
[<c0115e70>] (__warn) from [<c0115f38>] (warn_slowpath_null+0x20/0x28)
[<c0115f38>] (warn_slowpath_null) from [<c0407500>] (atmel_spi_transfer_one_message+0x6c4/0xb0c)
[<c0407500>] (atmel_spi_transfer_one_message) from [<c0404ddc>] (__spi_pump_messages+0x390/0x4d4)
[<c0404ddc>] (__spi_pump_messages) from [<c0405084>] (__spi_sync+0x158/0x16c)
[<c0405084>] (__spi_sync) from [<c04050bc>] (spi_sync+0x24/0x3c)
[<c04050bc>] (spi_sync) from [<bf0210b8>] (wilc_spi_tx_rx+0x98/0xc8 [wilc_spi])
[<bf0210b8>] (wilc_spi_tx_rx [wilc_spi]) from [<bf02130c>] (spi_cmd_complete+0x11c/0x6a8 [wilc_spi])
[<bf02130c>] (spi_cmd_complete [wilc_spi]) from [<bf0218c0>] (spi_internal_read+0x28/0x4c [wilc_spi])
[<bf0218c0>] (spi_internal_read [wilc_spi]) from [<bf021f8c>] (wilc_spi_init+0x68/0x1e4 [wilc_spi])
[<bf021f8c>] (wilc_spi_init [wilc_spi]) from [<bf00ec00>] (wilc_wlan_init+0x2c/0x2e4 [wilc])
[<bf00ec00>] (wilc_wlan_init [wilc]) from [<bf0052b8>] (wilc_wlan_initialize+0xe8/0x440 [wilc])
[<bf0052b8>] (wilc_wlan_initialize [wilc]) from [<bf005670>] (wilc_mac_open+0x60/0x1f0 [wilc])
[<bf005670>] (wilc_mac_open [wilc]) from [<c0595104>] (__dev_open+0xb8/0x11c)
[<c0595104>] (__dev_open) from [<c0595390>] (__dev_change_flags+0x94/0x148)
[<c0595390>] (__dev_change_flags) from [<c059545c>] (dev_change_flags+0x18/0x48)
[<c059545c>] (dev_change_flags) from [<c05f0874>] (devinet_ioctl+0x614/0x738)
[<c05f0874>] (devinet_ioctl) from [<c057a3bc>] (sock_ioctl+0xe0/0x2c0)
[<c057a3bc>] (sock_ioctl) from [<c01b41d8>] (do_vfs_ioctl+0x9c/0x884)
[<c01b41d8>] (do_vfs_ioctl) from [<c01b49f4>] (SyS_ioctl+0x34/0x58)
[<c01b49f4>] (SyS_ioctl) from [<c0107460>] (ret_fast_syscall+0x0/0x3c)
---[ end trace 6f40e11d8c7e31da ]---
WILC_SPI spi32766.0: spi transfer timeout
WILC_SPI spi32766.0: SPI transaction failed
WILC_SPI spi32766.0: Failed cmd write, bus error...
WILC_SPI spi32766.0: Failed internal read cmd...
WILC_SPI spi32766.0: Failed internal read protocol with CRC on, retrying with CRC off...
WILC_SPI spi32766.0: Failed cmd response, cmd (c4), resp (00)
WILC_SPI spi32766.0: Failed internal read cmd...
WILC_SPI spi32766.0: Failed internal read protocol...
wlan0: WLAN Iinitialization FAILED
wlan0: Failed to set driver handler
wlan0: Host cmd 24 failed
wlan0: [Host Interface] undefined
wlan0: IRQ request succeeded IRQ-NUM= 116 on GPIO: 69
wlan0: Detect chip WILC1000
wlan0: loading firmware wilc1000_wifi_firmware.bin
wlan0: WILC Firmware Ver = WILC_WIFI_FW_REL_15_00_RC4 Build: 8837
wlan0: Command - 35638 - has been received
wlan0: Command - 35590 - has been received
wlan0: Command - 35595 - has been received
wlan0: Command - 35591 - has been received
wlan0: Command - 35604 - has been received
wlan0: Command - 35610 - has been received
wlan0: Command - 35634 - has been received
wlan0: Command - 35636 - has been received
wlan0: Command - 35636 - has been received
wlan0: Command - 35626 - has been received
wlan0: Command - 35634 - has been received
WILC_SPI spi32766.0: Failed cmd response, cmd (c4), resp (00)
WILC_SPI spi32766.0: Failed internal read cmd...
WILC_SPI spi32766.0: Failed internal read protocol...
wlan0: WLAN Iinitialization FAILED
WILC_SPI spi32766.0: Failed cmd response, cmd (c4), resp (00)
root@roadrunner:/mnt/SDStorage#
root@roadrunner:/mnt/SDStorage#
root@roadrunner:/mnt/SDStorage# ifconfig
can0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:37

eth0 Link encap:Ethernet HWaddr 00:04:25:12:34:56
inet addr:192.168.1.208 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::204:25ff:fe12:3456/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:435 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:78946 (77.0 KiB) TX bytes:1538 (1.5 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan0 Link encap:Ethernet HWaddr fa:f0:05:f1:35:75
inet6 addr: fe80::f8f0:5ff:fef1:3575/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:878 (878.0 B)
root@roadrunner:/mnt/SDStorage#
zdhovey2000
Posts: 17
Joined: Fri Oct 13, 2017 9:52 pm

Re: WILC1000 not working in SAM5D2_Xplained Board

Mon Apr 30, 2018 8:45 am

I'm getting the same problem, Using the SamA5D4 and using SPI.

Sometimes it will initialize fine, but if I bring wlan0 down and then try to bring it back up again, it gives the same message but also sends:

MESSAGE #1

Code: Select all

[<c010cd1c>] (unwind_backtrace) from [<c010a77c>] (show_stack+0x10/0x14)
[<c010a77c>] (show_stack) from [<c0115e70>] (__warn+0xe4/0xfc)
[<c0115e70>] (__warn) from [<c0115f38>] (warn_slowpath_null+0x20/0x28)
[<c0115f38>] (warn_slowpath_null) from [<c0407500>] (atmel_spi_transfer_one_message+0x6c4/0xb0c)
[<c0407500>] (atmel_spi_transfer_one_message) from [<c0404ddc>] (__spi_pump_messages+0x390/0x4d4)
[<c0404ddc>] (__spi_pump_messages) from [<c0405084>] (__spi_sync+0x158/0x16c)
[<c0405084>] (__spi_sync) from [<c04050bc>] (spi_sync+0x24/0x3c)
[<c04050bc>] (spi_sync) from [<bf0210b8>] (wilc_spi_tx_rx+0x98/0xc8 [wilc_spi])
[<bf0210b8>] (wilc_spi_tx_rx [wilc_spi]) from [<bf02130c>] (spi_cmd_complete+0x11c/0x6a8 [wilc_spi])
[<bf02130c>] (spi_cmd_complete [wilc_spi]) from [<bf0218c0>] (spi_internal_read+0x28/0x4c [wilc_spi])
[<bf0218c0>] (spi_internal_read [wilc_spi]) from [<bf021f8c>] (wilc_spi_init+0x68/0x1e4 [wilc_spi])
[<bf021f8c>] (wilc_spi_init [wilc_spi]) from [<bf00ec00>] (wilc_wlan_init+0x2c/0x2e4 [wilc])
[<bf00ec00>] (wilc_wlan_init [wilc]) from [<bf0052b8>] (wilc_wlan_initialize+0xe8/0x440 [wilc])
[<bf0052b8>] (wilc_wlan_initialize [wilc]) from [<bf005670>] (wilc_mac_open+0x60/0x1f0 [wilc])
[<bf005670>] (wilc_mac_open [wilc]) from [<c0595104>] (__dev_open+0xb8/0x11c)
[<c0595104>] (__dev_open) from [<c0595390>] (__dev_change_flags+0x94/0x148)
[<c0595390>] (__dev_change_flags) from [<c059545c>] (dev_change_flags+0x18/0x48)
[<c059545c>] (dev_change_flags) from [<c05f0874>] (devinet_ioctl+0x614/0x738)
[<c05f0874>] (devinet_ioctl) from [<c057a3bc>] (sock_ioctl+0xe0/0x2c0)
[<c057a3bc>] (sock_ioctl) from [<c01b41d8>] (do_vfs_ioctl+0x9c/0x884)
[<c01b41d8>] (do_vfs_ioctl) from [<c01b49f4>] (SyS_ioctl+0x34/0x58)
[<c01b49f4>] (SyS_ioctl) from [<c0107460>] (ret_fast_syscall+0x0/0x3c)
When I try to bring it back up I get:

Message #2

Code: Select all

genirq: Flags mismatch irq 48. 00002008 (WILC_IRQ) vs. 00002008 (WILC_IRQ)
Failed to request IRQ GPIO: 2
My gpio is Port A.2 and after bootup, I can successfully scan and connect to my AP about 1 in 3 times, the other 2 out of 3 times I get the long message (message #1)
blue_z
Location: USA
Posts: 1767
Joined: Thu Apr 19, 2007 10:15 pm

Re: WILC1000 not working in SAM5D2_Xplained Board

Wed May 02, 2018 1:34 am

roberto2018 wrote:I have connect the SPI_SS, SPI_RXD, SPI_CLK, SPI_TXD and IRQ pins, and pull up the CHIP_EN, RESET_N ones.
You're not clear as which chip or module or board that you're using.
Your connection for the chip/module's reset signal could be problematic.
The datasheet(s) clearly specify that the reset signal should be asserted for at least 5 milliseconds after power-on and assertion of CHIP_EN.

Regards
roberto2018
Posts: 5
Joined: Wed Apr 18, 2018 3:13 pm

Re: WILC1000 not working in SAM5D2_Xplained Board

Wed May 02, 2018 12:50 pm

Thanks for the reply.
I'm using an ATWILC1000-SD module which I've configurated to operate over SPI signals as it has explained in the "DS50002692A", "Atmel-42434A-ATWILC1000-Getting-Started-with-SAMA5D3-Xplained-Board_UserGuide_032015" and "DS70005328A" document. The main difference is I've a SAMA5D2 board.
I fear the issue may be also in the driver software implementation.
Something works, like "iw wlan0 scan | grep 'SSID'" for the scanning, but a lot of errors comes out and the system crashes quicly.
Regards, Roberto.
blue_z
Location: USA
Posts: 1767
Joined: Thu Apr 19, 2007 10:15 pm

Re: WILC1000 not working in SAM5D2_Xplained Board

Wed May 02, 2018 9:08 pm

roberto2018 wrote:I fear the issue may be also in the driver software implementation.
Fear whatever you choose, but you still have the reset timing issue and the console output seems to indicate that your SPI connection has issues.
---[ end trace 6f40e11d8c7e31da ]---
WILC_SPI spi32766.0: spi transfer timeout
WILC_SPI spi32766.0: SPI transaction failed
WILC_SPI spi32766.0: Failed cmd write, bus error...

Regards
roberto2018
Posts: 5
Joined: Wed Apr 18, 2018 3:13 pm

Re: WILC1000 not working in SAM5D2_Xplained Board

Thu May 03, 2018 9:18 am

Thanks Blue.
About connection of RESET_N and CHIP_EN:
Threre is a lot of confusion in the application note.
As I have written, if I leave these pins simply pulled up as explained
in the "DS50002692A" document, I can read the MAC and scan the AP in view.
This situation could mean that the flow is correct.
If I connect them to the board as described in the header driver file
the module stops operation completely.
The timing may be wrong, but I'm not the driver developer.
I've tryied to enter in the driver code.
I found out the first timeout exists becouse the code wait for 17 bytes
when the module for the same command answers with 14 bytes.
Please if you have examples where linux works over SPI signals with
the WILC1000 module I'm really in need of this.
Regards, Roberto.
blue_z
Location: USA
Posts: 1767
Joined: Thu Apr 19, 2007 10:15 pm

Re: WILC1000 not working in SAM5D2_Xplained Board

Fri May 04, 2018 12:51 am

roberto2018 wrote:As I have written, if I leave these pins simply pulled up as explained in the "DS50002692A" document, ...
That User Guide mentions two (2) methods of using an SDI interface (i.e. 4.1 Using SPI Interface via MMC/SD Connector versus 4.2 Using SPI Interface via Wire Jumpers).
You write as if there is only one method, so your description of what you're doing is ambiguous.

roberto2018 wrote:If I connect them to the board as described in the header driver file ...
Don't know what this is.

BTW have you looked at the SD module's schematic, and noticed that the reset signal already has a (weak) pull-up?

When your setup does not meet the hardware (timing) specifications (for power-up) as listed in the datasheets, then IMO you have no basis for complaining that software does not function correctly.
When you do manage to get everything to function, then you can take shortcuts and try to ignore the spec. But it certainly doesn't work the other way 'round.

Regards
roberto2018
Posts: 5
Joined: Wed Apr 18, 2018 3:13 pm

Re: WILC1000 not working in SAM5D2_Xplained Board

Fri May 04, 2018 12:19 pm

Hello, I am honored to investigate the problem with you.
I attach the proposed connection by Atmel in

http://lroberto.byethost16.com/wilc1000 ... tation.pdf

and the wiring to then SAMA5D4 board.

http://lroberto.byethost16.com/wilc1000 ... _SAMA5.jpg

I've connected through then SD connector, however the module modification
for using through Tp or SD is basically the same.
I've respected the schematic.
Please note is non proposed the wiring of RESET_N and CHIP_EN pins
despite the driver configuration needs to indicate where they are connected

http://lroberto.byethost16.com/wilc1000/wilc_wlan.h

Here the lines:
#define MODALIAS "WILC_SPI"
/*
.#define GPIO_NUM 0x5B
.#define GPIO_NUM_CHIP_EN 94
.#define GPIO_NUM_RESET 60
*/
#define GPIO_NUM 69 /* PC5 */
#define GPIO_NUM_CHIP_EN 70 /* PC6 */
#define GPIO_NUM_RESET 71 /* PC7 */

If it is not the driver to driver the pin who has to do it?
Thanks, Roberto.
blue_z
Location: USA
Posts: 1767
Joined: Thu Apr 19, 2007 10:15 pm

Re: WILC1000 not working in SAM5D2_Xplained Board

Sat May 05, 2018 1:14 am

roberto2018 wrote:and the wiring to then SAMA5D4 board.
But previously you wrote that you're using a SAMA5D2 board!

roberto2018 wrote:Please note is non proposed the wiring of RESET_N and CHIP_EN pins despite the driver configuration needs to indicate where they are connected
Can't decipher this bad English.

Where is this code from? Why does it have DOS-style line termination?

roberto2018 wrote:Here the lines:
#define MODALIAS "WILC_SPI"
/*
.#define GPIO_NUM 0x5B
.#define GPIO_NUM_CHIP_EN 94
.#define GPIO_NUM_RESET 60
*/
#define GPIO_NUM 69 /* PC5 */
#define GPIO_NUM_CHIP_EN 70 /* PC6 */
#define GPIO_NUM_RESET 71 /* PC7 */
(Learn to use code tags for code snippets.)
Again, where is this from?
Is does not match anything from mainline (4.9.40) nor Linux4SAM!

Regards
roberto2018
Posts: 5
Joined: Wed Apr 18, 2018 3:13 pm

Re: WILC1000 not working in SAM5D2_Xplained Board

Sat May 05, 2018 9:01 am

Hello.
My board is a SAMA5D2 but the only examples that can be found from
Microchip are for the other CPUs.
Furthermore they do not explain how to drive the pins RESET_N and CHIP_EN inside Linux.
Result the module WILC1000 through SPI connection is not stable in Linux
and it is not working.
The file wlan.h has that termination for facilitating the reading,
but it does not interfere with the compilation.
The file wilc_wlan.h is taken from the ufficial repository
https://github.com/linux4wilc/driver/tr ... r/wilc1000
and it is intended for being configured for the own hardware.
Thanks anyway for your time.
Ragards, Roberto.

Return to “SAMA5-based”

Who is online

Users browsing this forum: No registered users and 2 guests