Black Panther X2 flashes OpenWrt: TF card can run, but eMMC is "lost"? A brick saving note takes you to revive in place in 10 minutes

1. Phenomenon review

follow the tutorial on the Internet, write openwrt-rk3566-panther-x2-ext4.img to the TF card with Win32DiskImager, power on → the network port light is on→ the computer gets 192.168.1.1 → everything is fine.
wanted to permanently move the system into 32 GB eMMC, so I dd if=xxx.img of=/dev/mmcblk0 bs=1M, and restarted the card without power.
the router indicator flashes wildly for 30 seconds and then stays on, but the computer has not been able to get the IP for a long time, the arp table is empty, and the ttl serial port is only stopped in one line
Waiting for root device PARTUUID=xxxx-xxxx...
After another 10 seconds, the kernel goes directly into initramfs. The network protocol stack did not rise at all - the "eMMC brick" was reached.

2. Why does TF card work, but eMMC does not?

a word: Image writing misalignment + root partition cannot be found → kernel stops initramfs → network protocol stack does not come up→ The computer "cannot find the IP".

3. 30 seconds to determine where the stuck is

TTL Serial port 115200 power-on
- see Hit any key to stop autoboot and keep pressing the space → to enter U-Boot.
- if prompted Card did not respond to voltage select! → the first 4 MiB was flushed, the bootloader is hung.
- if you keep Waiting for root device PARTUUID=... → but the root partition path is wrong, it is easy to fix.
computer network port capture packet capture
only DHCP Discover, no Offer→ network port is not initialized, confirming that "it is not hung to the root".

4. Three-step method of non-destructive brick rescue

(All the following operations are done in "OpenWrt started by TF card", do not write eMMC directly with a PC )

(1) Confirm the eMMC device name

lsblk

output example

mmcblk0 29.1G / ← eMMC mmcblk1 14.9G / ← TF Card

remember whether it's mmcblk0 or mmcblk2, DTS serial numbers can vary from batch to batch.

(2) with 4 MiB offset write mirror

official bootloader 4 MiB, the command must be seek=4:

dd if=/tmp/openwrt-rk3566-panther-x2-ext4.img of=/dev/mmcblk0 bs=1M seek=4 conv=fsync sync poweroff

not writing seek=4 will flush out boot0, really · Brick .

(3) Let the kernel find the root partition

Temporary Law (TTL On-site Change)
Power-on press the space to enter U-Boot:

setenv bootargs 'console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootwait' saveenv reset

permanent method (TF card system modification)
```
mount /dev/mmcblk0p1 /mnt vi /mnt/boot/boot.txt # Change root=PARTUUID=xxxx to root=/dev/mmcblk0p2 mkimage -T script -A arm64 -C none -d /mnt/boot/boot.txt /mnt/boot/boot.scr umount /mnt
```
as long as
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data appears in the serial port mode
the root is successful, and the network port light is on after 5 seconds, and the computer can get 192.168.1.x.

5. Lazy one-click method (no change bootargs)

ophub has provided eMMC dedicated edition image
openwrt-rk3566-panther-x2-ext4-emmc.img.gzHTML176_ The cmdline in it is /dev/mmcblk0p2 by default. Download and work as usual

zcat *.img.gz | dd of=/dev/mmcblk0 bs=1M seek=4 conv=fsync

192.168.100.1 will be released after flashing the power-up, and even TTL will be saved.

6. Obstacle Clearance Quick Inspection Form

7. Summary

"TF card can run" only proves that the image is fine, eMMC 90% of the boot failures are due to image writing misalignment or root partition path error.
keep in mind that "seek=4" write disk + "root=/dev/mmcblk0p2" will be revived in place within ten minutes,
use the 32 GB high-speed eMMC to full use, and say goodbye to the USB flash drive. Happy flashing!

Xiao AiReply

#27

Don't be greedy when flashing, eMMC operation is much more complicated than TF card, one step of mistake is lost, it is recommended that novices still use TF card to test safely to avoid hardware damage.

1 个月前

Idle clouds and w...Reply

#26

Before flashing, I didn't carefully check the image and partition settings, and directly dd to eMMC, which caused the system to fail and the network to fail, which was really a trick. It is recommended that you check more information to avoid stepping on thunder.

2 个月前

And listen to the...Reply

#25

The failure to flash is really devastating, the TF card is still easy to use, but the eMMC is directly "lost", the system startup is stuck in initramfs, and the network is not up, which is really anxious and angry.

Xiao MingReply

#24

I didn't check the parameters carefully before flashing, and I wrote dd directly to eMMC, which caused the system to fail to start, which is really frustrating.

In a single thoughtReply

#23

Don't rush to move the system to eMMC when flashing, it is easy to step on the pit. TF cards can be used, but eMMC operations need to be cautious to ensure that the image is written correctly, otherwise it may directly become bricked, which is really a headache.

Light pickerReply

#22

When flashing, I didn't pay attention to the image writing position, resulting in eMMC not being recognized, which was really a pitfall. It is recommended that novices must confirm the writing parameters to avoid the tragedy of "loss of contact".

3 个月前

Between mountains...Reply

#21

Don't operate blindly when flashing, eMMC writing is prone to errors, especially the incorrect partition settings, resulting in the system not being able to boot, and the network cannot be connected, which is really crashing.

The cool city is ...Reply

#20

The image position of the eMMC written to the computer is wrong, resulting in the system not being able to boot, the network protocol stack not loading, and the computer not being able to obtain the IP, which is really a headache.

Sword courage and...Reply

#19

I didn't pay attention to the image writing position when flashing, which caused the eMMC to fail to start, which is really a pitfall. It is recommended that novices read more tutorials to confirm the writing parameters to avoid similar problems.

Blooming seasonReply

#18

The wrong writing position when flashing causes eMMC to not recognize, which is really a trap! It is recommended that novices always confirm the partition parameters to avoid tragedy.

The stars are the...Reply

#17

When flashing, don't try to be convenient and direct dd, it is easy to write the wrong position to cause eMMC bricks, although the TF card can be used but not stable enough, it is recommended to find a reliable way to transplant the system.

The word "heart" ...Reply

#16

When flashing, be sure to confirm the image writing position, otherwise eMMC may directly become bricked, and you won't be able to get the IP after half an hour, which is really devastating.

Ink paintingReply

#15

You need to be extra careful when writing eMMC when flashing, as the wrong location or partition recognition failure will cause the system to fail to boot, which is really a headache. It is recommended that newbies back up before trying.

The wind stopped ...Reply

#14

I didn't check the image parameters carefully before flashing, and I wrote it directly to eMMC, which caused the system to fail to start, which was really a headache. Fortunately, there is this note, otherwise it may really become a "brick".

Boiling wine and ...Reply

#13

Don't be greedy when flashing, eMMC writing should be extra careful, one wrong step and lose the whole game, it's really collapsing! I hope newcomers can pay attention to the details and avoid stepping on pitfalls.

Black Panther X2 flashes OpenWrt: TF card can run, but eMMC is "lost"? A brick saving note takes you to revive in place in 10 minutes

1. Phenomenon review

2. Why does TF card work, but eMMC does not?

3. 30 seconds to determine where the stuck is

4. Three-step method of non-destructive brick rescue

(1) Confirm the eMMC device name

(2) with 4 MiB offset write mirror

(3) Let the kernel find the root partition

5. Lazy one-click method (no change bootargs)

6. Obstacle Clearance Quick Inspection Form

7. Summary

Comment List

Contact Us

Black Panther X2 flashes OpenWrt: TF card can run, but eMMC is "lost"? A brick saving note takes you to revive in place in 10 minutes

1. Phenomenon review

2. Why does TF card work, but eMMC does not?

3. 30 seconds to determine where the stuck is

4. Three-step method of non-destructive brick rescue

(1) Confirm the eMMC device name

(2) with 4 MiB offset write mirror

(3) Let the kernel find the root partition

5. Lazy one-click method (no change bootargs)

6. Obstacle Clearance Quick Inspection Form

7. Summary

Related Recommendations

Comment List

Contact Us