J784S4XEVM: J784S4XG01EVM - tisdk-adas-image-<machine>.wic.xz file missing

Hi Praveen Rao,

Thanks for the update. I have followed the process given in this https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-j784s4/09_01_00_06/exports/docs/linux/Overview/Processor_SDK_Linux_create_SD_card.html#create-sd-card-with-default-images-using-script and prepared my SD card using create-sdcard.sh script.

Note: I am using the prebuild files for preparing the SD card (Install pre-built images from SDK) and the content inside the uEnv.txt file is attached below.

psdk_setup_file=.psdk_setup
check_psdk_setup=load mmc 1:1 ${loadaddr} ${psdk_setup_file}

# Reset to the default environment
do_psdk_setup=env default -f -a; saveenv

# Update the Linux hostname based on board_name
# The SK also requires an additional dtbo to boot. Prepend it to name_overlays depending on board_name
uenvcmd=if test ${boot_fit} -eq 1; then setenv name_overlays $name_overlays_fit; fi; if test "$board_name" = "am69-sk"; then ; setenv args_all $argsi

# Setting the right U-Boot environment variables
dorprocboot=1
name_overlays=k3-j784s4-evm-virt-mac-client.dtbo k3-j784s4-vision-apps.dtbo

# Name overlays when booting from fit image
name_overlays_fit=ti/k3-j784s4-evm-virt-mac-client.dtbo ti/k3-j784s4-vision-apps.dtbo

At first I have connected the EVM's DISPLAY_PORT0 to my LG Monitor using DP to DP cable and for UART serial terminal usage I have used J49 Micro-B connector. Here I couldn't get my Display up. Then I have connected the EVM's DISPLAY_PORT1 to my LG Monitor using DP to DP cable and for UART serial terminal usage I have used J49 Micro-B connector. Even here I couldn't get my Display up. Attached are the dmesg logs of both occurences. 
Display Port 0: /cfs-file/__key/communityserver-discussions-components-files/791/default_5F00_dp0.txt

Display Port 1: /cfs-file/__key/communityserver-discussions-components-files/791/default_5F00_dp1.txt

Now I have modified the uEnv.txt file's name_overlays content. Replaced it to name_overlays=k3-j784s4-edgeai-apps.dtbo
Now when I tried to boot the kit with DISPLAY_PORT0 still couldn't get the display up and. Attached the dmesg logs of this. /cfs-file/__key/communityserver-discussions-components-files/791/edg_5F00_dp0.txt


Now I have changed to DISPLAY_PORT1 and now I can able to up my display. Attached the image of display and dmegs logs. 
/cfs-file/__key/communityserver-discussions-components-files/791/edg_5F00_dp1.txt

/resized-image/__size/320x240/__key/communityserver-discussions-components-files/791/dp.jpg

Now I tried to use the USB2.0 Interface [J5] for connecting my Mouse and Keyboard and both these ports doesn't work, even I tried my USB mass storage device but it doesn't work. I have connected these same setup in USB3.1 Gen1 Interface [J4] and it is working here (for connecting USB A type mouse and keyboard to this J4 interface I have used USB C to USB A converter).

We didn't use any custom software, but we are facing these issues. For Display what should we do and for USB2.0 Interface do we need to handle any switch or have jumper over any pins? Kindly help us with this.

Thanks,
Naveen.

Hello Naveen,

Since the original query was answered, and you are following up with new queries, we have to re-assign the thread to the right team. Thanks.

Hi Naveen,

Are you looking to use the display to run vision apps? Vision apps uses the RTOS driver for display which runs on R5 core.

To enable USB 2.0 hub, see the following FAQ: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1303008/faq-j721s2xsomxevm-enable-usb-2-0-hub-on-j7200-j721s2-j784s4

Thank you,

Fabiana

Hi Fabiana Jaimes,

> Are you looking to use the display to run vision apps?
   NO.

1. I want to use Linux SDK(which is supposed to be edge ai apps I guess).
But by default while following this https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-j784s4/09_01_00_06/exports/docs/linux/Overview/Processor_SDK_Linux_create_SD_card.html#create-sd-card-with-default-images-using-script link,
I can able to see the vision apps dtb only in uEnv.txt file. Though I changed it to edge ai apps dtb I am not gettting Display in PORT 0 but in PORT 1 am getting a display (but am not sure even this display is a proper one or not).

2. To enable USB2.0 I have gone through this https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1303008/faq-j721s2xsomxevm-enable-usb-2-0-hub-on-j7200-j721s2-j784s4 link. Here in this patch file 6811.0001-Enable-USB2.0-stacked-in-j721s2.patch which is give for J721s2 processor I can see the below contents to be added in the file k3-j721s2-som-p0.dtsi
+ usb_hub@0 {
+ gpio-hog;
+ gpios = <0 GPIO_ACTIVE_HIGH>;
+ output-high;
+ line-name = "USB2.0_MUX_SEL";
+ };
+ };

The same I have added for my J787s4 processor in the file k3-j784s4-evm.dtb (Below is the image of it)

and followed this https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-j784s4/09_02_00_05/exports/docs/linux/Foundational_Components_Kernel_Users_Guide.html#installing-the-kernel link and modified the kernel and installed in the SD card and in uEnv.txt file as well added the filename k3-j784s4-evm.dtb in name_overlays (name_overlays=k3-j784s4-evm.dtb k3-j784s4-edgeai-apps.dtbo) but still couldn't get the control of the mouse. Are we going wrong anywhere? Kindly help us with this.

Thanks,
Naveen

Hi Naveen,

Do you require both display ports for your use case? See section 2.3.6 Display Port Interfaces of the user guide to see what is supported on each display port: https://www.ti.com/lit/ug/spruj62/spruj62.pdf

I have looped in our USB expert to comment on item #2.

Thank you,

Fabiana

Hi Fabiana Jaimes

> Do you require both display ports for your use case? See section 2.3.6 Display Port Interfaces of the user guide to see what is supported on each display port: https://www.ti.com/lit/ug/spruj62/spruj62.pdf

Thank you for sharing this info "2.3.6 Display Port Interfaces [J8] [J9] The EVM supports two DisplayPort panels via standard DP cables interfaces [J8] [J9]. The processor's native DP [J9] supports resolutions up to 4K UHD (3840x216) including MST (Multi-Stream Transport) for connecting multiple panels. The second DisplayPort [J8] is supported via DP bridge device (SN65DSI86) and supports resolutions up to 1080p. The second DisplayPort (via bridge device) does not support integrated audio."

And regarding your question on whether we require both display ports for our use case ? Our concern is we are using prebuilt binaries for booting the kit and with that we couldn't use the processor's native DP[J9] port. What should we do in order to make it accessible. Like you said for USB, is there anything we need to do in device tree to make it accessible? Kindly help us with making this accessible. 

> I have looped in our USB expert to comment on item #2.
Thank you. I look forward to their insights on item #2

Thanks,
Naveen

Hi Naveen,

Our expert is out of office today. Expect an answer from them next week.

Thank you for your patience.

-Fabiana

HI Naveen,

Naveen K said:

and followed this https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-j784s4/09_02_00_05/exports/docs/linux/Foundational_Components_Kernel_Users_Guide.html#installing-the-kernel link and modified the kernel and installed in the SD card and in uEnv.txt file as well added the filename k3-j784s4-evm.dtb in name_overlays (name_overlays=k3-j784s4-evm.dtb k3-j784s4-edgeai-apps.dtbo) but still couldn't get the control of the mouse. Are we going wrong anywhere? Kindly help us with this.

can you help me with the below information.

• Share the dtb which you have used for the above test.
• Share the boot logs with the above changes.
• run the command gpioinfo in the linux kernal and share the output.

Regards
Diwakar

Hi Diwakar Dhyani,

Below are the informations you have asked for.

1. Share the dtb which you have used for the above test.
    File used k3-j784s4-evm.dts. Attached zip file contains both DTB and DTS files device_tree_files
    
2. Share the boot logs with the above changes.
    boot_logs.txt

3. Run the command gpioinfo in the linux kernal and share the output.
    gpioinfo_out.txt
    
Thanks,
Naveen.

Hi Diwakar Dhyani,

1. Thanks for the update, now I can able to get the USB2.0 Interface working.

2. Still the display related query has not yet been addressed. Kindly help me with that.

Thanks,
Naveen.

Hi Naveen,

I can help with the usb i will assign thread to relevant expert for display issue.

Regards
Diwakar

Hi Naveen,

I see in your dmesg logs that these errors come out:

[ 20.691697] cdns-mhdp8546 a000000.dp-bridge: get block[0] edid failed: -110
[ 20.698666] cdns-mhdp8546 a000000.dp-bridge: Failed to read EDID
[ 22.903173] cdns-mhdp8546 a000000.dp-bridge: Failed to read register
[ 90.925016] cdns-mhdp8546 a000000.dp-bridge: Failed to read register

DP0 currently has a known issue with EDID for negotiating resolution: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/drivers/gpu/drm/panel/panel-edp.c?h=ti-linux-6.1.y&id=50b06eec44cdae252de3154517333dca90394b12. To clarify, this is not an issue with the J784S4 SoC, but rather an issue with the SN65DSI86 DSI to eDP bridge.

We're targeting to fix this in our next 10.1 SDK release. If you are only in need for one display for your current development, then please use the second display port, because this port is a direct connection between SoC and display port and should not have this EDID issue.

Regards,

Takuma

Hi Takuma Fujiwara,

This seems a bit confusing for us. As per your information you have stated second display port is in direct connection with SoC and DP0 has issue because of SN65DSI86 DSI to eDP bridge.

But in this https://www.ti.com/lit/ug/spruj62/spruj62.pdf link, which was shared to us to get the information about Display Port it was mentioned:
The processor's native is DP [J9] which is Display Port 0 and The second DisplayPort [J8] is supported via DP bridge device (SN65DSI86) 

Can you confirm us with this. Because we are facing this issue reported in this https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1406229/j784s4xevm-j784s4xg01evm---gst-launch-fail link and we need to fix this. Kindly help us clarifying this.

Note: 
When we tried to boot the kit with DISPLAY_PORT0, couldn't get the display up and. Attached the dmesg logs of this. /cfs-file/__key/communityserver-discussions-components-files/791/edg_5F00_dp0.txt

Now we have changed to DISPLAY_PORT1 and we can able to up my display. Attached the image of display and dmegs logs. 
/cfs-file/__key/communityserver-discussions-components-files/791/edg_5F00_dp1.txt
/resized-image/__size/320x240/__key/communityserver-discussions-components-files/791/dp.jpg
Thanks,
Naveen.

Hi Naveen,

My apologies, you are correct. J8 is the DP bridge device.

To clarify about your setup, DISPLAY_PORT1, which has the silk screen of "Display Port2" and connector [J8] on the board, and connected via DP bridge device (SN65DSI86) is working, and J9 which has the native DP is not working?

As for the issue for gst-launch failure, it is most likely because kms is being used to render while weston is in use. Before the gst-launch command, stop weston with "systemctl stop weston", then run gst-launch.

Regards,

Takuma

Hi Takuma Fujiwara,

> To clarify, DISPLAY_PORT1, which has the silk screen of "Display Port2" and connector [J8] on the board, and connected via DP bridge device (SN65DSI86) is working, and J9 which has the native DP is not working?
   Yes, this is the case with us.

> As for the issue for gst-launch failure, it is most likely because kms is being used to render while weston is in use. Before the gst-launch command, stop weston with "systemctl stop weston", then run gst-launch.
   Okie, will try this one. However our major concern will be Display Port here. 

Thanks,
Naveen.

Hi Naveen,

I am not aware of any issues on DISPLAY_PORT1 on 9.2 SDK. 

Could you run kmsprint? It should print below:

root@j784s4-evm:~# kmsprint
Connector 0 (40) DP-1 (connected)
  Encoder 0 (39) NONE
    Crtc 0 (38) 1920x1080@60.00 148.500 1920/88/44/148/+ 1080/4/5/36/+ 60 (60.00) 0x5 0x48
      Plane 0 (31) fb-id: 67 (crtcs: 0 1) 0,0 1920x1080 -> 0,0 1920x1080 (AR12 AB12 RA12 RG16 BG16 AR15 AB15 AR24 AB24 RA24 BA24 RG24 BG24 AR30 AB30 XR12 XB12 RX12 XR15 XB15 XR24 XB24 RX24 BX24 XR30 XB30 YUYV UYVY NV12)
        FB 67 1920x1080
Connector 1 (50) eDP-1 (disconnected)
  Encoder 1 (49) NONE
root@j784s4-evm:~#

I also tried on 9.2 prebuilt adas image for J784S4, commented out the overlays in uEnv.txt, and can confirm that DP-1 comes up with weston.

Regards,

Takuma

Hi Takuma Fujiwara,

By saying DISPLAY_PORT1 do you mean DISPLAY_PORT0(The processor's native DP) which is J9 connector? If so, can you please share the prebuilt adas image which you have used for testing this.

Thanks,
Naveen.

Hi Naveen,

That is my apologies again. I keep confusing DISPLAY_PORT1 and 0 since the silk screen is Display Port1 and Display Port2. Yes, I meant to write DISPLAY_PORT1 = J9 connector = processor's native DP is in use and I am not aware of issues with this J9 connector using the native DP. I'll just refer to this connector as J9 connector from now on.

I used the create-sdcard.sh and chose the adas image option by following the instructions here: https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-j784s4/09_02_00_05/exports/docs/linux/Overview/Processor_SDK_Linux_create_SD_card.html#create-sd-card-with-default-images-using-script.

To note: I used 9.2 SDK to try to reproduce the same exact software set up. The only change I have made on top of the adas image is that I went into the uEnv.txt file and commented out the "name_overlays" line.

On your set up, I would like to see how the display is failing. As a first step, could I get the output from "kmsprint" to see if the display connection is detected? If it is detected, then it would mean display hardware itself was detected, but backlight or some other feature is not being turned on.

Regards,

Takuma

Hi Takuma Fujiwara,

After commenting out the name_overlays in our uEnv.txt file, we were able to get the display via the J9 port. Below is the output of kmsprint:
root@j784s4-evm:~# kmsprint
Connector 0 (40) DP-1 (disconnected)
Encoder 0 (39) NONE
Crtc 0 (38) 3840x2160@29.98 262.750 3840/48/32/80/+ 2160/3/5/23/- 30 (29.98) 0x9 0x40
Connector 1 (50) eDP-1 (disconnected)
Encoder 1 (49) NONE

But we will be using k3-j784s4-edgeai-apps.dtbo and with that if we try to up this display, then we are getting the below errors and couldn't up the display.
[ 9.902621] omap_i2c 2040000.i2c: controller timed out
[ 10.958618] omap_i2c 2040000.i2c: controller timed out
[ 12.014635] omap_i2c 2040000.i2c: controller timed out
[ 13.066627] omap_i2c 2040000.i2c: controller timed out

Is this a limitation when using the J9 connector? Please help clarify this.

Thanks,
Naveen

Hi Naveen,

Let me check on this. It could either be something to do with CMA, or the device tree overlay is touching the display somehow.

Regards,

Takuma

Hi Takuma Fujiwara,

Thank you for your response. We believe we can resolve this issue as soon as possible, as another critical thread (https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1406229/j784s4xevm-j784s4xg01evm---gst-launch-fail) is on hold due to this display issue.

Thanks,
Naveen.

Hi Naveen,

I see one change between SDK 8.6 and SDK 9.1 in device tree where in 9.1 (which uses kirkstone) we disable linux,cma: https://git.ti.com/cgit/edgeai/meta-edgeai/commit/recipes-kernel/linux/linux-ti-staging/j784s4-evm/0001-arm64-dts-ti-Add-DTB-overlay-for-vision-apps.patch?h=kirkstone&id=f524ee920d7389575ed287c22138cdd6611ddcb4

On the other hand, looking through source of 8.6 SDK, I see that we do not disable linux,cma:

Memory map looks to be slightly changed so we cannot do a copy and paste, but removing this status = "disabled" for linux,cma should fix the issue. 

Regards,

Takuma

Hi Takuma Fujiwara,

> but removing this status = "disabled" for linux,cma should fix the issue.
   I have made the change you have mentioned. Below is the change we have made in k3-j784s4-rtos-memory-map.dtsi file.
   

linux,cma {
	//status = "disabled";
};
linux_cma_region: linux-cma-buffers@980000000 {
	compatible = "shared-dma-pool";
	reusable;
	reg = <0x09 0x80000000 0x00 0x70000000>;
	linux,cma-default;
};

Hi Naveen,

Naveen K said:

Connector 0 (40) DP-1 (connected)

It's good to see that kmsprint reports the display as connected which means software-wise display is found.

Naveen K said:

[ 22.087968] cdns-mhdp8546 a000000.dp-bridge: get block[0] edid failed: -110

This is mainly for negotiating the EDID for display resolution. Unfortunate to see that it is failing.

Naveen K said:

Is this is the only display port through which we can stream our camera using the gstreamer command, or is it possible to use another display port as well?

If using the J784S4 EVM from TI, then both display port should be functional. The DP is a direct connection to SoC while eDP connection is through a DSI to eDP bridge, so there are some differences in the driver in-use. GStreamer should be able to output to either display.

Do you see the display fail to come up on both ports?

Regards,

Takuma

Hi Takuma Fujiwara,

Takuma Fujiwara said:

It's good to see that kmsprint reports the display as connected which means software-wise display is found.

There seems to be a bit of confusion based on our earlier respone with this one. Let me clarify that.
The kmsprint for J9 worked even before removing the status = "disabled" for linux,cma. In our earlier response (attached below), we have attached the wrong kmsprint log. Even before it showed Connector 0 (40) DP-1 (connected) and the log we gave was after removing the display cable and that's why it still shows Crtc 0 (38) 3840x2160@29.98 262.750 3840/48/32/80/+ 2160/3/5/23/- 30 (29.98) 0x9 0x40 and Connector 0 (40) DP-1 (disconnected). Apologies for that. The only change that this (status = "disabled" for linux,cma) bought was we didn't get this omap_i2c 2040000.i2c: controller timed out error.

Naveen K said:

After commenting out the name_overlays in our uEnv.txt file, we were able to get the display via the J9 port. Below is the output of kmsprint:
root@j784s4-evm:~# kmsprint
Connector 0 (40) DP-1 (disconnected)
Encoder 0 (39) NONE
Crtc 0 (38) 3840x2160@29.98 262.750 3840/48/32/80/+ 2160/3/5/23/- 30 (29.98) 0x9 0x40
Connector 1 (50) eDP-1 (disconnected)
Encoder 1 (49) NONE

Takuma Fujiwara said:

This is mainly for negotiating the EDID for display resolution. Unfortunate to see that it is failing.

Could this be the reason for the failure of our J9 display? What can we do to get this sorted out?

Takuma Fujiwara said:

If using the J784S4 EVM from TI, then both display port should be functional. The DP is a direct connection to SoC while eDP connection is through a DSI to eDP bridge, so there are some differences in the driver in-use. GStreamer should be able to output to either display.

Do you see the display fail to come up on both ports?

As reported earlier, we still can able to get the display up using the J8 connector without any software changes itself. We will be streaming at a resolution of 1920x1200. Can you confirm whether J8 will be able to display this when streamed via GStreamer? So that we can work on this J9 connector issue and as well as I can continue this https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1406229/j784s4xevm-j784s4xg01evm---gst-launch-fail thread parallely.

Kindly let us know if you need any further clarification from our end.

Thanks,
Naveen.

Hi Naveen,

Yes, the J8 connector can be used without any software changes, and GStreamer can be used to stream to the J8 connector. You may treat these two issues as separate while we debug the J9 connector.

Regards,

Takuma

Hi Takuma Fujiwara,

Thank you for confirming.
Since the continuation of that thread (https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1406229/j784s4xevm-j784s4xg01evm---gst-launch-fail) depends on the outcome of this one, I was waiting for this issue to be resolved so I could proceed with that thread accordingly. Now that you’ve confirmed, I will continue the discussion there, and we can also work on this J9 connector issue in parallel.

Thanks,
Naveen.

Hi Naveen,

Will need a bit more time to debug this, but it seems like the same procedure of using edgeai device tree overlay has worked in 8.6 SDK. I tried out the 8.6 SDK on my setup and screen comes up with the edgeai overlay. Some change between the two SDK is causing some issues - most likely something memory map related if CMA is not suspect.

Regards,

Takuma