I overwrote my corrupted bootloader with the new one (v3.10), then I updated both the SYS and APP with versions v1.50 and v2.50 respectively.
Now each time I power on the device it shows the license error message asking for the license number that I can skip pressing one of the buttons,
but it’s very very annoying.
You’ll find attached to this post the stock DSO Quad Bootloader v3.10; it has to be downloaded at the embedded Flash base address that’s 0x80000000.
Once restored the stock bootloader you will be asked for a License number that is calculated starting from your Hardware Serial number. In order to know it you can use the SYS FW 2.50 I modified to show you at startup the License number further to the Serial number.
So take care to note it down before doing any FW update that could potentially corrupt the original bootloader.
When you have taken note of your License number you can finally feel free to do any sort of experiment with your DSO Quad since you will be able to restore it completely at ANY time !
I have loaded your modified file Sys 250A.hex but do not see my license number upon restarting the DSO Quad. The start screen says that I have Sys version 1.50 and App version 2.50 .
Should I be seeing the license number on the bootup screen? If so, is there a possibility that someone replaced your modified Sys 2.50A with the original file?
I flash my quad with a new firmware - Sys_151 App_252 FPGA261, after it i want to know what is my LicenseNumber… and flash it with embedded’s sys file… after it usb logical drive won’t appeared.
Can you suggest me a solution?
something went wrong when I wanted to change logo picture. It ended up with corrupted bootloader
I’d like to make clear instructions how to make it work again (so it would help also to other users).
I have already ordered USB to RS232 TTL cable from ebay
Before I receive my USB cable, I’d like to be 100% sure what I need to do, step by step.
Dismantle DSO
Find CN7 connector
Short-circuit the PIN1 and PIN2 (which will put it into USART1 boot mode)
After I install that software, do I need to select anything special, like: Baud Rate, Parity, Echo, Timeout, …?
“Upload” “BootLoader v3.10.bin” to flash through that software
Is it now fixed? and can I at this step boot into boot mode and upload SYS file normally through USB mass storage?
I’d prefer to upload modified SYS to check License number first and after that upload everything again normally through USB files for FPGA, SYS and APP, am I right? I mean will it work?
Thank you for your time and your help, I really appreciate it.
Run Flash Loader Demo, select correct COM port, press Next, then I selected ‘512 mem version’ (can’t remember exact words) and also 0x80000000 from pages list
Select your DFU file and download it to your device
All done, now you can update everything else normally through ‘usb’ upgrade mode, FPGA, SYS, APP
Only problem I have now is that I bought it with:
Hardware Ver 2.81
DS203 Mini DSO SYS Ver 1.62
DS203 Mini DSO APP (PLUS A1) Ver 1.13
…but there’s not DFU file yet for my HW version at wiki pages. Wiki says that for “Hardware V2.81 - New FPGA chip is used, so FPGA configuration file has changed. SYS and APP are still compatible with HW2.7x version”, so I believe everything will work fine, except it says HW 2.72 on initial screen. After I downloaded DFU for 2.72, I upgraded FPGS, SYS and also APP to versions I bought it with.
BTW, trick with getting license key didn’t work. I tried DFU and SYS from this thread, but it didn’t work. Anyway, to confirm license key on the load screen is no problem for me.
Thanks again. Hope it helps also to someone else. If anyone gets bored, get DFU for HW2.81 please
For those who want to save their current state including DFU / License data etc. it is nice to have an archived dump file for emergency use with the serial port flash technique. This is a bit easier than starting with a stock DFU.
Creating a utility for this was mentioned earlier in this thread but I don’t recall seeing a hex for this.
Attached source + hex (FL_DUMP4) is for this. It loads by default into slot 4 and when run just saves the 256K of the processor flash memory as a flash.bin file. It just says saving followed by completed a few seconds later. You won’t see the completed flash.bin file until you reconnect the USB disk.
The DFU is actually the first 16K bytes of this and can be easily extracted using a binary editor. FlDump.zip (29.1 KB)
I am a little surprised by this as the DFU is more about loading new software and launching what is loaded. It doesn’t have a lot to do with the actual run-time operation. If the input channels are not working then I’d be double checking I had the correct FPGA, SYS and APP files. Now if the DFU is not allowing you to reload those properly then that’s a different issue.
Tank you,
I was too eager to get it working and was probably trying too hard. In the end my device died on me. As it seems one coil (USB power L7) and power stabilizer (U15) for 2,8V have gone bad probably because I used the same computer for power and serial connection. Looking at the schematics, that was probably a bad idea. Accidentaly shorting the pin 1 on CN7 durring programming would explain things too, but i have taken precausions for that, so not sure. I don’t know if I will be able to recover this device, but probably not. I managed to make a full system backup (although it’s the corrupted state) if anyone is interested. I also confirmed that I was able to restore to that state comletely. My plan was to rewrite all available parts of it and flash it back. With this, I would probably get it working. A little more patience would help.