Orange PI PLUS not boot on SD card

xlogan

Bonjour

Essayez avec cette image (link), c'est la meilleur que j'ai troué, Il est construit pour OPI-Plus, donc tu n'as pas besoin de changer rien.
Pardon mon française

-Logan

dhlii

didacgil9 replied at 2016-1-8 04:26
Hi,  for the question 1, just open the settings and scroll the menu looking for the icon with the le ...

I have pretty much the same problem.

I have dd'd a number of different images to SDcards, and have rarely if evver gotten any to boot.
But the unit will boot the internall eMMC.

I am guessing from your post that the instructions you provide are for Windows.
I use Linux.

It seems there is something odd about the SD setup for the Orange Pi Plus as dd has never given me problems creating useable images for other devices.
I am an embedded software developer, so I have worked with lots of other devices Raspberry Pi's Hummingboards, Beagle Boards, Olinuxino, .....
So what is the trick ?

Is there some instructions for rolling your own SD card. I have worked with other AllWinner boards - isn't the Orange Pi Plus boot much the same ?

didacgil9

I have worked also with other boards, like the Rpi, and it seems that the process for booting from the SD card is different in the OrangePi.
Notice that in the Orange Pi Plus you can define the image in the SDCard to be directly booted or to be copied to the internal EMMC.

I do not know how to perform the transfer of the image into the SD Card for direct booting in Linux. At home, I use Linux, Mac and Windows, and I just managed to perform the steps via Windows. I tried with some guidelines in Mac, and I could not make it either there.
So, if you have a chance, I would recommend that you give it a try with Windows (via VirtualBox, maybe).

Good luck

vineet

HI ,
I have raspberry pi TF burned SD card , put that card in Orange Pi 2 Plus H/w still showing same android so how where can i get the Boot option ??

vineet

didacgil9 replied at 2016-1-8 04:26
Hi,  for the question 1, just open the settings and scroll the menu looking for the icon with the le ...

i did same thing when  i am doing boot from card screen become black i have Orang Pi plus 2

dhlii

didacgil9 replied at 2016-1-26 14:20
I have worked also with other boards, like the Rpi, and it seems that the process for booting from t ...

The problem is that unless you can get the unit to boot the SDcard atleast once, you can not get anything new into the eMMC.

And I can not get the unit (Orange Pi Plus) to boot from SD at all.

When I put an SDcard in the unit and cycle the power NOTHING comes out the debug serial, and nothing loads.
I have tried several SDcards and Several different images.

I am gathering from the other posts here this is not an uncommon problem.

And I think everyone who has it has an Orange Pi Plus

DADA57

il faut remplacer ou en fait renommer les fichiers :
1) uImage_OPI-PLUS en uImage ( un fichier existe déjà sur la carte donc le remplacer)
2) script.bin.OPI-XXXX  en script.bin  ( un fichier existe déjà sur la carte donc le remplacer)

kirill

Hello!
I have same problem - OrangePi Plus v1.2 not boot from SD-card with u-boot builded from source.
Follow my steps:

1. git clone --depth=1 https://github.com/orangepi-xunlong/sunxi-bsp.git orangepi_bsp
   
2. cd orangepi_bsp
   
3. ./configure orangepi
   
4. make
   
5. scripts/sunxi-media-create.sh /dev/sde output/orangepi_hwpack.tar.xz norootfs

Copy code

sunxi-media-create.sh output:

1. # scripts/sunxi-media-create.sh /dev/sde output/orangepi_hwpack.tar.xz norootfs
   
2. 
   
3. ===
   
4. === Extracting HW Pack ===
   
5. ===
   
6. 
   
7. ===
   
8. === Copy U-Boot/SPL to SD Card ===
   
9. ===
   
10. 20+0 records in
    
11. 20+0 records out
    
12. 20480 bytes (20 kB) copied, 0.0694279 s, 295 kB/s
    
13. 232+1 records in
    
14. 232+1 records out
    
15. 238304 bytes (238 kB) copied, 0.0374332 s, 6.4 MB/s
    
16. Copy VFAT partition files to SD Card
    
17. 
    
18. ===
    
19. === Copy hwpack rootfs files ===
    
20. ===
    
21. Done.

Copy code

And current versions:

1. BSP 23ebf1e4adb72e24f0af6d5b02487edcb9c07575
   
2. cedarx-libs b8f52d913f73720e50d8f1b2f8610467b575dc45
   
3. linux-sunxi 57644f704667b72d02a0ab7aa8e30f593d089027
   
4. sunxi-boards ffee8aefc1372c98ee3e29d12a8c5d846488caf8
   
5. sunxi-tools 0dfb448fe495ed57c4a079791ac0b46fb0160a3a
   
6. u-boot-sunxi 41cf48dffa7f5df052c1918cdc03d4fb6927ab33

Copy code

How can I solve this problem?
Thank you and excuse my bad english.

kirill

Hello!
I try another way.
First, I restore orangepi-plus-debian-server-card-v0.9.img on SD-card, board start and I can use system via UART.
Second, I clone linux from https://github.com/orangepi-xunlong/linux-sunxi.git (commit 57644f704667b72d02a0ab7aa8e30f593d089027) and build default config:

1. $ make ARCH=arm sun7i_defconfig
   
2. $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- uImage

Copy code

uImage I copy on SD-card, board start, but linux can't load, follow full log:

1. HELLO! BOOT0 is starting!
   
2. boot0 version : 4.0.0
   
3. fel_flag = 0x00000000
   
4. rtc[0] value = 0x00000000
   
5. rtc[1] value = 0x00000000
   
6. rtc[2] value = 0x00000000
   
7. rtc[3] value = 0x00000000
   
8. rtc[4] value = 0x00000000
   
9. rtc[5] value = 0x00000000
   
10. rtc[6] value = 0x00000000
    
11. rtc[7] value = 0x00000000
    
12. DRAM DRIVE INFO: V0.8
    
13. DRAM Type = 3 (2:DDR2,3:DDR3,6:LPDDR2,7:LPDDR3)
    
14. DRAM CLK = 672 MHz
    
15. DRAM zq value: 003b3bfb
    
16. READ DQS LCDL = 001e1e1d
    
17. DRAM SIZE =1024 M
    
18. odt delay
    
19. dram size =1024
    
20. card boot number = 0
    
21. card no is 0
    
22. sdcard 0 line count 4
    
23. [mmc]: mmc driver ver 2014-12-10 21:20:39
    
24. [mmc]: ***Try SD card 0***
    
25. [mmc]: SD/MMC Card: 4bit, capacity: 30028MB
    
26. [mmc]: vendor: Man 00275048 Snr 019c0fb5
    
27. [mmc]: product: SD32G
    
28. [mmc]: revision: 3.0
    
29. [mmc]: ***SD/MMC 0 init OK!!!***
    
30. sdcard 0 init ok
    
31. The size of uboot is 000dc000.
    
32. sum=5f62b640
    
33. src_sum=5f62b640
    
34. Succeed in loading uboot from sdmmc flash.
    
35. Ready to disable icache.
    
36. Jump to secend Boot.
    
37. SUNXI_NORMAL_MODE   
    
38. [      0.347]e mode
    
39. 
    
40. U-Boot 2011.09-rc1 (Apr 21 2015 - 18:23:44) Allwinner Technology
    
41. 
    
42. [      0.354]version: 1.1.0
    
43. normal mode
    
44. [      0.362]pmbus:   ready
    
45. not set main pmu id
    
46. axp_probe error
    
47. [      0.377]PMU: pll1 1200 Mhz,PLL6=600 Mhz
    
48. AXI=400 Mhz,AHB=200 Mhz, APB1=100 Mhz
    
49. sid read already
    
50. fel key new mode
    
51. run key detect
    
52. no key found
    
53. no key input
    
54. dram_para_set start
    
55. dram_para_set end
    
56. normal mode
    
57. [      0.407]DRAM:  1 GiB
    
58. relocation Offset is: 35af9000
    
59. [box standby] read rtc = 0x0
    
60. [box_start_os] mag be start_type no use
    
61. user_gpio config
    
62. user_gpio ok
    
63. gic: normal or no secure os mode
    
64. workmode = 0
    
65. MMC:     0
    
66. [      0.481][mmc]: mmc driver ver 2014-12-10 9:23:00
    
67. [      0.486][mmc]: get sdc_phy_wipe fail.
    
68. [      0.490][mmc]: get sdc0 sdc_erase fail.
    
69. [      0.494][mmc]: get sdc_f_max fail,use default 50000000Hz
    
70. [      0.499][mmc]: get sdc_ex_dly_used fail,use default dly
    
71. [      0.505][mmc]: SUNXI SD/MMC: 0
    
72. [      0.518][mmc]: *Try SD card 0*
    
73. [      0.551][mmc]: CID 0x27504853 0x44333247 0x30019c0f 0xb500daff
    
74. [      0.556][mmc]: mmc clk 50000000
    
75. [      0.560][mmc]: SD/MMC Card: 4bit, capacity: 30028MB
    
76. [      0.565][mmc]: boot0 capacity: 0KB,boot1 capacity: 0KB
    
77. [      0.570][mmc]: ***SD/MMC 0 init OK!!!***
    
78. [      0.575][mmc]: erase_grp_size:0x1WrBlk * 0x200 = 0x200 Byte
    
79. [      0.580][mmc]: secure_feature 0x0
    
80. [      0.584][mmc]: secure_removal_type  0x0
    
81. [      0.588]sunxi flash init ok
    
82. script config pll_de to 864 Mhz
    
83. Not Found clk pll_video1 in script
    
84. script config pll_video to 297 Mhz
    
85. [boot]disp_init_tv
    
86. [DISP_TV] disp_init_tv enter g_tv_used
    
87. screen 0 do not support TV TYPE!
    
88. [BOOOT_DISP_TV] disp tv device_registered
    
89. unable to find regulator vcc-hdmi-18 from [pmu1_regu] or [pmu2_regu]
    
90. enable power vcc-hdmi-18, ret=-1
    
91. DRV_DISP_Init end
    
92. boot_disp.auto_hpd=1
    
93. auto hpd check has 100 times!
    
94. auto check no any connected, the output_type is 4
    
95. [disk_read_fs] no the partition
    
96. error: open disp_rsl.fex, maybe it is not exist
    
97. not support this mode[4], use inline mode[4]
    
98. attched ok, mgr0<-->device0, type=4, mode=4----
    
99. ready to set mode
    
100. [      1.968]finally, output_type=0x4, output_mode=0x4, screen_id=0x0, disp_par0
     
101. fail to find part named env
     
102. Using default environment
     
103. 
     
104. In:    serial
     
105. Out:   serial
     
106. Err:   serial
     
107. --------fastboot partitions--------
     
108. mbr not exist
     
109. base bootcmd=run setargs_mmc boot_normal
     
110. bootcmd set setargs_mmc
     
111. key 0
     
112. cant find rcvy value
     
113. cant find fstbt value
     
114. no misc partition is found
     
115. to be run cmd=run setargs_mmc boot_normal
     
116. [      2.005][mmc]: MMC Device 2 not found
     
117. [      2.009][mmc]: Can not find mmc dev
     
118. [      2.012][mmc]: read first backup failed in fun sdmmc_secure_storage_read l9
     
119. sunxi_secstorage_read fail
     
120. get secure storage map err
     
121. the private part isn't exist
     
122. WORK_MODE_BOOT
     
123. adver not need show
     
124. sunxi_bmp_logo_display
     
125. [disk_read_fs] no the partition
     
126. error: open bootlogo.bmp, maybe it is not exist
     
127. sunxi bmp info error : unable to open logo file bootlogo.bmp
     
128. [      2.045]Hit any key to stop autoboot:  0
     
129. [      5.507][mmc]: blkcnt should not be 0
     
130. ## Booting kernel from Legacy Image at 40007800 ...
     
131.    Image Name:   Linux-3.4.103+
     
132.    Image Type:   ARM Linux Kernel Image (uncompressed)
     
133.    Data Size:    4829288 Bytes = 4.6 MiB
     
134.    Load Address: 40008000
     
135.    Entry Point:  40008000
     
136.    Verifying Checksum ... OK
     
137.    Loading Kernel Image ... OK
     
138. OK
     
139. [      5.608][mmc]: MMC Device 2 not found
     
140. [      5.612][mmc]:  mmc  not find,so not exit
     
141. [      5.616]
     
142. Starting kernel ...
     
143. 
     
144. <6>Booting Linux on physical CPU 0
     
145. <6>Initializing cgroup subsys cpuset
     
146. <6>Initializing cgroup subsys cpu
     
147. <5>Linux version 3.4.103+ (kirill@kirill) (gcc version 4.9.2 ( 4.9.2-10) ) #1 S6
     
148. CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
     
149. CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
     
150. 
     
151. Error: unrecognized/unsupported machine ID (r1 = 0x00001029).
     
152. 
     
153. 
     
154. Error: unrecognized/unsupported machine ID (r1 = 0x00001029).
     
155. 
     
156. Available machine support:
     
157. 
     
158. ID (hex)        NAME
     
159. Available machine support:
     
160. 
     
161. ID (hex)        NAME
     
162. 000010bb        sun7i
     
163. 000010bb        sun7i
     
164. 0000102a        sun5i
     
165. 0000102a        sun5i
     
166. 00001008        sun4i
     
167. 00001008        sun4i
     
168. 
     
169. Please check your kernel config and/or bootloader.
     
170. 
     
171. Please check your kernel config and/or bootloader.

Copy code

I check linux source and found what 0x00001029 is sun6i

1. $ grep 4137 include/generated/mach-types.h
   
2. #define MACH_TYPE_SUN6I                4137

Copy code

Why orangepi-plus-debian-server-card-v0.9.img u-boot builded for sun6i?

jhc58

xlogan replied at 2016-1-23 06:06
Bonjour

Essayez avec cette image (link), c'est la meilleur que j'ai troué, Il est construit pour O ...

Bonjour,

Je confirme, ENFIN une image qui semble fonctionner correctement. Un couac lors de la mise à jour mais en relancant un apt-upgrade, tout s'est remis en ordre !

Un grand merci.