petit_miner

Hi there, I'm currently struggling to get the Cedrus VPU up and running. I have downloaded the specific version from bootlin and got the kernel up and running, however the V3s isn't supported by the Sunxi SRAM driver. This driver is important to get the VPU going. I tried altering the devicetree of the V3s to match a SoC that is somehow similiar, but it clearly failed for obvious reasons. I get this error message: [ 1.035259] cedrus 1c0e000.video-codec: Failed to claim SRAM [ 1.040990] cedrus 1c0e000.video-codec: Failed to probe hardware [ 2.478247] cedrus 1c0e000.video-codec: Failed to claim SRAM [ 2.484047] cedrus 1c0e000.video-codec: Failed to probe hardware [ 2.505765] cedrus 1c0e000.video-codec: Failed to claim SRAM [ 2.511591] cedrus 1c0e000.video-codec: Failed to probe hardware [ 8.595278] cedrus 1c0e000.video-codec: Failed to claim SRAM [ 8.601112] cedrus 1c0e000.video-codec: Failed to probe hardware I tried to understand whats going on in the linux/drivers/soc/sunxi/sunxi_sram.c file to adapt this driver to the V3s, but in the end I don't know how to do that. I hope somebody can help me with that or can give me a hint.

What kind of UART LCD? These Nextion LCDs? Yeah sure they should work witout any issues. But why you don't use the 24bit parallel LCD interface? You are much more flexible with them and also are much cheaper and you get higher resolution like 800x600. You can use LDOs with a current limit of 1A for every rail. You need: 3,3V; 3V; 1,8V and 1,2V. If you don't care about losses. DC DC Step down are way more efficient, but are more complex to integrate.

Have a look at my wiki on Github: https://github.com/petit-miner/Blueberry-PI/wiki You can skip step 3 since you have already created the kernel and the required devicetree file. However you need to create the boot.scr file in order to boot, have a look at step 2.2. I hope this helps.

I think it would be helpful if you could post these error messages. Have a look at my example devicetree files on Github: https://github.com/petit-miner/Blueberry-PI/tree/master/Software/devicetree%20examples And why do you have uploaded a dtsi file of the H3 SoC? To use my devicetree files just copy them to arch/arm/boot/dts/ overwrite the sun8i-v3s.dtsi file and search for the Makefile in this folder. Search in the Makefile for sun8i-v3s and delete these to listings. Replace them with sun8i-v3s-blueberrypi.dtb \ Then start compiling the kernel.

Thanks, my PC detects the HDMI input, but I'm stuck with this: # fswebcam -S 5 -d /dev/video0 -r 1280x1024 -p YUV420P test.jpg --- Opening /dev/video0... Trying source module v4l2... /dev/video0 opened. No input was specified, using the first. [ 2323.030032] sun6i-csi 1cb4000.csi: Unsupported pixformat: 0x32315559 with mbus code: 0x2008! Error starting stream. VIDIOC_STREAMON: Broken pipe Unable to use mmap. Using read instead. Unable to use read. I'm unable to set the correct pixelformat with media-ctl, or doesn't really know how to do it. I'm using a newer kernel version, in which you have to set the pixelformat using media-ctl. You can't capture anything, because the CSI controller is set to the wrong pixelformat and doesn't get checked by your kernel version (mine does).

The green color in an YUV image indicates that the incoming data is zero. I think you don't need to initialize the ADV7611, because the kernel does that for you. As mentioned in the init script you initialize the ADV7611 for 24bit mode, but you have connected it in the 8bit mode. What happens if you just execute script_edid ?

Test if the ADV7611 gets detected via I2C: dmesg | grep ADV I'm stuck with this too. You need to configure the EDID memory of the ADV7611 with media-ctl to tell the HDMI "sender" which resolutions are available. But I don't know how to do that.

Yes. But I think you need another config file, because I didn't know that the H5 is an Arm64 processor. I can't acess my linux machine right now, to test which config file you need. Maybe another person from the forum can help?

I created a working devicetree file for your board including support for the ADV7611. Replace /arch/arm64/boot/dts/allwinner/sun50i-h5-orangepi-zero-plus2.dts with the file linked down below and then follow my instructions to build the linux kernel. sun50i-h5-orangepi-zero-plus2.dts

The patch only adds the c source code to the linux kernel. As I posted on your thread you need to rebuild the kernel and change the devicetree source files to support the CSI /DVP and the ADV7611.

I suggest you clone the newest version of the linux kernel from Github and apply sunxi_defconfig . After that select the ADV7604 and the Sunxi V3s CSI (Sun6i-csi) in the menuconfig. then open arch/arm/boot/dts/ and search for your board devicetree file and modify it to support the ADV7611. Then build the kernel and after that look for the zImage in arch/arm/boot/ and also copy your compiled devicetree file from arch/arm/boot/dts/. Why do you modprobe sun6i-csi? The csi driver is mainline so you don't need that. The Reset line isn't a required property, but the Hotplug detection (HPD) pin is. The Hotplug Detection pin is an output to switch a transistor on to connect a 1k resistor between HDMI 5V and the Hotplug Detection line coming from the HDMI cable. So the HDMI source knows that EDID data can be read via HDMI I2C. The EDID Data tells the source which resolutions are avaible. Have a look at the attached schematic, even though it is for an FPGA it should be nearly the same. You don't need HPD Notif, FPGA_SCl, FPGA_SDA and of course not the FPGA schematic. dsi-shield-sch.pdf

I'm also working on the ADV7611 and I'm stuck too. I think you need to rework the devicetree. This is my devicetree for the ADV7611: &csi1 { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&csi1_clk &csi1_16bit>; port { csi1_ep: endpoint { remote-endpoint = <&hdmi_in>; bus-width = <16>; }; }; }; &i2c1 { pinctrl-0 = <&i2c1_pins>; pinctrl-names = "default"; status = "okay"; hdmi_receiver@4c { compatible = "adi,adv7611"; reg = <0x4c>; #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; }; port@1 { reg = <1>; hdmi_in: endpoint { remote-endpoint = <&csi1_ep>; bus-width = <16>; }; }; }; }; And it seems like your devicetree was decompiled at some point. It would be way better to work with the "real" source devicetree. How recent is your kernel? It maybe lacks support for the CSI / DVP.

Hi there, I was playing around with the new sun6i-csi driver and was able to capture up to 800x600, but if I try to capture with a higher resolution it will always fail: fswebcam -S 5 -d /dev/video0 -r 1600x1200 -p YUV420P test.jpg --- Opening /dev/video0... Trying source module v4l2... /dev/video0 opened. No input was specified, using the first. [ 2313.151304] sun6i-csi 1cb4000.csi: Wrong width or height 1600x1200 (800x600 expected) Error starting stream. VIDIOC_STREAMON: Broken pipe Unable to use mmap. Using read instead. Unable to use read. I have also tried to set a higher resolution with v4l2-ctl beforehand. It doesn't make an difference. v4l2-ctl --set-fmt-video=width=1600,height=1200,pixelformat=YUV420P I'm using a OV2640 with a maximal resolution of 1600x1200. This piece of code throws out the error message (from sun6i_video.c): if (source_fmt.format.width != video->fmt.fmt.pix.width || source_fmt.format.height != video->fmt.fmt.pix.height) { dev_err(video->csi->dev, "Wrong width or height %ux%u (%ux%u expected)\n", video->fmt.fmt.pix.width, video->fmt.fmt.pix.height, source_fmt.format.width, source_fmt.format.height); return -EPIPE; } video->mbus_code = source_fmt.format.code; return 0; } Maybe someone can help me with that. thanks

I think so, but I would suggest that you try the 4 Layer version. It has more interfaces (VGA out) and also uses 3 seperate DC DC step down modules which are easy to solder. I haven't tested the HDMI IN (ADV7611) yet, but every other interface works flawlessly. However I made a mistake while exporting the gerber files from eagle, the pcb misses the hole for the strain relief of the ethernet jack. It isn't that critical since the strain relief is made of plastic and you can easily cut it. If you want to I can sell you a bare PCB.

Thanks, I will give it a try. Since this is a compiled library, where I should put the compiled files ? And do I have to create systemlinks or something similiar?