Orin AGX fails at booting with inserted solectrix capture card

[huebnet]

So i’ve installed a solectrix base board with 2 MAXIS9296A deserializer chips, which are consuming 15W with 2 cameras in idle. The device seems to power the card, however I get those error messages while booting

Is the Orin itself getting to few power?

[kayccc]

Sorry for the late response.
Is this still an issue to support? Any result can be shared?

[JerryChang]

hello huebnet,

those were errors reported by nvgpu, which should not related to your deserializer chips.
anyways, may I confirm which Jetpack release version you’re working with, please check release tag i.e. $ cat /etc/nv_tegra_release for confirmation.

[huebnet]

Dear community, dear devs,

i’ve already found the problem and the solution for it and wanted to share the information with you.

I’ve attached my e-mail traffic with the solectrix support so everyone can understand whats the problem and what was going on.

So i stated the problem to solectrix and they answered:

We have already seen this problem.
It is due to the number of frame buffers or framesize allocated by our kernel module.
If the number of buffers * framesize exceeds a certain value, I think less than 256MB (or even only 128MB), then the graphics driver no longer loads correctly and delivers a resolution that only very few screens support.

You can control the framesize/buffers via the module options
/etc/modprobe.d/sxpf-options.conf
options sxpf framesize=8388608 buffers=8

With 2 cameras, 8 buffers should be sufficient.
You can set framesize according to the image size of your cameras.

Your workaround is of course also an option 😉.
I will add this to our FAQ.

My previous workaround stated in that response was:

I have found another addition to the topic, or rather a workaround.

To be able to run the proFrame 3.0 card on an Nvidia AGX Orin,
I have taken the following steps:

Software installed and driver installed via DKMS.
Added the driver to the blacklist in /etc/modprobe.d/blacklist-sxpf.conf with blacklist sxpf.
Load driver via cronjob @reboot modprobe sxpf.

Orin starts normally again, but the card is supplied with power and is also accessible.

I would suggest to configure the driver the correct way so the orin can start normally without blacklisting the driver and activating it via cronjob.

I hope that helps everyone which has the same or a similar problem with a GMSL2 capture card.

Best regards
Tim