This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM3352: Upgrading kernel from 3.14 to 5.4. NAND not detected.

Part Number: AM3352

Hello,

In 2015 my company developed a custom board based on the Beaglebone Black (AM3352) using the 3.14 kernel from https://github.com/beagleboard/linux. We now need to update to the 5.4 kernel. We have attempted to port our kernel source and device tree customization into the 5.4.0 kernel that we got from https://github.com/beagleboard/linux, and are currently configuring the 5.4 kernel with the same config file we used for 3.14. Although the system boots, not surprisingly most of our customizations are not functioning.
In particular, our kernel cannot detect our NAND flash (AMD/Spansion S34ML01G2). Wondering if anyone can point me to any resources that might help me through the process of configuring this 5.4 kernel to work with my flash part?
Any help would be greatly appreciated, thank you!
Anthony
  • Hi,

    One to take note of is that TI has not officially released a 5.4 kernel. There is a 5.4 kernel release planned shortly though, before the end of the year. I would recommend sourcing the kernel you are using from git.ti.com.

    I would recommend reviewing the device binding document Documentation/devicetree/bindings/mtd/gpmc-nand.txt and comparing your board DTS file with ones based on TI EVMs such as arch/arm/boot/dts/am335x-evm.dts.

    Best Regards,

    Schuyler

  • Hi Schuyler, thank you for the great information. Sorry for the delayed response, for some reason I never received a notification that anyone had replied. I actually did get the NAND working though. I was trying to use the same defconfig that we used in 3.14, and something had changed in 5.4 such that the correct options were no longer being enabled. After poking around in menuconfig I was able to get the correct options enabled and my NAND is once again functional.


    Thank you for taking the time to respond to my question - Anthony