• Content Count

  • Joined

  • Last visited

About dhlii

  • Rank
    Advanced Member

Profile Information

  • Gender
  • Location
  • Interests
    Embedded software.

Recent Profile Visitors

782 profile views
  1. Thanks, I eventually found confirmation of this on the Xulong web site. I am trying to make an IoT expansion board that the OPI0 plugs into, and seek to power the OPI0 from the expansion board.
  2. Thank you. The graphic is nice but I know where the power pins are. I just wanted to make sure that if I feed +5 to the 5V header - instead of drawing +5 from the 5V header that the OPI will be happy and run from it. Obviously I need to provide enough power. Thank You again
  3. Can you power an Orange Pi Zero or Orange Pi One from the 26/40 pin header ? I am pretty sure the answer is yes as the OPI Zero expansion board has a power jack. But is there any information regarding how to do this ? Do you feed the +5v or the +3.3v Is it the same for all of the RPI compatible headers ?
  4. I beleive the correct syntax is .config is # CONFIG_STRICT_DEVMEM is not set
  5. For some time I have been successfully building OrangePIOne and OrangePiSero full dev images on a debian stretch system by adding "stretch" to the supported list on approx. line 685 in lib/ But I have to change every time there is an update. It should be trivial to change the script such that instead of just dying on an unsupported system the option to go forward anyway - with the appropriate warnings, threats and magic disclaimers.
  6. dhlii


  7. I understand that building outside of Xenial is not supported, but can we not require things like editing files in /etc to permit someone to do it anyway. I have been using debian stretch for some time. For a while I had to run xenial in an lxc container with several personal patches if I wanted to make an sdcard image. But those issues got resolved months ago and I was suddenly able to successfully build directly from Stretch without containers. Now to do that I have to play games.
  8. I am also working to get g_ether up. I have succeeded but I have some first boot issues. I need the usb ethernet working the first time the unit boots. I have modified Armbian_5.27_Orangepilite_Debian_jessie_dev_4.10.1.img as follows: I have added g_ether to /etc/modules I have create /etc/modprobe.d/g_ether.conf with the contents options g_ether host_addr=12:a5:cf:42:92:fd dev_addr=5e:bc:ca:27:92:b1 idVendor=1317 idProduct=42146 This gets me a usb0 when the system boots. But it has no IP and is otherwise not useful. I added /etc/network/interfaces.d/usb0 auto usb0 iface usb0 inet static hwaddress ether 82:bc:09:47:28:a9 address netmask network gateway but the armbian setup does not source interfaces.d I appended source /etc/network/interfaces.d/* to /etc/network/ but still no joy. I added /etc/NetworkManager/systemconnections/USB Network [ethernet] mac-address=5E:BC:CA:27:92:B1 [connection] id=USB Network uuid=fbffa806-7cd2-4234-b406-ea7e6423a45a type=ethernet timestamp=1488840639 [ipv6] method=ignore [ipv4] method=link-local Still No joy. HOWEVER If I boot the SDcard, log in via Serial get through the firstrun stuff including creating a new user and reboot the system comes up with fully working usb0 But I need it to work the first time. I need to be able to bring the system up without a serial connection.
  9. I am familiar with Qemm and VirtualBox and VMplayer and .... They each have great value for specific tasks. They are not the approriate tool for every problem and they come with significant requirements. My latop is maxed out at 16GB, and I am unlikely to change that soon as newer laptops for all they offer have sacrificed features I want or need. Real virtualization is expensive in terms of resources. If the objective is compartmentalization chroot and LXC/LXD do that quite well And possibly docker which I am less familiar with. . And they do so at near zero additional resource cost.
  10. Wise advice - that we all should follow. I would never have ten different console sessions concurrently opened in my current user session. My preference would be to build inside of an LXC/LXD container, as this does not waste resources. I use real virtual machines primarily to run windows under Linux. Running a linux virtual machine in linux incurs a system wide performance hit. Regardless, thanks for the improvements, Hopefully building will work within LXC when I try that. Previously I was able to do everything except properly create a disk image - some of the loop device functionality was not quite perfect in LXC/LXD
  11. Just for information purposes. I was able to build from, 5.27 for an OrangePiLite complete image, debian Jesse, console server On Debian GNU/Linux 9 \n \l Linux dv7-dhlii 4.9.0-11-exton #12 SMP Sat Dec 17 10:10:47 CET 2016 x86_64 GNU/Linux This is the first time I have been able to successfully build Armbian on my base machine - rather than in a Virtual machine, or container. I am generally able to build whatever Armbian I want in an Ubuntu 16.04 Virtual Machine - though I dislike running linux virtual machines under Linux I have generally been about to build Armbian in and Ubuntu 16.04 LXC Container so long as I do not try to create a disk image - that was typically failing under Armbian 5.24 I have not yet tried 5.27. I am happy that for the moment I seem to be able to build Armbian on my base Debian Stretch install Thank You
  12. Then I guess I get to look at that, cause I have zero interest in the legacy kernel.
  13. I must have missed that. I am running Armbian 5.27/Linux 4.10 If that sets the MAC randomly ONCE that will do what I need. Thank you.
  14. Looking for any means of finding a unique and permanent MAC address for opilites. Is there some kind of serial number or other unique number of any kind in an H3 SOC or in something on an OPI Lite board that could be used to derive a MAC ? As things currently are I either have to manually setup the mac for each board I build - in a conf file in /etc/modprobe.d or live with the fact that the board comes up with a new mac/ip with every boot.
  15. Wow, that was fast. Thanks for the recomendations. My linux experience is inconsistent - I have a network driver in the source, but I spent a day or two trying to get one of the uarts working in the opilite device tree and failed. Most of my kernel work either is pre-device trees or on drivers that do not have anything to do with device trees. So I am expecting to have both fun and difficulties as I try to get a handle on this. If something breaks with 4.11 - well such is life. I will probably mutter a few curse words to myself, and deal with it. My work is extremely eclectic so I am jumping between opi's and linux and pic32's and arduino's and TI 1310's and STM32's and ... depending on the day and the project. The result is broad knowledge with occasional pockets of deep knowledge, but often significant ignorance about somethings that many here are proficient with