PINE64 - General Discussion on PineCube

FOSS Monitoring Applications

Tue, 06 Aug 2024 17:25:21 +0000

What is the recommended application to monitor the video from multiple PineCubes at a time? Looking for FOSS alternatives to BlueIris and Amcrest Survalance Pro

Do you sell a ready-made housing for the PineCube camera?

Sat, 26 Mar 2022 18:25:17 +0000

Hello.

Do you sell a ready-made housing for the PineCube camera?
If yes, where can you buy it?
Thanks.

Examples of surveillance video recordings via PineCube?

Sat, 26 Mar 2022 18:21:45 +0000

Hello.
Is it possible to view examples of video surveillance recordings through the PineCube camera?
Day, night (with IR illumination)?
Thanks.

What is the operating temperature of the PineCube?

Sat, 26 Mar 2022 18:13:19 +0000

Hello.
What is the operating temperature of the PineCube?
Can PineCube be used between -30 and +30 degrees Celsius?

cedar_ve driver not able to allocate memory

Fri, 19 Nov 2021 11:59:55 +0000

Hello

I have been trying to make use of the h264 encoder by obtaining the source code for the cedar_ve driver from here:

https://github.com/uboborov/sunxi-cedar-mainline

I have successfully built the driver, but when I try and load it the driver fails with the error in the kernel log:

Quote:[ 110.831285] sunxi-cedar 1c0e000.video-engine: could not assign reserved memory, ret: -22

I have checked the device tree to ensure that it is consistent with the sources in the above git repository.

I'm not sure why the driver is not able to allocate the needed memory. I have tried setting the CMA pool both from the boot parameters by adding:

Quote:setenv bootargs "${bootargs} cma=60M"

to boot.cmd and rebuilding before rebooting.

I have also tried adding this to my device tree:

Code:
    reserved-memory {

                #address-cells = <1>;

                #size-cells = <1>;

                ranges;

                /* Address must be kept in the lower 256 MiBs of DRAM for VE. */

                cma_pool: cma@44000000 {

                compatible = "shared-dma-pool";

                size = <0x6000000>;

                alloc-ranges = <0x4a000000 0x6000000>;

                reusable;

                linux,cma-default;

            };

        };

I updated the video engine entry in the deivce tree to that it referenced the cma_pool entry:

Code:
        ve: video-engine@01c0e000 {

                        compatible = "allwinner,sunxi-cedar-ve";

                        reg = <0x01c0e000 0x1000>,

                                <0x01c00000 0x10>,

                                <0x01c20000 0x800>;

                        memory-region = <&cedar_buf>;

                        syscon = <&syscon>;

                        clocks = <&ccu CLK_BUS_VE>, <&ccu CLK_VE>,

                                <&ccu CLK_DRAM_VE>;

                        clock-names = "ahb", "mod", "ram";

                        resets = <&ccu RST_BUS_VE>;

                        interrupts = ;

                        allwinner,sram = <&ve_sram 1>;

                };

But I still get the same error.

Has anyone successfully managed to get the cedar_ve driver to work on a pine cube? Is there a set of instructions that someone could point me to that will help me resolce this issue.

Andrew

setting a fixed Mac address on a PineCube

Fri, 19 Nov 2021 10:59:49 +0000

Hello

I have got a PineCube running Armbian, and is also using Uboot 2021.07-armbian.

I have found that the mac address keeps changing, and consequently the ip address keeps changing too. This is a real nuiscence.

I have looked for a soltution to this problem, and found some ideas on the One64 forum. Unforutnately the suggestions there didn't work for me on the PineCube.

I have tried adding these to /boot/boot.cmd (no both at once)

Code:
setenv bootargs "${bootargs} ethaddr=7e:50:d1:01:57:68"

setenv bootargs "${bootargs} mac_addr=7e:50:d1:01:57:68"

If I do

Quote:cat /proc/cmdline

I can see that the parameters are passed to the kernel, but are not being acted upon.

I have also tried adding these to /boot/armbianEnv.txt

Code:
mac_addr=7e:50:d1:01:57:68

ethaddr=7e:50:d1:01:57:68

Again not both at once.

Can someone please tell me what I need to do to get the mac address to remain the same on subsequent boots.

Thanks in advance

Andrew

Can PineCube stream 720p60fps?

Mon, 30 Aug 2021 15:34:57 +0000

I'm trying to make a mocap setup that relies on being able to capture 60fps video, is the pinecube capable of streaming 720p60fps? It can have some latency if needed.

Any hardware update planned?

Thu, 26 Aug 2021 06:42:54 +0000

Hello,

I'm willing to get a pinecube for a while, but the development progress seems stalled. I know that it's a side project for Pine64 and that there is the component shortage, so I don't expect to see move anytime soon. However, it seems that it's already really usable right now so I'm thinking about getting the dev kit.

It won't be a problem for me to install OS or do some settings with it, and I can live without a case. My may concern is if there is any hardware update planned? In other words, is the current version of pinecube working correctly and stable enough to be used? No major flaw?

Thanks

Unable to configure mmc2 on pinecube in 4 bit SDIO mode

Wed, 05 May 2021 22:50:08 +0000

Attempting to enable the third mmc port in 4 bit mode with little progress.  I enabled it via dts & disabled the spi0 port which shares the same pins. The system comes up, sees the peripheral.. but thats about as far as I can get.

I pulled off the RTK8189ES module and soldered my peripheral in its place and it works fine.

Some details...

dmesg log w/errors

[ 1.377523] sunxi-mmc 1c11000.mmc: initialized, max. request size: 16384 KB
[ 1.404182] mmc2: new high speed SDIO card at address 0001

[ 17.998911] sunxi-mmc 1c11000.mmc: data error, sending stop command
[ 18.005356] my_driver mmc2:0001:2: sdio readl failed -110

changes to sun8i-v3s.dtsi

mmc2: mmc@1c11000 {
compatible = "allwinner,sun7i-a20-mmc";
  reg = <0x01c11000 0x1000>;
  clocks = <&ccu CLK_BUS_MMC2>,
  <&ccu CLK_MMC2>,
  <&ccu CLK_MMC2_OUTPUT>,
  <&ccu CLK_MMC2_SAMPLE>;
  clock-names = "ahb",
"mmc",
"output",
"sample";
  resets = <&ccu RST_BUS_MMC2>;
  reset-names = "ahb";
  interrupts = ;
  pinctrl-names = "default";
  pinctrl-0 = <&mmc2_pins>;
  status = "disabled";
  #address-cells = <1>;
  #size-cells = <0>;
};

mmc2_pins: mmc2-pins {
pins = "PC0", "PC1", "PC3", "PC4",
"PC5", "PC6";
  function = "mmc2";
  drive-strength = <30>;
  bias-pull-up;
};

changes to sun8i-s3-pinecube.dts

&mmc2 {
vmmc-supply = <®_dcdc3>;
bus-width = <4>;
non-removable;
status = "okay";
};

/*
&spi0 {
status = "okay";
flash@0 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "winbond,w25q128", "jedec,spi-nor";
reg = <0>;
spi-max-frequency = <40000000>;
};
};
*/

How to get audio & HW encoding working?

Tue, 06 Apr 2021 17:36:05 +0000

Hello,

I have been trying to make hardware encoding and audio work on the PineCube under Armbian, but it does not appear that either is supported. For hardware encoding all gstreamer plugins and similar seem to rely on a 'cedarx' device which doesn't exist, and similarly no audio device exists in the tree either, even though the audio codec for the V3/V3s/S3 SoCs is supposed to be supported since kernel 4.12.

Is there a way to make these features work under Armbian, or are there alternatives that may work better?

Motion Eye OS

Mon, 22 Mar 2021 21:23:02 +0000

Has anybody run motion eye on the cube?
Also can you write an image to an SD card and boot with it like the Pinephone or a Raspberry Pi?
I have tried motioneyeos-pine64-20200606.img.xz and I was hoping to get it to connect to my network so I could avoid the serial-terminal process.
I haven't found any basic instructions to get this up and running.

OV5640 camera module reg read error

Sat, 13 Feb 2021 03:13:18 +0000

Got my PineCube today, and ran into a snag getting the camera working.

I'm running the latest Armbian Focal build (21.02.1 on kernel 5.10.12-sunxi), and whenever I try and access the camera module, whether via ffmpeg or gstreamer, I get the following errors in the syslog:

Quote:[ 2518.009350] ov5640 1-003c: ov5640_read_reg: error: reg=300a
[ 2518.014994] ov5640 1-003c: ov5640_set_power_on: failed to read chip identifier

Also happens about 13 seconds after boot.

Checked the CSI cable, and it seems to be properly seated on both ends. Any ideas?

(I think I got the cedar hardware H264 acceleration gstreamer plugin working, but this kinda derailed any actual testing.)

does POE work?

Tue, 12 Jan 2021 06:03:48 +0000

I can't get POE to work. I tried 3 different passive POE power injectors. No sign of life

Existing CAD model for PineCube?

Tue, 01 Dec 2020 00:04:09 +0000

I'd love to print a case for the PineCube so I don't break anything while I'm moving it around. Does a CAD model exist already in any capacity?

Ribbon cable routing

Mon, 26 Oct 2020 23:29:30 +0000

Got my camera, unboxed it, noticed one issue right away, the sensor(?) ribbon cable was not connected, which is easy enough to re-plug. I'm guessing that manipulations of the wifi antenna (brown piece in the middle of first pic) made it come loose. It's a rotate-to-close connector on the rear board, with the cable positioned in a way that any significant pressure would be towards the open position.

Will give it a whirl tonight to see how things work.