[U-Boot] U-Boot 1.3.4 CONFIG_SILENT_CONSOLE Does Not Work?
I'm using U-Boot 1.3.4. When building I've defined "CONFIG_SILENT_CONSOLE" and "CFG_DEVICE_NULLDEV". My board is an at91sam9261ek.
My U-Boot environment looks like this via "printenv":
bootargs=mem=64M console=ttyS0,115200 mtdparts=atmel_nand:4M(kernel)ro,-(rootfs) root=/dev/mtdblock1 rw rootfstype=jffs2 bootcmd=nand read 0x22200000 0x00000000 0x0019757C; bootm 0x22200000 bootdelay=1 baudrate=115200 silent=1
However when I boot my device I see u-boot spiting out the same stuff it does even if "silent" isn't selected, as well as linux but I'm focusing on getting u- boot working as the README / README.silent suggests first.
I know I've seen a few others on this group with the exact same problem as me, and the official response was "RTFM", but, unless I'm missing something hidden in the README's I need a little help, or there is a bug with u-boot.
Anyone can suggest something? Should "silent" be set to a specific variable? Is the stuff I see below normal for "silent", and it is working as it should?
This is what I get on the hyperterminal with the above configuration:
U-Boot 1.3.4 (Sep 30 2010 - 12:33:45)
DRAM: 64 MB NAND: 256 MiB DataFlash:AT45DB642 Nb pages: 8192 Page Size: 1056 Size= 8650752 bytes Logical address: 0xC0000000 Area 0: C0000000 to C00041FF (RO) Bootstrap Area 1: C0004200 to C00083FF Environment Area 2: C0008400 to C0041FFF (RO) U-Boot Area 3: C0042000 to C0251FFF Kernel Area 4: C0252000 to C083FFFF FS In: serial Out: serial Err: serial Hit any key to stop autoboot: 0
NAND read: device 0 offset 0x0, size 0x19757c 1668476 bytes read: OK ## Booting kernel from Legacy Image at 22200000 ... Image Name: Angstrom/2.6.30/at91sam9261ek Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1668412 Bytes = 1.6 MB Load Address: 20008000 Entry Point: 20008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK
Starting kernel ...
Uncompressing Linux............................................................. ............................................... [[[.SNIP.]]]
Dear NB,
In message loom.20100930T215540-882@post.gmane.org you wrote:
I'm using U-Boot 1.3.4. When building I've defined "CONFIG_SILENT_CONSOLE" and "CFG_DEVICE_NULLDEV". My board is an at91sam9261ek.
You are aware that U-Boot 1.3.4 is moe than 2 years old and as such hopelessly obsolete, aren't you? Don;t expect much help for ancient versions like this...
I can only comment on current code...
Anyone can suggest something? Should "silent" be set to a specific variable?
No. The actual value of the "silent" environment variable is not checked, only if it exists or not.
Is the stuff I see below normal for "silent", and it is working as it should?
No, you are not supposed to see that output.
Best regards,
Wolfgang Denk
Wolfgang Denk <wd <at> denx.de> writes:
You are aware that U-Boot 1.3.4 is moe than 2 years old and as such hopelessly obsolete, aren't you? Don;t expect much help for ancient versions like this...
I can only comment on current code...
Yeah. I've tried U-Boot 2010-06 but it doesn't have 9g10 support yet *which my custom board is using*, so I think I'm forced to use the linux4sam updated u-boot 1.3.4, or to port the patches myself; but my tests right now were just with uboot 1.3.4 and a 9261ek.
Basically I just wanted to know if I'm doing everything right and not missing a step, since others have posted with my same problems ~2 years ago when 1.3.4 was current, and it sounded like it was working from the replys.
I'm guessing now there is/was a bug but maybe it has already been fixed. When I get some free time I can re-build oe's uboot 2010-06 with SILENT support to see if it is working for a 9261ek.
If someone remembers anything about the "old" 1.3.4 + silent feature do mention it :)
Thanks
On Thursday, September 30, 2010 16:05:49 NB wrote:
However when I boot my device I see u-boot spiting out the same stuff it does even if "silent" isn't selected, as well as linux but I'm focusing on getting u- boot working as the README / README.silent suggests first.
ive seen issues depending on the env location. if the env cannot be loaded early, the *default env* is consulted for its silent settings, and then things "work" once the saved env is relocated.
might also want to check CONSOLE_IS_IN_ENV is enabled.
otherwise, your options are: - trace the code yourself - upgrade, and then trace the code yourself -mike
Mike Frysinger <vapier <at> gentoo.org> writes:
ive seen issues depending on the env location. if the env cannot be loaded early, the *default env* is consulted for its silent settings, and then "work" once the saved env is relocated.
might also want to check CONSOLE_IS_IN_ENV is enabled.
Yeah I think you are right. CONSOLE_IS_IN_ENV is enabled for me, but at91sam9261ek also has CONFIG_SKIP_LOWLEVEL_INIT and CONFIG_SKIP_RELOCATE_UBOOT, so that RELOCATE issue is probably what is hindering me.
I looked at the console_init function (part where it is doing if(getenv("silent") != NULL)... and that is always returning null, even if it is set dynamically and rebooted.
What I did was change the check so it looks at a jumper instead of the getenv("silent") since this is what I wanted it to do anyway and it seems to all work now :).
I do notice that U-Boot is silencing everything except the "uncompressing kernel.............................." but I see the file related to that and should be able to fix it.
Thanks for your help.
participants (3)
-
Mike Frysinger -
NB -
Wolfgang Denk