Nvsipl_camera Fusa error

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

Hi Nvidia:

I’m using imx728 case in CameraSIPL package to capture image, but it seems the fusa error cause capture failure.
Is it possible to stop the fusa check or there’s any other way to fix the problem?

Platform: jetson Agx orin.
BSP: jetpack 7.2
SIPL ver: jetson_sipl_api_r39.2.0_aarch64.tbz2

Thank you.

fusa_error
fusa_error1488×817 113 KB

4

hello Atehsints0613,

just curious what’s your camera connections, did you also check with sensor vendor to confirm the supported L4T version?

5

Hi Jerry:
My hardware setup is imx728 sensor , max96717, max96712 and the host is jetson agxorin devkit.

The log is from nvsipl_camera application in jetson_sipl_api_r39.2.0_aarch64.tbz2 by running the command ,

sudo /usr/sbin/nvsipl_camera -c R0SIM728S3RU2120NB2 -m 0x0001 -H -v 4 -N /var/nvidia/nvcam/settings/sipl/R0SIM728S3RU2120NB2.nito -Z -012R -r 5 -t ./module.json

fusa_error.log (26.0 KB)

The setup works fine in jetpack7.2 ARGUS framework, now I want to enable it in SIPL framework.
Thank you.

6

hello Atehsints0613,

it’s -t to specify a specific JSON file. could you please give it a try by using default settings.

I also doubt this, could you please check the hardware configuration with.. $ sudo /usr/sbin/nvsipl_query

7

Hi Jerry , thank you.

Because I’m using customized board to connect serdes camera, it is not working if using the default settings.

So far, I can configure the max96712, max96717, and all the registers of the imx728 sensor. However , it failed when the system preparing to streaming.

The following is imx728 information shown by commanding “sudo /usr/sbin/nvsipl_query”.

image
image721×916 4.64 KB

Thanks your help.

8

hello Atehsints0613,

all right, please also share the JSON file for cross check.
please also note that, the name field is now case-sensitive as mentioned by SIPL Query JSON Guide.

9

Hi Jerry, Thank you.

I followed the rules from JSON Guide to create json file, and modified some item value based on my hardware.
module.txt (1.7 KB)

Thank you.

10

hello Atehsints0613,

is this sensor validate before? please also share the PHY mode, CSI port, lane configuration, and data rate from your working Argus setup so we can compare them with the SIPL configuration.
besides.. please share syslog for digging into it, such as.. $ cat /var/log/syslog > syslog.txt

11

Hi Jerry.

The followings are the configurations in device-tree settings works on ARGUS.

phy mode: CPHY
csi port: csiA, csiB (port0 and port1)
lane configuration: 4-lane
data rate: 988000000 (serdes_pix_clk_hz with 1.3G symbol/sec, 4-lane, 12bits/pixel)

syslog.txt (332.7 KB)

Thank you.

12

hello Atehsints0613,

let me have confirmation, according to the logs below.. is it true that your sensor output with 0 embedded metadata lines?

nvsipl_camera: [TID=3257] Module_id 30 Severity 5 : BuildSensorProperty: embeddedTop 0
nvsipl_camera: [TID=3257] Module_id 30 Severity 5 : BuildSensorProperty: embeddedBot 0
nvsipl_camera: [TID=3257] Module_id 30 Severity 5 : BuildSensorProperty: csiInterfaceType 2
13

Hi Jerry, thank you.

I notice that the sipl driver can disable the embedded metadata line output if I configure “embeddedTopLines” and “embeddedBottomLines” with value “0” in json file. So I disable it.

image
image1031×102 4.11 KB

Thanks your help.

14

hello Atehsints0613,

honestly, the internal code flow doesn’t support with 0 embedded metadata lines at the moment.
if that’s possible, please test with at least 1-line of embeddedTop.

15

Hi Jerry;
Thanks your help.

I’ve tried embeddedTopLines with value “1”, it return error while checking CRC.

image
image1170×426 20.8 KB

I guess because SIPL cannot receive a complete frame, there is no embedded data for SIPL to parse to. Then it returns error.

Thank you.

16

hello Atehsints0613,

is this sensor actually output embedded metadata lines?
could you please share the sensor active region for reference?