Jump to content
  • 0

Problem *** Warning - bad CRC, using default environment


Stroke_papy
 Share

Question

Hello

I have a problem with my Xunlong Orange Pi PC Plus, if I put an SD card with Armbian_20.11.3_Orangepipcplus_buster_current_5.9.14 or focal (format with Etcher) it will boot with the MMC is not with the SD card i have an error

Trying to boot from MMC1

...

MMC:   mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment

...

mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr

...

EHCI failed to shut down host controller.
   Loading Ramdisk to 4969c000, end 49fff9c3 ... OK
   Loading Device Tree to 4962b000, end 4969bfff ... OK

Starting kernel ...

and after nothing happens

 

https://slexy.org/view/s2kxLKb95J

 

if I do a boot without an sd card

 

Trying to boot from MMC2

...

[  OK  ] Listening on Journal Socket.
         Starting Load Kernel Modules...
         Starting Journal Service...
         Starting Remount Root and Kernel File Systems...
         Starting Nameserver information manager...
         Starting Create list of required st... nodes for the current kernel...
         Starting Set console keymap...
         Mounting Debug File System...
         Mounting POSIX Message Queue File System...
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
         Mounting Configuration File System..

...

[   10.775055] mmc1: cache flush error -110
[   10.961936] sunxi-mmc 1c11000.mmc: data error, sending stop command
[   10.968312] sunxi-mmc 1c11000.mmc: send stop command failed
[   10.974505] mmcblk1: error -110 requesting status
[   10.974634] mmc1: cache flush error -110
[  OK  ] Found device /dev/ttyS0.
[   11.135772] sunxi-mmc 1c11000.mmc: data error,


 

and after nothing happens

 

https://slexy.org/raw/s21mCSfWbI?token=1872091d8c19f94b154ea4a415782e86b296ee756c8d9a0715264a3ddac4d388&ts=1608196059

 

what to do

 

Thank you very much

 

 

 

Link to comment
Share on other sites

5 answers to this question

Recommended Posts

  • 0
6 hours ago, Stroke_papy said:

*** Warning - bad CRC, using default environment

 

I read recently (in some thread in Kobol Club as I recall, but could not find it with a quick look just now) that this error is not important (it's just a warning).  If that's true, something else is the problem.

 

To me, this is a bigger clue:

 

6 hours ago, Stroke_papy said:

Starting kernel ...

and after nothing happens

 

So hardware seems to be fine, kernel is not starting for some reason.

 

6 hours ago, Stroke_papy said:

[FAILED] Failed to start Load Kernel Modules. See 'systemctl status systemd-modules-load.service' for details.

 

This is another clue.  Did you look in there?

Link to comment
Share on other sites

Donate and support the project!

  • 0

Hello
I tried to let the 10 min boot run
But nothing happens, the log

U-Boot SPL 2020.10-armbian (Dec 12 2020 - 00:49:41 +0100)
DRAM: 1024 MiB
Trying to boot from MMC1


U-Boot 2020.10-armbian (Dec 12 2020 - 00:49:41 +0100) Allwinner Technology

CPU: Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi PC Plus
DRAM: 1 GiB
MMC: mmc @ 1c0f000: 0, mmc @ 1c10000: 2, mmc @ 1c11000: 1
Loading Environment from FAT ... *** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Net: phy interface0
eth0: ethernet @ 1c30000
230 454 bytes read in 15 ms (14.7 MiB / s)
starting USB ...
Usb bus @ 1c1a000: USB EHCI 1.00
Usb bus @ 1c1a400: USB OHCI 1.0
Usb bus @ 1c1b000: USB EHCI 1.00
Usb bus @ 1c1b400: USB OHCI 1.0
Usb bus @ 1c1c000: USB EHCI 1.00
Usb bus @ 1c1c400: USB OHCI 1.0
Usb bus @ 1c1d000: USB EHCI 1.00
Usb bus @ 1c1d400: USB OHCI 1.0
scanning bus usb @ 1c1a000 for devices ... 1 USB Device (s) found
scanning bus usb @ 1c1a400 for devices ... 1 USB Device (s) found
scanning bus usb @ 1c1b000 for devices ... 1 USB Device (s) found
scanning bus usb @ 1c1b400 for devices ... 1 USB Device (s) found
scanning bus usb @ 1c1c000 for devices ... 1 USB Device (s) found
scanning bus usb @ 1c1c400 for devices ... 1 USB Device (s) found
scanning bus usb @ 1c1d000 for devices ... 1 USB Device (s) found
scanning bus usb @ 1c1d400 for devices ... 1 USB Device (s) found
       scanning usb for storage devices ... 0 Storage Device (s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions # 0, OK
mmc0 is current device
Scanning mmc 0: 1 ...
Found U-Boot script /boot/boot.scr
3967 bytes read in 4 ms (967.8 KiB / s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
153 bytes read in 3 ms (49.8 KiB / s)
11434329 bytes read in 552 ms (19.8 MiB / s)
7808464 bytes read in 375 ms (19.9 MiB / s)
Found mainline kernel configuration
32636 bytes read in 10 ms (3.1 MiB / s)
4185 bytes read in 8 ms (510.7 KiB / s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 45000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name: uInitrd
   Image Type: ARM Linux RAMDisk Image (gzip compressed)
   Data Size: 11434265 Bytes = 10.9 MiB
   Load Address: 00000000
   Entry Point: 00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
   Loading Ramdisk to 49518000, end 49fff919 ... OK
   Loading Device Tree to 494a7000, end 49517fff ... OK

Starting kernel ...

without the SD card I tried to I tried to go through the Kernel, I don't have the science for that !!!!

Autoboot in 2 seconds, press <Space> to stop
=>
=> systemctl
Unknown command 'systemctl' - try 'help'

what to do

Thank you very much

Link to comment
Share on other sites

  • 0
2 hours ago, Stroke_papy said:

I tried to let the 10 min boot run

 

Yes, if you took no other steps, this is expected.  I wasn't saying to let it run longer, I was suggesting that for some reason the kernel is not loading (seems like).

 

2 hours ago, Stroke_papy said:

Autoboot in 2 seconds, press <Space> to stop

=>

=> systemctl

Unknown command 'systemctl' - try 'help'

 

This is U-Boot environment, not GNU/Linux shell.  Type help (like it says) to see what you can do there.

 

Basically, you should need to just tell the kernel to boot.  Either manually, or fix the boot settings so that it works every time.

 

You may find something helpful in Recovery section of docs.  There are also some additional commands here.[0]

 

[0] It's on my list to add the latter link to the former page at some point.

Link to comment
Share on other sites

  • 0

ouch
without sd card I get this

=> mmc list
mmc @ 1c0f000: 0
mmc @ 1c10000: 2
mmc @ 1c11000: 1 (eMMC)
=> mmc dev 1
switch to partitions # 0, OK
mmc1 (part 0) is current device
=> ls mmc 1: 1 /
             System Volume Information /
             dtb /
   3636584 System.map-pc-plus
    230456 boot.bmp
      3628 boot.cmd
      3700 boot.scr
        86 orangepiEnv.txt
   5876450 uInitrd
   7745856 zImage

7 queue (s), 2 dir (s)
=> mmc read 0 0x7fffffff 1

MMC read: dev # 1, block # 2147483647, count 1 ... MMC: block number 0x80000000 exceeds max (0xe90000)
0 read blocks: ERROR


if i format the eMMC it is a good idea or not

mmc erase 0 0x80000000

thank you so much

Link to comment
Share on other sites

  • 0

Hello

I tried the tutorial https://docs.armbian.com/User-Guide_Recovery/

 

I tried that with the port Debug TTL UART

=> setenv bootargs init = / bin / bash root = / dev / mmcblk0p1 rootwait console = ttyS0,115200
=> ext4load mmc 0 0x49000000 / boot / dtb / $ {fdtfile}
** Unrecognized filesystem type **

I tried that but it's not good too

=> mmc list
mmc @ 1c0f000: 0 (SD)
mmc @ 1c10000: 2
mmc @ 1c11000: 1 (eMMC)

=> mmc dev 0
switch to partitions # 0, OK
mmc0 is current device


=> ls mmc 0 /
  7745856 zImage
  5876450 uInitrd
       86 orangepiEnv.txt
   230456 boot.bmp
     3628 boot.cmd
     3700 boot.scr
  3636584 System.map-pc-plus
            dtb /
            System Volume Information /

7 queue (s), 2 dir (s)


=> ls mmc 0 / dtb /
            ./
            ../
    30557 sun8i-h3-orangepi-pc-sapomat.dtb
    28814 sun8i-h2-plus-orangepi-zero.dtb
    28916 sun8i-h3-orangepi-2.dtb
    30376 sun8i-h3-orangepi-lite.dtb
    30046 sun8i-h3-orangepi-one.dtb
    30628 sun8i-h3-orangepi-pc-plus.dtb
    29462 sun8i-h3-orangepi-zero-plus2.dtb
    30098 sun8i-h3-orangepi-pc.dtb
    29751 sun8i-h3-orangepi-plus.dtb
    31103 sun8i-h3-orangepi-plus2e.dtb

10 queue (s), 2 dir (s)
=> ext4load mmc 0 0x49000000 /boot/dtb/sun8i-h3-orangepi-pc-plus.dtb
** Unrecognized filesystem type **


I think I'm making a mess that isn't good but where ??

 


Thank you so much

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...