SK-AM62A-LP: edgeai-gui-app not starting

Hello Expert,

On reboot seems that:

Welcome to Arago 2023.10!

[ 4.179307] systemd[1]: Hostname set to <am62axx-evm>.
[ 4.279682] systemd-sysv-generator[109]: SysV service '/etc/init.d/edgeai-launcher.sh' lacks a native systemd unit file. ~ Automatically generating a unit file for compatibility. Please update pa
ckage to include a native systemd unit file, in order to make it safe, robust and future-proof. ! This compatibility logic is deprecated, expect removal soon. !

Regards,
Sajan

Hi Sajan,

The Edge AI GUI App should automatically start after reboot. You don't have to manually start it. One reason that this might not work is if the screen connected to the AM62A EVM does not support 1920x1080 resolution. 

You can ignore the message :

Sajan Saji said:

[ 4.179307] systemd[1]: Hostname set to <am62axx-evm>.
[ 4.279682] systemd-sysv-generator[109]: SysV service '/etc/init.d/edgeai-launcher.sh' lacks a native systemd unit file. ~ Automatically generating a unit file for compatibility. Please update pa
ckage to include a native systemd unit file, in order to make it safe, robust and future-proof. ! This compatibility logic is deprecated, expect removal soon. !

Have you changed any of the setup or in edgeai-launcher.sh or the gui-app code?

Best regards,

Qutaiba

Hi Qutaiba,

The screen I connected support 1920x1080 resolution for sure. Didn't change anything in edgeai-launcher.sh. But runned script/setup_cameras_v3link.sh.
Did https://software-dl.ti.com/processor-sdk-linux/esd/AM62AX/10_01_00/exports/edgeai-docs/devices/AM62AX/linux/getting_started.html#mini-fusion this.

Best Regards,
Sajan 

Hi Sajan,

I would like to make sure that we are on the same page. So by default the gui app works fine after boot but when you setup the mini fusion board, the gui app stops. Is this correct? In that case, this is an issue with the mini fusion board and it setup. Please check the following:

• Make sure that the correct overlays are available on the uEnv.txt file. 
• If you are using a single imx219 camera, make sure that it is connected to the correct port based on the dtbo overlay in the step above. 
• Make sure to power the mini fusion board before the AM62A board.
• What do you see when you run the setup_cameras_v3link.sh? Please share the terminal print out.
• If the the camera is not setup correctly, please, run this "media-ctl -p" and share the print out. 

Best regards,

Qutaiba

Hi Qutaiba,

Qutaiba Saleh said:

Please share the terminal print out.

After the script is executed, seems the cam 0 to cam 3 detected with a log of "isp required: yes" like those things. I will give the exact terminal print on Tuesday; I am out of office today.

Qutaiba Saleh said:

correct overlays are available on the uEnv.txt file.

name_overlays=ti/k3-am62x-sk-csi2-v3link-fusion.dtbo ti/k3-v3link-imx219-0-0.dtbo ti/k3-v3link-imx219-0-1.dtbo ti/k3-v3link-imx219-0-2.dtbo ti/k3-v3link-imx219-0-3.dtbo

Hi Sajan,

I wish you nice time off. When back in office. Looks like the mini fusion board is working correctly for you. Is this right? I would like to know when the gui-app stops. Please, share the details related to the gui-app:

• Does it start normally on boot and then it stops?
• If it starts normally, when does it stops? What did you run? Please, share the terminal printout when the gui-app stops?

Best regards,

Qutaiba

Hi Qutaiba,

Qutaiba Saleh said:

Is this right

Yes, Mini fusion works correctly.

Qutaiba Saleh said:

Does it start normally on boot and then it stops?

Not starts on boot. setup_wallpaper comes after boot-up.

Qutaiba Saleh said:

share the terminal printout when the gui-app stops?

[   15.680160] audit: type=1701 audit(23.696:16): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=1313 comm="edgeai-gui-app" exe="/usr/bin/edgeai-gui-app" sig=6 res=1

Best Regards,
Sajan

Hi Sajan,

I see that you have another question about edgeai-gui-app in here: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1476243/sk-am62a-lp-query-on-edgeai-gui-app

Did you run the command suggested in the answer to disable the auto start of the egeai-gui-apps? If so you can enable it.

You can also try running it manually (just for testing) using

root@am62axx-evm:/opt/edgeai-gst-apps# cd /etc/init.d/   
root@am62axx-evm:/etc/init.d# systemctl stop weston
Stopping 'weston.service', but its triggering units are still active:
weston.socket
root@am62axx-evm-wifi:/etc/init.d# ./edgeai-launcher.sh start
IMX219 Camera 0 detected
    device = /dev/video-imx219-cam0
    name = imx219
    format = [fmt:SRGGB8_1X8/1920x1080]
    subdev_id = /dev/v4l-imx219-subdev0
    isp_required = yes
Starting edgeai-gui-app...
-s option no longer works and will be removed soon.
Please reconfigure to use constraints or trusted servers.
constraint configured without libtls support
constraint configured without libtls support
constraint configured without libtls support
ntpd successful

Best regards,

Qutaiba

Hi  Qutaiba,

Qutaiba Saleh said:

run the command suggested in the answer to disable the auto start

No, I didn't disabled it. I tried to boot-up without mini fusion it will start edgeai-gui-app. 

Warm Regards,
Sajan

Hi Sajan,

Thank you for providing the details. So the edgeai-gui-app start fine when the mini-fusion board is not connected? However, when the mini-fusion board is connected, the edgeai-gui-app does not start at boot while the mini-fusion board and all the camera connected to it are working fine?

I am looking at your uEvn.txt overlays. There are periods (.) between the first three files. This way, the three file names will be considered as a single file name. This will cause issues. 

If the above solution did not solve the issue, would you please run this command (media-ctl -p)  when the mini fusion board is connected and share the printout? 

Best regards,

Qutaiba

Hi Qutaiba,

My actual overlay does not contain periods, above overlay is copied from documentations. 

name_overlays=ti/k3-am62x-sk-csi2-v3link-fusion.dtbo ti/k3-v3link-imx219-0-0.dtbo ti/k3-v3link-imx219-0-1.dtbo ti/k3-v3link-imx219-0-2.dtbo ti/k3-v3link-imx219-0-3.dtbo

Qutaiba Saleh said:

run this command (media-ctl -p)  when the mini fusion board is connected and share the printout? 

root@am62axx-evm:/opt/edgeai-gst-apps# media-ctl -p
Media controller API version 6.6.58

Media device information
------------------------
driver          j721e-csi2rx
model           TI-CSI2RX
serial          
bus info        platform:30102000.ticsi2rx
hw revision     0x1
driver version  6.6.58

Device topology
- entity 1: 30102000.ticsi2rx (7 pads, 7 links, 1 route)
            type V4L2 subdev subtype Unknown flags 0
            device node name /dev/v4l-subdev0
        routes:
                0/0 -> 1/0 [ACTIVE]
        pad0: Sink
                [stream:0 fmt:UYVY8_1X16/640x480 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:lim-range]
                <- "cdns_csi2rx.30101000.csi-bridge":1 [ENABLED,IMMUTABLE]
        pad1: Source
                [stream:0 fmt:UYVY8_1X16/640x480 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:lim-range]
                -> "30102000.ticsi2rx context 0":0 [ENABLED,IMMUTABLE]
        pad2: Source
                -> "30102000.ticsi2rx context 1":0 [ENABLED,IMMUTABLE]
        pad3: Source
                -> "30102000.ticsi2rx context 2":0 [ENABLED,IMMUTABLE]
        pad4: Source
                -> "30102000.ticsi2rx context 3":0 [ENABLED,IMMUTABLE]
        pad5: Source
                -> "30102000.ticsi2rx context 4":0 [ENABLED,IMMUTABLE]
        pad6: Source
                -> "30102000.ticsi2rx context 5":0 [ENABLED,IMMUTABLE]

- entity 9: cdns_csi2rx.30101000.csi-bridge (5 pads, 2 links, 1 route)
            type V4L2 subdev subtype Unknown flags 0
            device node name /dev/v4l-subdev1
        routes:
                0/0 -> 1/0 [ACTIVE]
        pad0: Sink
                [stream:0 fmt:UYVY8_1X16/640x480 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:lim-range]
                <- "ds90ub960 4-0030":4 [ENABLED,IMMUTABLE]
        pad1: Source
                [stream:0 fmt:UYVY8_1X16/640x480 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:lim-range]
                -> "30102000.ticsi2rx":0 [ENABLED,IMMUTABLE]
        pad2: Source
        pad3: Source
        pad4: Source

- entity 15: ds90ub960 4-0030 (6 pads, 5 links, 1 route)
             type V4L2 subdev subtype Unknown flags 0
             device node name /dev/v4l-subdev2
        routes:
                0/0 -> 4/0 [ACTIVE]
        pad0: Sink
                [stream:0 fmt:UYVY8_1X16/640x480 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:lim-range]
                <- "ds90ub953 4-0044":1 [ENABLED,IMMUTABLE]
        pad1: Sink
                <- "ds90ub953 4-0045":1 [ENABLED,IMMUTABLE]
        pad2: Sink
                <- "ds90ub953 4-0046":1 [ENABLED,IMMUTABLE]
        pad3: Sink
                <- "ds90ub953 4-0047":1 [ENABLED,IMMUTABLE]
        pad4: Source
                [stream:0 fmt:UYVY8_1X16/640x480 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:lim-range]
                -> "cdns_csi2rx.30101000.csi-bridge":0 [ENABLED,IMMUTABLE]
        pad5: Source

- entity 24: ds90ub953 4-0044 (2 pads, 2 links, 1 route)
             type V4L2 subdev subtype Unknown flags 0
             device node name /dev/v4l-subdev3
        routes:
                0/0 -> 1/0 [ACTIVE]
        pad0: Sink
                [stream:0 fmt:SRGGB8_1X8/1920x1080 field:none colorspace:raw xfer:none quantization:full-range]
                <- "imx219 6-0010":0 [ENABLED,IMMUTABLE]
        pad1: Source
                [stream:0 fmt:SRGGB8_1X8/1920x1080 field:none colorspace:raw xfer:none quantization:full-range]
                -> "ds90ub960 4-0030":0 [ENABLED,IMMUTABLE]

- entity 29: ds90ub953 4-0045 (2 pads, 2 links, 1 route)
             type V4L2 subdev subtype Unknown flags 0
             device node name /dev/v4l-subdev4
        routes:
                0/0 -> 1/0 [ACTIVE]
        pad0: Sink
                [stream:0 fmt:SRGGB8_1X8/1920x1080 field:none colorspace:raw xfer:none quantization:full-range]
                <- "imx219 7-0010":0 [ENABLED,IMMUTABLE]
        pad1: Source
                [stream:0 fmt:SRGGB8_1X8/1920x1080 field:none colorspace:raw xfer:none quantization:full-range]
                -> "ds90ub960 4-0030":1 [ENABLED,IMMUTABLE]

- entity 34: ds90ub953 4-0046 (2 pads, 2 links, 1 route)
             type V4L2 subdev subtype Unknown flags 0
             device node name /dev/v4l-subdev5
        routes:
                0/0 -> 1/0 [ACTIVE]
        pad0: Sink
                [stream:0 fmt:SRGGB8_1X8/1920x1080 field:none colorspace:raw xfer:none quantization:full-range]
                <- "imx219 8-0010":0 [ENABLED,IMMUTABLE]
        pad1: Source
                [stream:0 fmt:SRGGB8_1X8/1920x1080 field:none colorspace:raw xfer:none quantization:full-range]
                -> "ds90ub960 4-0030":2 [ENABLED,IMMUTABLE]

- entity 39: ds90ub953 4-0047 (2 pads, 2 links, 1 route)
             type V4L2 subdev subtype Unknown flags 0
             device node name /dev/v4l-subdev6
        routes:
                0/0 -> 1/0 [ACTIVE]
        pad0: Sink
                [stream:0 fmt:SRGGB8_1X8/1920x1080 field:none colorspace:raw xfer:none quantization:full-range]
                <- "imx219 9-0010":0 [ENABLED,IMMUTABLE]
        pad1: Source
                [stream:0 fmt:SRGGB8_1X8/1920x1080 field:none colorspace:raw xfer:none quantization:full-range]
                -> "ds90ub960 4-0030":3 [ENABLED,IMMUTABLE]

- entity 44: imx219 6-0010 (1 pad, 1 link, 0 routes)
             type V4L2 subdev subtype Sensor flags 0
             device node name /dev/v4l-subdev7
        pad0: Source
                [stream:0 fmt:SRGGB8_1X8/1920x1080 field:none colorspace:raw xfer:none quantization:full-range
                 crop.bounds:(8,8)/3280x2464
                 crop:(688,700)/1920x1080]
                -> "ds90ub953 4-0044":0 [ENABLED,IMMUTABLE]

- entity 48: imx219 7-0010 (1 pad, 1 link, 0 routes)
             type V4L2 subdev subtype Sensor flags 0
             device node name /dev/v4l-subdev8
        pad0: Source
                [stream:0 fmt:SRGGB8_1X8/1920x1080 field:none colorspace:raw xfer:none quantization:full-range
                 crop.bounds:(8,8)/3280x2464
                 crop:(688,700)/1920x1080]
                -> "ds90ub953 4-0045":0 [ENABLED,IMMUTABLE]

- entity 52: imx219 8-0010 (1 pad, 1 link, 0 routes)
             type V4L2 subdev subtype Sensor flags 0
             device node name /dev/v4l-subdev9
        pad0: Source
                [stream:0 fmt:SRGGB8_1X8/1920x1080 field:none colorspace:raw xfer:none quantization:full-range
                 crop.bounds:(8,8)/3280x2464
                 crop:(688,700)/1920x1080]
                -> "ds90ub953 4-0046":0 [ENABLED,IMMUTABLE]

- entity 56: imx219 9-0010 (1 pad, 1 link, 0 routes)
             type V4L2 subdev subtype Sensor flags 0
             device node name /dev/v4l-subdev10
        pad0: Source
                [stream:0 fmt:SRGGB8_1X8/1920x1080 field:none colorspace:raw xfer:none quantization:full-range
                 crop.bounds:(8,8)/3280x2464
                 crop:(688,700)/1920x1080]
                -> "ds90ub953 4-0047":0 [ENABLED,IMMUTABLE]

- entity 62: 30102000.ticsi2rx context 0 (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video3
        pad0: Sink
                <- "30102000.ticsi2rx":1 [ENABLED,IMMUTABLE]

- entity 68: 30102000.ticsi2rx context 1 (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video4
        pad0: Sink
                <- "30102000.ticsi2rx":2 [ENABLED,IMMUTABLE]

- entity 74: 30102000.ticsi2rx context 2 (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video5
        pad0: Sink
                <- "30102000.ticsi2rx":3 [ENABLED,IMMUTABLE]

- entity 80: 30102000.ticsi2rx context 3 (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video6
        pad0: Sink
                <- "30102000.ticsi2rx":4 [ENABLED,IMMUTABLE]

- entity 86: 30102000.ticsi2rx context 4 (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video7
        pad0: Sink
                <- "30102000.ticsi2rx":5 [ENABLED,IMMUTABLE]

- entity 92: 30102000.ticsi2rx context 5 (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video8
        pad0: Sink
                <- "30102000.ticsi2rx":6 [ENABLED,IMMUTABLE]

Best Regards,
Sajan

Hi Sajan,

Your "media-ctl -p" output doesn't look right. Did you disable /opt/edgeai-gst-apps/scripts/setup_cameras.sh?

Please run it manually if you disable it. All entities in "meida-ctl -p" output should have the same format.

Regards,

Jianzhong

Hello Jianzhong,

Jianzhong Xu said:

disable /opt/edgeai-gst-apps/scripts/setup_cameras.sh

No, I didn't disable anything. Only source script/setupcameras_v3link.sh after every boot.

Should I need to run setup_cameras.sh. Using mini fusion with 4 imx219 cameras.

Best Regards,
Sajan

Sorry, my mistake. It should be setup_cameras_v3link.sh. This script doesn't run automatically, so you need to run it every time.

More information can be found at: https://dev.ti.com/tirex/explore/node?node=A__ATmvgyzeqCfCvoHoyFGZGw__AM62A-ACADEMY__WeZ9SsL__LATEST.

Scroll to Running Multiple FPD-Link Cameras.

Hi Jianzhong,

I think, It is not the issue that associated with setup_cameras_v3link.sh. Because edgeai-gui-app not starting on bootup.

Name overlay in the above shared documentation is below

Use overlays: k3-am62x-sk-csi2-v3link-fusion.dtbo, k3-v3link-imx219-0-0.dtbo, k3-v3link-imx219-0-1.dtbo, k3-v3link-imx219-0-2.dtbo, k3-v3link-imx219-0-3.dtbo

Should I add comma (,) between the .dtbo's.

Thanks

Sajan Saji said:

Should I add comma (,) between the .dtbo's.

No. The overlay you provided earlier looks good.

name_overlays=ti/k3-am62x-sk-csi2-v3link-fusion.dtbo ti/k3-v3link-imx219-0-0.dtbo ti/k3-v3link-imx219-0-1.dtbo ti/k3-v3link-imx219-0-2.dtbo ti/k3-v3link-imx219-0-3.dtbo

Sajan Saji said:

I think, It is not the issue that associated with setup_cameras_v3link.sh. Because edgeai-gui-app not starting on bootup.

I'm confused. Were you able to start the GUI app without connecting the V3link board?

Hello Jianzhong,

Jianzhong Xu said:

Were you able to start the GUI app without connecting the V3link board?

Yes. I can But How can edgeai-gui-app starts after sourcing setup_cameras_v3link.sh.

I did sourcing it many times but still I didn't even seen the edgeai-gui-app when mini fusion is connected.
Regards,
Sajan

Hi Jianzhong,

Please help me to figure out the problem associated with this environment.

Warm Regards,
Sajan

Hello Jianzhong,

It is working now. Can you detect the issue arises here. 

When I try to find out the issue setup_cameras renaming is solved the issue.

Anyway Thanks for your help.

Warm Regards,
Sajan

Hi Sajan,

Glad that it's working for you now. I guess the problem is that when you have 4x IMX219, the setup_cameras.sh is not properly setting up the cameras and media pipe. 

Regards,

Jianzhong