On Fri, Dec 02, 2022 at 05:42:55PM +0100, Miquel Raynal wrote:
Please also do it with the NAND chip described. If, when the NAND chip is described U-Boot tries to create partitions in the controller node, then the situation is even worse than I thought. But I believe
It's like that for U-Boot older than v2022.04 ... and IMO we cannot ignore it.
Said that from the code U-Boot looks into a `partition{}` node only as a direct child of the nand-controller, if there is a nand-chip in between the nand-controller{} and the partitions{} it will just ignore it.
I could try to see what it is doing exactly, but I would need a little bit more time, I just tried changing the DTS as wrote I got a non bootable system.
Francesco