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.

TMDSIDK572: Basic setup instructions for establishing an interface between a LInux development host and the AM572X industrial Development Kit Development target

Part Number: TMDSIDK572
Other Parts Discussed in Thread: AM5729

I am trying to configure the AM572X Industrial Development Kit development environment and boot the development board using a SD Card.

The Processor SDK Linux 06_04_00_106 documentation section 1.1.1.2 step 4 indicates:

"There are many ways to connect the host development platform and the target board. These connections will vary depending on how you like to develop and what you are trying to do. Here is an example of a common set up with a serial connection for console and Ethernet for networking (TFTP, NFS, etc.)"

The TMDSIDK572 development kit has a Texas Instruments XDS100v2 USB serial debug probe but I cannot find any documentation on how to set up the interface to establish a console to see the Linux boot process and establish a Linux shell. 

I tried minicom but there does not appear to be a console option.

  • Hello,

    Do you see a serial (ttyUSB*) when you connect the cable?

    Regards

    Hemant

  • I see a serial ttyUSB0 when I connect the cable. However, when I cycle power on the development board I get no response. I would expect to see typical Linux bootup messages and a Linux shell after the boot is complete. I am using a micro SD card that was supplied with the AM572X Industrial Development Kit. First I tried the micro SD card as supplied. When that did not work I following the instructions to create a new Linux boot SD card. I have not been able to get any response at all from the board. I am wondering if there is something I am doing wrong or if there is a problem with the board.

  • Hi David,

    UART Trace port is /dev/ttyUSB1 for all the am57xx-IDKs. The same micro-USB port enumerates 2 instances.

    /dev/ttyUSB0 & ./dev/ttyUSB1. You need to connect to minicom with /dev/ttyUSB1 If you insert your SD card you

    should see traces on that. BAUD rate 115200.

    Let me know.

    Best Regards,
    Keerthy

  • Keerthy,

    Thank you for your help and support.

    I have connected to minicom with /dev/ttyUSB1. I am confident that the connection is working because when I power down the development board minicom displays a message that the connection is not active. I also verified the minicom BAUD rate is set to 115200. However, when I cycle power on the development board with a Linux micro SD card installed, I get no traces whatsoever from the development board. Can you think of anything I may be missing? Could the development board be faulty? 

    Thanks,

    Dave   

  • Hi Dave,

    Does you SD card have boot partition? If yes what are the contents of the boot partition on your SD card?

    - Keerthy

  • Thank you again for your help.

    The SD card has a boot partition and a rootfs partition.

    I created the SD card using the "create-sdcard.sh" script provided with the SDK installation by following the directions in section "1.1.2 Linux SD Card Creation Guide" in the "Processor SDK Linux 06_03_00_006" document.

    Following is a screenshot of contents of the boot partition on the SD card:

  • Hi David,

    Those contents look fine to me. One more try before we check with our hardware experts
    is try to copy the attached MLO/u-boot.img to your boot partition.

    6507.MLO

    1401.u-boot.img

  • Thank you again for all your help.

    I will be out of the office on travel until Friday but will replace the current MLO and U-boot files on the micro-SD card with the ones you have provided and attempt to boot the development board as soon as I can.  

  • Thank you again for your help and support.

    I copied the provided 6507.MLO and 1401.u-boot.img files to the micro-SD boot partition and I am still unable to get any response from the AM5729 development board. Following is a snippet of the micro-SD boot partition with the provided files:

    Following is the minicom serial port setup:

    As mentioned in an earlier post, I am confident the port is working because when I power off the AM5729 development board I get the following message "Cannot open /dev/ttyUSB1" and when I power-up the development board the message goes away.

  • Hi David,

    Please rename them to MLO & u-boot.img. ROM Code will only pick up the file named MLO.
    So please one last try renaming them.

    - Keerthy

  • I renamed the files as directed and I am now getting some response from the development board. The board is still unable to boot but I am at least getting some response.

    What is the difference between the MLO/u-boot.img you provided vs. the MLO/u-boot.img created using the "create-sdcard.sh" script provided with the SDK installation?

    I have included a snippet of the messages that I am now receiving from the development board below. Note that when the boot fails the boot is reattempted so the message included bellow is sent over and over.

  • HI Dave,

    This is great! So board is all good no issues there. Now you are past the u-boot stage.

    So when you boot there is an autoboot countdown. Please press enter and halt at u-boot.
    Give the below commands and see if you can start booting LInux:

    env default -a
    saveenv
    boot

    Best Regards,
    Keerthy

  • When I execute the second command (saveenv) I get the error in the snippet below. I assume this may be because of a write permission on the mico-SD card but did not want to change anything other than specified in order not to introduce new variables. At any rate, when I execute the third command it is unable to boot and repeats the boot countdown sequence.

  • Hi Dave,

    There definitely seems to be an issue with your SD card creation.

    As a work around for now. Copy the am572x-idk.dtb & zImage to your boot partition
    & once you get to u-boot prompt try the below commands:

    setenv bootargs console=ttyO2,115200n8 root=/dev/mmcblk0p2 rootwait earlyprintk debug loglevel=8
    setenv bootcmd 'mmc dev 0; fatload mmc 0 0x81000000 zImage; fatload mmc 0 0x81800000 am572x-idk.dtb; bootz 0x81000000 - 0x81800000'
    boot

    See if you can boot up to kernel.

    Best Regards,
    Keerthy

  • Keerthy,

    Great news; I am now able to boot to kernel!

    As directed, I copied am572x-idk.dtb & zImage to the micro-SD boot partition. Then at the u-boot prompt entered the specified commands. Note, that if I cycle power the development board also boots to kernel without entering the specified commands.

    I really appreciate all of your help and support.

    Before closing this request and proceeding it is important that I understand where things went wrong so that I am able to create a bootable micro-SD card. How are the MLO/u-boot.img files you provided created and why did we need to copy am572x-idk.dtb & zImage to the boot partition? How are the provided files different than the files provided with the micro-SD card distributed with the development kit? Why would the micro-SD card created using the "create-sdcard.sh" script provided with the SDK installation by following the directions in section "1.1.2 Linux SD Card Creation Guide" in the "Processor SDK Linux 06_03_00_006" document not work? Where did things go wrong? Did I overlook important documentation? Is it possible that our SDK installation is corrupt?

    Before proceeding, I would really like to understand how things went wrong?

    Thanks

  • Dave,

    Awesome! Yes so your hardware is perfectly fine. Now like you have already doubted few steps try the following:

    This clean installation and then fresh SD Card creation should work. Please try it out.

    Best Regards,
    Keerthy

  • Keerthy,

    More great news!

    I followed your directions and reinstalled the SDK and created a SD Card and everything seems to work. After reviewing the documentation and my original installation, the only difference I can find is the SD Card script directive. For example, I crated the original SD card with the following command:

    sudo ./create-sdcard.sh

    The new working SD card was created with the following command:

    sudo ./create-sdcard.sh --device /dev/sdb --sdk /home/davida/ti-processor-sdk-linux-am57xx-evm-06.03.00.106/

    Is the --device script directive required? i.e.:

    --device /dev/sdb --sdk /home/davida/ti-processor-sdk-linux-am57xx-evm-06.03.00.106/

    Thanks again for all your help and support.

  • David,

    Yes that is the right way. You are telling the script the exact device the card has enumerated with & sdk tells the script the
    SDK to path to install. Resolve this issue.

    Best Regards,
    Keerthy