weyou Posted June 21, 2017 Posted June 21, 2017 I got my OPi PC2 last week and flashed the latest armbian server version. Every time I enter "reboot" on SSH to reboot the system, or plug in the power cable. The system can not boot up with a great probability. My power source is the charger for SAMSUNG smartphone. The specification indicates it can provide 5V/2A current. With the UART, I found the uboot process was stuck after the statement "INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9". The LED is OFF in that moment. Quote [89805.284271] reboot: Restarting system INFO: PSCI Affinity Map: INFO: AffInst: Level 0, MPID 0x0, State ON INFO: AffInst: Level 0, MPID 0x1, State ON INFO: AffInst: Level 0, MPID 0x2, State ON INFO: AffInst: Level 0, MPID 0x3, State ON U-Boot SPL 2017.01-rc1-g5df570f-dirty (Jun 13 2017 - 21:51:43) DRAM: 1024 MiB Trying to boot from MMC1NOTICE: BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):aa75c8d NOTICE: BL3-1: Built : 21:51:42, Jun 13 2017 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9 After plugging out/in the power cable multiple times, the system can be boot up successfully finally and works very well. I'd like to know anyone has the same problem? How can I solve this issue?
pfeerick Posted June 21, 2017 Posted June 21, 2017 I would suggest that you look at getting a different power supply, as mobile phone chargers are notorious for being unreliable for SBCs. They tend to either not provide their full current until the phone has *handshaked/negotiated* with the charger, are noisy, or drop their voltage they are loaded to below usable levels (as phone charging needs aren't that demanding). I would suggest you look at getting something like the white power supply (with interchangeable international plugs) for the raspberry pi. Also, please refrain from making multiple posts... someone *will* reply eventually 1
weyou Posted June 21, 2017 Author Posted June 21, 2017 17 minutes ago, pfeerick said: I would suggest that you look at getting a different power supply, as mobile phone chargers are notorious for being unreliable for SBCs. They tend to either not provide their full current until the phone has *handshaked/negotiated* with the charger, are noisy, or drop their voltage they are loaded to below usable levels (as phone charging needs aren't that demanding). I would suggest you look at getting something like the white power supply (with interchangeable international plugs) for the raspberry pi. Also, please refrain from making multiple posts... someone *will* reply eventually Thank you. I will try to change a new power supply. I was not intent to making multiple posts, it was just an accident Maybe my network issue, the edit page didn't have any response after my first clicking on the submit button. So I clicked twice... And I didn't find how to delete the duplicate one. 1
pfeerick Posted June 21, 2017 Posted June 21, 2017 No worries, I'll remove it (actually, I think another mod beat me to it!). Please do report back and let us know how you go. And someone else might post in the meantime with more info or more ideas.
weyou Posted June 21, 2017 Author Posted June 21, 2017 5 hours ago, pfeerick said: No worries, I'll remove it (actually, I think another mod beat me to it!). Please do report back and let us know how you go. And someone else might post in the meantime with more info or more ideas. I have tested it with a power supply of raspberry pi (5v/1.5a). But still get the same issue. I also measured the electric current is about 300mA during the system boot. Even during the stress test (stress -c 4 -i 4 -m 2), the peak current is less than 600mA. I find another phenomenon: If the uboot has about 3 second pause after printing "Trying to boot from MMC1". it will get stuck at the statement "INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9" later. For a success boot up, there is no pause after printing "Trying to boot from MMC1".
pfeerick Posted June 21, 2017 Posted June 21, 2017 Only other thing I can suggest is maybe the microSD is corrupt or faulty? (yes, clutching at straws with my limited knowledge ) If you can try re-writing the Armbian image using Etcher. And please keep in mind this warning from the download page: "All currently available OS images for H5 boards are experimental". I would be surprised if the images were that unstable that they wouldn't even boot, but the warning still stands... murky waters ahead! Other than that, I'll have to bow out and leave it for more experienced folks to chip in
weyou Posted June 22, 2017 Author Posted June 22, 2017 3 hours ago, pfeerick said: Only other thing I can suggest is maybe the microSD is corrupt or faulty? (yes, clutching at straws with my limited knowledge ) If you can try re-writing the Armbian image using Etcher. And please keep in mind this warning from the download page: "All currently available OS images for H5 boards are experimental". I would be surprised if the images were that unstable that they wouldn't even boot, but the warning still stands... murky waters ahead! Other than that, I'll have to bow out and leave it for more experienced folks to chip in I will try to find another mircoSD to write a new image. Will report back later. Thanks for your help.
joselalf Posted June 23, 2017 Posted June 23, 2017 Weyou, It may be obvious, but are you using a barrel type power supply? Looks like you are using an OTG (USB type) power supply, since you Are talking about Samsung and Raspberry Pi chargers. I have an orange Pi pc 2 and I use the manufacturer recommended AC adapter 3A, barrel type. 1
weyou Posted June 24, 2017 Author Posted June 24, 2017 On 6/23/2017 at 11:34 AM, joselalf said: Weyou, It may be obvious, but are you using a barrel type power supply? Looks like you are using an OTG (USB type) power supply, since you Are talking about Samsung and Raspberry Pi chargers. I have an orange Pi pc 2 and I use the manufacturer recommended AC adapter 3A, barrel type. I'm using the Samsung/RaspberryPi chargers with a USB to barrel connector cable. I didn't use the OTG(MicroUSB) interface .
joselalf Posted June 24, 2017 Posted June 24, 2017 Weyou, OPI PC2 is very stringent regarding power requirements. Failing the SD card replacement, You should try with the manufacturer recommended AC adaptor, 5V/3A, 4.0*1.7 barrel plug...I also tested other adaptors with my board, but none of them worked, until I ordered the recommended adaptor via Xulong Aliexpress page.
weyou Posted June 25, 2017 Author Posted June 25, 2017 8 hours ago, joselalf said: Weyou, OPI PC2 is very stringent regarding power requirements. Failing the SD card replacement, You should try with the manufacturer recommended AC adaptor, 5V/3A, 4.0*1.7 barrel plug...I also tested other adaptors with my board, but none of them worked, until I ordered the recommended adaptor via Xulong Aliexpress page. Thank you, joselalf. I will try to order the recommended AC adapter If I failed the SD card replacement.
Yuan Posted June 26, 2017 Posted June 26, 2017 As far as I can tell, Orange PI's should be supplied with a voltage of 5.4V. I use a metal case Mean Well RS-25-5 and have to fine tune the output to 5.4V. Below, random no booting issues occurs (It suppllies power to four unit of PC2's)
pfeerick Posted June 26, 2017 Posted June 26, 2017 @Yuan I can't say I'd agree with that voltage... I think it's a little too high. 5.3v is the highest I generally go at the power supply. Keeping in mine the USB spec tolerances of 4.75V-5-25V, so if the 5v rail is also providing the USB voltage (and it often does), you're in danger of pushing a higher voltage than what devices are expecting, unless you get enough of a voltage sag over the leads. Whether that is enough to blow up a USB device when you plug it in, I couldn't say as I haven't tested every device under the sun. However, I would expect it to shorten the live of some devices. What I would recommend is also measuring the voltage at the device, both with no load, and when the CPU is loaded, and making sure the voltage doesn't fall below 5.00v minimum, maybe even 5.10v, depending what it shoots back up to when not loaded.
Yuan Posted June 26, 2017 Posted June 26, 2017 57 minutes ago, pfeerick said: @Yuan I can't say I'd agree with that voltage... I think it's a little too high. 5.3v is the highest I generally go at the power supply. Keeping in mine the USB spec tolerances of 4.75V-5-25V, so if the 5v rail is also providing the USB voltage (and it often does), you're in danger of pushing a higher voltage than what devices are expecting, unless you get enough of a voltage sag over the leads. Whether that is enough to blow up a USB device when you plug it in, I couldn't say as I haven't tested every device under the sun. However, I would expect it to shorten the live of some devices. What I would recommend is also measuring the voltage at the device, both with no load, and when the CPU is loaded, and making sure the voltage doesn't fall below 5.00v minimum, maybe even 5.10v, depending what it shoots back up to when not loaded. I did some measurements on both PC (connected to a plastic case wall plug 5V2A rated voltage power supply, actual output voltage is 5.36V), and PC2's (connected to the SMPS mentioned above, actual voltage is 5.40V) from GPIO pins and USB cable ends under load (running stress command): I get exact same 5.36V on bot GPIO pins and USB cable ends on PC I get regulated 5.23V on GPIO pins and 5.23V on USB cable ends on PC2 (5.40V->5.23V) As I use these SBC's for headless server use with no USB device attached to them, haven't encountered to any problem. But you may be right that 5.36V is dangerous for USB devices though. 1
weyou Posted June 28, 2017 Author Posted June 28, 2017 I got an new SD card today. At first, I flashed the latest nightly build of armbian. Reboot it with "reboot" command or power cycle multiple times. The same issue happened again and again. The probability of occurrence is about 60%. Then, I flashed the stock image Debian_Server_jessie_PC2_V0_9_1.img which is downloaded from the office website of OPi. Reboot the OPi PC2 20 times, every time it can boot up successfully. Does this mean the u-boot used by armbian has some issue? Quote [ 170.953010] Restarting system. INFO: PSCI Affinity Map: INFO: AffInst: Level 2, MPID 0x0, State ON INFO: AffInst: Level 1, MPID 0x0, State ON INFO: AffInst: Level 0, MPID 0x0, State ON INFO: AffInst: Level 0, MPID 0x1, State OFF INFO: AffInst: Level 0, MPID 0x2, State OFF HELLO! BOOT0 is starting! boot0 commit : 8 boot0 version : 4.0 set pll start set pll end rtc[0] value = 0x00000000 rtc[1] value = 0x00000000 rtc[2] value = 0x0000000f rtc[3] value = 0x0000a102 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 =672 MHZ DRAM Type =3 (2:DDR2,3:DDR3,6:LPDDR2,7:LPDDR3) DRAM zq value: 0x003b3bf9 DRAM SIZE =1024 M DRAM simple test OK. dram size =1024 card no is 0 sdcard 0 line count 4 [mmc]: mmc driver ver 2016-03-15 20:40 [mmc]: sdc0 spd mode error, 2 [mmc]: Wrong media type 0x00000000 [mmc]: ***Try SD card 0*** [mmc]: HSSDR52/SDR25 4 bit [mmc]: 50000000 Hz [mmc]: 30528 MB [mmc]: ***SD/MMC 0 init OK!!!*** sum=710a857c src_sum=710a857c read boot-pkg from emmc 32800 sector Succeed in loading uboot from sdmmc flash. Entry_name = u-boot Entry_name = monitor Entry_name = scp set arisc reset to de-assert state Ready to disable icache. ▒R▒=▒ Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):3ffd944 NOTICE: BL3-1: Built : 11:09:10, Aug 30 2016 NOTICE: BL3-1 commit: 3ffd9442d4769d7fc0002770e3b69b55150a288e INFO: BL3-1: Initializing runtime services ERROR: Error initializing runtime service tspd_fast INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address = 0x4a000000 INFO: BL3-1: Next image spsr = 0x1d3 U-Boot 2014.07 (Nov 09 2016 - 15:49:10) Allwinner Technology uboot commit : 8 secure enable bit: 0 i2c: secure monitor exist [ 0.714]pmbus: ready u0:48105000 [ 0.718][ARISC] :arisc initialize [ 0.748][ARISC] :arisc para ok [SCP] :sunxi-arisc driver begin startup 2 [SCP] :arisc version: [sun8iw5_v0.03.00-244-gb750b8e] [SCP] :sunxi-arisc driver v1.20 is starting [ 0.764][ARISC] :sunxi-arisc driver startup succeeded axp: get node[charger0] error [SCP ERROR] :message process error [SCP ERROR] :message addr : 48105080 [SCP ERROR] :message state : 5 [SCP ERROR] :message attr : 2 [SCP ERROR] :message type : 80 [SCP ERROR] :message result : f3 [SCP WARING] :callback not install [SCP ERROR] :arisc twi read pmu reg 0x3 err probe axp806 failed axp_probe error [ 0.945]PMU: cpux 1008 Mhz,AXI=336 Mhz PLL6=600 Mhz,AHB1=200 Mhz, APB1=100Mhz MBus=400Mhz run key detect no key found no uart input DRAM: 1 GiB fdt addr: 0x76e9f0e0 Relocation Offset is: 35ef2000 axp: get node[charger0] error In: serial Out: serial Err: serial gic: sec monitor mode [box standby] read rtc = 0xf [box standby] start_type = 0x1 [box standby] to kernel boot_init_gpio used ir boot recovery not used workmode = 0,storage type = 1 [ 1.149]MMC: 0 [mmc]: mmc driver ver 2016-05-20 17:18:00-test0 [mmc]: get card2_boot_para:sdc_ex_dly_used 0 [mmc]: no mmc-hs400-1_8v! [mmc]: no mmc-hs200-1_8v! [mmc]: no mmc-ddr-1_8v! [mmc]: delete max-frequency from dtb SUNXI SD/MMC: 0 [mmc]: 50 MHz... [mmc]: sample: 63 - 158(ps) [mmc]: 100 MHz... [mmc]: sample: 33 - 151(ps) [mmc]: 200 MHz... [mmc]: sample: 17 - 147(ps) [mmc]: media type 0x0 [mmc]: Wrong media type 0x0 [mmc]: ************Try SD card 0************ [mmc]: host caps: 0x27 [mmc]: MID 1b PSN dcf20421 [mmc]: PNM 00000 -- 0x30-30-30-30-30 [mmc]: PRV 1.0 [mmc]: MDT m-10 y-2014 [mmc]: speed mode : HSSDR52/SDR25 [mmc]: clock : 50000000 Hz [mmc]: bus_width : 4 bit [mmc]: user capacity : 30528 MB [mmc]: ************SD/MMC 0 init OK!!!************ [mmc]: erase_grp_size : 0x1WrBlk*0x200=0x200 Byte [mmc]: secure_feature : 0x0 [mmc]: secure_removal_type : 0x0 [ 1.347]sunxi flash init ok [ 1.361]start drv_disp_init tv_init: tv_probe:000 no report hpd work,you need support the switch class! screen 0 don't support TV! tv_init: fetch tv1 err. drv_disp_init finish hdcp is closed by sys config. no the part:Reserve0 hpd_dev_num=2, id of def_output_dev is 0 hdmi hpd out, force open? fdt_setprop_u32 disp.init_disp(0x20b0404) code:<no error> fb_id=0, size=3686400, gd->ram_size=1073741824, SUNXI_DISPLAY_FRAME_BUFFER_SIZE=16777216 [ 1.931]end PowerBus = 0( 2:vBus 3:acBus other: not exist) no battery, limit to dc no battery exist sunxi_bmp_logo_display [boot disp] can not find the partition Reserve0 bmp_name=bootlogo.bmp ** Bad device size - sunxi_flash 0 ** sunxi bmp info error : unable to open logo file bootlogo.bmp fail to find part named env Using default environment --------fastboot partitions-------- mbr not exist base bootcmd=run mmcbootcmd bootcmd set setargs_mmc no misc partition is found to be run cmd=run mmcbootcmd cann't get the boot_base from the env read item0 copy0 Item0 (Map) magic is bad the secure storage item0 copy0 is bad read item0 copy1 Item0 (Map) magic is bad the secure storage item0 copy0 == copy1, the data is good the secure storage map is empty check user data form private the private part isn't exist update dtb dram start update dtb dram end serial is: 8400503640184c22044c [ 2.099]inter uboot shell Hit any key to stop autoboot: 0 Loading orangepi uEnv.txt from 40000000 ... reading uEnv.txt [mmc]: blkcnt should not be 0 140 bytes read in 3 ms (44.9 KiB/s) Loading boot environment ... Loading orangepi bootscript ... reading boot.scr ** Unable to read file boot.scr ** Booting with defaults ... Loading orangepi orangepi/OrangePiH5orangepi.dtb from 44000000 ... reading orangepi/OrangePiH5orangepi.dtb 56524 bytes read in 7 ms (7.7 MiB/s) Loading orangepi orangepi/uImage from 4007ffc0 ... reading orangepi/uImage 12200584 bytes read in 522 ms (22.3 MiB/s) reading initrd.img 1090786 bytes read in 48 ms (21.7 MiB/s) Loading orangepi initrd.img from 44300000 ... bootm kernel:4007ffc0 initrd:44300000 ... bootm initd_size:10a4e2 fdt_addr:44000000 ... ## Booting kernel from Legacy Image at 4007ffc0 ... Image Name: OrangePiH5 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 12200520 Bytes = 11.6 MiB Load Address: 40080000 Entry Point: 40080000 Verifying Checksum ... OK XIP Kernel Image ... OK reserving fdt memory region: addr=40020000 size=800 reserving fdt memory region: addr=48000000 size=1000000 reserving fdt memory region: addr=48100000 size=4000 reserving fdt memory region: addr=48104000 size=1000 reserving fdt memory region: addr=48105000 size=1000 Loading Ramdisk to 76d85000, end 76e8f4e2 ... OK Using Device Tree in place at 44000000, end 44015dbf Starting kernel ...
Bubba Posted June 28, 2017 Posted June 28, 2017 Go find the getting start guide and read it then come back. You need tell us you know what's what. H5 is a wip
Recommended Posts