OMAP L138 problem

Adam Koltys

Hi,

I am using omap l138 evm development kit, and I encountered a problem while booting linux. I am following "quick start guide" instructions, but instead of being able to log in as a root to linux i receive lots of strange symbols and tera term stops responding. Is there any solution to this problem? I attach few screenshots, so you can see what i get in my tera term.

over 15 years ago

0 tlee over 15 years ago

TI__Guru 62975 points

Adam,

That looks like it could be hardware instability. Have you run through the BSL tests? Also, try to re-seat the SOM.

-Tommy

0 Joe G. over 15 years ago in reply to tlee

TI__Mastermind 25886 points

Also is the uImage uncorrupted//the right format?

From your uboot variables it looks like you are booting from SPI flash.

Have you tried booting with NFS as an experiment?

0 Adam Koltys over 15 years ago in reply to tlee

Intellectual 560 points

Tommy,

I re-seated the SOM, but i didn't help. I also ran through the BSL tests and everything worked fine, but i still can't boot linux.

Joe G.

I was booting SPI flash, but i also tried to download uImage using tftp and then boot linux, but i recieved the same message in tera term.

0 tlee over 15 years ago in reply to Adam Koltys

TI__Guru 62975 points

Adam,

Can you post your binary images? It would be interesting to see if it works on someone else's board.

-Tommy

0 Joe G. over 15 years ago in reply to tlee

TI__Mastermind 25886 points

Might not be relevant, but please note:

http://e2e.ti.com/support/arm174_microprocessors/omap_applications_processors/f/42/p/32833/115826.aspx#115826

where "open loop" SPI Flash programming caused unintended effects (in my case killed uImage overwrote uboot).

0 Adam Koltys over 15 years ago in reply to tlee

Intellectual 560 points

Tommy,

Here is link to my binary file:

0 tlee over 15 years ago in reply to Adam Koltys

TI__Guru 62975 points

Adam,

That uImage booted to Linux ok over tftp on a colleague's EVM. We used the following UBoot settings:

setenv bootargs console=ttyS2,115200n8 noinitrd rw root=/dev/nfs nfsroot=158.218.62.147:/opt/arago mem=32M ip=dhcp
setenv bootcmd 'setenv autoload no; dhcp; setenv serverip 158.218.22.159; tftp 0xc0700000 uImage; bootm 0xc0700000'
saveenv
boot

-Tommy

0 Adam Koltys over 15 years ago in reply to tlee

Intellectual 560 points

Tommy,

Thanks for your efforts, I'll try it on Monday and tell if it helped.

0 Adam Koltys over 15 years ago in reply to tlee

Intellectual 560 points

Tommy,

I was trying your solution but i also recieved the same symbols. But then i realised somethnig, for all this time i was putting " " after coma while setting up rs232 communication parameters.

My command was like this:(...) console=ttyS2, 115200n8 (...),

Correct command: (...) console=ttyS2,115200n8 (...),

No wonder nobody noticed it before, it is almost invisible.

0 tlee over 15 years ago in reply to Adam Koltys

TI__Guru 62975 points

Adam,

Glad it's working for you. Thanks for following up with the resolution!

-Tommy

Processors

Processors forum

OMAP L138 problem