[Orange PI PC] - Not booting armbian.

[tbbw]

So... second sack at the sav here.
Last time i wrote i had a kingson sd card ( a low one ) but it was recomended to buy a Samsung Evo sd card instead.
So after i confirmed one of the kingston sd cards was bad i more or less whent thru the warranty getting a refund for that one ( not sure why i botherd since it was so cheap ).

Anyhow.
Got my Samsung EVO card and tryed with DD in linux and rufus wich you guys recomend for windows and still same issue with Armbian.
It boots the other distros like Debian and Ubuntu from the orange pi's webpage but no ethernet.
And when i try armbian i get the uboot text thru the ftdi but it does not find any boot device.
 

U-Boot SPL 2016.05-armbian (Jun 23 2016 - 11:35:25)
DRAM: 1024 MiB
Card did not respond to voltage select!
Could not determine boot source

resetting ...

One thing did make me wonder what's going on is something in the rufus log ( wich i attached ).
So i'm starting to think there is something wierd with the raw image not having a bootable partition or something.
Oh and i did do the "check device for bad blocks" for 4 passes first time i tryed and it took freaking ages but no errors since i wanted to rule that out first thing.
 

[tbbw]

Figured i'll link to the original topic with the kingston sd card here http://forum.armbian.com/index.php/topic/1495-solved-another-broken-sdcard-orange-pi-pc-h3-not-booting/

 

 

And fdisking in the boot flag on the partition made no diffrance.

Looking at a roll of ductape on my desk i started thinking along the lines since i can boot the images from orangepi's website... cant i boot that up and then dd the armbian's raw image directly into the built in memory and then power down, unplug sd card and then boot from that?
I'll try a usb stick first and see if that works since i did remember reading something about usb install on the armbian's website here: http://www.armbian.com/orange-pi-pc/
"NAND, SATA, eMMC and USB install script is included (nand-sata-install)"

[rodolfo]

Figured i'll link to the original topic with the kingston sd card here http://forum.armbian.com/index.php/topic/1495-solved-another-broken-sdcard-orange-pi-pc-h3-not-booting/

And fdisking in the boot flag on the partition made no diffrance.

 

oops ... sounds like you had some frantic moments. Just relax.

 

1. Your board basically works ( your tests with other images )

2. The SDcard works on other boards ( your tests )

3. Armbian for Orange Pi installed per http://www.armbian.com/documentation works ( tested by other Armbian users )

 

This leaves us with :

 

- possibly corrupted image ( downloaded image or copy to SDcard )

- power issues ( OPIs are very picky about sufficient and stable power supply - see related forum posts )

 

Do a fresh download of Armbian for your board, dd it to SDcard and proceed EXACTLY as per http://www.armbian.com/documentation

 

Best of luck and have fun.

[tbbw]

I wanted to rule out the 2amp 5v usb adaptor so i solderd a female usb connector onto a molex connector and i'm running it from my spare coarsair psu i'm getting a stable 5v from it.

As for corrupted image/download:

8c46c53ac41ad27f5541dcd48fd844a6e0d1148f423c5261e1c00323f64e9706 *./Armbian_5.14_Orangepipc_Ubuntu_xenial_3.4.112.raw

 

Could anyone check sha256 if it matches?

[tbbw]

I might aswell just try to build it from the github repo since i'm running out of ideas.

Nope same issue:
 

U-Boot SPL 2016.07-armbian (Aug 20 2016 - 10:50:46)
DRAM: 1024 MiB
Card did not respond to voltage select!
Could not determine boot source

resetting ...

[tbbw]

Since power was mentioned iwe tryed diffrent ways of powering it.
The way iwe always powerd it was thru the dc jack on the board.
I just now tryed the micro usb and it does not seem to want to power on with power thru the micro usb connector.
Not sure if i should attempt giving it 5v directly on that gpio header since i remember it bypassed alot of protection on the RasPi and probobly is simular for the OrangePi.
Anyhow... not given up yet since it feels like armbian is taunting me with this board.

[zador.blood.stained]

I wanted to rule out the 2amp 5v usb adaptor so i solderd a female usb connector onto a molex connector and i'm running it from my spare coarsair psu i'm getting a stable 5v from it.

As for corrupted image/download:

8c46c53ac41ad27f5541dcd48fd844a6e0d1148f423c5261e1c00323f64e9706 *./Armbian_5.14_Orangepipc_Ubuntu_xenial_3.4.112.raw

 

Could anyone check sha256 if it matches?

Just tested this image on Orange Pi PC. SHA256 matches your value. Image was written with Rufus.

U-Boot SPL 2016.05-armbian (Jun 23 2016 - 11:35:25)
DRAM: 1024 MiB
Trying to boot from MMC1


U-Boot 2016.05-armbian (Jun 23 2016 - 11:35:25 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi PC
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...
No controllers 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
2465 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
0 bytes read in 131 ms (0 Bytes/s)
** File not found /boot/.next **
** Unrecognized filesystem type **
** File not found .next **
36192 bytes read in 517 ms (68.4 KiB/s)
3136481 bytes read in 3392 ms (902.3 KiB/s)
5011808 bytes read in 5366 ms (911.1 KiB/s)
Kernel image @ 0x48000000 [ 0x000000 - 0x4c7960 ]
## Loading init Ramdisk from Legacy Image at 42000000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    3136417 Bytes = 3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
Using machid 0x1029 from environment

Starting kernel ...

So it's definitely a problem on your side.

[tbbw]

Hmm... you dont have the voltage select error in uboot.
I wonder if it's related somehow?

I also noticed when trying diffrent images not all of em have that voltage error message only some have.

Could it be a revision issue with my board?
Like "Orange Pi PC v1.2" vs some other version?

[zador.blood.stained]

I just now tryed the micro usb and it does not seem to want to power on with power thru the micro usb connector.

It's not designed to be powered through microUSB port

 

Not sure if i should attempt giving it 5v directly on that gpio header since i remember it bypassed alot of protection on the RasPi and probobly is simular for the OrangePi.

You can power it through GPIO pins (+5V to pin 4, GND to pin 6; pin 1 is marked with white triangle on PCB since GPIO connector orientation is different on different boards), but it is equivalent to powering through DC-IN socket. You can try this method if it gives you ability to try another power supply

 

Hmm... you dont have the voltage select error in uboot.

I wonder if it's related somehow?

I also noticed when trying diffrent images not all of em have that voltage error message only some have.

Could it be a revision issue with my board?

Like "Orange Pi PC v1.2" vs some other version?

I don't think there are other revisions available in public

 

Are there any non-Armbian images that print voltage error messages for you?

[tbbw]

No no voltage warnings on other images just armbian... well what i'm running with now is the Ubuntu_trusty_mini.img from orange pi's forum.
Issue with that one is the script.bin file in ther lil boot fat partition (even ther updated kernel+script.bin had this issue) makes the ethernet card have the fritz ( on closer inspection they dont have those two gpio pins set high ) and spams the dmesg with irq errors.
So since i compiled armbian from source i stole the script.bin file from armbian's boot folder and put it in the orangepi ubuntu_trusty_mini's fat partition ( all hail ductape ) and it boots up with working ethernet.
The big diffrance i spot right away with how they boot, armbian uses uboot and the orangepi's ubuntu trusty uses a diffrent boot loader with a vfat partition with the uImage and script.bin.

I do not get any errors from there in the bootup.

The orange pi's forum got a google drive where i checked a few other images out like ther regular debian builds and ther raspbian wich does seem to use uboot but half way in when it's going to mount the rootfs it tryes to mount mmcblk0p2 wich does not exist on those images and it halts there i was abit too lazy to install x on my other linux machine with gparted just to see what would hapen if i move the root partition and just put an empty partition in between to get the "p2" part to add up since it sounded like alot easyer solution since the setenv in was ignored for some reson and i'm abit too tierd right now to figure out where else it was getting that parition number from.

I might do an attempt in grabbing the first few mb of the raspbian ( yeah discoverd why you guys leave a few mb space between start of sd card and the actual rootfs ) or debian image from orangepi since they do contain working uboot mbr's and whacking in the actual root partition of armbian to see what hapens since ther uboot does spot the partition and does try to boot but tryes to mount the wrong partition number.

[tbbw]

HELLO! BOOT0 is starting!

boot0 version : 4.0.0

fel_flag = 0x00000000

rtc[0] value = 0x00000000

rtc[1] value = 0x00000000

rtc[2] value = 0x00000000

rtc[3] value = 0x00000000

rtc[4] value = 0x00000000

rtc[5] value = 0x00000000

rtc[6] value = 0x00000000

rtc[7] value = 0x00000000

DRAM DRIVE INFO: V0.8

DRAM Type = 3 (2:DDR2,3:DDR3,6:LPDDR2,7:LPDDR3)

DRAM CLK = 672 MHz

DRAM zq value: 003b3bfb

READ DQS LCDL = 001c1d1e

DRAM SIZE =1024 M

odt delay

dram size =1024

card boot number = 0

card no is 0

sdcard 0 line count 4

[mmc]: mmc driver ver 2014-12-10 21:20:39

[mmc]: ***Try SD card 0***

[mmc]: SD/MMC Card: 4bit, capacity: 14992MB

[mmc]: vendor: Man 001b534d Snr 0bc350f0

[mmc]: product: 00000

[mmc]: revision: 1.0

[mmc]: ***SD/MMC 0 init OK!!!***

sdcard 0 init ok

The size of uboot is 000dc000.

sum=ede66ee7

src_sum=ede66ee7

Succeed in loading uboot from sdmmc flash.

Ready to disable icache.

Jump to secend Boot.

SUNXI_NORMAL_MODE

[ 0.346]e mode

U-Boot 2011.09-rc1 (Jun 21 2015 - 19:33:17) Allwinner Technology

 

[ 0.354]version: 1.1.0

normal mode

[ 0.361]pmbus: ready

not set main pmu id

axp_probe error

[ 0.376]PMU: pll1 1200 Mhz,PLL6=600 Mhz

AXI=400 Mhz,AHB=200 Mhz, APB1=100 Mhz

sid read already

fel key new mode

run key detect

no key found

no key input

dram_para_set start

dram_para_set end

normal mode

[ 0.407]DRAM: 1 GiB

relocation Offset is: 35af9000

[box standby] read rtc = 0x0

[box_start_os] mag be start_type no use

user_gpio config

user_gpio ok

gic: normal or no secure os mode

workmode = 0

MMC: 0

[ 0.481][mmc]: mmc driver ver 2014-12-10 9:23:00

[ 0.486][mmc]: get sdc_phy_wipe fail.

[ 0.490][mmc]: get sdc0 sdc_erase fail.

[ 0.494][mmc]: get sdc_f_max fail,use default 50000000Hz

[ 0.499][mmc]: get sdc_ex_dly_used fail,use default dly

[ 0.505][mmc]: SUNXI SD/MMC: 0

[ 0.518][mmc]: *Try SD card 0*

[ 0.551][mmc]: CID 0x1b534d30 0x30303030 0x100bc350 0xf000e73d

[ 0.556][mmc]: mmc clk 50000000

[ 0.560][mmc]: SD/MMC Card: 4bit, capacity: 14992MB

[ 0.565][mmc]: boot0 capacity: 0KB,boot1 capacity: 0KB

[ 0.570][mmc]: ***SD/MMC 0 init OK!!!***

[ 0.574][mmc]: erase_grp_size:0x1WrBlk * 0x200 = 0x200 Byte

[ 0.580][mmc]: secure_feature 0x0

[ 0.583][mmc]: secure_removal_type 0x0

[ 0.587]sunxi flash init ok

script config pll_de to 864 Mhz

Not Found clk pll_video1 in script

script config pll_video to 297 Mhz

[boot]disp_init_tv

[DISP_TV] disp_init_tv enter g_tv_used

screen 0 do not support TV TYPE!

[BOOOT_DISP_TV] disp tv device_registered

unable to find regulator vcc-hdmi-18 from [pmu1_regu] or [pmu2_regu]

enable power vcc-hdmi-18, ret=-1

DRV_DISP_Init end

boot_disp.auto_hpd=1

auto hpd check has 50 times!

[disk_read_fs] no the partition

error: open disp_rsl.fex, maybe it is not exist

attched ok, mgr1<-->device1, type=2, mode=11----

ready to set mode

disp_tv_enable

[ 1.428]finally, output_type=0x2, output_mode=0xb, screen_id=0x1, disp_para=0x20b0000

fail to find part named env

Using default environment

 

In: serial

Out: serial

Err: serial

--------fastboot partitions--------

mbr not exist

base bootcmd=run setargs_mmc boot_normal

bootcmd set setargs_mmc

key 0

cant find rcvy value

cant find fstbt value

no misc partition is found

to be run cmd=run setargs_mmc boot_normal

[ 1.465][mmc]: MMC Device 2 not found

[ 1.469][mmc]: Can not find mmc dev

[ 1.473][mmc]: read first backup failed in fun sdmmc_secure_storage_read line 1849

sunxi_secstorage_read fail

get secure storage map err

the private part isn't exist

WORK_MODE_BOOT

adver not need show

sunxi_bmp_logo_display

[disk_read_fs] no the partition

error: open bootlogo.bmp, maybe it is not exist

sunxi bmp info error : unable to open logo file bootlogo.bmp

[ 1.506]Hit any key to stop autoboot: 0