• State
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 61 views
  • Users 0 members are here
Support feedback
Options
Options
Related

Original question:

J722SXH01EVM: How to display DP with J722S EVM + SN65DSI86 + ti-linux-kernel

J722SXH01EVM: I attempted to verify the operation of the DP connection by booting from a prebuilt image, but it did not boot.

K.Z
Expert 2570 points
Part Number: J722SXH01EVM

Tool/software:

Hi All,

Since SDK 11.1 has been released, I attempted to verify DP connectivity on the evaluation board (J722SXH01EVM). As a first step, I tried booting the board using the prebuilt image, but it did not start up.

The steps I followed are as below:

  • Downloaded the following file from the official TI page (www.ti.com/.../J722SXH01EVM
    ti-processor-sdk-linux-adas-j722s-evm-11_01_00_03-Linux-x86-Install.bin

  • Following the documentation (software-dl.ti.com/.../Processor_SDK_Linux_create_SD_card.html),
    executed:

    $ sudo <PSDK_PATH>/bin/create-sdcard.sh

    to create the SD card.

  • Inserted the created SD card into the board and checked via serial communication, but no U-Boot messages were displayed, and it appeared that the board did not boot.

Could you kindly advise on the correct procedure or any additional steps required?

Best Regards,

Ito

  • 0
    TI__Guru 51823 points

    Hi Ito-san,

    Can you confirm the following:

    1. Is the micro USB port labeled as "DEBUG USB" in-use?
    2. There should be 4 serial ports enumerated when connected to DEBUG USB. Is the 3rd instance connected? For example, if the serial device is enumerated as USB0, USB1, USB2, USB3, then USB2 should be the UART port that prints out U-Boot/Linux logs.

    As a sidenote, if using adas image, then display is by default disabled from Linux-side to allow RTOS control of display. So, if wanting Linux to have control, the uEnv.txt in boot partition must be edited so that the name_overlays and dorprocboot variables are commented out.

    Regards,

    Takuma

  • 0 in reply to Takuma Fujiwara
    Expert 2570 points

    Hi Takuma-san,

    Thank you for your reply.

    We are checking the connection via the port labeled USART on the evaluation board, and confirming communication with the PC through ttyUSB2.
    This setup is the same as what was used during operation verification with SDK version 11.1 and earlier, so we believe the connection is properly established.
    Also, the boot flag was set.
    Since there were no Image or dtb files in the boot partition, we suspect this might be one of the causes.
    If the "create-sdcard.sh" script does not fully prepare these files, would it be necessary to set them up separately?
    If so, could you kindly provide the steps or instructions for doing so?

    Best Regards,

    Ito

  • 0 in reply to K.Z
    TI__Guru 51823 points

    Hi Ito-san,

    I have also used the create-sdcard.sh to create the SD card and confirmed that it was working. The script should fully prepare the files necessary to boot to Linux login prompt. Linux kernel and dtb file are not located in boot partition, but they are instead located in the root partition's boot folder for the J7x generation of devices. Boot partition should instead have U-Boot kernel that would boot up the root partition and pull in the Linux kernel, dtb, and filesystem from root partition.

    In any case, it sounds like the script found the micro SD card since you mention there was a boot partition. Does the boot partition have any files? As long as there is a tiboot3.bin file, you should see some logs on the serial port.

    Regards,

    Takuma