• State
  • Locked Locked
  • Replies 12 replies
  • Subscribers 32 subscribers
  • Views 584 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.

PROCESSOR-SDK-AM68: Encountering board detection issue while running setup script for TI-AM68 Processor SDK.How can I resolve this and proceed with booting the board?

Apuroop Kumar Bhattaram
Prodigy 70 points
Part Number: PROCESSOR-SDK-AM68
Other Parts Discussed in Thread: AM68

dell@dell-Inspiron-5558:~/ti-processor-sdk-linux-j721s2-evm-09_02_00_04$ sudo ./setup.sh
[sudo] password for dell:
-------------------------------------------------------------------------------
TISDK setup script
This script will set up your development host for SDK development.
Parts of this script require administrator priviliges (sudo access).
-------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Verifying Linux host distribution
Ubuntu 22.04 LTS is being used, continuing..
--------------------------------------------------------------------------------

Starting with Ubuntu 12.04 serial devices are only accessible by members of the 'dialout' group.
A user must be apart of this group to have the proper permissions to access a serial device.

Are you running this script using sudo? The detected username is 'root'.
Verify and enter your Linux username below
[ root ]

User 'root' is already apart of the 'dialout' group

Do you wish to install required host packages (Press (Y) to run, (n) to skip)?
-------------------------------------------------------------------------------
setup package script
This script will make sure you have the proper host support packages installed
This script requires administrator priviliges (sudo access) if packages are to be installed.
-------------------------------------------------------------------------------
System has required packages!
System has required python3 packages!
--------------------------------------------------------------------------------
Package verification and installation successfully completed
--------------------------------------------------------------------------------
Do you wish to run nfs setup (Press (Y) to run, (n) to skip) ?
--------------------------------------------------------------------------------
In which directory do you want to install the target filesystem?(if this directory does not exist it will be created)
[ /home/dell/ti-processor-sdk-linux-j721s2-evm-09_02_00_04/targetNFS ]
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will extract the target filesystem to /home/dell/ti-processor-sdk-linux-j721s2-evm-09_02_00_04/targetNFS

Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
/home/dell/ti-processor-sdk-linux-j721s2-evm-09_02_00_04/targetNFS already exists
(r) rename existing filesystem (o) overwrite existing filesystem (s) skip filesystem extraction
[r] s
Skipping filesystem extraction
WARNING! Keeping the previous filesystem may cause compatibility problems if you are upgrading the SDK
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up the SDK to install binaries in to:
   /home/dell/ti-processor-sdk-linux-j721s2-evm-09_02_00_04/targetNFS/home/root/j721s2-evm

The files will be available from /home/root/j721s2-evm on the target.

This setting can be changed later by editing Rules.make and changing the
ROOTFS_PART variable.

Press return to continue
Rules.make edited successfully..
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will export your target filesystem for NFS access.

Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
/home/dell/ti-processor-sdk-linux-j721s2-evm-09_02_00_04/targetNFS already NFS exported, skipping..

Stopping nfs-kernel-server (via systemctl): nfs-kernel-server.service.
Starting nfs-kernel-server (via systemctl): nfs-kernel-server.service.
--------------------------------------------------------------------------------
Do you wish to run tftp setup (Press (Y) to run, (n) to skip) ?
--------------------------------------------------------------------------------
Which directory do you want to be your tftp root directory?(if this directory does not exist it will be created for you)
[ /tftpboot ]
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up the tftp server in the /tftpboot directory.

Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue

/tftpboot already exists, not creating..

/tftpboot/*Image-j721s2-evm.bin already exists. The existing installed file can be renamed and saved under the new name.
(r) rename (o) overwrite (s) skip copy
[r] s
Skipping copy of *Image-j721s2-evm.bin, existing version will be used

Successfully copied k3-am68-sk-base-board.dtb to tftp root directory /tftpboot

Successfully copied k3-j721s2-common-proc-board.dtb to tftp root directory /tftpboot

Successfully copied u-boot.dtb to tftp root directory /tftpboot

Successfully copied k3-am68-sk-bb-csi2-ov5640.dtbo to tftp root directory /tftpboot

Successfully copied k3-am68-sk-bb-rpi-cam-imx219.dtbo to tftp root directory /tftpboot

Successfully copied k3-am68-sk-fpdlink-fusion.dtbo to tftp root directory /tftpboot

Successfully copied k3-am68-sk-rpi-hdr-ehrpwm.dtbo to tftp root directory /tftpboot

Successfully copied k3-am68-sk-som-ddr-mem-carveout.dtbo to tftp root directory /tftpboot

Successfully copied k3-am68-sk-v3link-fusion.dtbo to tftp root directory /tftpboot

Successfully copied k3-fpdlink-imx390-rcm-0-0.dtbo to tftp root directory /tftpboot

Successfully copied k3-fpdlink-imx390-rcm-0-1.dtbo to tftp root directory /tftpboot

Successfully copied k3-fpdlink-imx390-rcm-0-2.dtbo to tftp root directory /tftpboot

Successfully copied k3-fpdlink-imx390-rcm-0-3.dtbo to tftp root directory /tftpboot

Successfully copied k3-fpdlink-imx390-rcm-1-0.dtbo to tftp root directory /tftpboot

Successfully copied k3-fpdlink-imx390-rcm-1-1.dtbo to tftp root directory /tftpboot

Successfully copied k3-fpdlink-imx390-rcm-1-2.dtbo to tftp root directory /tftpboot

Successfully copied k3-fpdlink-imx390-rcm-1-3.dtbo to tftp root directory /tftpboot

Successfully copied k3-fpdlink-imx390-rcm-2-0.dtbo to tftp root directory /tftpboot

Successfully copied k3-fpdlink-imx390-rcm-2-1.dtbo to tftp root directory /tftpboot

Successfully copied k3-fpdlink-imx390-rcm-2-2.dtbo to tftp root directory /tftpboot

Successfully copied k3-fpdlink-imx390-rcm-2-3.dtbo to tftp root directory /tftpboot

Successfully copied k3-fpdlink-ov2312-0-0.dtbo to tftp root directory /tftpboot

Successfully copied k3-fpdlink-ov2312-0-1.dtbo to tftp root directory /tftpboot

Successfully copied k3-fpdlink-ov2312-0-2.dtbo to tftp root directory /tftpboot

Successfully copied k3-fpdlink-ov2312-0-3.dtbo to tftp root directory /tftpboot

Successfully copied k3-j7200-evm-mcspi-loopback.dtbo to tftp root directory /tftpboot

Successfully copied k3-j721s2-evm-csi2-ov5640.dtbo to tftp root directory /tftpboot

Successfully copied k3-j721s2-evm-fusion.dtbo to tftp root directory /tftpboot

Successfully copied k3-j721s2-evm-gesi-exp-board.dtbo to tftp root directory /tftpboot

Successfully copied k3-j721s2-evm-pcie1-ep.dtbo to tftp root directory /tftpboot

/etc/xinetd.d/tftp already exists..
/tftpboot already exported for TFTP, skipping..

Restarting tftp server
Stopping xinetd (via systemctl): xinetd.service.
Starting xinetd (via systemctl): xinetd.service.
--------------------------------------------------------------------------------
Do you wish to run minicom setup (Press (Y) to run, (n) to skip) ?

--------------------------------------------------------------------------------"
This step will set up minicom (serial communication application) for
SDK development


For boards that contain a USB-to-Serial converter on the board such as:
   * BeagleBone
   * Beaglebone Black
   * AM335x EVM-SK
   * AM57xx EVM
   * K2H, K2L, and K2E EVMs

the port used for minicom will be automatically detected. By default Ubuntu
will not recognize this device. Setup will add a udev rule to
/etc/udev/ so that from now on it will be recognized as soon as the board is
plugged in.

For other boards, the serial will defualt to /dev/ttyUSB2. Please update based
on your setup.

--------------------------------------------------------------------------------


NOTE: If your using any of the above boards simply hit enter
and the correct port will be determined automatically at a
later step. For all other boards select the serial port
that the board is connected to.
Which serial port do you want to use with minicom?
[ /dev/ttyUSB2 ]

Copied existing /root/.minirc.dfl to /root/.minirc.dfl.old

Configuration saved to /root/.minirc.dfl. You can change it further from inside
minicom, see the Software Development Guide for more information.
--------------------------------------------------------------------------------
Do you wish to run uboot setup (Press (Y) to run, (n) to skip) ?

--------------------------------------------------------------------------------
This step will set up the u-boot variables for booting the EVM.
--------------------------------------------------------------------------------
Autodetected the following ip address of your host, correct it if necessary
[ 192.168.12.193
192.168.12.193 ]

Select Linux kernel location:
 1: TFTP
 2: SD card

[ 1 ]

Select root file system location:
 1: NFS
 2: SD card

[ 1 ]

Available kernel images in /tftpboot:
   Image-j721s2-evm.bin
   ti

Which kernel image do you want to boot from TFTP?
[ Image-j721s2-evm.bin ]

Successfully wrote minicom script with above parameters: /home/dell/ti-processor-sdk-linux-j721s2-evm-09_02_00_04/bin/setupBoard.minicom

--------------------------------------------------------------------------------
Would you like to run the minicom script and boot the board? (y/n)?
[ y ]


Detecting connection to board... portdefault: /dev/ttyUSB2
cannot read device status, Resource temporarily unavailable (11)
cannot read device status, Resource temporarily unavailable (11)
cannot read device status, Resource temporarily unavailable (11)
cannot read device status, Resource temporarily unavailable (11)
cannot read device status, Resource temporarily unavailable (11)
cannot read device status, Resource temporarily unavailable (11)
cannot read device status, Resource temporarily unavailable (11)
cannot read device status, Resource temporarily unavailable (11)
cannot read device status, Resource temporarily unavailable (11)

Unable to detect which port the board is connected to.
Please reconnect your board.
Press 'y' to attempt to detect your board again or press 'n' to continue...
(y/n)^C
dell@dell-Inspiron-5558:~/ti-processor-sdk-linux-j721s2-evm-09_02_00_04$

  • 0
    TI__Mastermind 19680 points

    Hi,

    Could you try connecting using /dev/ttyUSB0 instead of /dev/ttyUSB2?

    Thank you,

    Fabiana

  • 0 in reply to Fabiana Jaimes
    Prodigy 70 points


    Hi Fabiana,

    Thank you for your response. I had already attempted to connect using /dev/ttyUSB0, but unfortunately, I'm still encountering the same issue. I've also tried all available USB ports (/dev/ttyUSB0, 1, 2, 3), but with no success. The error message persists, indicating "cannot read device status, Resource temporarily unavailable (11)". Any further guidance or troubleshooting steps would be greatly appreciated.

    Best regards,
    B. Apuroop Kumar

  • 0 in reply to Apuroop Kumar Bhattaram
    TI__Mastermind 19680 points

    Hello,

    Are you able to connect via minicom in a separate terminal? Could you share dmesg logs when you connect the device to your PC?

    Thank you,

    Fabiana

  • 0 in reply to Fabiana Jaimes
    Prodigy 70 points

    Hello Fabiana,

    Thank you for your continued support. I've made some progress on our issue.

    Yesterday, we managed to successfully boot up the board via NFS by adjusting the uEnv.txt file with the following configurations:


    In the uEnv.txt file, we configured the boot parameters to enable booting via NFS. Specifically, we set the following parameters:

        svrip: This parameter specifies the IP address of the NFS server (192.168.12.193 in this case).
        ipaddr: This parameter sets the IP address of the AM68 board (192.168.12.211 in this case).
        image: This parameter defines the name of the image file (Image-j721s2-evm.bin in this case).
        rootpath: This parameter specifies the root path on the NFS server where the filesystem is located (/home/dell/ti-processor-sdk-linux-j721s2-evm-09_02_00_04/targetNFS in this case).
        fdtfile: This parameter sets the name of the device tree binary file (ti/k3-am68-sk-base-board.dtb in this case).
        netargs: This parameter sets the boot arguments for networking, including the console, root filesystem location, and IP address.
        netboot: This parameter defines the sequence of commands to load the kernel image and device tree from the network.
        uenvcmd: This parameter specifies the command to execute for network booting, which includes setting the server IP address and booting from the network.


    Additionally, to verify if the board successfully booted via NFS, I executed the mount command on the terminal. Here's the output:

    192.168.12.193:/home/dell/ti-processor-sdk-linux-j721s2-evm-09_02_00_04/targetNFS on / type nfs (rw,relatime,vers=3,rsize=4096,wsize=4096,nam)
    devtmpfs on /dev type devtmpfs (rw,relatime,size=7714660k,nr_inodes=1928665,mode=755)
    proc on /proc type proc (rw,relatime)
    sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
    securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
    tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
    devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
    tmpfs on /run type tmpfs (rw,nosuid,nodev,size=3269764k,nr_inodes=819200,mode=755)
    tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755)
    cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)

    ================================================================================================
    After that I exited from minicom and again as mentioned in the website related to AM68 SDK documentation
    (software-dl.ti.com/.../Run_Setup_Scripts.html)

    I executed the  setup script but again same error persists

    Furthermore, I ran the  `dmesg | grep ttyUSB` command to check for any relevant logs when connecting the device to my PC. Here's the output you requested:


    [11349.802093] usb 2-2: cp210x converter now attached to ttyUSB0
    [11349.802722] usb 2-2: cp210x converter now attached to ttyUSB1
    [11349.803360] usb 2-2: cp210x converter now attached to ttyUSB2
    [11349.803805] usb 2-2: cp210x converter now attached to ttyUSB3
    [11492.676091] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
    [11492.676845] cp210x ttyUSB1: cp210x converter now disconnected from ttyUSB1
    [11492.678904] cp210x ttyUSB2: cp210x converter now disconnected from ttyUSB2
    [11492.681607] cp210x ttyUSB3: cp210x converter now disconnected from ttyUSB3
    .......


    Could you provide further guidance or suggest additional troubleshooting steps to resolve this issue?

    Thank you once again for your assistance.

    Best regards,
    B. Apuroop Kumar

  • 0 in reply to Apuroop Kumar Bhattaram
    TI__Mastermind 19680 points

    Hi,

    Have you verified that you have administrator privileges (sudo access) on your host? Have you added yourself to the "dialout" group as outlined in the SDK documentation?

    Thank you,

    Fabiana

  • 0 in reply to Fabiana Jaimes
    Prodigy 70 points

    Hi Fabiana,

    Thank you for your suggestion. Yes, I've verified that I have administrator privileges (sudo access) on my host. The setup script also confirmed that the user 'root' is already part of the 'dialout' group, which allows proper access to serial devices.
    ------------------------------------------------------------------------------------
    dell@dell-Inspiron-5558:~/ti-processor-sdk-linux-j721s2-evm-09_02_00_04$ sudo ./setup.sh
    [sudo] password for dell:
    -------------------------------------------------------------------------------
    TISDK setup script
    This script will set up your development host for SDK development.
    Parts of this script require administrator priviliges (sudo access).
    -------------------------------------------------------------------------------

    --------------------------------------------------------------------------------
    Verifying Linux host distribution
    Ubuntu 22.04 LTS is being used, continuing..
    --------------------------------------------------------------------------------

    Starting with Ubuntu 12.04 serial devices are only accessible by members of the 'dialout' group.
    A user must be apart of this group to have the proper permissions to access a serial device.

    Are you running this script using sudo? The detected username is 'root'.
    Verify and enter your Linux username below
    [ root ]

    User 'root' is already apart of the 'dialout' group

    Do you wish to install required host packages (Press (Y) to run, (n) to skip)?
    -------------------------------------------------------------------------------
    setup package script
    This script will make sure you have the proper host support packages installed
    This script requires administrator priviliges (sudo access) if packages are to be installed.
    -------------------------------------------------------------------------------
    System has required packages!
    System has required python3 packages!
    -----------------------------------------------------------------------------------

     Any additional insights or further steps I could take to resolve the board detection issue, I would greatly appreciate your assistance.

    Best regards,
    B.Apuroop Kumar

  • 0 in reply to Apuroop Kumar Bhattaram
    TI__Mastermind 19680 points

    Thank you for verifying. I will be reassigning this thread to the correct engineer.

    -Fabiana

  • 0
    TI__Guru**** 165000 points

    Hi Apuroop,

    Apuroop Kumar Bhattaram said:
    Detecting connection to board... portdefault: /dev/ttyUSB2

    Couple of questions:

    • So you are able to connect to /dev/ttyUSB2 directly using minicom but with setup script you are unable to connect to /dev/ttyUSB2?
    • Are you getting logs on /dev/ttyUSB2?
    • I believe your PC is enumerating the /dev/ttyUSB0, /dev/ttyUSB1, /dev/ttyUSB2, /dev/ttyUSB3. Can you confirm the same?
    • AM68 SDK 9.2 is https://www.ti.com/tool/PROCESSOR-SDK-AM68A. Can you confirm that you are using that SDK version?
    • Make sure that you no other terminal where minicom is open before running the setup script.

    Thanks,
    Keerthy

  • 0 in reply to Keerthy J
    Prodigy 70 points

    Hi,
     


    1. Connecting via Minicom vs. Setup Script: Yes, I can connect to /dev/ttyUSB2 directly using Minicom, but when running the setup script, I'm unable to establish a connection to /dev/ttyUSB2.

    2. Logs on /dev/ttyUSB2: Unfortunately, I'm not receiving any logs on /dev/ttyUSB2 when attempting to run the setup script.

    3. Enumeration of Serial Ports: Yes, my PC is indeed enumerating /dev/ttyUSB0, /dev/ttyUSB1, /dev/ttyUSB2, and /dev/ttyUSB3.
    4. I downloaded SDK from www.ti.com/.../PROCESSOR-SDK-AM68

    Best Regards,
    B. Apuroop Kumar

  • 0 in reply to Apuroop Kumar Bhattaram
    TI__Guru**** 165000 points

    Hi,

    I meant are you getting logs on minicom once you power up the board with SD card?

    Also while running the setup script make sure you close all the minicom terminals.

    Best Regards,

    Keerthy 

  • 0 in reply to Keerthy J
    Prodigy 70 points

    Hi,

    Yes, when I power up the board with the SD card inserted, I am able to see logs on Minicom. However, when running the setup script, even after closing all Minicom terminals, I encounter the error message regarding the inability to detect the device status. This occurs specifically when attempting to run the Minicom script to boot the board.

    Best Regards,

    B. Apuroop Kumar.

  • 0 in reply to Apuroop Kumar Bhattaram
    TI__Guru**** 165000 points

    Hi Apuroop,

    We will reproduce the issue and get back to you early next week.

    Thanks,
    Keerthy