SDG5082,SDG5112,SDG5122 convert to SDG5162

[obi100]

Has anyone a firmware jtag flash dump from SDG5162
Or an older firmware update as SDG5000 V500R001B01D01P10R1
Would be great if that were so.

First, a few small numbers

Modify the Serial with: 258528 saved OK
Modify the Modell with: 369639 saved NO  (POWER OFF and ON the Modell is not on Flash saved)
Reset startup time with: 123321 saved OK  (POWER OFF and ON the startup time is 000 )
display developer with: 159264

Best regarts

obi100

[tautech]

Welcome to the forum.

The oldest version on Siglent websites is 5.01.01.10
http://siglentamerica.com/gjjrj-xq.aspx?id=819&tid=15

Good luck with your endeavours.

[obi100]

I have unfortunately already
But there is version 5.01.01.07R1

Who still has this version?

[tautech]

I have unfortunately already
But there is version 5.01.01.07R1

Who still has this version?

Nobody I know.
FW has only been on websites for a short time.

[janekivi]

But there is version 5.01.01.07R1
Who still has this version?

This was there maybe from factory and here is no downloadable firmware file...
https://www.eevblog.com/forum/testgear/tests-siglent-sdg5082-waveform-generator/msg239358/#msg239358
...
« on: May 30, 2013, 03:20:45 PM »
...
SDG5082   0213 manufacture, FW:5.01.01.07R1
...

But inside latest firmware is FPGA part and (Blackfin ?) program file where from address 0000DBD4 is compressed part.
Unpacked_SDG5000-V500R001B01D01P15R1.zip

[obi100]

i have the full flash dump from SDG5082 but the licence to convert to SDG5162 is the problem.

this is mach in Flash dump at 0X0013FEFD  020084001000

is  this the way?

UPDATE: So, that string does not appear to be in the dump file anywhere...  The file is exactly 128MB in size, and appears to contain lots of identifiable strings including my serial number and the entire contents of the HTML help system.

It doesn't make sense that it would be a "corrupted" dump if I'm seeing real, readable data, but I guess I'm not sure what I'm supposed to see.  Is there a different way to try the dump?  I ended up switching to the WinUSB driver and using the bfin-gdbproxy and bfin-elf-gdb approach.



Quote from: PeDre on August 17, 2014, 05:29:17 AM

    Can you find the hex pattern "020084001000" in your dump file, as in the rigup utils.c file?

    KeyData* ScanKeys(const void *data, size_t datasize)
    {
      /*
        Offset   Data
          0      02 00 84 00 10 00
          6      <16 bytes of XXTEAKey>
         22      20 00
         24      <16 bytes of RC5Key1>
         40      <16 bytes of RC5Key2>
         56      08 00
         58      <8 bytes of bit-shuffled ECC public key>
         66      40 00
         68      <64 bytes of some ASCII-HEX data>
        132      <END>
      */

    I used rigup 0.4: "rigup ds2072a ds2k_00_sdram.bin"

    Peter

« Last Edit: August 17, 2014, 05:40:56 AM by Slappy_g »