• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 99 subscribers
  • Views 613 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

SK-AM64B: ti-processor-sdk-linux-am64xx-evm-09.00.00.03: setup-uboot-env.sh cannot find the device

Stephan Karger
Intellectual 280 points
Part Number: SK-AM64B


Hello,

I connected a SK-AM64B to my pc using the usb-c connector with the label "DEBUG CONSOLE USB" and I have access to the board with minicom an /dev/ttyUSB1. 

Then I installed the SDK ti-processor-sdk-linux-am64xx-evm-09.00.00.03 and run setup.sh which calls ./bin/setup-uboot-env.sh which cannot find my evm. 

There is the following code section in this script.

board="unknown"
check_for_board() {
lsusb -vv -d 0403:6011 > /dev/null 2>&1

if [ "$?" = "0" ]
then
board="am65x"
fi
}

Could you please double check if the usb id or the board name has to be adapted. 

lsusb lists the following device on the board which I use to connect to.

Bus 003 Device 007: ID 10c4:ea70 Silicon Labs CP2105 Dual UART Bridge

Thanks.

  • +1
    TI__Guru 69867 points

    Hi Stephan,

    thanks for your report, I just had a look and that functionality is indeed broken. So I just filed an internal bug report (SITSW-2993) to get this fixed in a future release.

    Also looking at that script it seems to be mostly concerned with setting up some U-Boot environmental variables and the config for 'minicom'. I've not needed to use this script in many years myself for anything really; I always just see which ttyUSB ports get detected when plugging in a board (`dmesg` will tell you), and then pick a port from there and start communicating with the board. And then setup things in U-Boot manually depending on what I need to do. Actually looking at it some more the other concern is that script tries to save the environment (`saveenv` in U-Boot), which isn't even supported out of the box starting SDK v9.0.

    If you have something you need help figuring out setup-wise let me know,

    Regards, Andreas