Skip to contentSkip to conversation

Booting in reverse order

U-Boot-Users raajesh.n at indiatimes.com 3 participants 3 messages May 27, 2008 – May 28, 2008

lore
Share & tools
lore
#0 lore raw

Hi All,

We have installed new u-boot boot loader in a customized board , upon booting from flash we are observing that all which is displaying is in reverse order , we are not able find what is exact problem. we checked the endiness of the compiled code, It was compiled in little endian mode.

Any suggestion would be appreciated .

Best Regards,
Rajesh

#1 lore raw

Hi Rajesh,

Quoted 7 lines · On Tue, May 27, 2008 at 7:06 AM, <[email protected]> wrote:

Hi All,

We have installed new u-boot boot loader in a customized board , upon booting from flash we are observing that all which is displaying is in reverse order , we are not able find what is exact problem. we checked the endiness of the compiled code, It was compiled in little endian mode.

Any suggestion would be appreciated .

This is sadly lacking in detail. You need to provide information about your CPU (we have no idea if it's supposed to be little-endian), and instead of describing the problem, show it (cut & paste output). Keep it in ASCII please.

regards,
Ben

#2 lore raw
In reply to raajesh.n at indiatimes.com
Quoted 8 lines · raajesh.n at indiatimes.com

Hi All,

We have installed new u-boot boot loader in a customized board , upon booting from flash we are observing that all which is displaying is in reverse order , we are not able find what is exact problem. we checked the endiness of the compiled code, It was compiled in little endian mode.

Quoted 4 lines

Any suggestion would be appreciated .

Best Regards,
Rajesh

Ditto what Ben said about lacking information.

If your board is booting and sending characters out the serial channel as your message implies, congratulations, all the hard stuff is working.
I would look at your serial driver: how you get the characters out of
memory and stuff them in the UART. Guessing with too little data:
something in that area is getting byteswapped (or not byteswapped) wrongly. Another remote possibility is that your compiler (linker?) is storing strings byteswapped in memory for some strange reason.

Good luck,
gvb