FriendlyELEC-Forum

I think it is a hardware-related thing, you can't change to nv12 if the hardware you are connecting from does not support it.
For example, grabbing video from a second board HDMI 1920x1080(out) to HDMI (in) only supports GBR, but grabbing video from my 8K TV set i can have NV12.

By adjusting analog_gain and exposure we can get pretty nice images. see cam1 vs cam2 screenshot attached. cam1 (left) : w/o IR filter (3.3 mm F2.2) cam2 (right) : w IR filter (3.6 mm F2.0) [code]"InitTimeValue": 0.03, "InitGainValue": 8, These values correspond to exposure 1399 ...

Fixed my 120 FPS mistake, I can't have other modes (or I couldn't find a way to set 120 FPS mode as the current mode).

Camera 2 ( CSI-1 sensor with IR filter), 120 FPS, rendering frames at ~50 FPS.
that's all folks.

screenshot (jpeg, 55% quality to fit 256Kb)

Camera 1 and Camera 2:

I just received the board and i was able to test and grab some images. I rendered the frames at ~25 fps, so 3A is possibly capped at 30 fps. Maybe with libcamera one can have 120 fps, but I am not really sure if the driver can get 120 fps. I kept the original driver and added the 120 fps patch, mayb...

Nice work. How is your progress on the json file? I have nanopi-m4 with a dual camera (ov4689) working fine, maybe there is a way to convert the XML to the new json version (i am just speculating). i have seen someone trying to do this with another sensor. he had some success doing this, but sure it...

Try some other format and see if you get better FPS:
YUYV, YU12, NV21. Maybe 422P.
Please post the results.

[quote="EugenePopuro"]Thanks for the answer, I have clarified my question. I tried using the v4l2 gstreamer pipeline to capture the camera via OpenCV, but I get 17fps and an image with no white balance set (green tint). [quote]Read this thread: http://www.friendlyarm.com/Forum/viewtopic.ph...

In the latest rockchip BSP you can use standard V4L2 controls for the camera sensors. v4l2-ctl -d /dev/video0 -l User Controls exposure 0x00980911 (int) : min=4 max=1550 step=1 default=1536 value=1536 Image Source Controls vertical_blanking 0x009e0901 (int) : min=34 max=31247 step=1 default=34 value...

Just for the record, i just received a new sensor and found out the error reported here is due to a short on the last track of the FPC, luckily the sensor was not damaged. Changing the FPC was the fix.

[ 72.944191] rkisp1: MIPI mis error: 0x0000000e[/quote]

Thanks, i am able to pass the correct params with kernel 4.19.161 and have a bright image, really bright :). Just need a better denoise filter, just as the FE 4.4 has. ./rkisp_demo --device /dev/video0 --count 15 --width 2688 --height 1520 --format YU12 --gain 2 --expo 0.031 --output test_gain2_ov46...

Right, still dark and a lot of noise. Anyway, we know now the FE distro works but I was expecting to have a bit more exposure.
Can you print your command line and the output of the command? For the record. There are two MCAM400 cameras (w/IR and without), which one do you have?

[quote="ayaromenok"][quote="@lex"]I can't find any reference to this supposed fix in their kernel. Can you provide a link to that fix? I have tested with kernel 4.19.161 and could not get it to work. How did you test it and what parameters?[/quote] It's fixed in RkISP driver repo...

I can't find any reference to this supposed fix in their kernel. Can you provide a link to that fix?
I have tested with kernel 4.19.161 and could not get it to work.

How did you test it and what parameters?

[quote="ayaromenok"]All camera IQ files comes from RockChip camera_engine_rkisp repository (which was removed from public access in summer of 2020) - and it's no OV5647 IQ files. OV5648 is nearest. It's also important to use same version of IQ files with RkISP1 driver. I(acidentely) made a...

Here you find it: https://github.com/rockchip-linux/camera_engine_rkisp/blob/master/apps/rkisp_demo/rkisp_demo.cpp Changing the lens will not help. You need the 3A and set Exposure / Gain somehow. 3A is a closed source, Maybe contacting Rockchip or FE would help. Libcamera has evolved and there are ...

You can try this one, taken from FE OS image.
Care to explain how you took the jpg image?

[quote="GoblE"]Hi, I use the MCAM400 with a nanoPi M4 (image rk3399-sd-friendlydesktop-bionic-4.4-arm64-20201027). Image is very dark when there is not much light so I think there is no AEC or AGC. Do you know how I can enable it if there is ? Or do you know how I can access to registers t...

A few things to check: 1 - Did postgres install initialize the db cluster? 2 - You may be missing some dependencies? 3 - Check the logfile for any clue 4 - Do you have enough free space? 1 - I usually build and run PostgreSQL 9.x from source but I think this is valid for newer versions. Find where t...

Post the full kernel log from the working one and from the one with the issue.
Post the kernel config also (both).

[quote]3. Media size (free space) - you need at least 35-40Gb. [/quote]
This can be a problem right now for me.

Can you provide the kernel source code after all patches applied in tar.gz? Don't worry if it's for NanoPC T4.

Yes, I would like to follow your step by step instructions to build the latest LE natively on NanoPi M4 (does not matter if it is for NanoPC T4). Kernel 5.7.y. That is what i understand by your post: "Now everyone has the opportunity to build a new version of the LE at once on your device RK339...

Hi Balbes,

Sounds good, can you provide your step by step guide to build LE on-board, kernel 5.7.y? HW decoding?

BR

Ok, i think i missed that: https://github.com/friendlyarm/linux/co ... 25fb120da6

Is there an open source driver for the W500? Can you provide a link to the sources and what kernel version? I have my kernel with the S430 but not the new W500.

Short answer: a) Your modules seem fine b) Your OS Image must have the right configuration and that depends on which Image is in use. Triple check your soldering, If you think they are 100% correct you have some options: a) Try this: https://github.com/avafinger/nanopi-a64-kodi This is already confi...

CAM500A is not compatible with NanoPi A64. Look for CAM500B. You can convert CAM500A to CAM500B with some soldering skills.

[quote]I am really happy that it work because i had so much troubles running a GLES program on that device... actually even the glmark2 fbdev code compile but crash, i had to install the .deb, yagears don't compile out of the box and crash even with the .deb file... i don't know why, it seem there i...

[quote="ackstor"] use the GPU as a blitter (or more). That is exactly what i mean by 2D, draw Text and Bitmaps to a buffer and then blit it using mali, but this has no advantages. The better approach would be to draw Text and Bitmaps in OpenGLES 2.0 (with mali) to release CPU from this wor...

You have problems with mali userland. For the fbdev you need the mali blobs for fbdev and not X11. (and vice-versa) I think the FE Desktop Image is for the X11 mali only. It should work with friendlycore. Make sure mali is working on friendlycore, test their Qt sample, read: 6.12 Run Qt 5.10.0 Demo ...

90% cpu usage out of 800% , so the 3D rendering is done by mali.
/dev/fbX is shared with mali , that means you can write directly to /dev/fbX or use mali for 3D.

If you have a way to draw 2D with mali (in C), please share the code.

[quote="ackstor"]Hello, how did you compile it for the Fire 3 ? All I get is a segmentation fault / display not found whenever i compile OpenGL ES stuff on the Fire 3.[/quote] It is based on framebuffer and not X11. Adjust the code to your need: https://github.com/avafinger/mali-fbdev-stre...

As an alternative, you could try out this Image: https://github.com/avafinger/nanopi-m4-ubuntu-base-minimal#release-v18-os-image-for-emmc-only As a bonus, you get Kodi 18 RC5. After login you run kodi. Kodi will detect your 4K Display and set properly res. mode. Don't be fooled if you get the wrong ...

I THOUGHT THIS MAY BE OF INTEREST. I have published an enhanced version of the htop for monitoring system health, like Cpu Temp. Cpu Freq, Cpu Vcore in Real-time for NanoPi M4. Deb package and source code is on github: https://github.com/avafinger/htop-2.1.1_enhanced-version. Actually, this work on ...

Hi guidol, I have received some PM but could not reply to them (no rights to send PM from my user to anyone, i think) and could not PM you also in this forum. This patched kernel works really nice and also has an extended lifespan, so it is the way to go, unfortunately, I hit a wall to extend the ke...

Just a little progress, the crypto engine seems to be working, somehow i think... cryptsetup benchmark # Tests are approximate using memory only (no storage IO). PBKDF2-sha1 252061 iterations per second for 256-bit key PBKDF2-sha256 444311 iterations per second for 256-bit key PBKDF2-sha512 179550 i...

A little follow-up, I was expecting a punch on Gbps for the kernel 4.4.117 but got the usual speed on gigabit port, the good news, the new 8189ES driver really unleashes the power of RTL8189ETV, here are some benchmarks: Gbps : [code]ubuntu@nanopi-a64:~/iperf/iperf/src$ ./iperf3 -c 192.168.254.253 C...

The RTL8189ES driver has been fixed for kernel 4.4.117, it is working fine on a few tests here. I will push the source code to github after proved stable.

[attachment=0]wifi_rtl8189es.jpg[/attachment]

This might interest someone. I have been evaluating some modern kernel for the A64 and while mainline kernel 4.17 isn't ready i worked on linux 4.4.111 with bionic and xubuntu and gave it a try. This is not BSP (although based on) but rather u-boot passing a Flattened DTB to the patched kernel to gi...

The kernel and instructions you referred on the link are not for H2+.

Linux kernel source tree for FriendlyARM NanoPi (s3c2451)

There is no support for ov5640 on kernel 4.4, you should use kernel 3.4 instead of 4.4.
Kernel 3.4 has support for CAM500B.
There was a preliminary support for ov5640 on kernel 4.14 but seems to be halted or postponed. I have tried to enable ov5640 support on 4.4 without much success.

I have managed to build and run glmark2-es-fb , struggled to get g++ to build it on 1 GB memory board. Now i need a way to optimize it. Has anyone tested glmark2-es and got better results? glmark2-es results for 1280x720p, without heatsink temp is around 85 C, Cpu around 90% most of the time for one...

Maybe this can help: https://groups.google.com/forum/#!topic ... DPRFgUx0KY

I have made some tests and published some instructions on How to connect and work with a 3G USB modem on legacy and mainline kernel.

You can follow here: https://github.com/avafinger/3G_GSM_GPRS

hmm..., they are there compiled as modules: find /media/alex/rootfs/lib/modules/4.14.3-h5 -name *ppp*.ko /media/alex/rootfs/lib/modules/4.14.3-h5/kernel/drivers/net/ppp/ppp_deflate.ko /media/alex/rootfs/lib/modules/4.14.3-h5/kernel/drivers/net/ppp/pppox.ko /media/alex/rootfs/lib/modules/4.14.3-h5/ke...

Just a little reminder, if you plan to use Wifi , add a sane value to timeout in the file /etc/dhcp/dhclient.conf or you will have to wait for the 5 min timeout to connect wifi to you AP if there is no ethernet cable connected. change: 500 to 15 that seems to be reasonable or redo the wifi and netwo...

This is a 8GB ubuntu-minimal-image with kernel 4.14.3 configured as you asked for. You need to add the required packages to Dial to your 3G (wdial, pppd, etc..). user: ubuntu pasw: ubuntu Wifi connection ================ WPA_SUPPLICANT is used to connect Wifi to AP, please edit the file /etc/network...

Sure i can try, can you please tell which 3G/LTE modules are needed? I will enable USB mobile broadband and PPP support.

A nice good looking boot (13.5 secs), BT is loaded, now need a way to talk to a device.

https://gist.github.com/avafinger/9e363 ... 4e74a748d8

There are some alternatives, depending on how you build your SD CARD (uImage, zImage and how you build your u-boot) you could: a) Create your Image on a 8GB SD CARD size, boot from this SD CARD and do a 'dd' to copy the whole 8GB sd card image to eMMC (you need to have eMMC visible when booted from ...

Search found 77 matches