Meraki MR33 : Wrong Image Format for bootm command

USB BDM software. Bug report.
Post Reply
mark4545
Junior Member
Posts: 5
Joined: Tue May 28, 2019 9:21 pm

Meraki MR33 : Wrong Image Format for bootm command

Post by mark4545 »

All seems to go well, following your video guide to the letter, but it ends with the device in a boot loop.

I've tried the scripted and manual methods with the same results.

Am I doing something wrong?

Code: Select all

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----        28/07/2021     22:31            851 mr33.usp
-a----        28/07/2021     22:31      125435904 ubimr33.bin
-a----        28/07/2021     22:31        2162688 ubootmr332012.bin

Code: Select all

U-Boot 2017.07-RELEASE-g78ed34f31579 (Sep 29 2017 - 07:43:44 -0700)

DRAM:  242 MiB
machid : 0x8010001
Product: meraki_Stinkbug
NAND:  ONFI device found
ID = 1d80f101
Vendor = 1
Device = f1
128 MiB
Using default environment

In:    serial
Out:   serial
Err:   serial
machid: 8010001
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: attached mtd1 (name "mtd=0", size 115 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 456, bad PEBs: 464, corrupted PEBs: 0
ubi0: user volume: 6, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 35/16, WL threshold: 4096, image sequence number: 2086049366
ubi0: available PEBs: 11, total reserved PEBs: 445, PEBs reserved for bad PEB handling: 0
Read 0 bytes from volume part.safe to 84000000
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Read 0 bytes from volume part.old to 84000000
Wrong Image Format for bootm command
ERROR: can't get kernel image!
resetting ...

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1.1-00096
S - IMAGE_VARIANT_STRING=DAACANAZA
S - OEM_IMAGE_VERSION_STRING=CRM
S - Boot Config, 0x00000025
S - Core 0 Frequency, 0 MHz
B -       261 - PBL, Start
B -      1339 - bootable_media_detect_entry, Start
B -      2609 - bootable_media_detect_success, Start
B -      2623 - elf_loader_entry, Start
B -      4030 - auth_hash_seg_entry, Start
B -      6179 - auth_hash_seg_exit, Start
B -     73719 - elf_segs_hash_verify_entry, Start
B -    194080 - PBL, End
B -    194104 - SBL1, Start
B -    282736 - pm_device_init, Start
D -         6 - pm_device_init, Delta
B -    284261 - boot_flash_init, Start
D -     87402 - boot_flash_init, Delta
B -    375711 - boot_config_data_table_init, Start
D -     13987 - boot_config_data_table_init, Delta - (419 Bytes)
B -    392391 - clock_init, Start
D -      7584 - clock_init, Delta
B -    403379 - CDT version:2,Platform ID:8,Major ID:1,Minor ID:0,Subtype:1
B -    406865 - sbl1_ddr_set_params, Start
B -    411851 - cpr_init, Start
D -         2 - cpr_init, Delta
B -    416341 - Pre_DDR_clock_init, Start
D -         5 - Pre_DDR_clock_init, Delta
D -     13142 - sbl1_ddr_set_params, Delta
B -    429621 - pm_driver_init, Start
D -         2 - pm_driver_init, Delta
B -    500252 - sbl1_wait_for_ddr_training, Start
D -        27 - sbl1_wait_for_ddr_training, Delta
B -    515781 - Image Load, Start
D -    140732 - QSEE Image Loaded, Delta - (262104 Bytes)
B -    657011 - Image Load, Start
D -      2119 - SEC Image Loaded, Delta - (2048 Bytes)
B -    667173 - Image Load, Start
D -    123225 - APPSBL Image Loaded, Delta - (285640 Bytes)
B -    790821 - QSEE Execution, Start
D -        56 - QSEE Execution, Delta
B -    796993 - SBL1, End
D -    604969 - SBL1, Delta
S - Flash Throughput, 1993 KB/s  (550211 Bytes,  275935 us)
S - DDR Frequency, 672 MHz
usbbdm
Junior Member
Posts: 8760
Joined: Mon Jul 18, 2005 9:33 pm

Re: Meraki MR33 : Wrong Image Format for bootm command

Post by usbbdm »

Looks like you did not modify the boot rom.
I can help you via zoom remote desktop.
It is better if you have your original backup.
mark4545
Junior Member
Posts: 5
Joined: Tue May 28, 2019 9:21 pm

Re: Meraki MR33 : Wrong Image Format for bootm command

Post by mark4545 »

When you say "boot rom" are you referring to the u-boot?

I can do a zoom session, I'm in the UK but don't know your time zone. Next 2 hours are ok if that works for you?
usbbdm
Junior Member
Posts: 8760
Joined: Mon Jul 18, 2005 9:33 pm

Re: Meraki MR33 : Wrong Image Format for bootm command

Post by usbbdm »

Just saw your message and it might be too late for you. Come to main page and see if I am online so we can chat.
mark4545
Junior Member
Posts: 5
Joined: Tue May 28, 2019 9:21 pm

Re: Meraki MR33 : Wrong Image Format for bootm command

Post by mark4545 »

Looks like I've missed you.

I've tried to do it in pieces and u-boot seems to always fail on the first block

Code: Select all

-flshdct 0
Found Address= 00000000 S34ML01G100TF100
-erase u-boot
Erase starts...
Erase time 00:00:00 (.026)
Program Starts...
Program speed 4881.91 KB/s
Program time 00:00:00 (.443)
Program pass, if no further programming needed, power off/on the target
-cmpram u-boot
Time 00:00:02 (.258)
Compare data Failed address 738000,target 00,PC memory 7F
usbbdm
Junior Member
Posts: 8760
Joined: Mon Jul 18, 2005 9:33 pm

Re: Meraki MR33 : Wrong Image Format for bootm command

Post by usbbdm »

Do you have your own backup?
Try to read u-boot back and see what is in there. Might be a bad sector
usbbdm
Junior Member
Posts: 8760
Joined: Mon Jul 18, 2005 9:33 pm

Re: Meraki MR33 : Wrong Image Format for bootm command

Post by usbbdm »

If your u-boot has bad sector program to back up of the u-boot.
mark4545
Junior Member
Posts: 5
Joined: Tue May 28, 2019 9:21 pm

Re: Meraki MR33 : Wrong Image Format for bootm command

Post by mark4545 »

The device worked fine before I started playing with it.

I did take a backup using the script and I've tried to restore it (with script) but the device will not boot
mark4545
Junior Member
Posts: 5
Joined: Tue May 28, 2019 9:21 pm

Re: Meraki MR33 : Wrong Image Format for bootm command

Post by mark4545 »

I did manage to restore the backup and verify it but the device seems still bricked

Code: Select all

-flshdct 0
Found Address= 00000000 S34ML01G100TF100
-erase 0 8400000
Erase starts...
Erase time 00:00:01 (.674)
Program Starts...
Program speed 947.74 KB/s
Program time 00:02:26 (.044)
Program pass, if no further programming needed, power off/on the target
-flshdct 0
Found Address= 00000000 S34ML01G100TF100
-cmpram 0 8400000
Time 00:02:17 (.998)
Compare data OK
usbbdm
Junior Member
Posts: 8760
Joined: Mon Jul 18, 2005 9:33 pm

Re: Meraki MR33 : Wrong Image Format for bootm command

Post by usbbdm »

Just come to the main site and chat with me.
usbbdm
Junior Member
Posts: 8760
Joined: Mon Jul 18, 2005 9:33 pm

Re: Meraki MR33 : Wrong Image Format for bootm command

Post by usbbdm »

The problem is solved. The initial issue is there is contact issue so the backup was bad. After restore back up from my working openwrt nand everything is working.
Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests