MR33 Detection Issues

This forum discuss about how to JTAG different devices.
Post Reply
bearot99
Junior Member
Posts: 1
Joined: Wed Oct 20, 2021 3:05 pm

MR33 Detection Issues

Post by bearot99 »

Trying to follow the instructions listed here https://www.youtube.com/watch?v=8nCkiAG1Dsw, but I could not get the software to detect the chip on my MR33 (Version 2017.7).

I have the u-link NAND connected to my windows 10 PC along with the 360 clip + 48PIN connector (from Aliexpress)
This is what I got from the usbjtag software (version 1.24 and activated)
-flshdct 0
Unknown flash type!
Report these values http://www.usbjtag.com/phpbb3 00h,00h,00h,00h

The chip says
S34ML01G200TFV00
740BB820 A
C12 SPANSION

Could you please let me know what my next step would be?

Thanks in advance. :D
usbbdm
Junior Member
Posts: 8797
Joined: Mon Jul 18, 2005 9:33 pm

Re: MR33 Detection Issues

Post by usbbdm »

When all 00, it has connection issue. Try to press down firmly.
bearot99
Junior Member
Posts: 1
Joined: Wed Oct 20, 2021 3:05 pm

Re: MR33 Detection Issues

Post by bearot99 »

Thanks for your respond.

I heard the click sound, and I saw the connector is fully attached with the Tsop 48 chip. U-link Nand and the 360 clip are all brand new from the box (Well, I ordered the Nand first, and the 360 clip took 2 months to arrive).

I use a Fluke 12B multimeter to test out all 48 pins in the 360 clip connector, and they are all good.

Please review the image attached for more information.

https://drive.google.com/file/d/1SZuEtY7xf2CV485EJDor7bVAvUV24TSj/view?usp=sharing

Would you please let me know what I can try next?

Thanks
usbbdm
Junior Member
Posts: 8797
Joined: Mon Jul 18, 2005 9:33 pm

Re: MR33 Detection Issues

Post by usbbdm »

Clip does not mean you have enough contact. Keep pressing it and hit detect to see if you get non 0 return.
bearot99
Junior Member
Posts: 1
Joined: Wed Oct 20, 2021 3:05 pm

Re: MR33 Detection Issues

Post by bearot99 »

Problem is resolved for this topic, you must press firmly to make sure the good connection.

I do have another issue when flashing the MR33. I followed the process that you showed on YouTube, the device stuck at the boot loop once U-boot and ubi were flashed.

Code: Select all

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 -       262 - PBL, Start
B -      1342 - bootable_media_detect_entry, Start
B -      2627 - bootable_media_detect_success, Start
B -      2642 - elf_loader_entry, Start
B -      4057 - auth_hash_seg_entry, Start
B -      6239 - auth_hash_seg_exit, Start
B -     71315 - elf_segs_hash_verify_entry, Start
B -    193432 - PBL, End
B -    193456 - SBL1, Start
B -    282274 - pm_device_init, Start
D -         6 - pm_device_init, Delta
B -    283813 - boot_flash_init, Start
D -     88277 - boot_flash_init, Delta
B -    376150 - boot_config_data_table_init, Start
D -     14113 - boot_config_data_table_init, Delta - (419 Bytes)
B -    392972 - clock_init, Start
D -      7588 - clock_init, Delta
B -    403970 - CDT version:2,Platform ID:8,Major ID:1,Minor ID:0,Subtype:1
B -    407457 - sbl1_ddr_set_params, Start
B -    412440 - cpr_init, Start
D -         2 - cpr_init, Delta
B -    416930 - Pre_DDR_clock_init, Start
D -         5 - Pre_DDR_clock_init, Delta
D -     13141 - sbl1_ddr_set_params, Delta
B -    430209 - pm_driver_init, Start
D -         2 - pm_driver_init, Delta
B -    500732 - sbl1_wait_for_ddr_training, Start
D -        27 - sbl1_wait_for_ddr_training, Delta
B -    516464 - Image Load, Start
D -    140799 - QSEE Image Loaded, Delta - (262104 Bytes)
B -    657760 - Image Load, Start
D -      2119 - SEC Image Loaded, Delta - (2048 Bytes)
B -    667917 - Image Load, Start
D -    123274 - APPSBL Image Loaded, Delta - (285640 Bytes)
B -    791615 - QSEE Execution, Start
D -        56 - QSEE Execution, Delta
B -    797772 - SBL1, End
D -    606502 - SBL1, Delta
S - Flash Throughput, 1992 KB/s  (550211 Bytes,  276170 us)
S - DDR Frequency, 672 MHz


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: 696, bad PEBs: 224, corrupted PEBs: 0
ubi0: user volume: 5, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 725/329, WL threshold: 4096, image sequence number: 2086049366
ubi0: available PEBs: 257, total reserved PEBs: 439, 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 -       262 - PBL, Start
B -      1342 - bootable_media_detect_entry, Start
B -      2628 - bootable_media_detect_success, Start
B -      2642 - elf_loader_entry, Start
B -      4057 - auth_hash_seg_entry, Start
B -      6239 - auth_hash_seg_exit, Start
B -     71315 - elf_segs_hash_verify_entry, Start
B -    193431 - PBL, End
B -    193455 - SBL1, Start
B -    282274 - pm_device_init, Start
D -         6 - pm_device_init, Delta
B -    283813 - boot_flash_init, Start
D -     88277 - boot_flash_init, Delta
B -    376150 - boot_config_data_table_init, Start
D -     14113 - boot_config_data_table_init, Delta - (419 Bytes)
B -    392972 - clock_init, Start
D -      7572 - clock_init, Delta
B -    403954 - CDT version:2,Platform ID:8,Major ID:1,Minor ID:0,Subtype:1
B -    407441 - sbl1_ddr_set_params, Start
B -    412426 - cpr_init, Start
D -         2 - cpr_init, Delta
B -    416916 - Pre_DDR_clock_init, Start
D -         5 - Pre_DDR_clock_init, Delta
D -     13144 - sbl1_ddr_set_params, Delta
B -    430198 - pm_driver_init, Start
D -         2 - pm_driver_init, Delta
B -    500904 - sbl1_wait_for_ddr_training, Start
D -        27 - sbl1_wait_for_ddr_training, Delta
B -    516429 - Image Load, Start
D -    140675 - QSEE Image Loaded, Delta - (262104 Bytes)
B -    657603 - Image Load, Start
D -      2118 - SEC Image Loaded, Delta - (2048 Bytes)
B -    667763 - Image Load, Start
D -    123142 - APPSBL Image Loaded, Delta - (285640 Bytes)
B -    791330 - QSEE Execution, Start
D -        56 - QSEE Execution, Delta
B -    797488 - SBL1, End
D -    606219 - SBL1, Delta
S - Flash Throughput, 1994 KB/s  (550211 Bytes,  275909 us)
S - DDR Frequency, 672 MHz


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: 696, bad PEBs: 224, corrupted PEBs: 0
ubi0: user volume: 5, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 725/329, WL threshold: 4096, image sequence number: 2086049366
ubi0: available PEBs: 257, total reserved PEBs: 439, 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 -       262 - PBL, Start

I found this post on the community here, and it still does not work as expected.
http://mail.usbjtag.com/phpbb3/viewtopic.php?t=9832

The flash process went well, and I did not receive any errors. However, I got an error when I tried to verify it. Similar to the previous post, would you please provide a working openwrt nand dump for me? Appreciated it!

Code: Select all

/////////////////////////////////////////////
//    Meraki MR33
/////////////////////////////////////////////
1. Backup flash 
2. Restore flash 
3. program openwrt 
4. Exit 
Please select
4
Script finished
-cmpram 0 8400000
[u]Compare data Failed address 0,target D1,PC memory FF[/u]
Time 00:02:37 (.123)
usbbdm
Junior Member
Posts: 8797
Joined: Mon Jul 18, 2005 9:33 pm

Re: MR33 Detection Issues

Post by usbbdm »

How can I share the file?
I think during the programming your connection getting loose. Did you make good backup?
bearot99
Junior Member
Posts: 1
Joined: Wed Oct 20, 2021 3:05 pm

Re: MR33 Detection Issues

Post by bearot99 »

I have tried the backup, the process went through without any issues, but the unit stuck at the boot loop. So I think my backup is also bad due to the poor connection...
I tried to repeat the flash processes on the video, and it went back to the same error again.

Code: Select all

Compare data Failed address 0,target D1,PC memory FF
Should I try to flash them again? What else should I try next? Thanks
usbbdm
Junior Member
Posts: 8797
Joined: Mon Jul 18, 2005 9:33 pm

Re: MR33 Detection Issues

Post by usbbdm »

https://drive.google.com/file/d/1NKrqq1myi9ib093dZ03bTdheTv74Xuj_/view?usp=sharing
Try this whole backup. It should get your router back to life but might not have the openwrt on it.
bearot99
Junior Member
Posts: 1
Joined: Wed Oct 20, 2021 3:05 pm

Re: MR33 Detection Issues

Post by bearot99 »

Happy New Year! Thanks for sharing this with me. I tried this whole backup with option 2 (restore backup) on your script. Now I can't see anything from the UART terminal. Do you know what might be happening?

USBJTAG Window Outputs

Code: Select all

Please select the original flash file from backup 
-ldram 0
G:/Meraki/MR33/mr33/backup00.bin loaded
programing... 
-erase 0 8400000
Erase starts...
Erase time 00:00:01 (.640)
-sprogram 0 8400000
Program Starts...
Program speed 576.67 KB/s
Program time 00:04:00 (.019)
Program pass, if no further programming needed, power off/on the target
Press enter to continue.Spacebar and enter to break....
-flshdct 0
Found Address= 00000000 S34ML01G100TF100
-cmpram u-boot
Time 00:00:02 (.623)
Compare data OK
Exit Script
Terminal Outputs

Code: Select all

K▒▒▒▒-
▒▒▒B▒|▒2▒@▒8▒▒▒▒▒p▒▒p▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒

usbbdm
Junior Member
Posts: 8797
Joined: Mon Jul 18, 2005 9:33 pm

Re: MR33 Detection Issues

Post by usbbdm »

Your backup is bad. Especially the boot.
bearot99
Junior Member
Posts: 1
Joined: Wed Oct 20, 2021 3:05 pm

Re: MR33 Detection Issues

Post by bearot99 »

The backup file I used was from your google drive with your MR33 script. Is this the correct way to restore the backup? Is there any way to check the connection quality between the nand link and the chip? Thanks
usbbdm
Junior Member
Posts: 8797
Joined: Mon Jul 18, 2005 9:33 pm

Re: MR33 Detection Issues

Post by usbbdm »

Come to the main site and chat with me. I can help you via zoom remote desktop.
bearot99
Junior Member
Posts: 1
Joined: Wed Oct 20, 2021 3:05 pm

Re: MR33 Detection Issues

Post by bearot99 »

Thank you so much for all your help. I have successfully flashed the MR33. The 360 clip from Aliexpress needs some extra work to make good contact with the NAND chip (Use a really fine needle to push the contact pin out, and press & hold firmly during the flash process).

Good luck!
Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests