Hi,

 

     Just installed Armbian (5.14) on SD card and tried in my OrangePi plus.  It doesn't start to boot - it does nothing.

 

I can boot by initiating boot from the system console.  I've upgraded to 5.16 but still doesn't boot.

 

Also where do I get gpio?  I notice /boot/boot.cmd uses gpio but it doesn't exist.

 

Thanks

 

 

hello @nottledim,

 

- make sure you have a proper power supply (according to the board manufacturer)

- make sure you have a reliable SDcard

 

https://github.com/igorpecovnik/lib/blob/master/documentation/user-faq.md

I can boot by initiating boot from the system console.  I've upgraded to 5.16 but still doesn't boot.

 

Well, that's confusing. Armbian doesn't boot but you upgraded it to 5.16?

 

Anyway: You should elaborate a bit more on what you're doing, this might improve chances/quality of answers. In case you use a serial console and booting needs manual intervention then perhaps the UART adapter is stopping u-boot's autoboot behaviour (we see this from time to time and not only UART adapters are responsible for this but sometimes also USB peripherals).

 

GPIO statements in boot.cmd are unrelated to access to GPIO pins. Take a look into /etc/modules, load the approriate module and access GPIO pins from sysfs (Wiring$Something should also work but I never used this since I fail to understand why one has to use a cloned WiringPi library anyway)

Well, that's confusing. Armbian doesn't boot but you upgraded it to 5.16?

 

Sorry to confuse - it doesn't auto boot.  I have to attach a console to ttyS0 and tell it to boot.  It works after that.

 

Anyway: You should elaborate a bit more on what you're doing, this might improve chances/quality of answers. In case you use a serial console and booting needs manual intervention then perhaps the UART adapter is stopping u-boot's autoboot behaviour (we see this from time to time and not only UART adapters are responsible for this but sometimes also USB peripherals).

The only reason I used sys console was because it didn't boot and I was looking for some messages.  It stops at the boot prompt.

There's nothing special about this system - it's just an OP+ board an ethernet cable and a USB keyboard dongle.

 

The PSU can supply 2.5A if needed - it powers peripherals like HDD OK when they're attached.  I have no trouble booting other systems.

 

The SD card is new - a Samsung EVO 16G.  It looks genuine but who knows!  I'll try another if I can find one.  It is unproven in this case.

GPIO statements in boot.cmd are unrelated to access to GPIO pins. Take a look into /etc/modules, load the approriate module and access GPIO pins from sysfs (Wiring$Something should also work but I never used this since I fail to understand why one has to use a cloned WiringPi library anyway)

OK, thanks - Sounds interesting - I'll look into that. 

 

Thanks

Edited July 17, 201610 yr by zador.blood.stained
Fixed quote blocks for easier understanding

I can boot by initiating boot from the system console.  I've upgraded to 5.16 but still doesn't boot.

Please provide full u-boot output from serial console up to the point where it drops to a command prompt.

That was easier said than done.  I've not seen that before (because I've been starting

terminal emulator after applying power to OP+)

 

U-Boot SPL 2016.05-armbian (Jul 05 2016 - 17:49:33)
DRAM: 1024 MiB
Trying to boot from MMC1


U-Boot 2016.05-armbian (Jul 05 2016 - 17:49:33 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Plus
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0 (SD), SUNXI SD/MMC: 1
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB EHCI 1.00
scanning bus 0 for devices... 5 USB Device(s) found
scanning bus 1 for devices... Device NOT ready
   Request Sense returned 02 3A 00
2 USB Device(s) found
Hit any key to stop autoboot:  0
=>

 

 

I see it's trying to boot from emmc card rather than SD card.  emmc card contains a lorobis system.

I probably need to switch something back to default to SD card. 

 

How do I do that?

U-Boot SPL 2016.05-armbian (Jul 05 2016 - 17:49:33)

DRAM: 1024 MiB

Trying to boot from MMC1

This is definitely SPL from an  Armbian u-boot

 

Hit any key to stop autoboot:  0

=>

This looks like interrupted boot sequence, u-boot doesn't try to load anything and drops to a command prompt. Can you try disconnecting all USB devices before booting (and also start terminal emulator before powering on the board)?

That's interesting.  I removed everything and it didn't boot.  Then I noticed that innocent looking

keyboard dongle was still plugged in.  Once removed it booted:

 

 

U-Boot SPL 2016.05-armbian (Jul 05 2016 - 17:49:33)
DRAM: 1024 MiB
Trying to boot from MMC1


U-Boot 2016.05-armbian (Jul 05 2016 - 17:49:33 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Plus
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0 (SD), SUNXI SD/MMC: 1
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning bus 1 for devices... Device NOT ready
   Request Sense returned 02 3A 00
2 USB Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2444 bytes read in 182 ms (12.7 KiB/s)
## Executing script at 43100000
gpio: pin PL10 (gpio 298) value is 1
gpio: pin PG11 (gpio 203) value is 1
** File not found /boot/.verbose **
** File not found /boot/.next **
** Unrecognized filesystem type **
** File not found .next **
37328 bytes read in 436 ms (83 KiB/s)
3134678 bytes read in 3137 ms (975.6 KiB/s)
5011576 bytes read in 5011 ms (976.6 KiB/s)
Kernel image @ 0x48000000 [ 0x000000 - 0x4c7878 ]
## Loading init Ramdisk from Legacy Image at 42000000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    3134614 Bytes = 3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
Using machid 0x1029 from environment

Starting kernel ...

[sun8i_fixup]: From boot, get meminfo:
        Start:  0x40000000
        Size:   1024MB
ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1
ion_reserve_select: ion chipid  [0x2004620!
ion_reserve_common: ion reserve: [0x50000000, 0x60000000]!

Debian GNU/Linux 8 orangepiplus ttyS0

orangepiplus login:

 

I tried it again with he dongle in the other USB socket (usb1) and it boots OK. It also boots

OK if there is different device in usb2.

 Then I noticed that innocent looking

keyboard dongle was still plugged in.  Once removed it booted

 

So, that dongle wasn't so innocent ...

So, that dongle wasn't so innocent ...

no, so it would seem.  It works OK in usb1 socket.  I'm just wondering why. 

 

Maybe it's to do with the order the usb buses are started.  Dunno.

 

Anyway, I learned a lot from the whole exercise.