peter12

Well maybe not false temperature because I made thumb test and I was not able to keep my finger on CPU. So temperature must be really high.

Hello, I installed ARMBIAN 5.38 stable Debian GNU/Linux 9 (stretch) 4.14.14-sunxi on H3 OpiZeroPlus2 board and temperature is 60C (just after boot, nothing is running, CPU 0.5%) Is it normal? P.S. I saw overheating problem on H2+ OPi boards, but no idea if H3 also suffers from this.

Hi there, tomorrow I should obtain my OPi Zero Plus2. I see it does not have USB port (just GPIO for USB, so I could solder USB port for it with GPIO, no problem). Then, I will need to install my own raspbian.img on eMMC (I am using read only system). Till now I installed it on many SD cards to another Opi Zero's and used it so (because of lack eMMC). But how to install it on Opi Zero Plus2? Do I need to install it on SD card first and then go with nand-sata-install? Honestly, I would like to install it (the best) with USB or some other way, because I will need to install dozen of pieces and it is pretty time consuming to install if from SD card (and secondly I don't know if read-only images will install ok). Usually my armban.img file is between 1GB. Is there any way how to upload/install it directly to emmc from standard PC? What I really need to do is to simplify whole install process at minimum steps, because I will need to install it for more pieces probably.

Hello friends, I found these cameras for Orange Pi: https://www.aliexpress.com/item/Orange-Pi-Open-source-IP-Camera-with-wide-angle-lens-Smart-Home-Control-Device-for-PC/32652476606.html https://www.aliexpress.com/item/2MP-Camera-module-for-Orange-Pi-PC-Zero-One-PC-Plus-Plus2-Plus2e-Zero-Plus-2/32833966539.html Can it work directly with Orange Pi Zero Plus2-h3? Or is there any difference with h5? Do you know how many fps with which resolution does this camera have? Thanks.

Hi there, I want to build my product on Orange Pi Zero Plus2. I want to put it to enclosure and leave just power connector accessible. But I found this scenario - if user makes mistake in his wifi settings and then he saves these "faulty wifi settings", he will not be able to recover default wifi values anymore. How would you solve this? (the best approach without any additional buttons for gpio pins or additional elements)

Yes, I did. It was long time ago but I think it was something like reset latch pulse for LED at the start was needed.

H there, I am using OPi0 TV out. I know, there are hardcoded PAL and NTSC resolutions only. But I would like to ask, if there is any tutorial how to build it up with my own lower resolution e.g. 320x240? (i know I should recompile driver for it but any help where to start is appreciated) Many thanks.

hi please, I downloaded usbtv.zip but what with it please? which commands to run? I don't know if I understand step-by-step good: firstly I should download usbtv.zip then run come command to compile? and then run these (?):

Hi guys, I don't want to open new thread so i am posting here. Please is there any desktop armbian version for Orange pi zero h2+ available?

Images are 640x480px, so not so big data, but in uncompressed format. I am analyzing usually max. 60 images/s, in my case there is no need for 300 pics per second (for now).

my use case is analyze of fast changing pictures on device connected to Opi's USB OTG port. I am not able to use LAN crosscable between them, I just can use USB OTG or Wifi connection. So that is why I need to push "latency" and be as close as "real-time" possible. Example: connected device is sending data each 3ms, if I get it after another 5ms it means, these data are currently old because meanwhile another new data has been sent - so I need to push the "old" state as much as possibly, simply to say, to get the most fresh data.

Thank you. I am trying to achieve the best speed and latency, so I thought via USB OTG will it be the best. Any idea? My idea was to use USB OTG and communicate with OPiZero directly (many MBs/s and I need real-time aka close to no latency), so I could void all network components (such as routers, etc) - I have never used this type of communication before, so I am complete newbie with this, so any help is highly appreciated (such as which communication type to choose g_ether/g_serial/other, etc).

thank you for this feedback. And what do you think about Wifi latency? Will it be the same as LAN or worse?

Hello, I am using OPi Zero with Armbian. From computer (Win or Ubuntu) or from other device with Android I am sending data to OPiZero device via LAN (many MBs/s). Now I would like to use for the same data communication via Opi's USB-OTG (because LAN has high latency). I read about g_serial and g_ether. First question - I think g_ether mode is the best for my case (because of speed). Am I right? I tried to find some basic tutorial, how to prepare Opi OTG for this. Is there any tutorial for this please? I would like to connect Opi with OTG to any Android device and my app on Android device (or Windows, or Linux) should be able to send data via OTG to Opi. (and yes, I read about a bit harder part to make it working on Win box, essential for me is Android and Linux box) Many thanks in advance for pointing me right direction.

Oh man, that's briliant! Thanks for that, I will try it as soon as I have few minutes for it.

Hi friends, I read about H3-H5-A64, but I want to ask if Orange Pi Zero with H2+ will be supported, and if yes, when approx. is release date for stable armbian 5.34 with kernel 4.13? And if I can use Orange Pi R1 mainline 4.13 for Orane Pi Zero? (simply if it will work, or if any discrepancies are expected)

Hi @Igor, I saw one month ago that major update is released on 11th or 12th november. I wanted to try it but I can't find it, I searched even in Download area but no image released around this day is inside. Can you please help me where to find it? Even mention about it at main armbian.com page disappeared. Many thanks.

Sorry, my bad. Updated information here: Version: Raspbian, September 2017 Release date: 2017-09-07 Kernel version: 4.9 Release notes: Link

@tkaiser thanks for your great remarks! I found something new again.

@Rosimildo, @Igor (I am posting my reply to this and second thread too) I just wanted to let you know my findings - I tried it with RPi 3 with Raspbian and utv007 works great with the latest release. Maybe drivers could be ported to Armbian - I don't know, this is just idea because I don't have any experience with these driver things. By the way, If somebody is able to make utv007 work in Armbian, I would like to pay amount I can afford to help this great project and other people, too.

Hi Igor, I just wanted to let you know my findings - I tried it with RPi 3 with Raspbian and utv007 works great with the latest release. Maybe drivers could be ported to Armbian - I don't know, this is just idea because I don't have any experience with these driver things. By the way, If somebody is able to make utv007 work in Armbian, I would like to pay amount I can afford to help this great project and other people, too.

Done! Enjoy here:

Hi there, this very short tutorial is a solution when you need to backup/clone/save as small *.img file as possible of your whole fully bootable system (e.g. you have 8GB card but you want to make smaller system image for 2GB card). And another reason why I created this tutorial - I need to burn the same image to many microsd cards. I am using Windows (yup, hate me know) and Debian in these steps: Put your microsd card to Windows machine and make image of card with Win32diskimager. If your card is e.g. 8GB, you get *.img file with the same size (my name backup.img). Now in linux maxine (in my case Debian virtual machine) we are going to work with backup.img file. Run these commands in terminal (if you are not root use sudo at the start of each line) modprobe loop losetup -f losetup /dev/loop0 backup.img partprobe /dev/loop0 Run gparted with this command and move slider of main partition to the left to make partition smaller (leave some space, e.g. I left 400MB free space) gparted /dev/loop0 Click on Apply once you are happy with it. We can unload loopback device now losetup -d /dev/loop0 With fdisk find out end of last block fdisk -l backup.img In my case last block is 3571711 so I run command truncate --size=$[(3571711+1)*512] backup.img Done! Size of your backup.img file should be now about 1.5GB. You can burn this new backup.img file to another (or the same) card/s now. In my case I dramatically reduced time needed for burning data to many many cards (it saves hours/days when you need to burn a lot of microsd cards). Enjoy! P.S. this can be done also with just Debian, so no need for Windows, in this case you just need to make first step with backup.img with linux command (e.g. dd). And of course you can set up a script on your newly burned card to expand system partition to the whole microsd size during first boot, if needed.

Thank you very much for great clarification Igor!

Hi Igor, just a quick question - on 12th November is scheduled next major update. Will there be solved utv007 issue? Or where could I post this issue/bug for investigation and correction? I checked help is welcomed link but I have no idea where to post bugs. Many thanks for your great effort!