Arno Steffen wrote:
In one of my devices, uboot-environment is located at a bad block. "save Saving Environment to NAND... Erasing Nand... Skipping bad block at 0x000c0000
Writing to Nand... FAILED!"
In my memory mapping I have already reseverd 2blocks. How can I setup uboot in a way, that it will look at c0000 or (in case of bad block) at the next block e0000?
...
Maybe someone can give me an advice? Thanks
- Arno
...
Hello!
Is there a solution to this problem? I was going to ask exactly the same question, but then I found this topic.
My board config (ARM platform) is #define CONFIG_ENV_IS_IN_NAND 1 #define CONFIG_ENV_OFFSET 0xC0000 #define CONFIG_ENV_SIZE 0x20000
Now there is a board with a bad block exactly at 0xC0000 => nand bad
Device 0 bad blocks: 000c0000 02f40000 ...
If I try to write the environment, i get Saving Environment to NAND... Erasing Nand... Skipping bad block at 0x000c0000
Writing to Nand... FAILED!
Any hints?
Kind regards Daniel