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?

Hi there, I'm currently working on cross compiling libva-v4l2-request to test the VPU on the Allwinner V3s. I cloned the master branch from Github and told autoreconf to cross compile, but however it keeps looking for the wrong libva and libdrm libraries. Also everything with arm-linux-gnueabi fails somehow. I hope someone can help me with that. user@workpad:~/workspace/allwinnerV3s/libva-v4l2-request$ ./autogen.sh --host=arm-linux-gnueabi --build=x86_64-linux-gnu autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal autoreconf: configure.ac: tracing autoreconf: running: libtoolize --copy libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac, libtoolize: and rerunning libtoolize and aclocal. libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am. autoreconf: running: /usr/bin/autoconf autoreconf: running: /usr/bin/autoheader autoreconf: running: automake --add-missing --copy --no-force autoreconf: Leaving directory `.' checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for arm-linux-gnueabi-strip... no checking for strip... strip configure: WARNING: using cross tools not prefixed with host triplet checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether UID '1000' is supported by ustar format... yes checking whether GID '1000' is supported by ustar format... yes checking how to create a ustar tar archive... gnutar checking whether make supports nested variables... (cached) yes checking build system type... x86_64-pc-linux-gnu checking host system type... arm-unknown-linux-gnueabi checking how to print strings... printf checking for style of include used by make... GNU checking for arm-linux-gnueabi-gcc... no checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... yes checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking dependency style of gcc... gcc3 checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... no checking for arm-linux-gnueabi-dumpbin... no checking for arm-linux-gnueabi-link... no checking for dumpbin... no checking for link... link -dump checking the name lister (nm) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking how to convert x86_64-pc-linux-gnu file names to arm-unknown-linux-gnueabi format... func_convert_file_noop checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for arm-linux-gnueabi-objdump... no checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for arm-linux-gnueabi-dlltool... no checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for arm-linux-gnueabi-ar... no checking for ar... ar checking for archiver @FILE support... @ checking for arm-linux-gnueabi-strip... strip checking for arm-linux-gnueabi-ranlib... no checking for ranlib... ranlib checking command to parse nm output from gcc object... ok checking for sysroot... no checking for a working dd... /bin/dd checking how to truncate binary pipes... /bin/dd bs=4096 count=1 checking for arm-linux-gnueabi-mt... no checking for mt... mt checking if mt is a manifest tool... no checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for arm-linux-gnueabi-gcc... gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking whether gcc understands -c and -o together... (cached) yes checking dependency style of gcc... (cached) gcc3 checking dependency style of gcc... gcc3 checking whether byte ordering is bigendian... no checking for ANSI C header files... (cached) yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking for sin in -lm... yes checking for arm-linux-gnueabi-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for DRM... yes checking for LIBVA_DEPS... yes checking for LIBVA_DRM_DEPS... yes checking for MPEG2 support... no checking for H.264 support... no checking for H.265 support... no checking for VA drivers path... /usr/lib/x86_64-linux-gnu/dri checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating src/autoconfig.h config.status: src/autoconfig.h is unchanged config.status: executing depfiles commands config.status: executing libtool commands v4l2_request configuration summary: VA-API version ................... : 1.1.0 VA-API drivers path .............. : /usr/lib/x86_64-linux-gnu/dri H.264 support .................... : no H.265 support .................... : no MPEG2 support .................... : no

Hi, I'm struggling to get the driver working on my V3s. Could you please show me your devicetree files and which command you used to capture the images? I tried fswebcam, but I only get a greenish image however I can see the shapes of things. thanks