[New Orange Pi Prime fried? Unable to boot.]

Thanks guidol. The previous output was with the producer's instructions and their original Pi Prime image.

I've tried it with armbian (the image you linked to) and two different SD cards. The other one is a Sandisk Ultra 32GB (class 10). Both cards give the same output (with the armbian image):

 

U-Boot SPL 2018.11-armbian (Feb 08 2019 - 11:30:47 +0100)
DRAM: 2048 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.0(debug):30490b1
NOTICE:  BL31: Built : 19:11:09, Feb  6 2019
NOTICE:  BL31: Detected Allwinner H5 SoC (1718)
NOTICE:  BL31: No DTB found.
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
NOTICE:  BL31: PMIC: Defaulting to PortL GPIO according to H5 reference design.
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9

 

While this looks promising (to me), I'm not getting output on HDMI or LAN. I don't know if I can log in using the TTL connection, but pressing enter yielded no results.

[New Orange Pi Prime fried? Unable to boot.]

On 1/26/2019 at 3:33 PM, martinayotte said:

I think that will give you real answers when you will be able to see boot log ...

 

Finally got the converter. Here is the result:

HELLO! BOOT0 is starting!

boot0 commit : 82a2e49cc2a78c99a14cb67b3cb4284805382f0c


boot0 version : 4.0

set pll start

set pll end

rtc[0] value = 0x00000000

rtc[1] value = 0x00000000

rtc[2] value = 0x00000000

rtc[3] value = 0x00000000

rtc[4] value = 0x00000000

rtc[5] value = 0x00000000

DRAM BOOT DRIVE INFO: V0.6

the chip id is 0x00000001

the chip id is 0x00000001

the chip id is 0x00000001

the chip id is 0x00000001

the chip id is 0x00000001

axp not exist

DRAM CLK =624 MHZ

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

DRAM zq value: 0x003b3bf9

DRAM SIZE =2048 M

DRAM simple test OK.

dram size =2048

card no is 0

sdcard 0 line count 4

[mmc]: mmc driver ver 2016-03-15 20:40

[mmc]: sdc0 spd mode error, 2

[BUDDY] CARD_TYPE 0

[mmc]: Wrong media type 0x00000000

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

[mmc]: HSSDR52/SDR25 4 bit

[mmc]: 50000000 Hz

[mmc]: 30436 MB

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

[MMC] BLCOK ARG:cmd.cmdidx 18

[MMC] BLCOK ARG:cmd.resp_type 21

[MMC] BLCOK ARG:cmd.flags 0

[MMC] BLCOK ARG:data.block 64

[MMC] BLCOK ARG:data.blocksize 512

[MMC] BLCOK ARG:data.flags 1

[MMC] BLCOK ARG:cmd.cmdarg 32800

[BUDDY2] nectblck net

[MMC2] BLCOK ARG:cmd.cmdidx 12

[MMC2] BLCOK ARG:cmd.resp_type 29

[MMC2] BLCOK ARG:cmd.flags 0

[MMC2] BLCOK ARG:data.block 64

[MMC2] BLCOK ARG:data.blocksize 512

[MMC2] BLCOK ARG:data.flags 1

[MMC2] BLCOK ARG:cmd.cmdarg 0

[MMC] BLCOK ARG:cmd.cmdidx 18

[MMC] BLCOK ARG:cmd.resp_type 21

[MMC] BLCOK ARG:cmd.flags 0

[MMC] BLCOK ARG:data.block 2176

[MMC] BLCOK ARG:data.blocksize 512

[MMC] BLCOK ARG:data.flags 1

[MMC] BLCOK ARG:cmd.cmdarg 32864

[BUDDY2] nectblck net

[MMC2] BLCOK ARG:cmd.cmdidx 12

[MMC2] BLCOK ARG:cmd.resp_type 29

[MMC2] BLCOK ARG:cmd.flags 0

[MMC2] BLCOK ARG:data.block 2176

[MMC2] BLCOK ARG:data.blocksize 512

[MMC2] BLCOK ARG:data.flags 1

[MMC2] BLCOK ARG:cmd.cmdarg 0

sum=9286958d

src_sum=e28ddf42

Fail in checking uboot.

[MMC] BLCOK ARG:cmd.cmdidx 18

[MMC] BLCOK ARG:cmd.resp_type 21

[MMC] BLCOK ARG:cmd.flags 0

[MMC] BLCOK ARG:data.block 64

[MMC] BLCOK ARG:data.blocksize 512

[MMC] BLCOK ARG:data.flags 1

[MMC] BLCOK ARG:cmd.cmdarg 24576

[BUDDY2] nectblck net

[MMC2] BLCOK ARG:cmd.cmdidx 12

[MMC2] BLCOK ARG:cmd.resp_type 29

[MMC2] BLCOK ARG:cmd.flags 0

[MMC2] BLCOK ARG:data.block 64

[MMC2] BLCOK ARG:data.blocksize 512

[MMC2] BLCOK ARG:data.flags 1

[MMC2] BLCOK ARG:cmd.cmdarg 0

PANIC : sunxi_flash_init() error --2--,toc1 magic error

PANIC : sunxi_flash_init() error --0--

Ready to disable icache.

 

Duckduckgoing didn't fetch me anything useful fo "Fail in checking uboot" nor "toc1 magic error". It looks like it's seeing the SD card properly, but then hits kernel panic. I'm guessing toc1 has something to do with the CPU.

 

[New Orange Pi Prime fried? Unable to boot.]

Thanks for the blazingly fast reply Igor. 

I've tried booting after the board cooled down; I left it alone for an entire night, but to no avail.

Perhaps it's a good idea to add a warning that a heatsink is required on the hardware page. I'll have a look around if I can do that myself.

 

[New Orange Pi Prime fried? Unable to boot.]

Hi,

 

My Orange Pi Prime stopped working within an hour of use.

 

Setup:

Orange Pi Prime v1.0 (201811)
Official PSU, rated 5V 3A
Official plastic case (without heatsinks)

Display attached using HDMI

Network attached

100mA keyboard attached

SD Card: Sandisk 64G Ultra

SD Card tested "The real thing"
SD Card formatted to factory defaults

Images (Armbian Stretch next for Orange Pi Prime) checked for authenticity and integrity

SD flashed using Etcher

 

First boot succesful

Installed tmux
Set up SSH using armbian-config and used it to connect
Installed docker using armbian-config successfully

 

When trying to install ISPConfig:
the SSH connection timed out,
and when I switched my screen back to HDMI I could see the display was corrupted (colored streaks),

armbian-config's did give a generic error message (something like "Error during installation").
The Pi Prime did not respond,
the case was quite warm.

 

After that I could not get it to boot again. I've tried both Armbian images,
and one of the Debian server Orange Pi Prime images.

 

Measured supply voltage (at the barrel connector's pins): 5.25V

On further inspection I saw some discoloration on the CPU and on one of the memory chips:

 

 

The ambient room temperature is around 21 degrees celcius

I don't have a USB to TTL converter yet.

I also measured some of the resistors and found that R3 (KEYADC to AVCC and KEYLADC) was only 39K instead of 100K as it should be according to the schematics.