I am using BBB with kernel 5.10.65-ti-r23, i am customizing BB-SPIDEV1 in overlay. but i am unable to enable BB-SPI1 in BBB. And SPI1 is not showing in ls /dev/spi*
&spi1 {
#address-cells = <1>;
#size-cells = <0>;
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&bb_spi1_pins>;
/*
* Select the D0 pin as output and D1 as
* input. The default is D0 as input and
* D1 as output.
*/
//ti,pindir-d0-out-d1-in;
ti,spi-num-cs = <1>;
cs-gpios = <&gpio3 17 GPIO_ACTIVE_LOW>;
wilc_spi: wilc_spi@0 {
compatible = "microchip,wilc1000", "microchip,wilc3000", "spidev";
/*symlink = "bone/spi/1.0";
pinctrl-0 = <&bb_spi1_wilc_pins>;*/
reg = <0>;
spi-max-frequency = <16000000>;
interrupt-parent = <&gpio0>;
/*interrupts = <26 IRQ_TYPE_EDGE_FALLING>;*/
irq-gpios = <&gpio0 26 GPIO_ACTIVE_HIGH>;
reset-gpios = <&gpio1 17 GPIO_ACTIVE_LOW>;
chip_en-gpios = <&gpio1 28 GPIO_ACTIVE_HIGH>;
status = "okay";
spi-cpol;
spi-cpha;
};
};
Also, i have added /boot/uEnv.txt i have updated cape_enable=bone_capemgr.enable_partno=BB-SPIDEV1, but bone_capemgr is not there in /sys/devices:
I refered this link for kernel upgarde: https://embetronicx.com/tutorials/linux/device-drivers/setup-beaglebone-board-linux-device-driver-tutorial/
1 Like
Yeah, no… It hasn’t been that way for years overlay capemgr is gone. Beagleboard:BeagleBoneBlack Debian - eLinux.org
Thanks Robert,
shall i refer the attached link “Beagleboard:BeagleBoneBlack Debian - eLinux.org”.
Could you please tell me other procedure what i followed is right?
i want to enable SPI1 with &spi1 {
wilc_spi: wilc_spi@0 { }; };.
Last 3 weeks am struggling to enable this.
Loop back test with SPI1 with channel@0 { is working but the above changes is not working.
Could you please help me to resolve this issue.
Please do the needful
Mainline 5.10.x doesn’t have support for the wilc3000, where did you get your driver… Which wilc3000 development board are you using?
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/net/wireless/microchip?h=v5.10.186
Regards,
I love when a board needs to be reworked…
can we assume you did above ^ ?
Regards,
Me too, yes i did it for SPI
I have referred section 2 in the “ATWILC Devices Linux® Porting Guide” for kernel modification
Have you patched the driver and enabled the config options? v5.10.65-ti-r23 is way behind the current release of v5.10.168-ti-r63?
Yes,
Major change in driver
Kconfig:
workspace_June23/embetronix/BBG/linux_working Old copy/drivers/net/wireless/kconfig
#source “drivers/net/wireless/microchip/Kconfig”
source “drivers/net/wireless/mchp/Kconfig”
Makefile:
workspace_June23/embetronix/BBG/linux_working Old copy/drivers/net/wireless/Makefile
#obj-$(CONFIG_WLAN_VENDOR_MICROCHIP) += microchip/
obj-$(CONFIG_WLAN_VENDOR_MCHP) += mchp/
mchp driver folder:
workspace_June23/embetronix/BBG/linux_working Old copy/drivers/net/wireless/mchp/
Ko file: wilc-spi.ko:
During run time->
Mkdir mchp in /lib/firmware for wilc3000 .bin files:
Wifi config : i am referring “https://www.linux4sam.org/bin/view/Linux4SAM/WilcFaq” and AT3000 linux porting guide as i mentioned above
Hi Robert,
Could you please confirm me, whether, SPI1.0 dts file changes was right from myside.
From microchip side provided response :
“The response looks like resp (00) which may be SPI not receiving anything.
In the preivious waveform, it seems SPI SS stayed low which means active. and MISO stayed unchanged while MOSI is changing. It may be possible that WILC didn’t respond or the clock is not proper”
Could you please guide me, what could be the problem in BBB customization wheather in SPI overlay function or driver function.
Please help me to resolve this issue
