[U-Boot] silent console with nand
Is it possible to have a silent console with the 'silent' environment variable if the environment is stored in NAND?
Essentially both: #define CONFIG_SILENT_CONSOLE #define CONFIG_ENV_IS_IN_NAND
are defined, but I am not seeing a dark console with silent=1.
I've seen the messages concerning the environment stored in SPI Flash and was probably thinking that it applies to NAND as well. I'm just looking for confirmation or another #define to get it to work. I realize that another option is to compile it into my default environment but I want to take advantage of the 'silent' switch.
Thanks.
Dear "Bishop, Mark",
In message 5D308BD40154E4439D82454FE483A50206A4F026@EVS4.nam.ci.root you wrote:
Is it possible to have a silent console with the 'silent' environment variable if the environment is stored in NAND?
The storage location of the environment should have nothing to do with the functionality.
Essentially both: #define CONFIG_SILENT_CONSOLE #define CONFIG_ENV_IS_IN_NAND
are defined, but I am not seeing a dark console with silent=1.
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?
I've seen the messages concerning the environment stored in SPI Flash and was probably thinking that it applies to NAND as well. I'm just
Again - the storage location has nothign to do with functionality; but there are some broken configurations out there that should be fixed.
Best regards,
Wolfgang Denk
On 05/20/2012 02:09 PM, Wolfgang Denk wrote:
Dear "Bishop, Mark",
In message 5D308BD40154E4439D82454FE483A50206A4F026@EVS4.nam.ci.root you wrote:
Is it possible to have a silent console with the 'silent' environment variable if the environment is stored in NAND?
The storage location of the environment should have nothing to do with the functionality.
Essentially both: #define CONFIG_SILENT_CONSOLE #define CONFIG_ENV_IS_IN_NAND
are defined, but I am not seeing a dark console with silent=1.
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.
-Scott
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
participants (3)
-
Bishop, Mark -
Scott Wood -
Wolfgang Denk