Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bricked r30gb - no backup but RS232 working #976

Open
Reni2005 opened this issue Dec 11, 2024 · 13 comments
Open

Bricked r30gb - no backup but RS232 working #976

Reni2005 opened this issue Dec 11, 2024 · 13 comments

Comments

@Reni2005
Copy link

Hello, during a storm my camera stopped working, probably due a not correct firmware upgrade. When I connect a RS232 to the camera I get this:

`
▒▒0▒▒▒[38]HELLO! BOOT0 is starting Nov 14 2019 20:01:31!
[43]BOOT0 commit : 81c18ee
[46]board init start
[48]set pll start
[50]set pll end
[52][pmu]: bus read error
[54]board init ok
[56]chip id check OK
[58]DRAM BOOT DRIVE INFO: V0.41
[61]DRAM CLK = 528 MHz
[63]DRAM Type = 2 (2:DDR2,3:DDR3)
[67]DRAMC read ODT off.
[69]DRAM ODT off.
[71]DRAM SIZE =64 M
[78]DRAM simple test OK.
[80]rtc standby flag is 0x0, super standby flag is 0x0
[86]dram size =64
[88]spinor id is: ef 40 17, read cmd: 03
[92]Succeed in reading toc file head.
[96]The size of toc is 4c000.
[149]Entry_name = optee
[152]Entry_name = u-boot
[156]Entry_name = dtb
[159]Jump to secend Boot.
MESSAGE: [0x0] TEE-CORE: OP-TEE version: sun8iw19p1_v0.6.0-12-g97f2688 #1 2019年 11月 08日 星期五 08:26:51 UTC arm
ERROR: [0x0] TEE-CORE:platform_standby_fdt_parse:126: no pmu node
ERROR: [0x0] TEE-CORE:sunxi_twi_parse_from_dt:84: no pmu node

U-Boot 2018.05-00006-g8e30467 (Sep 25 2020 - 18:47:17 +0800) Allwinner Technology

[00.204]DRAM: 64 MiB
[00.207]Relocation Offset is: f9f94000
[00.218]secure enable bit: 0
[00.221]CPU=816 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz MBus=132Mhz
[00.227]gic: sec monitor mode
[00.230]flash init start
[00.232]workmode = 0,storage type = 3
SF: Detected w25q64cv with page size 256 Bytes, erase size 64 KiB, total 8 MiB
[00.249]sunxi flash init ok
[00.252]Loading Environment from SUNXI_FLASH... start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x3e00, len: 0x100
OK
[00.313]try sprite_led_gpio config
xxxxxxxxxxxxxxlijun uboot xiaoyiledinit
[00.320]sprite_led_gpio start
00.323update dtb dram start
[00.328]update dtb dram end
[00.330]update dts
root_partition is rootfs
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
set root to /dev/mtdblock2
[00.393]update part info
[00.395]update bootcmd
mmc driver ver uboot2018:2019-8-15 16:34:00
get mem for descripter OK !
[00.408]get sdc_wipe fail.
[00.410]get sdc0 sdc_erase fail.
[00.413]get sdc0 sdc_boot fail.
[00.416]get sdc0 sdc_odly_50M fail.
[00.419]get sdc0 sdc_sdly_50M fail.
[00.422]get sdc0 sdc_odly_50M_ddr fail.
[00.426]get sdc0 sdc_sdly_50M_ddr fail.
[00.429]get sdc0 sdc_freq fail.
[00.432]get sdc0 sdc_b0p fail.
[00.435]get card0_boot_para:sdc_ex_dly_used fail
[00.440]get card-pwr-gpios handler:1119307304
[00.444]get card0_boot_para:time_pwroff:200ms
[00.450]Using default timing para
[00.652]init mmc 0 clock and io
devnum 0, prv 43fbd410, bdesc 42b7476c
SUNXI SD/MMC: 0
[00.660]==================== work mode: 0 0, sample_mode:0
[00.665]=============== start mmc_init_boot...
[00.684]Card did not respond to voltage select!
[00.688]mmc_init: -95, time 28
[00.690]mmc_init: mmc init fail, err -95
card0 init failed
No sd-card insert,will normal boot
Hit any key to stop autoboot: 0
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
[01.713]partinfo: name boot, start 0x20, size 0xe80
start: 0x300, len: 0x40
start: 0x340, len: 0xe11
[02.162]android.hardware = sun8iw19p1

Booting kernel from Legacy Image at 45000000 ...

Image Name: ARM OpenWrt Linux-4.9.118
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1875936 Bytes = 1.8 MiB
Load Address: 40008000
Entry Point: 40008000
[02.229]Starting kernel ...
`

And doesn't continue. Can I try to flash a backup?
@roleoroleo
Copy link
Owner

The kernel is probably broken.
You could try the unbrick procedure adding the kernel partition (mtdblock1).
https://github.com/roleoroleo/yi-hack-Allwinner-v2/wiki/Unbrick-the-cam

Insert a sd card and try again the boot, you should read a log where the cam tries to find some file inside the card.
I don't remember if the kernel partition can be restored by the bootloader. If not, you should create xiaoyi.onebin

Otherwise, considering that you already have the serial port connected, try the hard way.
But using mtdblock1.

@Reni2005
Copy link
Author

Reni2005 commented Dec 13, 2024 •
edited
Loading

The kernel is probably broken. You could try the unbrick procedure adding the kernel partition (mtdblock1). https://github.com/roleoroleo/yi-hack-Allwinner-v2/wiki/Unbrick-the-cam

Insert a sd card and try again the boot, you should read a log where the cam tries to find some file inside the card. I don't remember if the kernel partition can be restored by the bootloader. If not, you should create xiaoyi.onebin

Otherwise, considering that you already have the serial port connected, try the hard way. But using mtdblock1.

Thank you for the answer. Should I try something like this before?: #270 (comment)

Or in this kind of model I should see directly the kernel?
The camera stopped working after a storm, however if I get a RS232 comunication should it be still recoverable? I mean it dosen't seem "braind3ad".

I'm gonna wait some days before "putting hands on it" because I need another person to keep the "tx" and "rx" cable pressed because there's no screw to open it completely and because of that I cannot solder.

One last question: where should I find a working backup?

Post scriptum:

Insert a sd card and try again the boot, you should read a log where the cam tries to find some file inside the card. I don't remember if the kernel partition can be restored by the bootloader. If not, you should create xiaoyi.onebin

So If I get a backup and make a file with the unbriking tool I can put the created file in the root of a FAT32 sd card and the camera should be able to read it and flash it?

@roleoroleo
Copy link
Owner

Thank you for the answer. Should I try something like this before?: #270 (comment)

You could but probably it's not necessary.

One last question: where should I find a working backup?

When you apply the hack the 1st time, the hack procedure creates a full backup.
You should find it in the backup folder of the sd card. Otherwise, if you know the version of your current fw, I cand send you.
Available versions:

  • 9.0.05.32_202004101552
  • 9.0.05.33_202009251856
  • 9.0.05.99_202011091624
  • 12.1.05.1_202302091435

So If I get a backup and make a file with the unbriking tool I can put the created file in the root of a FAT32 sd card and the camera should be able to read it and flash it?

For the other paritions it works, I never tried the kernel.
Otherwise the hard way: https://github.com/roleoroleo/yi-hack-Allwinner-v2/wiki/Unbrick-the-cam#restore-backup-partition

=> sunxi_card0_probe
=> fatload mmc 0 45000000 mtdblock1.bin
=> sf probe
=> sf erase 60000 1d0000
=> sf write 45000000 60000 1d0000

Where:

  • 45000000 is the address of the location where you copy termporarily the file mtdblock1.bin.
  • 60000 is the offset of the kernel from the flash base
  • 1d0000 is the size of mtdblock1.bin

@Reni2005
Copy link
Author

The camera stopped working before February 9, 2023. I would greatly appreciate it if you could send me the "9.0.05.99_202011091624" backup. However, I am not entirely sure about this version, as it has been a long time since the camera stopped functioning. What might happen if the version is incorrect? Could it result in the kernel working but the boot failing because the "home" partition might have the wrong version?

@roleoroleo
Copy link
Owner

If you don't know exactly the version you must flash mtd1, 2, 3, 4.
archive.tar.gz

@Reni2005
Copy link
Author

Reni2005 commented Dec 15, 2024 •
edited
Loading

If you don't know exactly the version you must flash mtd1, 2, 3, 4. archive.tar.gz

Thank you very much, in these days I'll try.

In short the steps I'm gonna follow if I understood correctly

1) Flash mtd1 via hard way
2) Reset 
3) Insert micro-SD with mtd2,3,4 processed by unbrick tool and read on serial what's happening

I think I'm going to do only mtblock4 the hard way because the wiring is not soldered and the hand goes dizzy 🥴.
If the bootloader is okay the device shouldn't have any hardware damage that would prevent booting?
Gvien that every procedure of flashing has a risk, the bootloader cannot be bricked by flashing these .bin files right?

@roleoroleo
Copy link
Owner

In short the steps I'm gonna follow if I understood correctly

Yes.

If the bootloader is okay the device shouldn't have any hardware damage that would prevent booting?

Yes, if the bootloader is ok you can flash all other partitions.

Gvien that every procedure of flashing has a risk, the bootloader cannot be bricked by flashing these .bin files right?

It depends: with the hard way, if you use wrong addresses, you can overwrite the bootloader.

@Reni2005
Copy link
Author

Reni2005 commented Dec 18, 2024 •
edited by roleoroleo
Loading

In short the steps I'm gonna follow if I understood correctly

Yes.

If the bootloader is okay the device shouldn't have any hardware damage that would prevent booting?

Yes, if the bootloader is ok you can flash all other partitions.

Gvien that every procedure of flashing has a risk, the bootloader cannot be bricked by flashing these .bin files right?

It depends: with the hard way, if you use wrong addresses, you can overwrite the bootloader.

Hello, I'm having difficulties connecting both tx and rx doing it the "hard way". How can I try to flash bootloader via soft way? The ./unbrick.sh factory makes only three files and (backup, rootfs and home) but not the kernel one. Can I try to make it manually? (I can connect tx but the wiring is not stable because I connect an arduino cable directly to the contact without soldering because I cannot tear it down more)

I tried to flash mtd 2 3 4 and gives me an error:

▒[140]HELLO! BOOT0 is starting Nov 14 2019 20:01:31!
[145]BOOT0 commit : 81c18ee
[148]board init start
[150]set pll start
[153]set pll end
[154][pmu]: bus read error
[157]board init ok
[159]chip id check OK
[161]DRAM BOOT DRIVE INFO: V0.41
[164]DRAM CLK = 528 MHz
[166]DRAM Type = 2 (2:DDR2,3:DDR3)
[170]DRAMC read ODT  off.
[172]DRAM ODT off.
[175]DRAM SIZE =64 M
[181]DRAM simple test OK.
[184]rtc standby flag is 0x0, super standby flag is 0x0
[189]dram size =64
[192]spinor id is: ef 40 17, read cmd: 03
[196]Succeed in reading toc file head.
[199]The size of toc is 4c000.
[252]Entry_name        = optee
[255]Entry_name        = u-boot
[260]Entry_name        = dtb
[263]Jump to secend Boot.
MESSAGE: [0x0] TEE-CORE: OP-TEE version: sun8iw19p1_v0.6.0-12-g97f2688 #1 2019年 11月 08日 星期五 08:26:51 UTC arm
ERROR:   [0x0] TEE-CORE:platform_standby_fdt_parse:126: no pmu node
ERROR:   [0x0] TEE-CORE:sunxi_twi_parse_from_dt:84: no pmu node


U-Boot 2018.05-00006-g8e30467 (Sep 25 2020 - 18:47:17 +0800) Allwinner Technology

[00.308]DRAM:  64 MiB
[00.311]Relocation Offset is: f9f94000
[00.322]secure enable bit: 0
[00.325]CPU=816 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz  MBus=132Mhz
[00.331]gic: sec monitor mode
[00.333]flash init start
[00.336]workmode = 0,storage type = 3
SF: Detected w25q64cv with page size 256 Bytes, erase size 64 KiB, total 8 MiB
[00.352]sunxi flash init ok
[00.356]Loading Environment from SUNXI_FLASH... start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x3e00, len: 0x100
OK
[00.416]try sprite_led_gpio config
xxxxxxxxxxxxxxlijun uboot xiaoyiledinit
[00.424]sprite_led_gpio start
[00.427](weak)update dtb dram start
[00.431]update dtb dram  end
[00.434]update dts
root_partition is rootfs
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
set root to /dev/mtdblock2
[00.497]update part info
[00.499]update bootcmd
mmc driver ver uboot2018:2019-8-15 16:34:00
get mem for descripter OK !
[00.512]get sdc_wipe fail.
[00.514]get sdc0 sdc_erase fail.
[00.517]get sdc0 sdc_boot fail.
[00.520]get sdc0 sdc_odly_50M fail.
[00.523]get sdc0 sdc_sdly_50M fail.
[00.526]get sdc0 sdc_odly_50M_ddr fail.
[00.530]get sdc0 sdc_sdly_50M_ddr fail.
[00.533]get sdc0 sdc_freq fail.
[00.536]get sdc0 sdc_b0p fail.
[00.539]get card0_boot_para:sdc_ex_dly_used fail
[00.544]get card-pwr-gpios handler:1119307304
[00.548]get card0_boot_para:time_pwroff:200ms
[00.553]Using default timing para
[00.756]init mmc 0 clock and io
devnum 0, prv 43fbd410, bdesc 42b7476c
SUNXI SD/MMC: 0
[00.764]==================== work mode: 0 0, sample_mode:0
**[00.769]=============== start mmc_init_boot...
card_caps:0x3000000a
host_caps:0x3000003f
[00.887]unable to read ssr
[00.890]unable to read ssr
[00.894]the mode SD Legacy (freq : 25 MHz)
 Unrecognized filesystem type 
check_file [/one_r30gb.bin] exsit
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
part_name:boot start_offset:0x20 part_size:1900544
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
part_name:rootfs start_offset:0xea0 part_size:1179648
 (10.5 MiB/s)
file_name /rootfs_r30gb read image[2] size:1179712
## image[2] bad data checksum
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
part_name:home start_offset:0x17a0 part_size:3407872
 (10.7 MiB/s)
file_name /home_r30gb read image[3] size:3407936
## image[3] bad data checksum
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
part_name:backup start_offset:0x31a0 part_size:1245184
 (10.5 MiB/s)
file_name /backup_r30gb read image[4] size:1245248
## image[4] bad data checksum
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
part_name:env start_offset:0x3b20 part_size:131072
Nothing updated, start normal boot**
Hit any key to stop autoboot:  0
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
[02.623]partinfo: name boot, start 0x20, size 0xe80
start: 0x300, len: 0x40
start: 0x340, len: 0xe11
[03.072]android.hardware = sun8iw19p1
## Booting kernel from Legacy Image at 45000000 ...
   Image Name:   ARM OpenWrt Linux-4.9.118
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1875936 Bytes = 1.8 MiB
   Load Address: 40008000
   Entry Point:  40008000
[03.139]Starting kernel ...

image

This is the root of my SD. I unpacked all tar.gz made by ./unbrick.sh factory in the sd card. Did I make some procedure wrong?

EDIT
I was thinking, can I build a .sh script in the micro sd root to run it via RS232? in this way I'd sure to not miss characters while writing commands on an unstable channel

@roleoroleo
Copy link
Owner

The problem is: "bad data checksum" but I don't know why it happens.
Are you sure that the files are created without errors when you run build.sh?

I was thinking, can I build a .sh script in the micro sd root to run it via RS232? in this way I'd sure to not miss characters while writing commands on an unstable channel

You can run a shell command only if kernel and rootfs are running properly.

Please try my files:
archive2.tar.gz

@Reni2005
Copy link
Author

Hello, I tried both ways (soft and hard).

`U-Boot 2018.05-00006-g8e30467 (Sep 25 2020 - 18:47:17 +0800) Allwinner Technology

[00.295]DRAM: 64 MiB
[00.298]Relocation Offset is: f9f94000
[00.309]secure enable bit: 0
[00.312]CPU=816 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz MBus=132Mhz
[00.318]gic: sec monitor mode
[00.321]flash init start
[00.323]workmode = 0,storage type = 3
SF: Detected w25q64cv with page size 256 Bytes, erase size 64 KiB, total 8 MiB
[00.339]sunxi flash init ok
[00.343]Loading Environment from SUNXI_FLASH... start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x3e00, len: 0x100
OK
[00.404]try sprite_led_gpio config
xxxxxxxxxxxxxxlijun uboot xiaoyiledinit
[00.411]sprite_led_gpio start
00.414update dtb dram start
[00.419]update dtb dram end
[00.421]update dts
root_partition is rootfs
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
set root to /dev/mtdblock2
[00.484]update part info
[00.486]update bootcmd
mmc driver ver uboot2018:2019-8-15 16:34:00
get mem for descripter OK !
[00.499]get sdc_wipe fail.
[00.501]get sdc0 sdc_erase fail.
[00.504]get sdc0 sdc_boot fail.
[00.507]get sdc0 sdc_odly_50M fail.
[00.510]get sdc0 sdc_sdly_50M fail.
[00.513]get sdc0 sdc_odly_50M_ddr fail.
[00.517]get sdc0 sdc_sdly_50M_ddr fail.
[00.520]get sdc0 sdc_freq fail.
[00.523]get sdc0 sdc_b0p fail.
[00.526]get card0_boot_para:sdc_ex_dly_used fail
[00.531]get card-pwr-gpios handler:1119307304
[00.535]get card0_boot_para:time_pwroff:200ms
[00.540]Using default timing para
[00.743]init mmc 0 clock and io
devnum 0, prv 43fbd410, bdesc 42b7476c
SUNXI SD/MMC: 0
[00.751]==================== work mode: 0 0, sample_mode:0
[00.756]=============== start mmc_init_boot...
card_caps:0x3000000a
host_caps:0x3000003f
[00.863]unable to read ssr
[00.866]unable to read ssr
[00.870]the mode SD Legacy (freq : 25 MHz)
** Unrecognized filesystem type **
check_file [/one_r30gb.bin] exsit
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
part_name:boot start_offset:0x20 part_size:1900544
(10.7 MiB/s)
file_name /kernel_r30gb read image[1] size:1900608
image[1] wrong type
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
part_name:rootfs start_offset:0xea0 part_size:1179648
(10.4 MiB/s)
file_name /rootfs_r30gb read image[2] size:1179712
image[2] bad data checksum
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
part_name:home start_offset:0x17a0 part_size:3407872
(10.8 MiB/s)
file_name /home_r30gb read image[3] size:3407936
image[3] bad data checksum
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
part_name:backup start_offset:0x31a0 part_size:1245184
(10.6 MiB/s)
file_name /backup_r30gb read image[4] size:1245248
image[4] bad data checksum
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
part_name:env start_offset:0x3b20 part_size:131072
Nothing updated, start normal boot
Hit any key to stop autoboot: 0
=> help
? - alias for 'help'
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootm - boot application image from memory
env - environment handling commands
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
fatsize - determine a file's size
fatwrite- write file into a dos filesystem
fdt - flattened device tree utility commands
help - print command description/usage
mmc - MMC sub system
mmcinfo - display MMC info
part_update- part_update
printenv- print environment variables
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv - set environment variables
sf - SPI flash sub-system
source - run script from memory
sunxi_card0_probe- probe sunxi card0 device
sunxi_flash- sunxi_flash sub-system
version - print monitor, compiler and linker version
=> sunxi_card0_probe
Unknown command 'sunxi__card0_probe' - try 'help'
=> sunxi
Unknown command 'ssunxi' - try 'help'
=> sunxi_card0_probe
card0 has inited
=>
=>
=> fatload mmc 0 45000000 mtdblock1.bin
1900544 bytes read in 169 ms (10.7 MiB/s)
=> sf probe
sf: bus-0 cs-0 spedd-50000000Hz mode-3000
SF: Detected w25q64cv with page size 256 Bytes, erase size 64 KiB, total 8 MiB
=> sf erase 60000 1d0000
SF: 1900544 bytes @ 0x60000 Erased: OK
=> sf write 45000000 60000 1d0000
device 0 offset 0x60000, size 0x1d0000
SF: 1900544 bytes @ 0x60000 time:3204 ms Written: OK
=> reset
resetting ...
[43]HELLO! BOOT0 is starting Nov 14 2019 20:01:31!
[48]BOOT0 commit : 81c18ee
[51]board init start
[53]set pll start
[55]set pll end
[57][pmu]: bus read error
[59]board init ok
[61]chip id check OK
[63]DRAM BOOT DRIVE INFO: V0.41
[66]DRAM CLK = 528 MHz
[69]DRAM Type = 2 (2:DDR2,3:DDR3)
[72]DRAMC read ODT off.
[74]DRAM ODT off.
[77]DRAM SIZE =64 M
[83]DRAM simple test OK.
[86]rtc standby flag is 0x0, super standby flag is 0x0
[91]dram size =64
[93]spinor id is: ef 40 17, read cmd: 03
[97]Succeed in reading toc file head.
[101]The size of toc is 4c000.
[154]Entry_name = optee
[157]Entry_name = u-boot
[161]Entry_name = dtb
[164]Jump to secend Boot.
MESSAGE: [0x0] TEE-CORE: OP-TEE version: sun8iw19p1_v0.6.0-12-g97f2688 #1 2019年 11月 08日 星期五 08:26:51 UTC arm
ERROR: [0x0] TEE-CORE:platform_standby_fdt_parse:126: no pmu node
ERROR: [0x0] TEE-CORE:sunxi_twi_parse_from_dt:84: no pmu node

U-Boot 2018.05-00006-g8e30467 (Sep 25 2020 - 18:47:17 +0800) Allwinner Technology

[00.209]DRAM: 64 MiB
[00.212]Relocation Offset is: f9f94000
[00.223]secure enable bit: 0
[00.226]CPU=816 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz MBus=132Mhz
[00.232]gic: sec monitor mode
[00.235]flash init start
[00.237]workmode = 0,storage type = 3
SF: Detected w25q64cv with page size 256 Bytes, erase size 64 KiB, total 8 MiB
[00.254]sunxi flash init ok
[00.257]Loading Environment from SUNXI_FLASH... start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x3e00, len: 0x100
OK
[00.318]try sprite_led_gpio config
xxxxxxxxxxxxxxlijun uboot xiaoyiledinit
[00.325]sprite_led_gpio start
00.328update dtb dram start
[00.333]update dtb dram end
[00.335]update dts
root_partition is rootfs
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
set root to /dev/mtdblock2
[00.398]update part info
[00.400]update bootcmd
mmc driver ver uboot2018:2019-8-15 16:34:00
get mem for descripter OK !
[00.413]get sdc_wipe fail.
[00.415]get sdc0 sdc_erase fail.
[00.418]get sdc0 sdc_boot fail.
[00.421]get sdc0 sdc_odly_50M fail.
[00.424]get sdc0 sdc_sdly_50M fail.
[00.427]get sdc0 sdc_odly_50M_ddr fail.
[00.431]get sdc0 sdc_sdly_50M_ddr fail.
[00.434]get sdc0 sdc_freq fail.
[00.437]get sdc0 sdc_b0p fail.
[00.440]get card0_boot_para:sdc_ex_dly_used fail
[00.445]get card-pwr-gpios handler:1119307304
[00.449]get card0_boot_para:time_pwroff:200ms
[00.455]Using default timing para
[00.658]init mmc 0 clock and io
devnum 0, prv 43fbd410, bdesc 42b7476c
SUNXI SD/MMC: 0
[00.665]==================== work mode: 0 0, sample_mode:0
[00.670]=============== start mmc_init_boot...
card_caps:0x3000000a
host_caps:0x3000003f
[00.801]unable to read ssr
[00.804]unable to read ssr
[00.808]the mode SD Legacy (freq : 25 MHz)
** Unrecognized filesystem type **
check_file [/one_r30gb.bin] exsit
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
part_name:boot start_offset:0x20 part_size:1900544
(10.7 MiB/s)
file_name /kernel_r30gb read image[1] size:1900608
image[1] wrong type
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
part_name:rootfs start_offset:0xea0 part_size:1179648
(10.4 MiB/s)
file_name /rootfs_r30gb read image[2] size:1179712
image[2] bad data checksum
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
part_name:home start_offset:0x17a0 part_size:3407872
(10.8 MiB/s)
file_name /home_r30gb read image[3] size:3407936
image[3] bad data checksum
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
part_name:backup start_offset:0x31a0 part_size:1245184
(10.6 MiB/s)
file_name /backup_r30gb read image[4] size:1245248
image[4] bad data checksum
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
part_name:env start_offset:0x3b20 part_size:131072
Nothing updated, start normal boot
Hit any key to stop autoboot: 0
start: 0x2e0, len: 0x1
start: 0x2e1, len: 0x1
start: 0x2e2, len: 0x2
[02.696]partinfo: name boot, start 0x20, size 0xe80
start: 0x300, len: 0x40
start: 0x340, len: 0xe12
[03.173]android.hardware = sun8iw19p1

Booting kernel from Legacy Image at 45000000 ...

Image Name: ARM OpenWrt Linux-4.9.118
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1876616 Bytes = 1.8 MiB
Load Address: 40008000
Entry Point: 40008000
[03.240]Starting kernel ...

`

I don’t understand why I had to manually write "sunxi_card0_probe". However, rebooting didn’t resolve the issue; it’s still stuck at "Starting Kernel." The camera doesn’t even flash the partitions you sent me giving me the same error (except with the kernel where i get a "image[1] wrong type").

Could I have provided the wrong model? Here is a picture of the external board:
photo_2024-12-23_12-37-04 -

In case it’s helpful, here is a picture of my SD card's root folder:
image

@roleoroleo
Copy link
Owner

I'm not sure about the kernel, is the only partition I never restored.
The model is ok, it looks for *_r30gb files.
I think the only way is the hard way.

@Reni2005
Copy link
Author

Did I filash mtd 1 correctly? It stil doesn't boot after that

@roleoroleo
Copy link
Owner

Try to flash other partitions: rootfs, home and backup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@roleoroleo @Reni2005