OPi One images

Matt_Edwards

Hi,
Firstly let me say I am a newby and will ask forgiveness now if I should say something stupid.

My set up is:

5v 8Amp  power supply ( this is a SMPS I had available)

USB Voltage monitor connected

USB Keyboard Mouse Combo

I have been loading images on to a couple of 8G Micro SD cards and then observing the result.

		Imager software
Sequence	OS Image	Phoenix Card 3.1.0	Etcher v1.0.0-beta.17	Result / Observations
1	sun8iw7p1_android_orangepi_pc_uart0_v0.8.0	Yes		1. Red LED On,        2. Green Led On then Off after about 5 seconds,     3. Screen shows H3 Quad Core logo then disappears after about a  minute     4. SSH not possible after 5 minutes - error message "Network  connection refused"     5. after 25minutes screen with space image and Chineese text flashed. top  right corner shows network connectivity icon, Mouse and keyboard not  recognised     6. still can't SSH to OPIOne       7. Screen flashes blank and then home page.   Powered down after 40 minutes
2	Armbian_5.14_Orangepione_Debian_jessie_3.4.112_desktop		Yes	1. No Red LED, Screen  blank     2. No change after 5 minutes     3. Powered down after 10 minutes
3	pcDuino4STB_android_H3_4.4_8188-20150608.img	Yes		1. Red LED Turns On, Screen  shows "Android TV box"     2. No Lan activity LED     3. Powered down after 15 minutes and no change
4	Armbian_5.20_Orangepione_Debian_jessie_3.4.112		Yes	1. No Red LED, Screen blank,  Green LAN activity LED flashes     2. No change after 5 minutes     3. Powered down after 15 minutes
5	Lubuntu_1404_For_OrangePiPC_v0_8_0_.img		Yes	1. Red LED turns On     2. Screen Blank     3. No Lan activity LED     4. powered Down after 60 minutes
6	OrangePI_Ubuntu_Vivid_Mate.img		Yes	1. Red LED turns On     2. Screen Blank     3. No Lan activity LED     4. Powered Down after 20 minutes
7	Raspbian_For_OrangePi_PC_v0_8_0.img		Yes	1. Red LED turns On     2. Screen Blank     3. No Lan activity LED     4. Powered Down after 20 minutes
9	Volumio1.5_for_OrangePi_v0.2.img		Yes
8	OpenELEC-H3.arm-7.0-devel-20161026221335-r23113-g64b34b3-opione.img		Yes	1. Red LED stays Off     2. Screen goes in to Power Saving mode     3. Lan activity LED flashed Powered downafter30minutes

As shown above my success rate sucks.  I monitor the USB voltage and noticed it is usually 5volts but it dips down to 4.8volts occassionly.
I really would like to make this work.  Any distro in english will suffice.
Should monitoring the serial debug port on start up be my next step?

Matt_Edwards

I went ahead and added a Serial debug terrminal.

1. 
   
2. U-Boot SPL 2016.09-armbian (Sep 15 2016 - 07:19:14)
   
3. DRAM: 512 MiB
   
4. Trying to boot from MMC1
   
5. 
   
6. 
   
7. U-Boot 2016.09-armbian (Sep 15 2016 - 07:19:14 +0200) Allwinner Technology
   
8. 
   
9. CPU:   Allwinner H3 (SUN8I 1680)
   
10. Model: Xunlong Orange Pi One
    
11. DRAM:  512 MiB
    
12. MMC:   SUNXI SD/MMC: 0
    
13. *** Warning - bad CRC, using default environment
    
14. 
    
15. In:    serial
    
16. Out:   serial
    
17. Err:   serial
    
18. Net:   phy interface0
    
19. eth0: ethernet@1c30000
    
20. Hit any key to stop autoboot:  0
    
21. switch to partitions #0, OK
    
22. mmc0 is current device
    
23. Scanning mmc 0:1...
    
24. Found U-Boot script /boot/boot.scr
    
25. 2886 bytes read in 160 ms (17.6 KiB/s)
    
26. ## Executing script at 43100000
    
27. gpio: pin PL10 (gpio 298) value is 1
    
28.    Warning: value of pin is still 0
    
29. gpio: pin PG11 (gpio 203) value is 1
    
30. 0 bytes read in 116 ms (0 Bytes/s)
    
31. ** File not found /boot/.next **
    
32. ** Unrecognized filesystem type **
    
33. ** File not found .next **
    
34. 35908 bytes read in 430 ms (81.1 KiB/s)
    
35. 3114523 bytes read in 326 ms (9.1 MiB/s)
    
36. 5025168 bytes read in 473 ms (10.1 MiB/s)
    
37. ## Loading init Ramdisk from Legacy Image at 43300000 ...
    
38.    Image Name:   uInitrd
    
39.    Image Type:   ARM Linux RAMDisk Image (gzip compressed)
    
40.    Data Size:    3114459 Bytes = 3 MiB
    
41.    Load Address: 00000000
    
42.    Entry Point:  00000000
    
43.    Verifying Checksum ... OK
    
44. Using machid 0x1029 from environment
    
45. 
    
46. Starting kernel.....

Copy code

Is this what I should expect?

igorpec

1. gpio: pin PL10 (gpio 298) value is 1
   
2.    Warning: value of pin is still 0
   
3. gpio: pin PG11 (gpio 203) value is 1

Copy code

This is suspicious ... would need to check.

You have nothing after "Starting kernel" ?

Can you edit .env or boot.cmd and set verbosity to 9 and try again. If you edit boot.cmd you need to convert it to boo.scr ...

Matt_Edwards

I suspect i have two issues:
I was using two different SD cards and I think one may be faulty or non optimal.  I accidentally removed it without powering it down and thought nothing of it. I will source a couple more today.  I have since got the  Armbian_5.20_Orangepione_Debian_jessie_3.4.112 to load.  
The other issue may be temperature.  I swapped OPI One boards and is loaded immediately.  I notice the H3 on the first board felt too hot. it was uncomfortable to hold my finger on it.  Today I will source a heatsink glue to stick an aluminium heat sink on the H3 chip.

The investigation continues and I will re-run the above image attempts when I get new hardware

Matt_Edwards

igorpec replied at 2016-12-12 16:08
This is suspicious ... would need to check.

You have nothing after "Starting kernel" ?

It appears I have a dead OPI One.  New SD card don't change the situation help.
I loaded Armbian_5.20_Orangepione_Debian_jessie_3.4.112 on a new Micro SD card.  
On boot up the following was output from the debug port:

1. Terminal log file
   
2. Date: 13/12/2016 - 8:01:41 PM
   
3. -----------------------------------------------
   
4. 
   
5. U-Boot SPL 2016.09-armbian (Sep 15 2016 - 07:19:14)
   
6. DRAM: 512 MiB
   
7. Trying to boot from MMC1
   
8. 
   
9. 
   
10. U-Boot 2016.09-armbian (Sep 15 2016 - 07:19:14 +0200) Allwinner Technology
    
11. 
    
12. CPU:   Allwinner H3 (SUN8I 1680)
    
13. Model: Xunlong Orange Pi One
    
14. DRAM:  512 MiB
    
15. MMC:   SUNXI SD/MMC: 0
    
16. *** Warning - bad CRC, using default environment
    
17. 
    
18. In:    serial
    
19. Out:   serial
    
20. Err:   serial
    
21. Net:   phy interface0
    
22. eth0: ethernet@1c30000
    
23. Hit any key to stop autoboot:  0
    
24. switch to partitions #0, OK
    
25. mmc0 is current device
    
26. Scanning mmc 0:1...
    
27. Found U-Boot script /boot/boot.scr
    
28. 2886 bytes read in 143 ms (19.5 KiB/s)
    
29. ## Executing script at 43100000
    
30. gpio: pin PL10 (gpio 298) value is 1
    
31.    Warning: value of pin is still 0
    
32. gpio: pin PG11 (gpio 203) value is 1
    
33. ** File not found /boot/.verbose **
    
34. ** File not found /boot/.next **
    
35. ** Unrecognized filesystem type **
    
36. ** File not found .next **
    
37. 35908 bytes read in 405 ms (85.9 KiB/s)
    
38. 3114523 bytes read in 307 ms (9.7 MiB/s)
    
39. 5025168 bytes read in 451 ms (10.6 MiB/s)
    
40. ## Loading init Ramdisk from Legacy Image at 43300000 ...
    
41.    Image Name:   uInitrd
    
42.    Image Type:   ARM Linux RAMDisk Image (gzip compressed)
    
43.    Data Size:    3114459 Bytes = 3 MiB
    
44.    Load Address: 00000000
    
45.    Entry Point:  00000000
    
46.    Verifying Checksum ... OK
    
47. Using machid 0x1029 from environment
    
48. 
    
49. Starting kernel ...
    
50. 
    
51. 
    
52. -----------------------------------------------
    
53. Date: 13/12/2016 - 8:02:04 PM
    
54. End log file
    

Copy code

It has the same suspission code.  I also confirm there is nothing after Starting kernel.

BTW I also checked the new SD card in the other OPIOne that I got working.

igorpec

HW failure or DOA is rear but possible. If you have the other device working and since you already try a lot of different options ...