Share this post

Link to post

Share on other sites

Thanks IgZero. After failing in every other direction I went, I accepted my fate, downgraded and followed your instructions. For the first time, my camera is visible to linux. Now I can finally start playing with the project I bought the damn orange for.. :-)

Share this post

Link to post

Share on other sites

Ok pinned the problem : it is the boot.cmd/boot.scr which is NOT updated with a straight upgrade from 5.20 to >=5.25.

Let's resume this :

- if you load the original boot.cmd from 5.20, gc2035/vfe_v4l4 simply work.

- if you load the updated boot.cmd from 5.25/5.26/5.27 gc2035/vfe_v4l2 stop to work (croaking about CSI not able to detect a target chip).

That's all folks!

Now should someone versed in u-boot parameters arcanes invest some time to see what's the real difference which impacts gc2035/vfe_v4l2, and eventually corrects/documents it to everybody potentially banging their head about this in the future ?

Share this post

Link to post

Share on other sites

Now should someone versed in u-boot parameters arcanes invest some time to see what's the real difference which impacts gc2035/vfe_v4l2, and eventually corrects/documents it to everybody potentially banging their head about this in the future ?

Previously in the boot script there was a command to enable CSI related regulator by setting a GPIO pin. This was removed some time ago since this is not a good way to deal with this, it has to be solved by a kernel driver modification that uses FEX configuration.

Share this post

Link to post

Share on other sites

Hi, well is it not a module problem? As it sounds like it is a boot configuration problem as graki said, but zador.blood.stainedexplained different. I was fiddeling quite a while without making it work. I recompiled the kernel with newest sources -> did not make any differences. So what is the action to take to make it work?