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/EVMK2H: UART Boot K2EVM-HK Board

Part Number: EVMK2H

Tool/software: Linux

I have a K2EVM-HK board that I'd like to boot u-boot via UART following the documentation here: http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components_U-Boot.html

I'm using the version of u-boot recommended here: software-dl.ti.com/.../Release_Specific_Release_Notes.html

URL: git://git.ti.com/ti-u-boot/ti-u-boot.git
Branch: ti-u-boot-2018.01
Commit ID: 313dcd69c2b32648266f91bcf223f9e539bc4201

I build u-boot-spl.bin and u-boot.img (attached below) using gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf

~$ export CROSS_COMPILE=arm-linux-gnueabihf-
~$ make k2hk_evm_defconfig
~$ # enable CONFIG_SPL_YMODEM_SUPPORT
~$ make

I run:

~$ stty -F /dev/ttyUSB0
speed 115200 baud; line = 0;
-brkint -imaxbel

~$ sx -kb spl/u-boot-spl.bin </dev/ttyUSB0 >/dev/ttyUSB0
Sending spl/u-boot-spl.bin, 167 blocks: Give your local XMODEM receive command now.

~$ # power on the EVM with SW1 set to UART boot mode (0100).

Bytes Sent:  21504   BPS:8055                            

Transfer complete

~$ sx -kb --ymodem u-boot.img </dev/ttyUSB0 >/dev/ttyUSB0
Retry 0: Timeout on pathname

Transfer incomplete



Using minicom, I see the "CCCC" characters prior to sending u-boot-spl.bin. However, after sending u-boot-spl.bin successfully, I don't receive any "CCCC" characters for sending u-boot.img.

What could be going wrong?

uboot-files.tar

  • Hi,

    As far as I can see from the log the MLO file (or u-boot-spl.bin) was not transferred properly:
    "Transfer incomplete"

    Also I think that your changes in the config file might not have taken effect. What I recommend is:
    1. Add CONFIG_SPL_YMODEM_SUPPORT = y directly in k2hk_evm_defconfig
    2. Add define CONFIG_SPL_YMODEM_SUPPORT in include/configs/k2hk_evm.h and prior to building the u-boot with make execute make k2hk_evm_config -> this builds the spl configuration and after that build the u-boot.img.

    Best Regards,
    Yordan
  • I've tried the following:


    add "#define CONFIG_SPL_YMODEM_SUPPORT 1" to include/configs/k2hk_evm.h
    add "CONFIG_SPL_YMODEM_SUPPORT=y" to configs/k2hk_evm_defconfig

    ~$ export CROSS_COMPILE=arm-linux-gnueabihf-
    ~$ make distclean
    ~$  make k2hk_evm_config
    ~$  make

    (new u-boot.img and u-boot-spl.bin attached below)

    While trying UART boot, I get the same issue:

    ~$ stty -F /dev/ttyUSB0
    speed 115200 baud; line = 0;
    -brkint -imaxbel

    ~$ sx -kb spl/u-boot-spl.bin </dev/ttyUSB0 >/dev/ttyUSB0
    Sending spl/u-boot-spl.bin, 167 blocks: Give your local XMODEM receive command now.
    Bytes Sent:  21504   BPS:2087                            

    Transfer complete

    ~$ sx -kb --ymodem u-boot.img </dev/ttyUSB0 >/dev/ttyUSB0
    Retry 0: Timeout on pathname

    Transfer incomplete

    uboot-files-2.tar

  • I still can't seem to be able to boot via UART.

    I suspect that the problem might be in u-boot-spl.bin since it looks like it is being transferred completely.

    Am I correct in that u-boot-spl.bin should be sending "CCCC"s if it is running correctly?

    In case it matters, the EVM subset I'm using is the XTCIEVMK2X.
  • Correct, you need to get "CCCCC" on your console after you send u-boot-spl.bin. If you don't get the "CCCCC" it means that ROM code did not boot the u-boot-spl.bin. This may be because the image is wrong.

    Try the following. Remove all your changes from u-boot. Then execute the following commands:
    cd ti-processor-sdk-linux-k2hk-evm-05.00.00.15/
    make u-boot_clean
    make u-boot

    This will build spl/u-boot-spl.bin. When you power on your board & see "CCCC" characters transfer this newly built u-boot-spl.bin file and then the u-boot.img over uart.

    Best Regards,
    Yordan
  • This didn't work either.

    Do I have to go through software-dl.ti.com/.../Overview_Getting_Started_Guide.html

    Edit: Do I have to go through the Overview_Getting_Started_Guide.html#program-evm-user-guide above prior to being able to boot using UART.

  • Edit: Do I have to go through the Overview_Getting_Started_Guide.html#program-evm-user-guide above prior to being able to boot using UART.


    YES, you should go through the whole User Guide to get familiar with the Linux SDK release & what it supports.

    Best Regards,
    Yordan
  • Hello j e.

    For K2E the processor can boot "u-boot.bin" directly. It is not a two stage process requiring spl. Use "sx -kb u-boot.bin < /dev/ttyUSB0 > /dev/ttyUSB0"