| Products > Test Equipment |
| Siglent .ads firmware file format |
| << < (37/85) > >> |
| SMB784:
--- Quote from: BillB on July 02, 2018, 12:57:23 pm ---Anyway, what is odd, is that you were able to correctly generate the factory OS update USB configuration. Was that the same process that didn't work for your attempt with the modified OS update? --- End quote --- That is correct, I used the exact same process on the same computer to generate the modified OS update USB configuration as the one I used to generate the factory OS update USB configuration. The factory USB configuration worked, and the modified USB configuration didn't. Then when I generated the modified USB configuration on my RPi, it worked right away. It's very strange. Indeed, TV84 was probably correct in his advice that I check the CRC values. I didn't actually check them, because I was in the process of learning how to check them when I tried making the USB on the RPi. However, it seems strange to me that the simple act of copying the files over to the USB on one system would change the CRC values of those files when doing that exact same process on a different system does not modify them in any way. Anyways it was a fun, albeit frustrating experience, with a rather bewildering but ultimately satisfying end result. Thanks again to all of you who helped me. |
| tv84:
Updated my parsing list of all Siglent FWs. Now we can see the extra details of the files used in the ZIPs. The only UID/GID combinations are: 1000/1000 65534/65534 (only in some SDG800 .ADS when the rw_uImage is used) |
| kerouanton:
thank you all especially janekivi and tv84 for reversing the .ads file format. I'm still new at that and as I'm learning Python it motivated me to reimplement the decoding process. I followed the steps described on some of your posts, but I am still far from what tv84 outputs in his parsing list. Up to now, I am able to : 1. extract a .ads file from the downloaded zip file and load it in memory. 2. calculate the checksum 3. reverse the bytes 4. xor it with increasing pattern 5. xor it from the center 6. save the result What should be the next steps, for example to locate and isolate each part? |
| janekivi:
Next you need probably put this before reverse and XOR https://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/msg984820/#msg984820 to get SPD3303X-E_1.01.01.02.05-EN.hex like there, inside is the same jpg image starting at 0x00024D68 https://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/msg1181598/#msg1181598 |
| kerouanton:
--- Quote from: janekivi on July 15, 2016, 07:47:52 pm ---Let's take a look in SDG1000-V100R001B01D01P31.ADS for example --- End quote --- I am trying to move forward on my python .ads decoding script, but as a newbie I'm a bit lost and expect to rely on janekivi replies to see if I'm able to get the same results. For this, I need this exact SDG1000-V100R001B01D01P31.ADS file, but I wasn't able to find the correct download URL, both on siglent.com, siglentamerica.com, and old.siglentamerica.com. Has anyone the download url, so I can move forward and try getting the same results on my script? Also, as far as I understood, some parts of the file are 3des encrypted (some parts only as with my actual script I am able to get clear-text strings such as model number, at least on the SPD3303 .ads file), but I'm still unable to understand how janekivi found the right offset and length of the encrypted part, as well as the key itself. The method used to investigate and find those is challenging for me! As both of you, I'm just playing around with those files for fun, as I try to learn Python and nothing more (well, having a root access on my devices is fun too). Thanks |
| Navigation |
| Message Index |
| Next page |
| Previous page |