OrangePi zero

[ghost]

It's possible to support the OrangePi zero (or Orange Pi One). A singleboardcomputer with ethernet, Wifi, USB for 6,99 USD (11 UDS incl. shipping).

http://www.orangepi.org/orangepizero/

https://www.aliexpress.com/item/New-Orange-Pi-Zero-H2-Quad-Core-Open-source-development-board-beyond-Raspberry-Pi/32760774493.html?spm=2114.12010108.1000013.1.QShuX2&scm=1007.13339.33317.0&pvid=24f5796c-ef4a-40f8-9b8e-eeba11e453e0&tpp=1

peter

[mictre65]

+1 on this request! Just picked up 2 OrangePi Zeros today actually. Thanks Calin for a very good software! /M

[ccrisan]

The Orange PI Zero (and Orange PI PC) support is in the works. I hope to make it available with the next release.

[mictre65]

Support of those devices would be much appreciated. Thanks again!

[ghost]

great! thx!

[ccrisan]

I have spent countless hours trying to port motionEyeOS to the Orange PI (kindly donated by a user). I have just given up and here are the reasons:

1. Building instructions point to missing repos on github. I couldn't figure out if they were renamed, moved, or just deleted.

2. Setting up instructions have no links or references to where one could download the required u-boot files. They pretend the files are somehow magically present in my home folder.

3. Both the legacy and mainline kernels have been wrapped into a single repository, making it impossible to instruct BuildRoot to procure kernel sources from the repo. I had to create my own repo for that purpose.

4. The mainline kernel has no camera module support. This is a deal breaker for motionEyeOS, forking me to go with the legacy 3.4 kernel.

5. The above all-in-one repo contains an enormous number of scripts in charge of building an entire OS for all the Orange PI boards in the world. I have looked through them and tried to apply what they do to motionEyeOS - I failed.

6. The "community" around these boards is a joke. Various efforts are scattered all around their crappy forum (that takes ages to load) and the user-contributed instructions are incomplete, most of the time yielding errors.

7. There are many Orange PI boards, extremely poorly documented, making it impossible to identify possible compatibilites between them. If I somehow manage to build motionEyeOS for my Orange PI One board, I have no idea if it worked for any other Orange PI model.

8. After many many hours spent trying to make my OS boot on an Orange PI, I have finally managed to see u-boot telling its story, followed by the Linux kernel. What I wasn't able to do was to specify the root partition (/dev/mmcblk0p2 in motionEyeOS's case). The "official" u-boot and boot scripts and fex files and whatnot appear to ignore any uEnv.txt or boot.scr or whatever I place on the boot partition.

This being said, I am giving up on the Orange PI crappy boards. Unless anyone is willing to step up and help me with the booting part, motionEyeOS will not run on these boards.

My work so far on Orange PI has been done on a separate branch.

[mictre65]

@Crisan. Thanks for the efforts on MotionEyeos. I agree the documentation and download sites are a joke. However downloading the OpZero image Ubuntu image from the Armbian site and installing MotionEye (not the OS) on it works fine so Im quite happy.

[ghost]

Yepp, I see. Useless hardware without a good documentation or a community. @Crisan. Thank you very much for your time, rearly !

[ericjanvanputten]

@mictre65 Im trying to get motioneye on a orange pi zero now as well but get stuck around this part mkdir -p /etc/motioneye

tried multiple OSes.

scratch that - i managed to get a bit further!

[ericjanvanputten]

@xblox mmm good to know, I might still give it a go as I wanted to see if this would work better/cheaper then to buy 2x RPi3's

[bortek]

Closing this issue due to interest. If still interested please post your question in the forum page.