• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map






Everything posted by dhlii

  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
  16. Wow! Device Tree Overlays working - GREAT!!! I am looking to add a push button to a GPIO on the OPI Lite. Does this mean I should be able to loosely follow the directions for doing the same thing using a button overlay for the RPI and with the appropriate OPI changes get it to work such that pushing the button is like hitting a key or a keyboard and I can "read" whether the button was pushed from the standard input stream ?
  17. Sorry, I was apparently not clear. I am not expecting that a stock Armbian SDcard will provide the facilities I am looking for. If there is a driver that exposes a pseudo Ethernet interface and link on both ends of the Orange PI H3 USB OTG connector, I can manage all the rest of the configuration to accomplish what I am after. Further I am not looking to connect an OPI to a BBB - though what I am seeking would allow that. I am looking to be able to deliver a black bock OPI Lite based product that can be plugged into a USB port on a laptop and web browsed to setup some configuration parameters. I do not want a client to have to connect to a serial port or plug in a USB Ethernet dongle to be able to configure the Unit prior to setting up Wifi and other parameters. .
  18. I have worked with a BeagleBone Black which has a very nice feature. Out of the box you can connect it to a laptop via USB and it sets up a network between the BBB and the laptop. Is there some kind of equivalent to allow the USB OTG ports of these boards to be used for a PC to Device network ? I am particularly interested in the H3's
  19. I have a xenail Buld environment now and I am getting the same problem. I did notice that during build I am prompted for a user/password to connect to github, I am just returning for each of these and it seems to continue OK, and I did not notice other errors in the build. But I end up with something that does not run.
  20. I thought trusty was supported ? If you want me to use another build host I can put together a VM for whatever you want. I would really love it if builds worked on debian, and I guess at some point I could look into that myself. Regardless, what do you want me to try to build under ?
  21. I have used multiple SD cards. Further the Same card works with 5.20 images. Thx
  22. The attached logs are one for each of the 4.9 and 3.4.113 builds - both have the same problem The attached files are NOT .txt files, they are the gziped tar files of the build logs as created by the build, but the forum software will not allow me to attach them without renaming. logs-22_10_2016-22_24_32.tgz.txt logs-31_10_2016-22_38_56.tgz.txt
  23. Do you just want the output of compile redirected ? Where are the build logs.
  24. Also fails 5.24 Jessie 4.9.0 Looks like a u-boot problem [14:22:59:581] U-Boot SPL 2016.09.01-armbian (Nov 01 2016 - 17:58:53) [14:22:59:585] DRAM: 512 MiB [14:22:59:594] Trying to boot from MMC1 [14:22:59:736] U-Boot 2016.09.01-armbian (Nov 01 2016 - 17:58:53 +0000) Allwinner Technology [14:22:59:742] CPU: Allwinner H3 (SUN8I 1680) [14:22:59:745] Model: Xunlong Orange Pi One [14:22:59:748] DRAM: 512 MiB [14:22:59:765] MMC: SUNXI SD/MMC: 0 [14:22:59:837] *** Warning - bad CRC, using default environment [14:22:59:846] In: serial [14:22:59:846] Out: serial [14:22:59:849] Err: serial [14:22:59:849] Net: phy interface0 [14:22:59:852] eth0: ethernet@1c30000 [14:22:59:856] Hit any key to stop autoboot: 0 [14:22:59:918] switch to partitions #0, OK [14:22:59:922] mmc0 is current device [14:23:00:522] Failed to mount ext2 filesystem... [14:23:00:525] ** Unrecognized filesystem type ** [14:23:00:528] starting USB... [14:23:00:533] USB0: USB EHCI 1.00 [14:23:00:537] USB1: USB OHCI 1.0 [14:23:00:542] scanning bus 0 for devices... 1 USB Device(s) found [14:23:01:677] USB device 0: unknown deviceâ⊠[14:23:01:680] BOOTP broadcast 1â⊠[14:23:01:932] BOOTP broadcast 2â⊠[14:23:02:434] BOOTP broadcast 3â⊠[14:23:02:789] DHCP client bound to address (1110 ms)â⊠[14:23:02:793] *** Warning: no boot file name; using 'CEDF14C7.img'â⊠[14:23:02:801] Using ethernet@1c30000 deviceâ⊠[14:23:02:801] TFTP from server; our IP address is; sending through gatewayâ⊠[14:23:02:810] Filename 'CEDF14C7.img'.â⊠[14:23:02:816] Load address: 0x42000000â⊠[14:23:02:816] Loading: *<0x08>T â⊠[14:23:07:840] TFTP error: 'File not found' (1)â⊠[14:23:07:848] Not retrying...â⊠[14:23:07:848] missing environment variable: pxeuuidâ⊠[14:23:07:856] missing environment variable: bootfileâ⊠[14:23:07:856] Retrieving file: pxelinux.cfg/01-02-20-26-75-9d-1câ⊠[14:23:07:864] *** ERROR: `serverip' not setâ⊠[14:23:07:864] missing environment variable: bootfileâ⊠[14:23:07:864] Retrieving file: pxelinux.cfg/CEDF14C7â⊠[14:23:07:871] *** ERROR: `serverip' not setâ⊠[14:23:07:871] missing environment variable: bootfileâ⊠[14:23:07:880] Retrieving file: pxelinux.cfg/CEDF14Câ⊠[14:23:07:880] *** ERROR: `serverip' not setâ⊠[14:23:07:880] missing environment variable: bootfileâ⊠[14:23:07:887] Retrieving file: pxelinux.cfg/CEDF14â⊠[14:23:07:887] *** ERROR: `serverip' not setâ⊠[14:23:07:895] missing environment variable: bootfileâ⊠[14:23:07:895] Retrieving file: pxelinux.cfg/CEDF1â⊠[14:23:07:895] *** ERROR: `serverip' not setâ⊠[14:23:07:906] missing environment variable: bootfileâ⊠[14:23:07:906] Retrieving file: pxelinux.cfg/CEDFâ⊠[14:23:07:906] *** ERROR: `serverip' not setâ⊠[14:23:07:906] missing environment variable: bootfileâ⊠[14:23:07:915] Retrieving file: pxelinux.cfg/CEDâ⊠[14:23:07:915] *** ERROR: `serverip' not setâ⊠[14:23:07:923] missing environment variable: bootfileâ⊠[14:23:07:923] Retrieving file: pxelinux.cfg/CEâ⊠[14:23:07:923] *** ERROR: `serverip' not setâ⊠[14:23:07:930] missing environment variable: bootfileâ⊠[14:23:07:930] Retrieving file: pxelinux.cfg/Câ⊠[14:23:07:937] *** ERROR: `serverip' not setâ⊠[14:23:07:937] missing environment variable: bootfileâ⊠[14:23:07:937] Retrieving file: pxelinux.cfg/default-arm-sunxiâ⊠[14:23:07:949] *** ERROR: `serverip' not setâ⊠[14:23:07:949] missing environment variable: bootfileâ⊠[14:23:07:949] Retrieving file: pxelinux.cfg/default-armâ⊠[14:23:07:957] *** ERROR: `serverip' not setâ⊠[14:23:07:957] missing environment variable: bootfileâ⊠[14:23:07:957] Retrieving file: pxelinux.cfg/defaultâ⊠[14:23:07:965] *** ERROR: `serverip' not setâ⊠[14:23:07:965] Config file not foundâ⊠[14:23:07:971] BOOTP broadcast 1â⊠[14:23:07:971] DHCP client bound to address (4 ms)â⊠[14:23:07:979] Using ethernet@1c30000 deviceâ⊠[14:23:07:979] TFTP from server; our IP address is; sending through gatewayâ⊠[14:23:07:988] Filename 'boot.scr.uimg'.â⊠[14:23:07:988] Load address: 0x43100000â⊠[14:23:07:995] Loading: *<0x08>â⊠[14:23:08:281] TFTP error: 'File not found' (1)â⊠[14:23:08:281] Not retrying...â⊠[14:23:08:281] BOOTP broadcast 1â⊠[14:23:08:281] DHCP client bound to address (3 ms)â⊠[14:23:08:290] Using ethernet@1c30000 deviceâ⊠[14:23:08:290] TFTP from server; our IP address is; sending through gatewayâ⊠[14:23:08:297] Filename 'boot.scr.uimg'.â⊠[14:23:08:303] Load address: 0x42000000â⊠[14:23:08:303] Loading: *<0x08>â⊠[14:23:08:333] TFTP error: 'File not found' (1)â⊠[14:23:08:333] Not retrying...â⊠[14:23:08:333] =>
  25. Any chance there is a summary somewhere of what does/does not work with 4.x.x kernels on H3's ? I do not need HDMI.