Jump to content

OPI PC+ not booting on eMMC (internal 8GB) since...

Philip63

By Philip63
in Beginners

 Share

Recommended Posts

Philip63

Philip63

Posted
Posted

Hello,

 

just registered on this forum because i can't troubleshoot my issue even if some posts seems to look like my issue and this forum doesn't unknown from me from some others reasons.
Orange PI pc plus
OpenELEC-H3.arm-7.0-devel-20161026221641-r23113-g64b34b3-opipcplus.img
on eMMC since few months.
After successfully make (for USB support) and tested 'u-boot-sunxi-with-spl.bin' on my SD card, i decided to write it onto the eMMC after booting from SD card with this kind of command:
dd if=./u-boot-sunxi-with-spl.bin of=/dev/mmcblk0 bs=1024 seek=8

now i have this output (from UART) see bellow
 

thanks in advance for help

Philip63

 

--console output--

compilation 'u-boot-sunxi-with-spl.bin' OK
boot depuis SD pour upgrade u-boot + SPL sur eMMC (pour prise en compte USB)
test sur SD = OK :
dd if=./u-boot-sunxi-with-spl.bin of=/dev/mmcblk1 bs=1024 seek=8

mais depuis cette commande impossible de booter a partir de eMMC:
dd if=./u-boot-sunxi-with-spl.bin of=/dev/mmcblk0 bs=1024 seek=8

--

pas de SD inseree
sous console UART:

U-Boot SPL 2017.11-00391-g34dd853 (Nov 30 2017 - 19:51:13)           < la date de ma compilation
DRAM: 1024 MiB
Trying to boot from MMC2


U-Boot 2017.11-00391-g34dd853 (Nov 30 2017 - 19:51:13 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi PC Plus
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
In:    serial
Out:   serial
Err:   serial
Net:   phy interface0
eth0: ethernet@1c30000
Hit any key to stop autoboot:  0

=> version
U-Boot 2017.11-00391-g34dd853 (Nov 30 2017 - 19:51:13 +0100) Allwinner Technology

arm-linux-gnueabihf-gcc (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
GNU ld (GNU Binutils for Ubuntu) 2.26.1

=> mmc list
SUNXI SD/MMC: 0
SUNXI SD/MMC: 1 (eMMC)

=> mmc dev
switch to partitions #0, OK
mmc1(part 0) is current device

=> mmc list
SUNXI SD/MMC: 0
SUNXI SD/MMC: 1 (eMMC)

=> mmc part

Partition Map for MMC device 1  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            1048577         6b6009a0-01     0c Boot
  2     1052672         14217216        6b6009a0-02     83

=> fatls mmc 1:1
  6234464   KERNEL
 134189056   SYSTEM
    32276   script.bin
      295   boot.scr
            eMMC-8GB-internal/     < un flag pour etre sur

4 file(s), 1 dir(s)

=> ext2ls mmc 1:2
<DIR>       1024 .
<DIR>       1024 ..
<DIR>      12288 lost+found
<DIR>       1024 .kodi
<DIR>       1024 music
<DIR>       1024 pictures
<DIR>       1024 tvshows
<DIR>       1024 videos
<DIR>       1024 screenshots
<DIR>       1024 .update
<DIR>       1024 .cache
<DIR>       1024 .config
<DIR>       1024 .ssh
<DIR>       1024 .smb
<DIR>       1024 mnt
            2726 .ash_history
<DIR>       1024 .dvdcss
        20706289 gadgetmodulekernel_151226a.tgz
<DIR>       1024 tmp
            8192 fel-sdboot.sunxi
=> mmc info
Device: SUNXI SD/MMC
Manufacturer ID: 15
OEM: 100
Name: 8WPD3
Tran Speed: 52000000
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 7.3 GiB
Bus Width: 8-bit
Erase Group Size: 512 KiB
HC WP Group Size: 8 MiB
User Capacity: 7.3 GiB WRREL
Boot Capacity: 4 MiB ENH
RPMB Capacity: 512 KiB ENH
=>

--
trace:

=> reset
resetting ...

U-Boot SPL 2017.11-00391-g34dd853 (Nov 30 2017 - 19:51:13)
DRAM: 1024 MiB
Trying to boot from MMC2


U-Boot 2017.11-00391-g34dd853 (Nov 30 2017 - 19:51:13 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi PC Plus
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
In:    serial
Out:   serial
Err:   serial
Net:   phy interface0
eth0: ethernet@1c30000
Hit any key to stop autoboot:  0
MMC: no card present
mmc_init: -123, time 2
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot.scr
reading /boot.scr
295 bytes read in 14 ms (20.5 KiB/s)
## Executing script at 43100000
MMC: no card present
mmc_init: -123, time 2
** Bad device mmc 0 **
MMC: no card present
mmc_init: -123, time 2
** Bad device mmc 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
SCRIPT FAILED: continuing...
*******************************TEST*******************************
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 125


../..

zador.blood.stained

zador.blood.stained

Posted
Posted
14 minutes ago, Philip63 said:

U-Boot SPL 2017.11-00391-g34dd853 (Nov 30 2017 - 19:51:13)

This commit sunxi: remove MMC index hack made between v2017.09 and v2017.11 changed the logic for numbering SD/MMC devices, so older boot scripts that used "mmc 0" in all commands are breaking on upgrade.

For the reference this will affect Armbian too - that's why I held the u-boot version for this (Armbian 5.25) stable release at 2017.09.

Philip63

Philip63

Posted
  • Author
Posted

Hi,

 

first, thanks for reply

 

 

before:

=> mmc rescan
=> mmc list
SUNXI SD/MMC: 1
SUNXI SD/MMC: 0 (eMMC)
=> mmc info
Device: SUNXI SD/MMC
Manufacturer ID: 15
OEM: 100
Name: 8WPD3
Tran Speed: 52000000
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 7.3 GiB
Bus Width: 8-bit
Erase Group Size: 512 KiB
HC WP Group Size: 8 MiB
User Capacity: 7.3 GiB WRREL
Boot Capacity: 4 MiB ENH
RPMB Capacity: 512 KiB ENH

=> part list mmc 0

Partition Map for MMC device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            1048577         6b6009a0-01     0c Boot
  2     1052672         14217216        6b6009a0-02     83
=> fstype mmc 0:1
fat
=> fstype mmc 0:2
ext4
=>

 

after;

=> mmc rescan
=> mmc list
SUNXI SD/MMC: 0
SUNXI SD/MMC: 1 (eMMC)
=> mmc info
Device: SUNXI SD/MMC
Manufacturer ID: 15
OEM: 100
Name: 8WPD3
Tran Speed: 52000000
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 7.3 GiB
Bus Width: 8-bit
Erase Group Size: 512 KiB
HC WP Group Size: 8 MiB
User Capacity: 7.3 GiB WRREL
Boot Capacity: 4 MiB ENH
RPMB Capacity: 512 KiB ENH
=> part list mmc 0
MMC: no card present
mmc_init: -123, time 1
** Bad device mmc 0 **

=> fstype mmc 0:1
MMC: no card present
mmc_init: -123, time 2
** Bad device mmc 0 **
=> fstype mmc 1:1
fat
=> fstype mmc 1:2
ext4
=>


i dont understood all what to do but

is there something possible to do from u-boot prompt?

 

thanks

zador.blood.stained

zador.blood.stained

Posted
Posted
6 minutes ago, Philip63 said:

is there something possible to do from u-boot prompt?

Yes. If you know how your boot script looks like you can enter commands manually (substituting "mmc 0" with "mmc 1") to boot the OS and replace the u-boot or boot script from there or you can boot a different OS from SD to access the eMMC.

Philip63

Philip63

Posted
  • Author
Posted (edited)
On 01/12/2017 at 11:17 PM, zador.blood.stained said:

Yes. If you know how your boot script looks like you can enter commands manually (substituting "mmc 0" with "mmc 1") to boot the OS and replace the u-boot or boot script from there or you can boot a different OS from SD to access the eMMC.

 

On 01/12/2017 at 11:17 PM, zador.blood.stained said:

Hi Zador,
and there is a way to display boot.scr contents from u-boot prompt?

 

Edited by Philip63
relolved
Philip63

Philip63

Posted
  • Author
Posted (edited)

retrieve an recent output (hope it is the good one):

 

setenv machid 1029
setenv bootm_boot_mode sec
#setenv bootargs console=ttyS0,115200 boot=/dev/mmcblk1p1 disk=/dev/mmcblk1p2 consoleblank=0
fatload mmc 0 0x43000000 script.bin
fatload mmc 0 0x42000000 KERNEL
bootm 0x42000000

Edited by Philip63
resolved
Philip63

Philip63

Posted
  • Author
Posted (edited)

=> load mmc 1:1 0x5000000 boot.scr
reading boot.scr
295 bytes read in 14 ms (20.5 KiB/s)

 

=> md 0x5000000
05000000: 00000000 00000000 00000000 00000000    ................
05000010: 00000000 00000000 00000000 00000000    ................
05000020: 00000000 00000000 00000000 00000000    ................
05000030: 00000000 00000000 00000000 00000000    ................
05000040: 00000000 00000000 00000000 00000000    ................
05000050: 00000000 00000000 00000000 00000000    ................
05000060: 00000000 00000000 00000000 00000000    ................
05000070: 00000000 00000000 00000000 00000000    ................
05000080: 00000000 00000000 00000000 00000000    ................
05000090: 00000000 00000000 00000000 00000000    ................
050000a0: 00000000 00000000 00000000 00000000    ................
050000b0: 00000000 00000000 00000000 00000000    ................
050000c0: 00000000 00000000 00000000 00000000    ................
050000d0: 00000000 00000000 00000000 00000000    ................
050000e0: 00000000 00000000 00000000 00000000    ................
050000f0: 00000000 00000000 00000000 00000000    ................
=>

Edited by Philip63
removed
Philip63

Philip63

Posted
  • Author
Posted (edited)

Hi,

 

my question;

is there something possible to do from u-boot prompt?

your answer:

Yes. If you know how your boot script looks like you can enter commands manually (substituting "mmc 0" with "mmc 1") to boot the OS and replace the u-boot or boot script from there or you can boot a different OS from SD to access the eMMC.

 

now (tomorow morning) , what can i do please

thanks

Edited by Philip63
Philip63

Philip63

Posted
  • Author
Posted (edited)

hello there,

 

according with zador advices,

i tried to build an boot.scr (with mkimage) with 'mmc 1' instead of 'mmc 0' but boot from eMMC fail anyway.

 

output:

U-Boot SPL 2017.11-00391-g34dd853 (Nov 30 2017 - 19:51:13)
DRAM: 1024 MiB
Trying to boot from MMC2


U-Boot 2017.11-00391-g34dd853 (Nov 30 2017 - 19:51:13 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi PC Plus
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
In:    serial
Out:   serial
Err:   serial
Net:   phy interface0
eth0: ethernet@1c30000
Hit any key to stop autoboot:  0
MMC: no card present
mmc_init: -123, time 2
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot.scr
reading /boot.scr
378 bytes read in 15 ms (24.4 KiB/s)
## Executing script at 43100000
 **Unable to read file script.bin                            <  fatload mmc 1 0x43000000 script.bin from /boot.scr
 **Unable to read file KERNEL                              < fatload mmc 1 0x42000000 KERNEL from /boot.scr
bootm - boot application image from memory

Usage:
bootm [addr [arg ...]]

 

--

but from u-boot prompt (and then i dont understand at all) it seem to be okay but bootm fail and resetting...

 

=> fatload mmc 1 0x43000000 script.bin
reading script.bin
32276 bytes read in 25 ms (1.2 MiB/s)

=> imi 0x43000000

## Checking Image at 43000000 ...
Unknown image format!

 

=> fatload mmc 1 0x42000000 KERNEL
reading KERNEL
6234464 bytes read in 294 ms (20.2 MiB/s)
=> imi

## Checking Image at 43200000 ...
Unknown image format!
=> imi 0x42000000

## Checking Image at 42000000 ...
   Legacy image found
   Image Name:   Linux-3.4.113
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    6234400 Bytes = 5.9 MiB
   Load Address: 40008000
   Entry Point:  40008000
   Verifying Checksum ... OK

 

=> bootm 0x42000000
## Booting kernel from Legacy Image at 42000000 ...
   Image Name:   Linux-3.4.113
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    6234400 Bytes = 5.9 MiB
   Load Address: 40008000
   Entry Point:  40008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
resetting ...

U-Boot SPL 2017.11-00391-g34dd853 (Nov 30 2017 - 19:51:13)
DRAM: 1024 MiB
Trying to boot from MMC2


U-Boot 2017.11-00391-g34dd853 (Nov 30 2017 - 19:51:13 +0100) Allwinner Technology

../..

 

any idea ?

 

thanks

Edited by Philip63
resolved with other u-boot-sunxi-with-spl.bin
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept