Jump to content

Christos

Members
  • Posts

    306
  • Joined

  • Last visited

Everything posted by Christos

  1. @zador.blood.stained Thanks. That was the final blow on this board. I gave up on it quite some time ago due to the fact that its expansion pinheader is not compatible to any audio add-on (really bad design from orangepi..) but just made a compilation since I happened to have the board. Should left it in the drawer, its a waste. It looks orangepi has put all of us into a really big mess with the PC2. For what is worth it though, you guys are the best, regardless of my opinion on the specific board, your work is exceptional.
  2. Is the build repository able to build PC2 images? Tried a PC2 build (Debian jessie desktop) a few hours ago (up to commit a0a3bbe) and got this problem, repeated reboots
  3. Thanks for mentioning that Thomas. BTW my board shows 1604 underneath. Yet, in their wiki pages, Friendlyarm does not mention any 1605 revision and for their latest (until today 17/Jan/2017) they have only the 1604 schematic! -> http://wiki.friendlyarm.com/wiki/index.php/NanoPi_M3 How did you came accross that info you refer to? Is it on their product or wiki pages?
  4. @tkaiser Thanks for housekeeping here. Attached are a couple of screenshots on how I have connected the fan on the board providing to it 3.3V thus having a bit lower noise level than connecting it to 5V. Friendlyarm's images were shown to connect on a pair of unpopulated pins behind the audio jack whereas those pins are just gpio related and provide no power at all. that is the error I was talking about and hope that friendlyarm will eventually figure it out and rectify it on their photos.
  5. @friendlyarm Do you intend to have a new heatsink design for A64 in such a way that does not block the A64 board's I2S pins? P.S. (if of course your nickname actually belongs to FA vendor)
  6. @friendlyarm I have to tell you that this image is mis-leading. There is no populated 2-pin pinheader right behind the spk/mic jack. And those two pins are not power.. The image you show has errors as I said before. You can try it yourself. In order for the fan to work, it has to be either connected for optimal speed/noise in the I2S pins1+2 or in the main 40-pin connector. @friendlyarm You have to corret your image as it made quite some trouble to many M3 heatsink users. P.S. I made those remarks based on the nickname and the assumption that this nickname ihas some FA direct-affiliation. If not, pls ignore the comments.
  7. @friendlyarm The problem there is that the I2S header will get covered from heatsink, you should come with a Heatsink alternative design for NanoPi A64 that uses the other two diagonal corners for grip to pcb.
  8. @zikzak For M3, you have to connect the fan power cable to the I2S connector, Black->pin1, Red->pin2 (FA's relevant M3 fan pictures are in error..) this way the fan is working at speeds controlled by temp CPU giving 3.3V and works much better.
  9. Nice to know that. Is there a quick/easy way of extracting just the rootfs from the images?
  10. As I had some funny issues with HDMI once, I changed the (brand new) cable with another (differrent cable) and it works ok since. Just sayin..
  11. Have you considered 'cloud' storage options, or quite possibly the 'unlimited bandwidth' hosting providers? -> https://alreadyhosts.com/ -> https://hostingfacts.com/
  12. Is making the image files available as releases in github a possible solution? IF that can be done then you off-load your own servers. Dont know if that is possible or permitted though.
  13. Thanks @Igor , Performed a new git clone and now its ok again with all the added gizmos I put on. Lesson learned, will not ask again that question unless I have done a new git clone and flushed any cache.
  14. Did a fresh OrangePi Plus2E image, legacy, Debian jessie, desktop, RT, but the SD boot gives this U-Boot SPL 2016.11-armbian (Jan 06 2017 - 14:49:44) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2016.11-armbian (Jan 06 2017 - 14:49:44 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus 2E I2C: ready DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment HDMI connected: Setting up a 1920x1080 hdmi console (overscan 0x0) hdmi enabled Error: no valid bmp image at 66000000 In: serial Out: vga Err: vga Net: phy interface7 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 6944 bytes read in 145 ms (45.9 KiB/s) There is no valid bmp file at the given address switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2092 bytes read in 178 ms (10.7 KiB/s) ## Executing script at 43100000 Wrong image format for "source" command SCRIPT FAILED: continuing... switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2092 bytes read in 170 ms (11.7 KiB/s) ## Executing script at 43100000 Booting from SD 144 bytes read in 123 ms (1000 Bytes/s) 3138997 bytes read in 406 ms (7.4 MiB/s) 5100840 bytes read in 519 ms (9.4 MiB/s) ** File not found /boot/.next ** ** File not found .next ** 36808 bytes read in 491 ms (72.3 KiB/s) SCRIPT FAILED: continuing... starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 USB4: USB EHCI 1.00 USB5: USB OHCI 1.0 scanning bus 0 for devices... 4 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus 4 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning bus 3 for devices... 2 USB Device(s) found scanning bus 5 for devices... 1 USB Device(s) found USB device 0: unknown device BOOTP broadcast 1 *** Unhandled DHCP Option in OFFER/ACK: 44 *** Unhandled DHCP Option in OFFER/ACK: 44 DHCP client bound to address 192.168.1.12 (154 ms) *** Warning: no boot file name; using 'C0A8010C.img' Using ethernet@1c30000 device TFTP from server 0.0.0.0; our IP address is 192.168.1.12; sending through gateway 192.168.1.1 Filename 'C0A8010C.img'. Load address: 0x42000000 Loading: * TFTP error: 'File not found (/var/tmp/C0A8010C.img)' (1) Not retrying... missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-02-20-40-62-97-69 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8010C *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8010 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A801 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A80 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0 *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-sunxi *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm *** ERROR: `serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default *** ERROR: `serverip' not set Config file not found BOOTP broadcast 1 *** Unhandled DHCP Option in OFFER/ACK: 44 *** Unhandled DHCP Option in OFFER/ACK: 44 DHCP client bound to address 192.168.1.12 (120 ms) Using ethernet@1c30000 device TFTP from server 0.0.0.0; our IP address is 192.168.1.12; sending through gateway 192.168.1.1 Filename 'boot.scr.uimg'. Load address: 0x43100000 Loading: * TFTP error: 'File not found (/var/tmp/boot.scr.uimg)' (1) Not retrying... BOOTP broadcast 1 *** Unhandled DHCP Option in OFFER/ACK: 44 *** Unhandled DHCP Option in OFFER/ACK: 44 DHCP client bound to address 192.168.1.12 (137 ms) Using ethernet@1c30000 device TFTP from server 0.0.0.0; our IP address is 192.168.1.12; sending through gateway 192.168.1.1 Filename 'boot.scr.uimg'. Load address: 0x42000000 Loading: * TFTP error: 'File not found (/var/tmp/boot.scr.uimg)' (1) Not retrying... => Is the environment working ok for others after todays commits?
  15. The new vagrant method looks like it is broken.. In order to login with ssh it asks for password and we do not know it, it does not work as vagrant/vagrant, ubuntu/vagrant, ubuntu/reverse and everything else tried. Can the vagrant armbian instructions be more specific to this? ( although it looks like a serious vagrant bug -> https://bugs.launchpad.net/cloud-images/+bug/1569237 ) /edit followed this guide to setup, executing exactly what is referenced -> https://github.com/igorpecovnik/lib/blob/master/README-Vagrant.md and managed to have a vagrant box up and running, but no means to login to it /edit2 Host system: Win7/64, VirtualBox 5.0.30, Vagrant 1.9.1 (PC used currently as 'normal' VirtualBox for the current Armbian build with Ubuntu16.04.1LTS)
  16. Didnt search for customize-image.sh at that time, only custom fex buid etc. (Google-Fu.. )
  17. Ok zador, just wondering how it could be done and did not find anything relevant after searched in the forum and docs. Thanks
  18. @Igor, Is this something that can be done? or we can have userpatches only for u-boot and kernel sources?
  19. In my recent builds got this Processing file /home/christos/armbian/lib/patch/kernel/sun8i-default/ov5640-enhanced-driver-with-vfe-drc-table-fix.patch patch unexpectedly ends in middle of line I build always with RT enabled (option 4) so don't know if this is the cause, even though I'm not using the ov5640, just mentioning that FYI if you plan for a new release.
  20. Hi, Where should I place a .patch in order to be taken into account on a next custom armbian built? This is for building legacy images. Need to have a modified nanopineo.fex and got a .patch for it, where should I place it in order to be applied on top of the armbian-provided one? P.S. Seen this -> https://docs.armbian.com/Developer-Guide_User-Configurations/ but it only mentions u-boot and kernel.
  21. @zador.blood.stained, so, if we build a new H3 image, the boot artifacts will be gone? Its the 1d38c5b patch right? Good..
  22. Congrats, Cool !! Is there any TFT available with connection like this one (SPI) and larger size eg 4.3", 5" or similar for our H3 boards?
  23. Ok thanks, then it must be my build env. here, its a 16.04 vbox, I'll regenerate it. thanks @zador.blood.stained
  24. Tried to build making a new git clone of the repository. So far tried to test by building orangepipcplus and orangepiplus2e, both stop in the screen 'Choose image type'. Options selected for both are 'Os image for installation to SD card', 'vendor provided / legacy ..) kernel, 'Debian 8 jessie', 'Image with desktop'environment'. Also, another try to build for nanopineo stopped in the same place. It seems that today's commits (29/12/2016) got something to do with this, I was able to generate images up to yesterday. @Igor, @zador.blood.stained can you please let me know if it works ok with you after today's commits?
  25. Nice new board with AllWinner A64, quad core 64bit A53, priced at 25$ -> http://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=159
×
×
  • Create New...