STM32MP157C kernel 6.1 nand not working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2023-11-01 05:15 AM
I have developed a custom stm32mp157c board with a nand IC as storage using the FMC peripheral. This has worked fine with kernel v5.15, but I am trying to upgrade to kernel v6.1 due to driver related issues of the ethernet switch. However I can't seem to detect the mtd device anymore with the new kernel. I have done some digging and it seems it might be related to the new sys bus driver for the etzpc. The nand driver (FMC2) does currently not seem to load at boot.
Can anyone point me in the right direction? Is dit an issue with my devicetree or is there something wrong in de kernel.
- Labels:
-
STM32MP15 Lines
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2023-11-27 02:43 AM
Hi ,
When changing to kernel 6.1 did you also upgrade BSP component accordingly ?
ST only validate kernel V6.1 on top of V5 ecosystem BSP components.
Olivier
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-01-07 09:53 PM
Hi,
I'm having a similar issue migrating from ecosystem v3 to v5, even though running TFA, Optee, U-boot all running fine from the latest release.
I can see stm32-sys-bus enumerating all the peripherals, but the driver for memory-controller@58002000 (stm32mp1-fmc2-ebi) and subsequently nand-controller (stm32mp1-fmc2-nfc) never gets probed, so no rootfs...
Any ideas why this is happening?
