Products > Test Equipment

Rigol DSXXXX .GEL firmware file format

<< < (34/38) > >>

konnor:
The fragment of code(from the loader), what write the version code,  I cited above. I do not know of any other version storage locations in the bootloader. The main firmware simply reads the version from the memory.

tv84:
I updated my previous post about the Bootloaders versions with the informations shared in these last posts.

https://www.eevblog.com/forum/testgear/rigol-dsxxxx-gel-firmware-file-format/msg1481222/#msg1481222

If you see any error or have any of the missing versions (or NAND/NVRAM dumps) please post or pm me.

tv84:
As konnor suggested (I only suspected :) ), the bootloader version is HARDCODED in the code (one of the last functions in the block). Here is an extract of the bootloaders that I have:

Bootloader v1.0 - MainProcess
00 50 2D E9                             STMFD           SP!, {R12,LR}
FC 00 A0 E3 7F 0C 80 E3           MOV             R0, #0x7FFC
10 10 A0 E3 40 1B 81 E3           MOV             R1, #0x10010 ; BOOT VERSION
00 10 80 E5                             STR             R1, [R0]

Bootloader v1.2 - MainProcess
10 40 2D E9                             STMFD           SP!, {R4,LR}
00 40 B0 E1                             MOVS            R4, R0
FC 00 A0 E3 7F 0C 80 E3          MOV             R0, #0x7FFC
12 10 A0 E3 40 1B 81 E3          MOV             R1, #0x10012 ; BOOT VERSION
00 10 80 E5                             STR             R1, [R0]

Bootloader v1.4 - MainProcess
10 40 2D E9                             STMFD           SP!, {R4,LR}
00 40 B0 E1                             MOVS            R4, R0
FC 00 A0 E3 7F 0C 80 E3          MOV             R0, #0x7FFC
14 10 A0 E3 40 1B 81 E3          MOV             R1, #0x10014 ; BOOT VERSION
00 10 80 E5                             STR             R1, [R0]

Finally, now we can see the version of a bootloader without loading it into the scope.

janekivi:
It's funny how we hack all this backwards. I do some dirty hardware hack and then you
disassemble it right way. I have EEPROM there with connector and did flash it in TL866
with different files to see their versions.
Now it is simple. You take SparrowBootloader.sb, unpack it with sbtool, take look at the
right address and all is clear :)

For example there is my bootloader, version 0.0.1.2
In hex is the main function region with version number.

mrpackethead:
I'm wondering if anyone has done anything with the most recent MSO5000/7000 and their Gel file? Its looking at bit different from previous versions.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod