How do I get the meta-st-stm32mp recipe to run menuconfig?
I want to add a SPI driver for the ATWINC3400 part. The WILC3000 driver exists for the 5.10 kernel and I want to enable it in my STM32MP157 project by reconfiguring the kernel.
I believe I also need to make a device-tree modification to enable the SPI bus and a couple of GPIO pins for my design.
Can you point me to how do do both of these?
@karlchansen , i believe Shawn Hymel went over this in Part 4 of this series…
If not i’ll take a look at it this week.
Thanks! Iĺl take a look at the series.
Are you available for paid support for device-tree modification to support a custom design?
Our design uses the Seeed Studio Odyssey SOM, and we are having problems getting Ethernet, WiFi, and USB-A connections working.
I strongly suspect device-tree configuration, but it is also possible we have one or more errors in our design.
My company is willing to pay for a couple weeks of consulting time to get us through this problem. If you are unable to assist, can you provide any references for someone with solid device-tree expertise?
Thanks for any info!
19HkX2r-FUTyUkMNEcOSHBHzWtCimozzY (296.4 KB)
Attached is a PDF. The uploader gives it a random name. The WiFi is distinct from Seeed’s Odyssey carrier board for the SOM, but the ethernet chip and USB are (should be?) essentially identical.
The Linux boot gives these errors:
*Starting Network Name Resolution...*
[ 29.285204] stm32-dwmac 5800a000.ethernet eth0: no phy at addr -1
[ 29.289851] stm32-dwmac 5800a000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
The complete bootlog is also attached.
BootLog-2022Mar09.txt (34.8 KB)
Got the Ethernet “somewhat” working. It comes up, but when I plug in a network connection the connection goes up & down every 30 seconds or so in GBit mode, until eventually it comes up in 100MBit mode. Better than this morning. We are also getting different behavior on three different boards, so I suspect that there may be some hardware issues.
Moving to the SPI/WiFi issue for the next couple of days so our design house can check the Ethernet stuff.
I’m seeing this too on the base board…
[ 16.828022] stm32-dwmac 5800a000.ethernet eth0: no phy at addr -1
[ 16.838681] stm32-dwmac 5800a000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19
I found the kernel patch, for ext-clock got merged upstream… But i think we need to Switch to ATF-OP-TEE → u-boot boot, to get the pll in the correct frequency…
I just updated the directions to use ARM’s trusted Firmware + u-boot… Still seeing the issue, so more debugging…
[ 18.570032] stm32-dwmac 5800a000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[ 18.741707] stm32-dwmac 5800a000.ethernet eth0: no phy at addr -1
[ 18.754092] stm32-dwmac 5800a000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[ 18.896787] stm32-dwmac 5800a000.ethernet eth0: no phy at addr -1
[ 18.910049] stm32-dwmac 5800a000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[ 19.024669] stm32-dwmac 5800a000.ethernet eth0: no phy at addr -1
[ 19.042050] stm32-dwmac 5800a000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
PS, boot looks different with teh Trusted Firmware…
NOTICE: CPU: STM32MP157CAC Rev.B
NOTICE: Model: Seeed Studio Odyssey-STM32MP157C Board
NOTICE: BL2: v2.5(release):v2.5
NOTICE: BL2: Built : 10:49:24, Mar 10 2022
NOTICE: BL2: Booting BL32
NOTICE: SP_MIN: v2.5(release):v2.5
NOTICE: SP_MIN: Built : 10:49:27, Mar 10 2022
U-Boot 2022.01 (Mar 10 2022 - 10:48:11 -0600)
CPU: STM32MP157CAC Rev.B
Model: Seeed Studio Odyssey-STM32MP157C Board
Board: stm32mp1 in trusted - stm32image mode (seeed,odyssey-stm32mp157c)
DRAM: 512 MiB
- MPU : 650 MHz
- MCU : 208.878 MHz
- AXI : 266.500 MHz
- PER : 24 MHz
- DDR : 533 MHz
WDT: Started watchdog@5a002000 with servicing (32s timeout)
NAND: 0 MiB
MMC: STM32 SD/MMC: 0, STM32 SD/MMC: 1
Loading Environment from MMC... OK
invalid MAC address in OTP 00:00:00:00:00:00
Error: ethernet@5800a000 address not set.
No ethernet found.
Hit any key to stop autoboot: 0
Boot over mmc0!
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:4...
Retrieving file: /boot/extlinux/extlinux.conf
1: Linux 5.17.0-rc7-armv7-lpae-x6
Retrieving file: /boot/vmlinuz-5.17.0-rc7-armv7-lpae-x6
append: console=ttySTM0,115200 root=/dev/mmcblk0p4 ro rootfstype=ext4 rootwait
Retrieving file: /boot/dtbs/5.17.0-rc7-armv7-lpae-x6/stm32mp157c-odyssey.dtb
Kernel image @ 0xc2000000 [ 0x000000 - 0xbaf200 ]
## Flattened Device Tree blob at c4000000
Booting using the fdt blob at 0xc4000000
Loading Device Tree to cffe9000, end cffff59a ... OK
Starting kernel ...
Are you able to do paid consulting? We have funds available if you are. We are hoping with the correct skillset we can get the remaining issues resolved in under a couple weeks of work.
@karlchansen Sorry i’m not… It would best to either contact these guys:
or these developers, who worked on this before…
05:56PM - 08 Jul 20 UTC
This commit adds device tree files supporting
SBC from Seeed Studio based on STM