Please select To the mobile version | Continue to access the desktop computer version

OrangePi

 Login            
 Register            
Search
Hot search: orangepi
View: 1875|Reply: 5

OPi One images

[Copy link]

2

Threads

6

Posts

87

Credits

Registered member

Rank: 2

Credits
87
Post time 2016-12-12 08:20:36 | Show all posts |Read mode
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
SequenceOS ImagePhoenix Card 3.1.0 Etcher v1.0.0-beta.17Result / Observations
1sun8iw7p1_android_orangepi_pc_uart0_v0.8.0Yes1. 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
2Armbian_5.14_Orangepione_Debian_jessie_3.4.112_desktopYes1. No Red LED, Screen  blank
    2. No change after 5 minutes
    3. Powered down after 10 minutes
3pcDuino4STB_android_H3_4.4_8188-20150608.imgYes1. Red LED Turns On, Screen  shows "Android TV box"
    2. No Lan activity LED
    3. Powered down after 15 minutes and no change
4Armbian_5.20_Orangepione_Debian_jessie_3.4.112Yes1. No Red LED, Screen blank,  Green LAN activity LED flashes
    2. No change after 5 minutes
    3. Powered down after 15 minutes
5Lubuntu_1404_For_OrangePiPC_v0_8_0_.imgYes1. Red LED turns On
    2. Screen Blank
    3. No Lan activity LED
    4. powered Down after 60 minutes
6OrangePI_Ubuntu_Vivid_Mate.imgYes1. Red LED turns On
    2. Screen Blank
    3. No Lan activity LED
    4. Powered Down after 20 minutes
7Raspbian_For_OrangePi_PC_v0_8_0.imgYes1. Red LED turns On
    2. Screen Blank
    3. No Lan activity LED
    4. Powered Down after 20 minutes
9Volumio1.5_for_OrangePi_v0.2.imgYes
8OpenELEC-H3.arm-7.0-devel-20161026221335-r23113-g64b34b3-opione.imgYes1. 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?

2

Threads

6

Posts

87

Credits

Registered member

Rank: 2

Credits
87
 Author| Post time 2016-12-12 09:22:40 | Show all posts
I went ahead and added a Serial debug terrminal.

  1. U-Boot SPL 2016.09-armbian (Sep 15 2016 - 07:19:14)
  2. DRAM: 512 MiB
  3. Trying to boot from MMC1


  4. U-Boot 2016.09-armbian (Sep 15 2016 - 07:19:14 +0200) Allwinner Technology

  5. CPU:   Allwinner H3 (SUN8I 1680)
  6. Model: Xunlong Orange Pi One
  7. DRAM:  512 MiB
  8. MMC:   SUNXI SD/MMC: 0
  9. *** Warning - bad CRC, using default environment

  10. In:    serial
  11. Out:   serial
  12. Err:   serial
  13. Net:   phy interface0
  14. eth0: ethernet@1c30000
  15. Hit any key to stop autoboot:  0
  16. switch to partitions #0, OK
  17. mmc0 is current device
  18. Scanning mmc 0:1...
  19. Found U-Boot script /boot/boot.scr
  20. 2886 bytes read in 160 ms (17.6 KiB/s)
  21. ## Executing script at 43100000
  22. gpio: pin PL10 (gpio 298) value is 1
  23.    Warning: value of pin is still 0
  24. gpio: pin PG11 (gpio 203) value is 1
  25. 0 bytes read in 116 ms (0 Bytes/s)
  26. ** File not found /boot/.next **
  27. ** Unrecognized filesystem type **
  28. ** File not found .next **
  29. 35908 bytes read in 430 ms (81.1 KiB/s)
  30. 3114523 bytes read in 326 ms (9.1 MiB/s)
  31. 5025168 bytes read in 473 ms (10.1 MiB/s)
  32. ## Loading init Ramdisk from Legacy Image at 43300000 ...
  33.    Image Name:   uInitrd
  34.    Image Type:   ARM Linux RAMDisk Image (gzip compressed)
  35.    Data Size:    3114459 Bytes = 3 MiB
  36.    Load Address: 00000000
  37.    Entry Point:  00000000
  38.    Verifying Checksum ... OK
  39. Using machid 0x1029 from environment

  40. Starting kernel.....
Copy the Code


Is this what I should expect?

8

Threads

617

Posts

4156

Credits

Moderator

Rank: 7Rank: 7Rank: 7

Credits
4156
Post time 2016-12-12 16:08:46 | Show all posts
  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 the 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 ...

2

Threads

6

Posts

87

Credits

Registered member

Rank: 2

Credits
87
 Author| Post time 2016-12-13 05:07:00 | Show all posts
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

2

Threads

6

Posts

87

Credits

Registered member

Rank: 2

Credits
87
 Author| Post time 2016-12-13 17:09:36 | Show all posts
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. U-Boot SPL 2016.09-armbian (Sep 15 2016 - 07:19:14)
  5. DRAM: 512 MiB
  6. Trying to boot from MMC1


  7. U-Boot 2016.09-armbian (Sep 15 2016 - 07:19:14 +0200) Allwinner Technology

  8. CPU:   Allwinner H3 (SUN8I 1680)
  9. Model: Xunlong Orange Pi One
  10. DRAM:  512 MiB
  11. MMC:   SUNXI SD/MMC: 0
  12. *** Warning - bad CRC, using default environment

  13. In:    serial
  14. Out:   serial
  15. Err:   serial
  16. Net:   phy interface0
  17. eth0: ethernet@1c30000
  18. Hit any key to stop autoboot:  0
  19. switch to partitions #0, OK
  20. mmc0 is current device
  21. Scanning mmc 0:1...
  22. Found U-Boot script /boot/boot.scr
  23. 2886 bytes read in 143 ms (19.5 KiB/s)
  24. ## Executing script at 43100000
  25. gpio: pin PL10 (gpio 298) value is 1
  26.    Warning: value of pin is still 0
  27. gpio: pin PG11 (gpio 203) value is 1
  28. ** File not found /boot/.verbose **
  29. ** File not found /boot/.next **
  30. ** Unrecognized filesystem type **
  31. ** File not found .next **
  32. 35908 bytes read in 405 ms (85.9 KiB/s)
  33. 3114523 bytes read in 307 ms (9.7 MiB/s)
  34. 5025168 bytes read in 451 ms (10.6 MiB/s)
  35. ## Loading init Ramdisk from Legacy Image at 43300000 ...
  36.    Image Name:   uInitrd
  37.    Image Type:   ARM Linux RAMDisk Image (gzip compressed)
  38.    Data Size:    3114459 Bytes = 3 MiB
  39.    Load Address: 00000000
  40.    Entry Point:  00000000
  41.    Verifying Checksum ... OK
  42. Using machid 0x1029 from environment

  43. Starting kernel ...


  44. -----------------------------------------------
  45. Date: 13/12/2016 - 8:02:04 PM
  46. End log file
Copy the 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.

8

Threads

617

Posts

4156

Credits

Moderator

Rank: 7Rank: 7Rank: 7

Credits
4156
Post time 2016-12-13 19:33:54 | Show all posts
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 ...
You have to log in before you can reply Login | Register

Points Rules

Archiver|Mobile edition|Darkroom|OrangePi En ( 粤ICP备14086627号-2

2019-11-12 17:27 GMT+8 , Processed in 0.033026 second(s), 22 queries .

Powered by Discuz! X3.2

© 2014-2015 orangepibbs en.

Quick Reply To Top Return to the list