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.

AM5746: AM5746 UART Booting

Part Number: AM5746
Other Parts Discussed in Thread: AM5748

Hello.

Can you please refer me to a document/s that describe/s the process of UART boot of the AM5746 processor?

Regards,

Bud Miljkovic

  • Hi Budimir,

    On the latest 6.03 SDK, we do not have the support for this boot mode.

    Requesting you to take a look at this FAQ for the details:

    e2e.ti.com/.../959283

    Best Regards,
    Keerthy

  • Hello Keerthy,

    I did looked at the link you provided and found some relevant info about what I want to achieve.

    I tried to use it but with no success.

    Thus, let me rephrase what I want to do achieve:

    I would like to boot the AM5748 processor on my Industrial Development Kit board via UART.

    I have found, following the link you gave me, which refers to Processor SDK Linux 06_03_00_106 document section, the following write-up:

    3.1.1.10.1. Booting U-Boot from the console UART

    In some cases we support loading SPL and U-Boot over the console UART. You will need to use the spl/u-boot-spl.bin and u-boot.img files to boot. As per the TRM, the file is to be loaded via the X-MODEM protocol at 115200 baud 8 stop bits no parity (same as using it for console). SPL in turn expects to be sent u-boot.img at the same rate but via Y-MODEM. An example session from the host PC, assuming console is on ttyUSB0 and already configured would be and the lrzsz package is installed

    $ sx -kb /path/to/u-boot-spl.bin < /dev/ttyUSB0 > /dev/ttyUSB0
    $ sx -kb --ymodem /path/to/u-boot.img < /dev/ttyUSB0 > /dev/ttyUSB0
    
    

    So, I have modified the SYSBOOT pad resistors to provide only UART peripheral booting and as the result I can see some output (some charaters) on the J19 USB connector connected to my Linux box where it is monitored by the putty when I power up the IDK board, which I take as the ASIC ID message, beaing sent by ROM code.

    What I realy need to understand is how to get the XMODEM transmission to succeed.

    Here is what I curretnly do:

    • Setup the UART port on my Linux box:
      sudo stty -F /dev/ttyUSB1 115200 cs8 -parenb -cstopb -ixon
    • Power up the IDK board

    • Execute the sx command from above, which should enable the transver of the u-boot-spl.bin file:
      $ sx -kb Logging/u-boot-spl.bin < /dev/ttyUSB1 > /dev/ttyUSB1
    • The immedate output of the above command is:
      Sending Logging/axu-boot-spl.bin, 864 blocks: Give your local XMODEM receive command now.

      I do not quite understand what the "Give your local XMODEM receive command now" is refering to as I would expect 'the receive command' should come from the ROM code sent via UART3 from IDK.

    • After some time of about ~15-20 sec, the following printed and the command exits:
      Retry 0: Receiver Cancelled

      Transfer incomplete

    I would really appreciate if somone can provide some instruction of how to acheive what was descritber in the 3.1.1.10.1. Booting U-Boot from the console UART section I quoted above.

    Regards,

    Bud Miljkovic

  • Hi Budimir,

    This is an elaborate document which helps: https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/AM57_5F00_UART_5F00_Boot_5F00_SOP_5F00_By_5F00_TI_5F00_Rio_5F00_Final.pdf

    Just repeating myself the UART boot is not supported on the latest SDK.

    Best Regards,
    Keerthy