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: Boot Problem

Part Number: PROCESSOR-SDK-AM68
Other Parts Discussed in Thread: BEAGLEY-AI

Tool/software:

I'm facing a very similar situation as is on this post on an EVM board I bought last week: https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1349101/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.

I did not see a solution posted on how to resolve this issue. Can TI please help resolve this or send a link where a solution was identified?

Thanks,

Robert

  • Hi, any updates on this? On the side I managed to boot the board but now I'm not able to see any output on the connected HDMI monitor. Is there a good reference on this issue as well?

    -Robert

  • Hi Robert,

    Regarding booting the board (glad you are able to boot), are you able to just use minicom separately and forego the setup.sh script? I personally use picocom to connect to my board.

    For the HDMI monitor, can you send me the dmesg log as well as the outputs for the following commands:

    dmesg | grep -i hdmi
    dmesg | grep -i deferred
    dmesg | grep -i dss
    modetest -M tidss
    kmsprint
    kmstest

    Best,
    Jared

  • Hi Jared,

    Here are tho outputs I get:

    root@am68a-sk:/opt/edgeai-gst-apps# dmesg | grep -i hdmi
    [    0.335106] platform connector-hdmi: Fixed dependency cycle(s) with /bridge-dvi
    [    0.349842] platform bridge-dvi: Fixed dependency cycle(s) with /connector-hdmi

    root@am68a-sk:/opt/edgeai-gst-apps# dmesg | grep -i dss     
    [    0.297446] platform 4800000.dsi: Fixed dependency cycle(s) with /bus@100000/ds0
    [    0.317121] platform 4800000.dsi: Fixed dependency cycle(s) with /bus@100000/ds0
    [    0.325430] platform 4a00000.dss: Fixed dependency cycle(s) with /bus@100000/ds0
    [    0.342617] platform 4a00000.dss: Fixed dependency cycle(s) with /bridge-dvi
    [    0.357350] platform bridge-dvi: Fixed dependency cycle(s) with /bus@100000/dss0
    [    9.129794] [drm] Initialized tidss 1.0.0 20180215 for 4a00000.dss on minor 1
    [    9.569000] tidss 4a00000.dss: [drm] fb0: tidssdrmfb frame buffer device

    root@am68a-sk:/opt/edgeai-gst-apps# kmsprint
    Connector 0 (40) HDMI-A-1 (disconnected)
      Encoder 0 (39) NONE
        Crtc 0 (38) 1920x1080@60.00 148.500 1920/88/44/148/+ 1080/4/5/36/+ 60 (60.08
          Plane 0 (31) fb-id: 65 (crtcs: 0 1) 0,0 1920x1080 -> 0,0 1920x1080 (AR12 )
            FB 65 1920x1080
    Connector 1 (50) eDP-1 (disconnected)
      Encoder 1 (49) NONE

    root@am68a-sk:/opt/edgeai-gst-apps# kmstest                                     
    Connector 0/@40: HDMI-A-1                                                       
      Crtc 0/@38: 1920x1080@60.00 148.500 1920/88/44/148/+ 1080/4/5/36/+ 60 (60.00)8
      Plane 0/@31: 0,0-1920x1080                                                    
        Fb 66 1920x1080-XR24                                                        
    press enter to exit

    dmesg | grep -i deferred does not give any output

    For some reason it shows the HDMI is disconnected, but it is physically connected. I used the same display with a RPI5 and a Beagley-ai and they are both able to drive the display!

    Thanks,

    Robert

  • I tried it with another display I bought and it's able to drive it with no issues. This other one that's not working is a larger 27'' display that has it's own power supply.

    Thanks,

    Robert

  • Hi Robert,

    It's strange that the device is enumerating but is showing as disconnected. Can you send the non-functioning display's product name as well as your full dmesg logs?

    Best,
    Jared

  • Hi Jared,

    The display is Acer SB270. Since the board is able to drive a display similar to the one I'll use on the final product, I'm okay with not spending more time on this issue. Should I see this issue resurface with another display, I will bring it up for investigation.

    Thanks,

    Robert