Jump to content

Recommended Posts

Posted

Hello, I'm trying to boot an Orange Pi Plus with Armbian 5.20, and it does not work.

 

I've already check that both OPi and my sdcard work fine, because I can flash and boot the images on orangepi.org site.

 

Besides, I checked how u-boot starts with both Armbian and "debian server" orangepi.org image (both attached)

post-1813-0-84351600-1474643699_thumb.png

post-1813-0-37180400-1474643701_thumb.png

Posted

Hi! I've managed to make Armbian boot.

 

One of orangepi.org images could access the internal eMMC, so I thought that I could flash/boot that image, and then flash Armbian directly on eMMC. And that did the trick! Now my new OPi+ runs Armbian.

 

A tricky workaround, but it worked, so what the heck  :D

post-1813-0-77224500-1474906923_thumb.png

post-1813-0-78746700-1474906925_thumb.png

Posted

One of orangepi.org images could access the internal eMMC, so I thought that I could flash/boot that image, and then flash Armbian directly on eMMC. And that did the trick! Now my new OPi+ runs Armbian.

 

Thanks for reporting this. That means also we've a(nother) problem with mainline u-boot regarding access to SD card in early boot stage on some devices :(

 

If your time permits could you please download this image and just try to boot: Armbian_5.14_Orangepipcplus_Debian_jessie_3.4.112.7z  (this one uses an older u-boot version).

 

@Igor/@Zador: what about a H3 mini image that just contains u-boot/kernel and hands out the whole eMMC device as USB Mass Storage gadet (like it's done here). This way users could flash eMMC directly from Etcher (using the virtual USB thumb drive) and it would be also the fastest way to create an eMMC clone on the Fast Ethernet equipped devices.

Posted

Just for experiment I compiled sunxi-fel for Windows and installed libUSB driver in single click with Zadig tool. So we could provide an application/set of scripts for Linux and Windows to do this.

 

For OS X too:

macbookpro-tk:sunxi-tools tk$ ./sunxi-fel ver
AWUSBFEX soc=00001680(H3) 00000001 ver=0001 44 08 scratchpad=00007e00 00000000 00000000

It didn't work, results attached.

 

That's strange since u-boot+spl 2016.05 from the old image immediately try to boot u-boot 2016.09. Don't know what to think about  :wacko:

Posted

That's strange since u-boot+spl 2016.05 from the old image immediately try to boot u-boot 2016.09. Don't know what to think about  :wacko:

U-boot 2016.05 had some issues detecting correct boot device. So looks like in this case SPL decides that it booted from eMMC and proceeds to load u-boot from eMMC instead of SD.

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines