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.

Linux: DM3730 UART3 download x-load.bin problem

Other Parts Discussed in Thread: DM3730

Tool/software: Linux

Customer inquiry;

I am trying to get the 3730 to boot via its UART3.  Just after power-up, the Boot ROM correctly sends its ASIC ID, and we respond with the image file size (32-bits Little-Endian) followed by the x-load.bin raw image file.  That much goes smoothly, but the 3730 never comes up,it's mean that the x-load.bin did not execute ,I don't know where the mistake came from。x-load or pserial.

my ways is use the pserial download the x-load.bin and ukermit download u-boot.bin

  • Hi user5052928,

    Could you specify what kind of DM3730 board you are using? For example if you are using EVM board you should check the switch configuration required for peripheral booting from UART3.
    Also check whether the x-loader loading is properly completed as it is described in the linked below tutorial:
    projects.goldelico.com/.../

    BR
    Tsvetolin Shulev
  • thanks
    the kind od DM3730 of mine is omap3evm
    configure with ""make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm omap3evm_config""
    SYS.BOOT[5:0] = 110111
    the sequence is UART3-> MMC2
    I follow the ways of elinux.org/BeagleBoardRecovery
    and the TI documentation says that the UART3 x-load.bin will be copied to internal SRAM at 0x40200000
    so I check the TEXT_BASE and i found that

    /* board/omap3evm/config.mk */
    # (C) Copyright 2006
    # Texas Instruments, <www.ti.com>
    #
    # OMAP3EVM board uses OMAP3430 (ARM-CortexA8) cpu
    # see http://www.ti.com/ for more information on Texas Instruments#
    #
    # OMAP3EVM has 1 bank of 128MB mPOP-SDRAM on CS0
    # Physical Address:
    # 8000'0000 (bank0)

    # For use if you want X-Loader to relocate from SRAM to DDR
    #TEXT_BASE = 0x80e80000

    # For XIP in 64K of SRAM or debug (GP device has it all availabe)
    # SRAM 40200000-4020FFFF base
    # initial stack at 0x4020fffc used in s_init (below xloader).
    # The run time stack is (above xloader, 2k below)
    # If any globals exist there needs to be room for them also
    TEXT_BASE = 0x40200800
    PLATFORM_RELFLAGS += -DONE_BIT_ERROR_CORRECT


    I have tried and failed to boot the 3730 using 0x40200800,40200000,0x80e80000
    but it still doesn't work as well
    so i don't know how to do
  • Could you post the console output to check the pserial and ukermit work?

    BR
    Tsvetolin Shulev
  • Hi Tsvetolin Shulevk
    the x-load.bin works well when it booting from the emmc.
    as long as the x-load.bin works, i can transmit the u-boot.bin successful and uboot start booting .(MLO works at mmc )
    when i transmit the x-load.bin successful with the tools of pserial ,i can't tansmit u-boot.bin to the board.
    so i think the reason why it can't transmit the u-boot.bin is that the x-load.bin doesn't works.
    because once it works ,i can transmit the u-boot.bin successful.



    i defined the DEBUG to check whether the pserial works.
    # ./pserial -p /dev/ttyUSB1 -f x-load.bin
    lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
    Output information may be incomplete.
    s_open[100]:Serial port /dev/ttyUSB1 opend fine

    s_configure[204]:c_cflag: 0x00001db2

    s_configure[225]:Serial port /dev/ttyUSB1 configured fine

    Waiting For Device ASIC ID: Press Ctrl+C to stop
    s_read[321]:Serial read requested=1, read=1

    s_read[321]:Serial read requested=7, read=7

    ASIC ID Detected: OMAP 3630 with ROM Version 0x0707
    s_read[321]:Serial read requested=50, read=50

    Sending 2ndFile:
    s_write[352]:Serial wrote Requested=4 wrote=4

    send download_command succeed
    s_write[352]:Serial wrote Requested=4 wrote=4

    s_write[352]:Serial wrote Requested=2048 wrote=2048

    Downloading file: 10.806% completed (2048/18952 bytes)s_write[352]:Serial wrote Requested=2048 wrote=2048

    Downloading file: 21.612% completed (4096/18952 bytes)s_write[352]:Serial wrote Requested=2048 wrote=2048

    Downloading file: 32.419% completed (6144/18952 bytes)s_write[352]:Serial wrote Requested=2048 wrote=2048

    Downloading file: 43.225% completed (8192/18952 bytes)s_write[352]:Serial wrote Requested=2048 wrote=2048

    Downloading file: 54.031% completed (10240/18952 bytes)s_write[352]:Serial wrote Requested=2048 wrote=2048

    Downloading file: 64.837% completed (12288/18952 bytes)s_write[352]:Serial wrote Requested=2048 wrote=2048

    Downloading file: 75.644% completed (14336/18952 bytes)s_write[352]:Serial wrote Requested=2048 wrote=2048

    Downloading file: 86.450% completed (16384/18952 bytes)s_write[352]:Serial wrote Requested=2048 wrote=2048

    Downloading file: 97.256% completed (18432/18952 bytes)s_write[352]:Serial wrote Requested=520 wrote=520

    Downloading file: 100.000% completed (18952/18952 bytes)s_close[292]:Serial closed /dev/ttyUSB1 fine


    File download completed.


    so please tell me why the x-load.bin doesn't works? it transmit completed.

    thanks
    Edison
  • Hi Tsvetolin Shulev
    I follows the ways of e2e.ti.com/.../2260372
    and uboot starts just fine.
    thanks
    Edison