• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 616 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

boot uboot from uart2 of OMAPL138 failed

ben zhan
Intellectual 700 points
Other Parts Discussed in Thread: OMAPL138

hi,

    I generated a u-boot_uart.bin by  AISgen for D800K008 tool,  , the input file is uboot elf file, the out file  AISgen tool generated is a ais.bin file , I want to boot uboot from uart2 of OMAPL138 deviceI start the  OMAPL138 Host tool V1.2, some informations displayed below,but there are something error,I don't know why.it can't read the file.

My serial cable is a PCI-RSA2 card,It is a PCI to serial card.  pls give a suggestion, thanks!

(File IO): Read 193844 bytes from file C:\Documents and Settings\kcom\桌面\u-boot_uart.bin.
(Serial Port): Opening COM4 at 115200 baud...
(AIS Parse): Read magic word 0x41504954.
(AIS Parse): Waiting for BOOTME... (power on or reset target now)
(AIS Parse): BOOTME received!
(AIS Parse): Performing Start-Word Sync...
(AIS Parse): Performing Ping Opcode Sync...
(AIS Parse): Processing command 0: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 1: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 2: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 3: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 4: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 5: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 6: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 7: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 8: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 9: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 10: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 11: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 12: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 13: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 14: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 15: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 16: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Processing command 17: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(Serial Port): Read error: The operation has timed out.
(AIS Parse): I/O Error in read!
(Serial Port): Read error: The operation has timed out.
(AIS Parse): I/O Error in read!
(Serial Port): Read error: The operation has timed out.
(AIS Parse): I/O Error in read!
(Serial Port): Read error: The operation has timed out.
(AIS Parse): I/O Error in read!
(Serial Port): Read error: The operation has timed out.
(AIS Parse): I/O Error in read!
(Serial Port): Read error: The operation has timed out.
(AIS Parse): I/O Error in read!
(Serial Port): Read error: The operation has timed out.
(AIS Parse): I/O Error in read!
(Serial Port): Read error: The operation has timed out.
(AIS Parse): I/O Error in read!
(Serial Port): Read error: The operation has timed out.
(AIS Parse): I/O Error in read!
(Serial Port): Read error: The operation has timed out.
(AIS Parse): I/O Error in read!
(Serial Port): Read error: The operation has timed out.
(AIS Parse): I/O Error in read!
(AIS Parse): Opcode Sync failed after 11 consecutive I/O failures.
(AIS Parse): Boot aborted.
(Serial Port): Closing COM4.

  • 0
    TI__Genius 17355 points

    It seems likely that some setting you are applying in the AIS image via the Function Execute command is messing up the UART communication.  Can you provide the configuration you are using or the AIS file?

    Regards, Daniel

  • 0 in reply to Daniel Allred
    Prodigy 90 points

    Daniel,

    Would you be able to comment or review a CFG that I have as well?

    This is result is in trying to load U-boot as the loader.

    ...

    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Executing function...
    (AIS Parse): Processing command 33: 0x5853590D.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Executing function...
    (AIS Parse): Processing command 34: 0x58535901.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Loading section...
    (AIS Parse): Loaded 771864-Byte section to address 0x80000000.
    (AIS Parse): Processing command 35: 0x00585359.
    (AIS Parse): Performing Opcode Sync...
    (Serial Port): Read error! (The operation has timed-out.)
    (AIS Parse): I/O Error in read!
    (Serial Port): Read error! (The operation has timed-out.)
    (AIS Parse): I/O Error in read!
    (Serial Port): Read error! (The operation has timed-out.)

    Thanks,


    Steve

  • 0 in reply to Steve Poulsen
    TI__Genius 17355 points

    I think your load address is wrong.  You are trying to load a 750K section to a region of memory (the L3 Shared RAM at 0x80000000) that is only 128K big.  Also, a u-boot binary image shouldn't be that big (it's only like 150KB) and its load address is usually 0xC1080000 (for this part - I don't why is that specifically, whoever ported the u-boot originally decided that).  But all of that points to some problems in how you created your boot image.

    Regards, Daniel