Michał Fita Posted August 6 Share Posted August 6 I have a `.dts` file built on Raspberry Pi OS for Raspberry Pi 5, that has following section allowing to provide options to both userspace `dtoverlay` and as parameters in `/boot/firmware/config.txt`: __overrides__ { rotation = <&cam_node>,"rotation:0"; orientation = <&cam_node>,"orientation:0"; media-controller = <&csi>,"brcm,media-controller?"; cam0 = <&i2c_frag>, "target:0=",<&i2c_csi_dsi0>, <&csi_frag>, "target:0=",<&csi0>, <&cam_node>, "VIN-supply:0=",<&cam0_reg>; }; Then following use: sudo dtoverlay -v ovaone cam0=on Overrides proper fields in the overlay fragments on Raspberry Pi OS, but despite overrides being recognized they don't seem to apply and camera driver is starting with wrong I²C attached. The same problem with with `dtparam` in `config.txt` as it works on Raspberry Pi OS, but not on Armbian (I actually wonder how other `dtparam`s work on Armbian). I have to patch the `.dts` file prior to compilation with I²C references replaced for `fragment@100` and `fragment@101`. Our `.dts` is just a little stripped version of original for imx219 camera. Suggestions or explanations welcome. 0 Quote Link to comment Share on other sites More sharing options...
SteeMan Posted August 6 Share Posted August 6 Moved post to Raspberry Pi sub forum and added the Rpi5 tag. 0 Quote Link to comment Share on other sites More sharing options...
Michał Fita Posted August 6 Author Share Posted August 6 Correction: I figured why it doesn't work at boot. The question remains open for `dtoverlay` userspace. This tool is not versioned, hard to compare what version Armbian is using in comparison with recent Raspberry Pi OS. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.