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/AM5728: UART Boot failure

Part Number: AM5728
Other Parts Discussed in Thread: BEAGLEBOARD-X15, , PMP

Tool/software: Linux

Hi.

We would like to use the UART to load files to boot the board(AM572X EVM) into U-Boot.

our software version is ti-processor-sdk-linux-am57xx-evm-04.00.00.04.

we followed https://e2e.ti.com/support/processors/f/791/p/628934/2321462?tisearch=e2e-sitesearch&keymatch=u-boot.img#2321462 and AM57_UART_Boot_SOP_By_TI_Rio_Final.pdf .

we successed u-boot-spl.bin on AM572X EVM. but we failed u-boot.img on AM572X EVM.

we don't find any problem.

our board is as follwing. GP EVM verion is beyond A2.  It is connected the J3/J4/J6 to [1:2] for serial boot, and is connected the J5.

We sucess it on window as follwing below it.

perl serial-boot.pl -p com5 -s c:\Perl\u-boot-spl.bin -d 1

we don't see "CCCC" at Tera Term on windows. Anyway, we failed uploading u-boot.img on windows. It don't send any bytes.

We think that window don't support uart-boot. and then tryed to boot uart on uBuntu.

perl ./serial-boot.pl -p /dev/ttyUSB0 -s u-boot-spl.bin -d1 -t40

our minicon settings is as below it.

we don't see "CCCC" at minicom  on uBuntu. Anyway, we failed uploading u-boot.img.

we try it other image(tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/u-boot-ti-staging/2017.01+gitAUTOINC+9fd60700db-r4/package/boot).

but we have same problem.

we don't find any our problem.( uart tx/rx is correct, and the our image is compiled with CONFIG_SPL_YMODEM_SUPPORT.

I want to resolve it .

Thanks a lot.

our compiled image is attacted so that you will test it.

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/jun.7z

 

  • Joonho,

    Refer to the below e2e thread:

    e2e.ti.com/.../2016378

    Regards,
    Pavel
  • hi.
    we review the url as you indicate and retry it. we have no difference with the url.
    first, we wonder why we don't see "CCCC" at Tera Term or Minicom. our image have no problem(it is surely compiled with CONFIG_SPL_YMODEM_SUPPORT) and console settings is surely "115200 baud 8 stop bits no parity".
    we tryed it with no - Software Flow control.

    second, Y-modem with u-boot.img transfer is always failed. What is the problem ?

    Thanks a lot.
  • Hi.

    we   retry it  with none -> even on parity of console setting. However, we have the same problem.

    I think that our evem board have any problem.

    our compiled image  with CONFIG_SPL_YMODEM_SUPPORT as following it.

    < u-boot.map >https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/u_2D00_boot.7z

    .text.xyzModem_stream_open

                   0x0000000080817424      0x170 common/built-in.o

                   0x0000000080817424                xyzModem_stream_open

    ....

    .text.load_serial_ymodem

                   0x0000000080806ea0       0x90 cmd/built-in.o

    ..

    Is it right ?

    Thanks a lot.

  • Joonho,

    I just tested on my AM572x EVM (rev A2) and I am able to boot the EVM from UART according to the instructions provided in the e2e thread I have sent to you in my previous reply.

    Please double check the below points:

    1. Modify u-boot/configs/am57xx_evm_defconfig file as below and build new u-boot-spl.bin and u-boot.img

    + CONFIG_SPL_YMODEM_SUPPORT=y

    2. Open two consoles, one within u-boot/am57xx_evm/ folder and one withing your home directory.

    In home directory console, execute "picocom -b 115200 /dev/ttyUSB0" and just monitor this console for now

    In u-boot/am57xx_evm console, I execute the below command:

    u-boot-2018.01/am57xx_evm$ perl serial-boot.pl -p /dev/ttyUSB0 -s spl/u-boot-spl.bin -d1 -t40

    Then I have the below message:

    ----Please reset the Board NOW (timeout=40 sec)----

     

    Then I power on the EVM and the u-boot-spl.bin transfer starts. At the end I have the below message:

    spl/u-boot-spl.bin file download completed

     

    At that time, the home directory console I start to see CCCCC stream. See the print screen attached:

    3. In u-boot/am57xx_evm console I execute the below command:

    u-boot-2018.01/am57xx_evm$ sx -kb --ymodem u-boot.img < /dev/ttyUSB0 > /dev/ttyUSB0
    Sending: u-boot.img
    Bytes Sent: 998784   BPS:10035                           
    Sending:
    Ymodem sectors/kbytes sent:   0/ 0k
    Transfer complete

    And I see u-boot.img is executed in the other console:

      ���bo���ro[HU�E�R�CC(STX)/0(CAN) packets, 5 retries
    Loaded 998708 bytes


    U-Boot 2018.01-00444-g17164f4a5d-dirty (Dec 12 2018 - 15:34:22 +0200)

    CPU  : DRA752-GP ES1.1
    Model: TI AM5728 BeagleBoard-X15
    Board: AM572x EVM REV A.20
    DRAM:  2 GiB
    MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
    GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
    part_get_info_efi: *** ERROR: Invalid GPT ***
    GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
    part_get_info_efi: *** ERROR: Invalid Backup GPT ***
    SCSI:  SATA link 0 timeout.
    AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
    flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst
    scanning bus for devices...
    Found 0 device(s).
    Net:   
    Warning: ethernet@48484000 using MAC address from ROM
    eth0: ethernet@48484000
    Hit any key to stop autoboot:  0
    MMC: no card present
    MMC: no card present
    MMC: no card present
    MMC: no card present
    Trying to boot Linux from eMMC ...
    switch to partitions #0, OK
    mmc1(part 0) is current device
    SD/MMC found on device 1
    ** Unable to read file /boot/zImage **
    Trying to boot Android from eMMC ...
    switch to partitions #0, OK
    mmc1(part 0) is current device

    MMC read: dev # 1, block # 2263040, count 5208064 ...

    Regards,
    Pavel

  • Hi.

    Thansk for your kindly answer.

    we follow that you say. but, we  have same error( we don't see "CCCC").

    we attach our print screen(console display on Ubuntu,  I think that you don't see console display very well, so we send cleared print screen.) 

    At two print screen, When we send u-boot-spl.bin, Monitor of picocon displays "VA!:".

    also, After we complete sending u-boot-spl.bin, Monitor of picon don't display "CCCC".

    we attath our compiled image and config(tt2.7z : u-boot.img, u-boot-spl.bin, .config, am57xx_evm_defconfig). but, we surely compiled with CONFIG_SPL_YMODEM_SUPPORT.

    we see xyxModem.o and spl_y_modem.o.

    What's the problem ?

       < console display >

      < cleared print screen >

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/7266.tt2.7z

  • Joonho,

    I tested with your u-boot-spl.bin file and I observe the same issue on my side, this u-boot-spl.bin is not working properly, I have no CCC stream on my console.

    I am attaching my working fine u-boot-spl.bin file, please try with it:

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/7750.u_2D00_boot_2D00_spl.bin

    I am using the default u-boot code base, only modified am57xx_evm_defconfig as already discussed.

    Note that this u-boot-spl.bin is based on ti-processor-sdk-linux-am57xx-evm-05.01.00.11/board-support/u-boot-2018.01

    Please try with my u-boot-spl.bin and if successful, you might try the whole flow with PSDK 5.01 and see if you will be ok there.

    Regards,
    Pavel

  • Hi.
    we can see "CCC" through 7750.u-boot-spl.bin .
    we have successed as follow it with 7750.u-boot-spl.bin .

    root@ubunto-TI:~/AM5728_4.0/xxx/uart_boot# sx -kb --ymodem u-boot.img < /dev/ttyUSB0 > /dev/ttyUSB0
    Sending: u-boot.img
    Bytes Sent: 854656 BPS:9974
    Sending:
    Ymodem sectors/kbytes sent: 0/ 0k
    Transfer complete

    but, we don't see u-boot.img is executed successfully in the other console.

    we can only see unknown characters as follow it.


    €ÿ³)Ò0`b$U
    ÀD(¢ @ÿ³)Ò0`b$U
    @D(¢ €ü³)Ò0`b$U
    €D(¢ € @ü³)Ò0`bU

    @ @Q @ÿ³)Ò0`b$U
    @D(¢ @ü³)Ò0`b$U
    ÀD(¢ @ü³)Ò0`b$U
    @D(¢ @ü³)Ò0`b$U
    @Q @ÿ³)Ò0`b$U
    ÀD(¢ @ü³)Ò0`b$U
    ÀD(¢ @ü³)Ò0`b$U
    ÀQ @ÿ



    We've build u-boot.img with PSDK4.x(ti-processor-sdk-linux-am57xx-evm-04.00.00.04). So this problem happen ?

    Thanks a lot.
  • Hi.

    we can see "CCCC" through 7750.u-boot-spl.bin.

    and then, we can upload u-boot.img successfully as follow it.

    <  ymodem log >

    root@ubunto-TI:~/AM5728_4.0/xxx/uart_boot# sx -kb --ymodem u-boot.img < /dev/ttyUSB0 > /dev/ttyUSB0

    Sending: u-boot.img

    Bytes Sent: 854656   BPS:9974                            

    Sending:

    Ymodem sectors/kbytes sent:   0/ 0k

    Transfer complete

    Thanks a lot.

  • Joonho,

    Glad to see you have fixed your issue now.

    Regards,
    Pavel
  • Hi. Pavel.
    TI PSDK have no any problem for uart boot.

    It(uart boot failure) have our problem.
    our uboot source changed from uart3 to uart10 before 1 years.
    Change of this uart cause uart boot failure.
    I am so sorry that we didnt realize it(uart change).

    Thanks you very much for many help.
    TI PSDK is very so good ....