SDM3045X to SDM3055X-E "Improvement" Thread

[vileslide]

Try formatting the smallest (preferably name brand) USB drive you have with this utility: https://www.sdcard.org/downloads/formatter/

Yes to your questions- if you can get the recovery to work, and downgrade to the correct firmware, then you should be able to proceed as normal with the conversion.

Whether or not that works with your hardware version is a good question, and if it doesn't, then run the recovery package again.

Thanks - I'll get some smaller USB sticks tomorrow, my friends have 1GB and 4GB ones.

Siglent Support says downgrading is possible and the manual for the recovery package says the maximum supported size is 8GB.

Should I turn "CHS format size adjustment" on when formatting the drives?

[KungFuJosh]

I usually just do a quick format. You can try whatever you want and see if it works.

[vileslide]

 

I've been at this for 2 hours again - Firmware updates won't work, even when using the verified 64GB Stick and the currently installed firmware (it was sent to me by Siglent)

I'm now formatting USB drives with small capacities again, this time to 8KB FAT32, to see if that works. So far I wasn't able to get into recovery mode.

 

[KungFuJosh]

That list of flash drives was tested mostly on oscilloscopes for regular use, not necessarily recovery.

You want smaller FAT or FAT32 flash drives, with probably 4k clusters at most for recovery. I'm pretty sure I used the annoying 32GB flash drive for recovery on my SDM3045X.

But, again, your big issue is that your firmware has that 02 in it. Did Siglent send you a firmware version with 02 in the version number?

[vileslide]

You want smaller FAT or FAT32 flash drives, with probably 4k clusters at most for recovery. I'm pretty sure I used the annoying 32GB flash drive for recovery on my SDM3045X.

But, again, your big issue is that your firmware has that 02 in it. Did Siglent send you a firmware version with 02 in the version number?

Oh, that would have been good to know previously - I tried a 64GB drive for firmware flashing, but it keeps failing.



Yes Siglent sent me that Firmware - if I try to upgrade to it, I just get the "upgrade fail". Not sure what to make of it.

Edit: To be clear, I now have the .ads file of the firmware my dmm is currently on. I'm now formatting the drives back to 4KB.

[KungFuJosh]

Which 64GB drive did you get? If it's one I have, I can try recovery on mine with it.

Have you tried the SD formatter utility I linked? (only useful on 32GB or smaller though)

[vileslide]

I got these two:

Kingston DataTraveler Micro USB Stick 64GB 200MB/s Metall USB 3.2 Gen 1 - DTMC3G2/64GB

Kingston DataTraveler Exodia M USB Stick 3.2 Gen 1 DTXM/128GB

I tried your tool, but it didn't work. But, good news! I found someone selling a sealed Kingston 4GB drive in my town for 3€. Gonna pick it up and see if that works.


So far I tested the 64GB Stick, a Platinum 4GB, a 1GB no name, a 8GB PNY and another 8GB no name. Also 16GB and 32GB no name - all of them are recognised by the DMM, with them blinking at boot time, but updates/downgrades always fail and the recovery utility won't start.

[KungFuJosh]

Kingston DataTraveler Micro USB Stick 64GB 200MB/s Metall USB 3.2 Gen 1 - DTMC3G2/64GB

That drive worked fine for me to run recovery. Now I need to upgrade my meter again.

It's formatted FAT32, but I don't remember what I formatted it with. Might have been on my Macbook.

Thanks,
Josh

[vileslide]

Kingston DataTraveler Micro USB Stick 64GB 200MB/s Metall USB 3.2 Gen 1 - DTMC3G2/64GB

That drive worked fine for me to run recovery. Now I need to upgrade my meter again.

That's good news Thanks a lot for verifying that!

Now I just need to see if I can get it to work - I have EaseUS partition Master for that, it does the job quite nicely. Just formatted the drive to FAT32@4KB and copied the files.

I guess now it's just a matter of testing whether the recovery utility does anything and if I have to keep on (re)formatting 

[vileslide]

I guess now it's just a matter of testing whether the recovery utility does anything and if I have to keep on (re)formatting 

Yeah well, it didn't :') I just get a *beep beep* after startup and nothing more. Am I missing something? I just need to insert the Stick with the meter on, then turn it off and on again, right?

[KungFuJosh]

I guess now it's just a matter of testing whether the recovery utility does anything and if I have to keep on (re)formatting 

Yeah well, it didn't :') I just get a *beep beep* after startup and nothing more. Am I missing something? I just need to insert the Stick with the meter on, then turn it off and on again, right?

I also converted back to 55X-E with no issue using that 64GB Kingston drive.

There's 3 likely options why it isn't working for you:

1. Something wrong with the formatting of the drive.
2. Incorrect recovery package.
3. Recovery package not on flash drive correctly.


Did you unzip the recovery package and put all the files in the ROOT of the flash drive?

Thanks,
Josh

[vileslide]

I'm formatting the drive again with a full wipe at 1KB - that will likely take a while.

Yes all files are extracted from the .zip and I placed them in the root directory. Screenshot for confirmation.

[KungFuJosh]

I'm formatting the drive again with a full wipe at 1KB - that will likely take a while.

Yes all files are extracted from the .zip and I placed them in the root directory. Screenshot for confirmation.

The file sizes and dates are all identical to the recovery package I have, except the ro_uImage file which is off by a day.

If that recovery isn't working, it might be the wrong recovery. Email them and tell them it isn't working with your SDM. Mention your firmware number, and ask if it's the correct package for that revision.

[vileslide]

If that recovery isn't working, it might be the wrong recovery. Email them and tell them it isn't working with your SDM. Mention your firmware number, and ask if it's the correct package for that revision.

I also got the files for the other two DMMs of that series. I was told they only have a single recovery file for each DMM and that it's independent of the firmware.

[KungFuJosh]

I also got the files for the other two DMMs of that series. I was told they only have a single recovery file for each DMM and that it's independent of the firmware.

It should be independent of the fw, but it isn't working. Is it compatible with your hardware is the better question to ask them.

[vileslide]

Just did that, but let's wait and see if they get back to me.

In the end, I fear that all this will culminate in the FW not working on my HW iteration 

Thanks for all the help

[tv84]

The new FW package is very different:

Code: [Select]

File Header Size: 00000070
00000000 - File Checksum: EAE87BCB [00000004-0223DE1C] (with only the File Header decrypted)  CKSM OK
00000004 - File Size: 0223DDAD (without 0x70 bytes of the File Header)
0000000C - Product_ID: 11800
00000026 - Vendor/Brand: SIGLENT
0000003A - USB Host Controller: ISP1763
****************************************************
Decrypting the 0x2800 and 0x1400 blocks...
Reversing file...
XORing with 0xFF (incrementing pattern)...
XORing with 0xFF from 0x0111EED7 until 0x0223DDAC
****************************************************
00000000 --- Section Checksum: E86B7384
00000004 --- Section Size: 0223DD79 [00000034-0223DDAC]  CKSM OK
00000008 --- Section Type: 7   (config.zip)
00000034 --- 0223DDAC  ***** ZIP file *****
Offset    Ver  Flag  Comp  Size      Packed    Modified             CRC32                          Name                                                Permissions Extra Details
00000000  1.0  0000  0000  004389F5  004389F5  14/03/2023 10:26:24  92F4DA01  [00000040-00438A34]  common.zip                                          -rw-r--r--  MT: 14/03/2023 02:26:48  UID: 1009  GID: 1001
00438A39  1.0  0000  0000  00DF1A76  00DF1A76  14/03/2023 10:26:26  31BB58DD  [00438A77-0122A4EC]  emmc.zip                                            -rw-r--r--  MT: 14/03/2023 02:26:52  UID: 1009  GID: 1001
0122A4F1  1.0  0000  0000  010133F8  010133F8  14/03/2023 10:26:27  39F8C5B3  [0122A52F-0223D926]  nand.zip                                            -rw-r--r--  MT: 14/03/2023 02:26:53  UID: 1009  GID: 1001
0223D92B  2.0  0000  0008  000007DA  000002BA  14/03/2023 10:26:24  9E1916E5  [0223D96A-0223DC23]  update.sh                                           -rwxr--r--  MT: 14/03/2023 02:26:48  UID: 1009  GID: 1001
Disk Entries: 4   Total Entries: 4   Directory Size: 315 bytes  [0223DC5C-0223DD96]
****************************************************
  File Processed OK


[KungFuJosh]

The new FW package is very different:

I wonder what the new firmware for the 3065X will look like. They're supposed to have new firmware sooner or later that adds support for their new EasyDMM-X software (and hopefully some nice updates besides that).

[vileslide]

It's also triple the size of the previous iterations - I'm uncertain if there will be any firmware hacks for that then 

[tv84]

It's also triple the size of the previous iterations - I'm uncertain if there will be any firmware hacks for that then 

The size is because it now contains 2 flavors: UBIFS (for old models) and non-UBIFS (for new models).

Regarding a hack, it doesnt have nothing to do with the size of the FW but with the similarities of the HW. So, we need to see if the SDM3055X-E will also have a new HW model. Until then, there is no crossflashing for the newer SDM3045X HW model.   And, no need to go after downgrades...

Also, regarding the downgrade possibility, I think Siglent support's info that it can be done is somewhat wrong! Or, at least, I hope it is. Because if the upgrade function would allow a lower version number, one could risk flashing the old NAND FW versions in a EMMC (new HW) model... 

So, the downgrade could be possible BUT only on an old HW model.

[vileslide]

Thanks for your insight, that explains the behaviour of my DMM.

I'm quite certain that in the end, the recovery stick was working, but the DMM refused to accept it - it gave a "beep beep" at startup, instead of a "beep" (the latter happens if a USB device is recognised).

Well, f*** XD I'm happy that my efforts lead to a clear response in the end, and I'm thankful for all the support you guys gave me, but I would have wished for a different outcome 

The only reason why I wanted the 55X-E Firmware was that the 0-2V range is really annoying with its clicks and delays - I don't even care for the added precision digit, as most work I do boils down to "voltage there, voltage within 10% range" - that's also why I didn't want to cough up 150€ more for the 55X.

Having a bench multimeter at all is already a luxury for the work I do tbh.

[StoneR]

Having a bench multimeter at all is already a luxury for the work I do tbh.

Then a new Siglent was probably not the best choice for this use.

For less money you can have a HP or Agilent 34401A (6 1/2 digits) that starts in a couple seconds instead of 16 seconds or more.

Better for small and fast works, especially when you have small checks to do from time to time.

For me the 16 seconds boot duration, without standby mode, is a no go. The flashing green LED when it is off could suggest a standby mode, but in reality it's nothing of the sort.

Then i've sold my 3045X and bought a second hand 34401A.

I was not aware of this when i bought the 3045X regardless the Internet readings i did before to buy.

Internet is often hiding this kind of problems, except in some rare reviews.

Next time i will not buy a product without testing it before.

[Kleinstein]

Internet is often hiding this kind of problems, except in some rare reviews.

There is a general problem that negative results or failed experiments often don't show up. So not many videos about a failed try to hack the new meter version.
It depends where you are how easy it is to get a used 34401 for a good price - the situation is much better in the US than in Europe.

[vileslide]

Then a new Siglent was probably not the best choice for this use.

For less money you can have a HP or Agilent 34401A (6 1/2 digits) that starts in a couple seconds instead of 16 seconds or more.

While I appreciate your input and somewhat aggree, there is another part at play here which hinders me more often than I'd like to admit:

I have OCD and already have a Siglent Oscilloscope and Function Generator on my desk - I bought a cheaper alternative for the latter at first and, although it would have served all my needs, the build quality and design annoyed and bothered me so much, that I eventually returned it and bought the Siglent one.


I'm happy with the nice display and I don't care too much about the accuracy provided, but it's still nice to have. It integrates nicely with the other equipment which is also worth something to me.

Finally, I have to say that the choice offerd on ebay in Austria is very limited. I didn't want to buy a Fluorescent display type meter and since it's a bit hard to test every function on arrival, buying used also comes with some risk which just wasn't worth it to me. In the end, I'd save 200€, which is about 8% of my monthly income - so for about 1,25 days of work I get peace of mind for years to come.


I know this might not make sense to people without OCD and objectively I could have made a better deal, but I just wanted it, so I bought it - I hope my explanation above sheds a bit more light on my thinking process.

(although now I'm thinking about returning it and sourcing the same model from Amazon, with the hopes of getting an older model since their pricing isn't the best) 

[Kleinstein]

The transition to the new firmware version was already quite some time ago. So chances are low to get the old version from Amazon or a regular online shop. Chance would be good when getting a used one, but chances are not high to find a used one at all.