Dear Scott Wood,
In message 4FBA6F26.2060903@freescale.com you wrote:
There may be problems with your current implementation, like the environment not being available soon enough. You can test this by changing the console bausrate using setenv / saveenv. Cn you still see all boot messages?
The environment is often not available early enough when booting from NAND. CONFIG_NAND_ENV_DST was meant to address this, but I only see one board using it so far. CONFIG_NAND_ENV_DST also may need some fixing regarding where saveenv writes the environment, if there's a bad block in the preceding U-Boot image.
I would think that more boards are using this technology; they probably pre-date the instroduction of CONFIG_NAND_ENV_DST and do not use CONFIG_NAND_ENV_DST but rather code this manually.
Best regards,
Wolfgang Denk