[U-Boot-Users] RE: LCD on OMAP2430

I realized about the Bad CRC warning afterwards. Anyway, the U-Boot hangs after that message and I do not see stdout, stdin and stderr that should come up on the console. How can I change that to my target LCD? I know that stdin cannot be LCD, it has to be UART, But how can I change stdout to LCD? Can any one help?
Thanks, Jigisha
-----Original Message----- From: Woodruff, Richard [mailto:r-woodruff2@ti.com] Sent: Wednesday, March 29, 2006 11:13 AM To: Goswami Jigisha-ejg014; u-boot-users@lists.sourceforge.net Subject: RE: [U-Boot-Users] LCD on OMAP2430
Hello,
*** Warning - bad CRC, using default environment
This message is coming from common/env_common.c file. Can anyone help
me
identify the mistake?
This warning is nothing to worry about; it just means you have not saved a copy of your environment into flash. The built in defaults will be used then. If you do a 'saveenv' then reboot the message will go away. It's a little more work in a production sense to program up a proper per-device value but its doable, though a little harder for things like NAND.
Is that all I have to do to enable my target LCD within U-Boot? My
goal
is to be able to write images on the LCD verify if it is OK.
In the past I have added such support into u-boot for an OMAP device. That code likely would be a good starting point and probably would work with a few tweaks.
Regards, Richard W.

In message 4F9B2712E6C4C74582548D2260EE1D2D9E24B3@ct11exm64.ds.mot.com you wrote:
I realized about the Bad CRC warning afterwards. Anyway, the U-Boot hangs
Are you sure that it hangs? Do you have the LCD display connected? What do you see on it.
after that message and I do not see stdout, stdin and stderr that should come up on the console. How can I change that to my target LCD? I know that stdin cannot be LCD, it has to be UART, But how can I change stdout to LCD? Can any one help?
Read the code. If LCD is enabled, both stdout and stderr will go to the LCD by default - which is probably why you don't see anything so you think the board is hanging while it's running fine.
Try typing a few times ENTER, followed by a "setenv stdout serial" (even if you don't see any echo for your typing).
Best regards,
Wolfgang Denk
participants (2)
-
Goswami Jigisha-ejg014
-
Wolfgang Denk