Dear Lucas Endres,
In message CAKZOPtKY-WJsZf_PpoC4gV_8Y8PvHSGJm4hhah2Znq=rvGMYxQ@mail.gmail.com you wrote:
I know it's an issue on the NAND initialization, but I am neither very familiar to the U-Boot code nor to debugging errors. What follows is the console output I get when trying to run nand_init_chip() from my standalone application:
You are not supposed to do things like that. For standalone applications, ther eis only a very limited, well-defined set of functionality exported by U-Boot. NAND access is not part of it.
I need to run a badblocks test on the NAND device, and I successfully do it in the board initialization from within the U-Boot environment, but not from the standalone environment.
Why do you want to do it from a standalone application?
Best regards,
Wolfgang Denk