I've been using the RV1106 core board so far and I'm very pleased by their performance. The buildroot SDK is well done. And I managed to integrate rk media libs with libav for audio-video. Mainly because rv1103/06 do not work with ffmpeg/ gstreamer out of the box.
From what I know about this particular SoC, the RV1126 is a lot like it's bigger brothers - it has it's own gstreamer plugin and the camera can basically be driven by it.
Can you guys confirm the camera works under debian?
Luckfox AURA CSI clarification
Hello, we have provided the Luckfox AURA Debian 13 image, which can be used to drive the camera normally in Debian 13.
Thank you! I got the image, but my board is still in transit so I couldn't test this yet!
Looking forward to the Core1126!
Looking forward to the Core1126!
I apologize for bothering you again, but I'm a little bit confused.
Looking at the Pico Zero, which works with the imx415, i can see the i2c lines are pulled up to 1v8.
On the Aura, they're pulled up to 3v3. On one of them. On the other connector, no pullups that I can see.
Also, CSI1_IO0/1 go... where?! What purpose do they serve? Is the camera mclk generated on-board? Is the nreset line unused?
Going by the chip's datasheet, GPIO4_A1 would be the CAM_CLK0_OUT. But it goes to MIPI_DPHY_CSI1_RX*. GPIO4_B0 is CAM_CLK1_OUT, wired to... MIPI_DPHY_CSI0_RX*?!
But what about voltage levels?! Which go where?!
I really hope this schematic is temporary, and you'll continue with the great work you've done so far. The great docs and detailed schematics are the reason why I have more luckfox board in my drawers than any other vendor's. As it stands, though, the provided schematic for the Aura is severely gutted and next to useless.
I design my own cameras and I kinda need this info to proceed. I am 100% open to signing NDAs if needed, no problem.
Looking at the Pico Zero, which works with the imx415, i can see the i2c lines are pulled up to 1v8.
On the Aura, they're pulled up to 3v3. On one of them. On the other connector, no pullups that I can see.
Also, CSI1_IO0/1 go... where?! What purpose do they serve? Is the camera mclk generated on-board? Is the nreset line unused?
Going by the chip's datasheet, GPIO4_A1 would be the CAM_CLK0_OUT. But it goes to MIPI_DPHY_CSI1_RX*. GPIO4_B0 is CAM_CLK1_OUT, wired to... MIPI_DPHY_CSI0_RX*?!
But what about voltage levels?! Which go where?!
I really hope this schematic is temporary, and you'll continue with the great work you've done so far. The great docs and detailed schematics are the reason why I have more luckfox board in my drawers than any other vendor's. As it stands, though, the provided schematic for the Aura is severely gutted and next to useless.
I design my own cameras and I kinda need this info to proceed. I am 100% open to signing NDAs if needed, no problem.
Hello, at present, the core part of the schematic diagram is restricted by the protocol and cannot be made public. The current schematic diagram shows all the peripheral circuit designs, which is equivalent to hiding the possible future launched Core1126B. We have not retained any other design details.
CSI1_IO0 is connected to GPIO4A1 through a 22R protection resistor, and CSI1_IO1 is connected to GPIO4_B1 through a 22R protection resistor. Both GPIO4_B1 and GPIO4A1 are at a 3.3V voltage standard. MIPI_DPHY_CSI1_RX* is directly connected to RV1126B.
CSI1_IO0 is connected to GPIO4A1 through a 22R protection resistor, and CSI1_IO1 is connected to GPIO4_B1 through a 22R protection resistor. Both GPIO4_B1 and GPIO4A1 are at a 3.3V voltage standard. MIPI_DPHY_CSI1_RX* is directly connected to RV1126B.
Hello again.
My Aura just arrived and I have to say, I'm a little surprised at how bad it went so far. Did any of you guys test the images provided?
The buildroot comes with ffmpeg baked in, but you didn't bother with including support for *_rkmpp, which is the hw encoder.
The debian build comes with gstreamer. I can't see any support for mpph265enc, nor for mpph264enc.
Without hardware encoding up and running, this board serves absolutely no purpose.
Surely I must be missing something.
Do you have any pipeline to test the camera? Or at least the encoder?
My Aura just arrived and I have to say, I'm a little surprised at how bad it went so far. Did any of you guys test the images provided?
The buildroot comes with ffmpeg baked in, but you didn't bother with including support for *_rkmpp, which is the hw encoder.
The debian build comes with gstreamer. I can't see any support for mpph265enc, nor for mpph264enc.
Code: Select all
aura@aura:~$ gst-launch-1.0 videotestsrc ! video/x-raw,width=1920,height=1080,framerate=30/1 ! videoconvert ! mpph265enc ! h265parse ! matroskamux streamable=true ! tcpserversink host=0.0.0.0 port=5000
(gst-plugin-scanner:2130): GStreamer-WARNING **: 01:32:40.349: Failed to load plugin '/usr/lib/aarch64-linux-gnu/gstreamer-1.0/libgsttheora.so': /lib/aarch64-linux-gnu/libfontconfig.so.1: undefined symbol: FT_Set_Var_Design_Coordinates
(gst-plugin-scanner:2130): GStreamer-WARNING **: 01:32:40.373: Failed to load plugin '/usr/lib/aarch64-linux-gnu/gstreamer-1.0/libgstpango.so': /lib/aarch64-linux-gnu/libfontconfig.so.1: undefined symbol: FT_Set_Var_Design_Coordinates
WARNING: erroneous pipeline: no element "mpph265enc"
aura@aura:~$
Surely I must be missing something.
Do you have any pipeline to test the camera? Or at least the encoder?
Just like RV1106, we are using IPC-SDK. By default, the rockit library is used for hardware encoding. Rockit adds an additional layer of encapsulation on top of the rkmpp library. The default rkipc program that starts up uses this library. At startup, you can obtain the encoded video data through rtsp://<ip address>/live/0.
Rockchip has two RV1126B SDK branches on the official website. On the LINUX-SDK, the gstreamer with the rkmpp plugin is used by default. However, we only have the authorization for IPC-SDK, so we are currently only maintaining the IPC-SDK branch. If you need to use the gstreamer with the rkmpp plugin, you need to manually install it. The installation method is as follows:
1. Obtain the SDK and upload gst-plugins-base1.0, gstreamer, gst-rkmpp, mpp from the sysdrv/tools/board/debian/packages/arm64/ directory to the board.
2. Run it on Luckfox Aura.
3. Test code (The first run requires a moment of waiting)
Currently, we only plan to provide technical support for the use of the rokit library. After obtaining more LINUX-SDK materials, we will consider whether to achieve compatibility between rkmpp and rokit.
Rockchip has two RV1126B SDK branches on the official website. On the LINUX-SDK, the gstreamer with the rkmpp plugin is used by default. However, we only have the authorization for IPC-SDK, so we are currently only maintaining the IPC-SDK branch. If you need to use the gstreamer with the rkmpp plugin, you need to manually install it. The installation method is as follows:
1. Obtain the SDK and upload gst-plugins-base1.0, gstreamer, gst-rkmpp, mpp from the sysdrv/tools/board/debian/packages/arm64/ directory to the board.
2. Run it on Luckfox Aura.
Code: Select all
sudo apt update
sudo apt-get install -fy --allow-downgrades ./mpp/*
sudo apt-get install -fy --allow-downgrades ./gstreamer/*
sudo apt-get install -fy --allow-downgrades ./gst-plugins-base1.0/* sudo apt-get install -fy --allow-downgrades ./gst-rkmpp/*
sudo apt install gstreamer1.0-plugins-bad Code: Select all
gst-launch-1.0 videotestsrc num-buffers=600 ! video/x-raw,format=NV12,width=640,height=320,framerate=60/1 ! mpph264enc ! h264parse ! qtmux ! filesink location=h264.mp4
Currently, we only plan to provide technical support for the use of the rokit library. After obtaining more LINUX-SDK materials, we will consider whether to achieve compatibility between rkmpp and rokit.