OMAP-U-Boot-Utils

GoogleGroups
1

I'm trying to to use u-boot-utils, instead of the Windows application
shipped with TI OMAP3 EVM, to boot the OMAP3 EVM over UART3. But I
have some problems with that.

What happens is this:

$ ./pserial -p /dev/ttyS0 -f /var/lib/tftpboot/omap/u-boot.bin
Waiting For Device ASIC ID: Press Ctrl+C to stop
(here i reboot my card)
ASIC ID Detected.
* (__here the EVM continue to boot with the already installed u-boot)
Sending 2ndFile:
Downloading file: 100.000% completed(333092/333092 bytes)
File download completed.

The u-boot-utils source code is cloned from GIT repo today.

The action at line marked with a * shouldn't happen. The EVM should of
course not had booted before after the file is downloaded completely.
Can anyone help me with this?

Best regards,
Kjetil Aamodt
TANDBERG

2

$ ./pserial -p /dev/ttyS0 -f /var/lib/tftpboot/omap/u-boot.bin
Waiting For Device ASIC ID: Press Ctrl+C to stop
(here i reboot my card)
ASIC ID Detected.
* (__here the EVM continue to boot with the already installed u-boot)
Sending 2ndFile:
Downloading file: 100.000% completed(333092/333092 bytes)
File download completed.

Hi Kjetil,

Seems like the ROM-code times out before u-boot-utils sends back a "Boot
message". The ROM-code timeout is 300ms. More info can be found in the TRM
(spruf98b.pdf) chapter 25.4.5

Best regards - Good luck
  Søren

3

Søren Steen Christensen said the following on 03/14/2009 12:40 AM:

$ ./pserial -p /dev/ttyS0 -f /var/lib/tftpboot/omap/u-boot.bin
Waiting For Device ASIC ID: Press Ctrl+C to stop
(here i reboot my card)
ASIC ID Detected.
* (__here the EVM continue to boot with the already installed u-boot)
    

this is interesting -> pserial does not verify the ASIC ID. I think that
might be the problem here.. maybe the SYSBOOT is setup to boot off
NOR/NAND as the first boot device.. pserial thinks that is asic id and
proceeds.. (btw, did you connect on UART3?)..