Spectrum Analyzer - Rigol DSA815

[TurboTom]

Why would one buy a DSA815TG (unless at substantially reduced price) while at virtually the same expense the SSA3000X is avalable that's better in almost every aspect?

To answer your question -- currently there's no known method to permanently hack the recent versions of the DSA815. There's the FRAM WP "trick" that freezes your trial time that's granted with new machines but that has some unpleasant side effects (some other user settings won't get stored anymore).

Cheers,
Tom

[danny_isr]

"Why would one buy a DSA815TG (unless at substantially reduced price) while at virtually the same expense the SSA3000X is avalable that's better in almost every aspect?
"
Because we already own one

[videobruce]

Some guys prefer a more established company. While Siglent isn't brand new, their track record is shorter and they are less known. 

[ted572]

Please see -> https://www.eevblog.com/forum/testgear/sniffing-the-rigol's-internal-i2c-bus/msg1196690/#msg1196690  especially if you have a DSA815 with the newer Main Board Hardware version 7 and above and want to get the Options License installed.  This could be a false alarm, but please consider this. . .
Important! See EDIT 5/10/2017 added below:   

Good day everyone,
My DSA-815TG runs with the current Firmware 1.18 under Hardware 0.04 and boot loader 1.03. Generating keys with RIGLOL and activating the same under 1.18 works perfectly fine, the 10Hz RBW option was accepted but obviously has no effect as this option is available per default these days. All other options except for the last one are active as expected.
Raj

Hello Raj: I understand from reading your post that you installed the Rigol Options with firmware 00.01.18 installed.
Although this is the first time that I have heard of anyone being able to use the Riglol Keygenerator for installing Option License Codes on DSA815 firmware 00.01.09 and above.  Are you sure that you installed your options with firmware (FW) version 00.01.18?
History: When Rigol introduced firmware 00.01.09 it was no longer possible to use the the Riglol Keygenerator to activate the Options.  We had to revert back to FW 00.01.08, or earlier to get the Options activated.  And as long as we had BootLoader .02, or .03 we could do this with the 'Boot Method'.  Although those with BootLoader .04 could not because this BootLoader did not allow the FW Boot Method to work any longer.  It is the newer FW (.09 and later) that prevents the Keygenerator from working, and it is BootLoader .04 that prevents using the FW Boot Methode from working any longer.
If Raj's experience is correct, then it may then be possible for users with the new Main Board Hardware (V. 7 and above) to also install the Options.  This would be fantastic news for them, and these users could give it a try (with Caution!, at their own risk) to see if it works.

EDIT 5/10/2017: I have not heard of this working for anyone.  Therefore I recommend avoiding experimenting with this method.   Sorry for the false alarm, although if it had worked several DSA815 users would have been very happy. . .

The following links depict how users have been able to Recover Lost Trial Options with FW 00.01.18:   https://www.eevblog.com/forum/testgear/spectrum-analyzer-rigol-dsa815/msg1139507/#msg1139507   https://www.eevblog.com/forum/testgear/spectrum-analyzer-rigol-dsa815/msg1035627/#msg1035627   https://www.eevblog.com/forum/testgear/spectrum-analyzer-rigol-dsa815/msg1096397/#msg1096397   https://www.eevblog.com/forum/testgear/spectrum-analyzer-rigol-dsa815/msg1098206/#msg1098206   https://www.eevblog.com/forum/testgear/spectrum-analyzer-rigol-dsa815/msg1098284/#msg1098284   https://www.eevblog.com/forum/testgear/spectrum-analyzer-rigol-dsa815/msg1098337/#msg1098337   https://www.eevblog.com/forum/testgear/spectrum-analyzer-rigol-dsa815/msg1100397/#msg1100397   https://www.eevblog.com/forum/testgear/spectrum-analyzer-rigol-dsa815/msg1102736/#msg1102736

[Daruosha]

Please see -> https://www.eevblog.com/forum/testgear/sniffing-the-rigol's-internal-i2c-bus/msg1196690/#msg1196690  especially if you have a DSA815 with the newer Main Board Hardware version 7 and above and want to get the Options License installed.  This could be a false alarm, but please consider this. . .   

Good day everyone,
My DSA-815TG runs with the current Firmware 1.18 under Hardware 0.04 and boot loader 1.03. Generating keys with RIGLOL and activating the same under 1.18 works perfectly fine, the 10Hz RBW option was accepted but obviously has no effect as this option is available per default these days. All other options except for the last one are active as expected.
Raj

Hello Raj: I understand from reading your post that you installed the Rigol Options with firmware 00.01.18 installed.
Although this is the first time that I have heard of anyone being able to use the Riglol Keygenerator for installing Option License Codes on DSA815 firmware 00.01.09 and above.  Are you sure that you installed your options with firmware (FW) version 00.01.18?
History: When Rigol introduced firmware 00.01.09 it was no longer possible to use the the Riglol Keygenerator to activate the Options.  We had to revert back to FW 00.01.08, or earlier to get the Options activated.  And as long as we had BootLoader .02, or .03 we could do this with the 'Boot Method'.  Although those with BootLoader .04 could not because this BootLoader did not allow the FW Boot Method to work any longer.  It is the newer FW (.09 and later) that prevents the Keygenerator from working, and it is BootLoader .04 that prevents using the FW Boot Methode from working any longer.
If this is correct, then it may then be possible for users with the new Main Board Hardware (V. 7 and above) to also install the Options.  This would be fantastic news for them, and these users should at least give it a try to see if it works for them!

Sorry to disappoint you, but i tried the keygen on my unit with the board version 0.09 and the firmware 01.18 (factory installed) and the keys didn't work.

[smgvbest]

Please see -> https://www.eevblog.com/forum/testgear/sniffing-the-rigol's-internal-i2c-bus/msg1196690/#msg1196690  especially if you have a DSA815 with the newer Main Board Hardware version 7 and above and want to get the Options License installed.  This could be a false alarm, but please consider this. . .   

Good day everyone,
My DSA-815TG runs with the current Firmware 1.18 under Hardware 0.04 and boot loader 1.03. Generating keys with RIGLOL and activating the same under 1.18 works perfectly fine, the 10Hz RBW option was accepted but obviously has no effect as this option is available per default these days. All other options except for the last one are active as expected.
Raj

Hello Raj: I understand from reading your post that you installed the Rigol Options with firmware 00.01.18 installed.
Although this is the first time that I have heard of anyone being able to use the Riglol Keygenerator for installing Option License Codes on DSA815 firmware 00.01.09 and above.  Are you sure that you installed your options with firmware (FW) version 00.01.18?
History: When Rigol introduced firmware 00.01.09 it was no longer possible to use the the Riglol Keygenerator to activate the Options.  We had to revert back to FW 00.01.08, or earlier to get the Options activated.  And as long as we had BootLoader .02, or .03 we could do this with the 'Boot Method'.  Although those with BootLoader .04 could not because this BootLoader did not allow the FW Boot Method to work any longer.  It is the newer FW (.09 and later) that prevents the Keygenerator from working, and it is BootLoader .04 that prevents using the FW Boot Methode from working any longer.
If this is correct, then it may then be possible for users with the new Main Board Hardware (V. 7 and above) to also install the Options.  This would be fantastic news for them, and these users should at least give it a try to see if it works for them!

Sorry to disappoint you, but i tried the keygen on my unit with the board version 0.09 and the firmware 01.18 (factory installed) and the keys didn't work.

I can also confirm with a FW.16 Boot 1.04 it does not work
upgrade to FW.18 it does not work
and I've lost my trials going to FW.18
my board was a V8

so not a happy camper here.  I think there was something in this thread about getting the trial back so I need to go look

[ted572]

I can also confirm with a FW.16 Boot 1.04 it does not work
upgrade to FW.18 it does not work
and I've lost my trials going to FW.18
my board was a V8

so not a happy camper here.  I think there was something in this thread about getting the trial back so I need to go look

Hello Sandra:  I just sent you a PM with links to how you can recover your Trial Options.   Regards, Ted

[smgvbest]

I can also confirm with a FW.16 Boot 1.04 it does not work
upgrade to FW.18 it does not work
and I've lost my trials going to FW.18
my board was a V8

so not a happy camper here.  I think there was something in this thread about getting the trial back so I need to go look

Hello Sandra:  I just sent you a PM with links to how you can recover your Trial Options.   Regards, Ted

got it,  thank you.  I will let it run and hope
i did see some reports of the time to run was related to how much you had left of your trial.  I had 34+ hours so it will be interesting if i have to leave it on for 34+ hours
started at 7:55pm and as of 5:25am still missing trials
as of this morning at 5:25am I now have my trials back after 34hrs of on time of the SA.

[Daruosha]

I can also confirm with a FW.16 Boot 1.04 it does not work
upgrade to FW.18 it does not work
and I've lost my trials going to FW.18
my board was a V8

so not a happy camper here.  I think there was something in this thread about getting the trial back so I need to go look

Hello Sandra:  I just sent you a PM with links to how you can recover your Trial Options.   Regards, Ted

got it,  thank you.  I will let it run and hope
i did see some reports of the time to run was related to how much you had left of your trial.  I had 34+ hours so it will be interesting if i have to leave it on for 34+ hours
started at 7:55pm and as of 5:25am still missing trials
as of this morning at 5:25am I now have my trials back after 34hrs of on time of the SA.

Just out of curiosity, could you downgrade ti the earlier version and recover the trial licenses?

[smgvbest]

I can also confirm with a FW.16 Boot 1.04 it does not work
upgrade to FW.18 it does not work
and I've lost my trials going to FW.18
my board was a V8

so not a happy camper here.  I think there was something in this thread about getting the trial back so I need to go look

Hello Sandra:  I just sent you a PM with links to how you can recover your Trial Options.   Regards, Ted

got it,  thank you.  I will let it run and hope
i did see some reports of the time to run was related to how much you had left of your trial.  I had 34+ hours so it will be interesting if i have to leave it on for 34+ hours
started at 7:55pm and as of 5:25am still missing trials
as of this morning at 5:25am I now have my trials back after 34hrs of on time of the SA.

Just out of curiosity, could you downgrade ti the earlier version and recover the trial licenses?

I did not try to do that.

[ted572]

Just out of curiosity, could you downgrade ti the earlier version and recover the trial licenses?

Hi Daruosha:  As I understand it with the Newer DSA815 (with Main Board 7 and above) that there is no way to return to a earlier FW version once you have installed FW 00.01.18.  And to install FW .18 you must have the 'FRAM Write Protect disabled' if you previously had it enabled (U1105 pin 7 & 8 soldered together).  And consequently when you install FW .18 you loose the Trial Options.  Although I understand that they can be recovered again as the following links say.  Please go to my post at -> https://www.eevblog.com/forum/testgear/spectrum-analyzer-rigol-dsa815/msg1203247/#msg1203247  and visit the links at the bottom, for how others have recovered the Trials.

[danny_isr]

I wonder if someone can explain what those options actually do, and how useful they really are?
I understand that the RBW 10Hz option is now available for everybody. So does the average user really needs the other options ?
I'm not an RF guy (obviously), and i would like to understand if this is something that as a hobby SA will i ever need that ?

[robots]

I accidentaly flashed wrong firmare into dsa815, and it killed serial number, TG license and all calibration. They don't check in bootloader 01.02 what model is the firmware for, they just flash it - over calibration region.

Rigol is asking 700EUR for recal, or 850EUR for new board + shipping cost !!!.

Could someone with bootloader 01.02 help me ? and send flash dump (complete, using command ":SYST:FRE?") so i can find the place where the serial number is located and fix it. I want to have at least TG working

Or if someone knows how/where is the sn stored, could you give me hint ?

[ted572]

For continuity on the discussion about the DSA815 with the newer Main Board Hardware version 7 and above with BootLoader 4, where we want to get the Options License installed;  See ->  https://www.eevblog.com/forum/testgear/sniffing-the-rigol's-internal-i2c-bus/msg1205818/#msg1205818  -  For comments regarding DSA815 BootLoader 2/3 vs 4, format for installing the Option serials, the DSA815 'FW Install Boot Method', etc.

[smgvbest]

granted, however the DSA815 support boot from USB and the blackfin supports uart boot.  so if we have the boot code in LDR format and put that on a USB drive or load via uart to get 1.03 in then could we not backload FW1.0x then?

Hi Sandra:  The Blackfin's interface capability can be limited/overridden by the instructions from the Boot Loader. Or purposely left out by the hardware designer for expediency because it wasn't required for the task.  I think that the current .04 Boot Loader most likely preempts doing this, so I think someone will have to directly force a .03 Boot Loader (or equivalent) in place of the .04.
I don't have any vested interest here, because I have the original hardware with all of the permanent Options (so far anyway).  If I had the newer unit I would be charging into this relentlessly with a DSA815 open on my bench, to try to at least understand high level system architecture used.  I did this for my units Front End, LOs, Mixers, and IFs through to the DSP.  https://www.eevblog.com/forum/testgear/spectrum-analyzer-rigol-dsa815/msg1059060/#msg1059060
You may want to consider sketching out your units digital control logic, as it may help shed more light on all this.  Most of the ICs have vendor P/Ns, and some have SMT Codes.  Doing this with Peter's info may help pull it together.
EOT and Cheers, Ted

Edit:  This discussion should back here -> 'Re: Spectrum Analyzer - Rigol DSA815'

Trying to move this back here,  I thought reading your message you thought it belonged in the other thread which is why I put it there.
my comment on the bootloader is based on when you power on the DSA it shows to press 'PRESET' to boot from U-DISK.  so could we possibly put a 1.03 Boot loader or 1.06 FW on at that point?  has anyone tried?   I realize we don't know what file it's looking for  but a USB protocol analyzer might help there. 

[smgvbest]

So what I found so far is if a *.sys file is on a USB Drive and plugged in it will read it and immediate try to flash it.
you power on and hold preset it will read the USB Drive and install the file on there.  I reinstalled 1.18 this way and didn't loose my trials this time.
I do not have a older FW file though to try

[robots]

I think Cybernet should be able to shed more light on the boot sequence of the DSA. It should be very similar (if not same) as DS2000. He also developed u-boot for this platform. But i dont think its possible to contact him :-/.

It would also solve my problem with deleted serial number. I could write the flash and fix the unit.

Ultimate goal would be to flash uboot instead of the rigol's bootloader and load any firmware.

https://www.eevblog.com/forum/testgear/sniffing-the-rigol's-internal-i2c-bus/msg581433/#msg581433

Here are some other notes on the architecture:
https://www.eevblog.com/forum/testgear/sniffing-the-rigol's-internal-i2c-bus/msg581767/#msg581767

I think i have stumbled on the problem with shadowed address lines. I am getting very inconsistent memory readouts.

[robots]

I dont know if such thing is available, but i wrote this tool to split .sys update file into blocks as they are written into the flash. Written in python.
firmware 18 has these blocks:
00080000 - firmware, compressed by unknown compression
00180000 - main fpga (screen, memory)
00270000 - rf fpga
00290000 - texts (buttons, UI)
00294000 - texts in diff language
00298000 - ditto
0029c000 - more of them
002a0000 - firmware for FX2 (usb slave chip)
002b0000, 002ec1b0 - font ?
00300000 - help
00320000 - help in cn
00340000 - text messages
.. more texts in diff languages
00370022 - version number
0037f000 - 0002 ? idk

[robots]

Update on DSA815-TG.

DO NOT EVER NEVER EVER DO:
when booting press F3 will ERASE EVERYTHING, serial number, model number everything. This is very tempting right now, but it will put your device into factory clean state!!

- DSA815-Tg hardware is not able to work on frequencies >1.5GHz. I thought it might be only locked by software. I changed my model from DSA815 to DSA830. While i could tune pass 1.5GHz, the signal would be disappear at about ~1518Mhz. Maybe missing vco for higher range.

- DSA815 serial number, mac address, model number, can all be changed by simply running update with proper .sys file.

- save your flash content when playing with this equipment.

[smgvbest]

What are you using to save your flash content?  JTAG Dump?  are you using OpenOCD or other tool?

[robots]

scpi works pretty well.

Jtag has access to only part of FLASH memory at time and you have to switch it. Like mentioned here : https://www.eevblog.com/forum/testgear/sniffing-the-rigol's-internal-i2c-bus/msg581767/#msg581767 but the address of the fpga is different for DSA. I dont know how it works yet.

[cybernet]

never done much with the DSA except verifying that it used the same crypto algos back then (posted my DSA ida in the other thread).
But what you wanna do is, take openocd + gdb for blackfin, and step through the bootup process. if memory serves right execution started somewhere 0xef000000 as init vector (the blackfin datasheet is your friend), and then u trace through it. probably an LDR stream somewhere that gets then copied to RAM and executed, find the copy action, then dump the RAM blocks and you will have a boot loader image. reassemble that as an LDR stream.


here is a sample for a lcd test tool for the ds2000, and creating a RigolDsExe.ldr which the ds2000 will happly execute from an USB stick. (maybe the DSA does too, never tried, give it an endless loop and see if it hangs actually)

files below are posted in the other thread.

Code: [Select]

#!/bin/bash

CC=/opt/uClinux/bfin-elf/bin/bfin-elf-gcc

rm *.o
$CC -nostartfiles -nodefaultlibs -c init.S -Iinclude -mcpu=bf526 
$CC -nostartfiles -nodefaultlibs -c main.c -Iinclude -mcpu=bf526 
$CC -nostartfiles -nodefaultlibs init.o main.o -T bfin.ld -o my.elf
bfin-uclinux-ldr -T bf526 -c --dma 6 RigolDsExe.ldr my.elf
bfin-uclinux-objcopy --gap-fill=0xff -O binary my.elf my.bin
cp my.bin /var/lib/tftpboot/


[robots]

cybernet:
Bootloader on DSA is different. There is no mention of direct loading of LDR. Maybe it has to be packed in .SYS file. I will check that.
Did you ever release that u-boot for ds2000 ?

On the calibration data lost:
I have been able to take "calibration" data from another DSA, and load them into this one. At least i dont get the stupid error about calibration data being lost, and TG can be enabled.

[cybernet]

@uboot its in the other thread - a tar.gz of the patched sources of a 2014 uboot, if i remember correctly, it was mostly some cleanup of the interrupt handlers that where needed which pointed into code that was then replaced with the uboot ldr + added lcd support. that part was actually pretty easy, you'd have to diff it against the original source i didnt bother to do that back then.

[kattyil]

Gday everyone. Interestingly this seems to be a nightmare to everyone on boot 1.04 and newer. As said, my 815 had and still has boot 1.03. All options were still in trial mode. Since the rigol service line has assured me that 1.18 Firmware can perfectly run on my older board and boot loader, I went directly from my original fimware to 1.18. After that, as expected, all of my trials had disappeared. After that I generated the keys with the generator and was able to activate them with no issues (had to enter them twice as I did not use all caps). Finding a way to revert to boot 1.03 might help but also sounds risky. I probably would not go there. Good luck! Raj