Open PawxSpec opened 5 years ago
I am not able to look at the fpga bin you provided for few hours but it seems really big. On DS203 it was something around 135kb. Perhaps something else was included from lib or app sections?
i dumped the memory region starting at the fpga section and ending at the logo screen (addresses are obtained from BIOS and easily verifiable by looking at the dump with hex viewer). so there is big section full of FFs
@gabonator Yes looking at Bios code it does look like 0x08070000 is start of FPGA. Have you tried flashing with a hex file? fpga-hex.zip
I've also ripped out just the App V1.20 portion from full dump shared by darkonerakot DS213AppV1.20.hex.zip
and here is just the DFU bootloader, afk can only be flashed with St-link as the bootloader should protects itself. DS213_DFU_V3_42_D.zip
So it should work out if flash fgpa.hex then app1.20.hex?
I believe so. I don't have ds213 so didn't try it myself. You could just try the fpga and reboot. If no fpga error then it flashed. Then flash the app.
DS213 has these attributes in its bios structure: App1Base 0x08008000 App2Base 0x08028000 FpgaBase 0x08070000 LogoBase 0x0807d800 MaxLimit 0x08080000
So I extracted the fpga by this command:
dd if=ds213v20.bin bs=1 count=$((0xd800)) skip=$((0x70000)) of=ds213v20_fpga.bin
and converted to hex:
arm-none-eabi-objcopy --input-target=binary --output-target=ihex --change-addresses 0x08070000 ds213v20_fpga.bin ds213v20_fpga.hex
When tried to upload the hex file through DFU, the upload process is supiciously fast, so it seems the dfu does not write anything (cant remember if the dfu renames it to ERR or not, will verify later)
Now I am trying to upload the fpga binary through my OS, I just need to convert the binary file into ELF somehow
I guess Dfu bootloader should be same since 1.21 1.22 doesnt contain it.
gabonator, does your hex have :020000040807EB on the first line?
darkonerakot, yes DFU seem to never change. Really no need and requires st-link.
@MotoMaxis
:020000040807EB
:10000000001200100000FFFFA20000200000C72027
:1000100052942508425294A129425294A5094210B3
:1000200084210842108421094A000000A200002116
:1000300000006020DD2000200008E240000FDF808B
...
That looks good. I am really shocked that they don't allow to flash FPGA. It must be fault in DFU.
So I tried it, first I flashed FPGA over DFU then 1.20App, I dont know if fpga is overwrited but APP is flashed as I see on bootscreen logo, time scale bug existing as rest of trigger bugs, I quickly tested it on "trigger bug chart" so I think it didnt workout. Hope it is usefull information for you.
Got it!
Time to celebrate :)
please explain with more details, I can not run elf files
system_ds213.hex is simple operating system running on DS213 that can load ELF files stored on EEPROM. You need to flash the file somehow (copy it in dfu mode over usb cable, or use dfu load tool. Then copy all the elf files to the device using usb cable, turn off-on and you should see file manager in which you can run various applications
Image loaded at 0x00000000 press F1 to retry
@darkonerakot its ok, the fpga elf is not real executable, so it does not have entry point (address where the program instructions begin), just restart the device
I tested 52osc.elf bugs are a littlebit defferent, left voltmeter is funny bug) pause is not working scale too, I gonna try another app, but I like idea of file manager and application choose,that`s cool.
But what is important - the fpga image was updated and now you can flash back the original oscilloscope application over DFU...
So I tested with APP1.20 and looks stable, general bugs is still here, but previous 1.22 was too bad, with fgpa it works a little bit better, signal is not shaking, single mode working fine, "trigger bug chart" the same, in conclusion I would say now it is more stable. 1.22 with newest FGPA was not even able to start norm mode sometimes. I like this FGPA and APP.
@darkonerakot The question is - is the oscilloscope usable for general measurement? Having those issues - would you return it to the seller, or is it ok for you? I do not have currently time to investigate the issues. I would rather spend time to port the DS203 interface to DS213 than learn how to use their user interface :) So what is your opinion?
With current Firmware wich also contains bugs device is better, single mode works fine on the trigger, yes it worked before but 50/50 success, now it is works better, yes trigger isssues still there range of time is the same. But many of minor bugs such a sound bug, brightness etc is gone. I am not gonna sell it since I get more usable device now. You should know trigger issues is not only problems that were in it. I tried to flash 1.22 before and it didnt help. Upd: I like filemanager thing, I hope minidso publish fpga open source. I testing it now and it looks way more better than before.
@darkonerakot I would rather spend time to port the DS203 interface to DS213 than learn how to use their user interface :) So what is your opinion?
I know you ain't asking me, but I am a click away from buying DS213, provided you would rather spend time on porting your DS203 stuff to DS213 ;)
@sibradzic don’t buy DS213, buy DS203 instead, it has much better support, it works compared to DS213 and you will find tons of alternative firmwares for this device.
@sibradzic don’t buy DS213, buy DS203 instead, it has much better support, it works compared to DS213 and you will find tons of alternative firmwares for this device.
I tried to find shop with ds203, unfortunately they told me same: there is no any ds203(( and I am totally agree with you, ds213 is not worth it.
any chances we can see apps from wildcat? analyzer etc...? Upd: I like this experiments, I would like to test something else.
I’ve been following this chat, I don’t know much about FPGAz and how to program them. I’m 17 right now and planning to take a course in this field but for now I don’t know how to help. oh wait, I think I can help with testing experimental firmwares, I have stlink V2 at hand and also happen to have a bench Oscilloscope and Function generator to match the results. Let me know if I can help I really want to see this tiny device be of some use.
@gabonator That's brilliant! Hats off to you. Now people can flash fpga region on ds213.
I have news from mini-dso team
In fact, we have made more than 90% progress in bug repair of FPGA. The new upgrade firmware will now be released after the A / D has been repaired. It is expected to be within one month.
@aviralpatel do you own DS203 or DS213 or LA104?
@gabonator I have DS213.
I have news from mini-dso team
In fact, we have made more than 90% progress in bug repair of FPGA. The new upgrade firmware will now be released after the A / D has been repaired. It is expected to be within one month.
@aviralpatel do you own DS203 or DS213 or LA104?
That is good news!
I have news from mini-dso team
In fact, we have made more than 90% progress in bug repair of FPGA. The new upgrade firmware will now be released after the A / D has been repaired. It is expected to be within one month.
@aviralpatel do you own DS203 or DS213 or LA104?
That's great! I'm a bit lost regarding the possibility of using your firmware on the ds213. Is that possible already (but doesn't solve the trigger bugs)? Or are you working on porting it? Or none of the above? Thanks for your work in any case
There is a guy who fixed trigger bug http://www.minidso.com/forum.php?mod=redirect&goto=findpost&ptid=3397&pid=8516
There is a guy who fixed trigger bug http://www.minidso.com/forum.php?mod=redirect&goto=findpost&ptid=3397&pid=8516
just tried it, good work, but auto mode is buggy, I would like to use gabonator`s file manager with option to switch between this scope programms, 1st for auto mode 2nd for single mode, profit)
Websocket oscilloscope running on DS213! Still in beta, not ready for release and public testing, but looks promising!
Can you share some more info how to build good software for dso213 because all of the workarounds for the trigger bugs I have seen sofar has been binary only. What I know is that
1) 1.20 fw seems to be more stable than 1.22? But I could not find the fw 1.20 anywhere, only 1.22
2) 1.22 application source code has been released on http://www.minidso.com/forum.php?mod=viewthread&tid=3339&extra=page%3D1
3) Cortol123 has released binary fix on http://www.minidso.com/forum.php?mod=viewthread&tid=3397&extra=page%3D1&page=2 Based on the explanation it has been by making changes to 1.22 source code released by minidso to workaround the fpga bugs during initialization phase.
4) Gabonator has released here the fpgapatch zip on this bug size that fix some problems. Has it been done by extracting the fpga binary part from fw 1.20 release? And is the patch supposed to be installed on top of the official 1.22 release?
5) To get a working system, should one install both the Gabonators fpga patch and the Cortols app changes?
6) Has anybody set up source code repository for maintaining these and possible other future fixes for dso213?
There is a new official firmware + FPGA update: http://www.minidso.com/forum.php?mod=viewthread&tid=3357 direct link: http://www.minidso.com/forumdownload/DS213%20APP%202.14%20FPGA018.zip
the trigger bug in single shot mode seems fixed but we still cant zoom in after the waveform is acquired. It's late here, I'm gonna sleep, will test this one tomorrow.
Just tested 1.24 TL TH in auto is buggy. Zoom in out is locked now in pause, norm mode has so many bugs: 1) freq mesurement 2) Xpos change on 200ms
5 minutes test, I think it is low cost FPGA, if I find something else will let you now. Low cost FPGA?
if you zoom in too much on the waveform it gets stuck, the only way to get it working is by either restarting or by pausing and then resuming.
Based on the speed at which minidso updates their firmware, I wonder if this team can help fix some of the remaining bugs and some feature requests ;-)
In addition to what aviral and darkonerakot have mentioned:
1) zoom during pause/HOLD mode 2) Xpos change on 200ms 3) Disable 'SLOW' mode or prevent SLOW mode from forcing the Xpos and 20mS timebase. I tend to scroll the wheel in the wrong direct to SLOW mode and it changes the settings. Disable would be my preference.
I am still at least happy that this is somewhat usable and excited for websocket and other gabonator tweaks!!!
If anyone is still available on this thread......how would i download the newest firmware for the DS213 i somehow erased the firmware from the device and its asking for anew i attempted to use the 1.24 link above: http://www.minidso.com/forumdownload/DS213%20APP%202.14%20FPGA018.zip
....and the device isnt retaining the information thanks
I happened upon here after dusting off my ds213. I was pleased to see that they fixed the trigger issues. Ended up abouts here. I certainly do like that some of those ds203 gui layouts and that web sockets lookin front end does look pretty nice too. Any idea of the function generator can be turned off or is there a magic value that it has the least impact? I've just been using 10Hz and can't realistically interpret the total impact it does have on a reading. If anyone hadn't noticed before, leave that a or b probe floating and crank the square wave up to 8MHz. It's very noticeable there.
There is an update now (2020.06.30) in the minidso forum. Nothing to write home about.
APP V1.26: Automatically call the corresponding parameter table according to the ADC string in DFU The problem of using U disk to set parameters. Increase the gear when the channel A and channel B probe attenuation is 10 times Fixed an issue where the SaveBuf and SaveCSV options in the menu would occasionally freeze.
Thread: http://www.minidso.com/forum.php?mod=viewthread&tid=3357&extra=page%3D1%26filter%3Dtypeid%26typeid%3D154 Direct link: http://www.minidso.com/forumdownload/DS213%20APP%201.26%20FPGA018.zip
How to:
1.Enter DS213 DFU mode. (turn on device while holding play pause button) 2.Copy FPGA_CFG.ADR to DFU disk, Then the DFU disk will restart. 3.Copy STMU_213_018.bin to DFU disk, Then the DFU disk will restart. 4.Copy DS213AppV1.26.hex to DFU disk. 5.Restart DS213.
After these steps I get the error "FPGA Configuratoin err!" and it jumps directly into the DFU mode.
What can I do to un-brick my beloved DS213?
any news about time scale in pause?
After these steps I get the error "FPGA Configuratoin err!" and it jumps directly into the DFU mode.
What can I do to un-brick my beloved DS213?
I had exactly the same issue with 2.14. I reached the support. They have sent me the old versions of all files and it still didn't un-brick the DS213. In the end they asked me to try on another computer and to my surprise that solved the issue. I was very skeptical about that, as I used that same machine to update my TS80 soldering iron (made by the same guys) and it didn't had any issues with it. Don't really know what the issue was, but try with another computer, just to be on the safe side.
any news about time scale in pause?
I tried the limitations reported by @caykroyd1 and they are still there. Not a deal breaker for me to be honest, I rather like the device (although I must confess I find touch screen oscilloscopes way faster to use).
Thank you for the response. I followed your instructions and the device still wont retain the information. I even created a folder for the files and when i reset the device the folder and the files are gone from the device. Still in limbo....lol
Craig
On Fri, Jul 3, 2020 at 1:38 PM David Buezas notifications@github.com wrote:
There is an update now in the minidso forum. Nothing to write home about.
APP V1.26: Automatically call the corresponding parameter table according to the ADC string in DFU The problem of using U disk to set parameters. Increase the gear when the channel A and channel B probe attenuation is 10 times Fixed an issue where the SaveBuf and SaveCSV options in the menu would occasionally freeze.
Thread: http://www.minidso.com/forum.php?mod=viewthread&tid=3357&extra=page%3D1%26filter%3Dtypeid%26typeid%3D154 Direct link: http://www.minidso.com/forumdownload/DS213%20APP%201.26%20FPGA018.zip
How to:
1.Enter DS213 DFU mode. (turn on device while holding play pause button) 2.Copy FPGA_CFG.ADR to DFU disk, Then the DFU disk will restart. 3.Copy STMU_213_018.bin to DFU disk, Then the DFU disk will restart. 4.Copy DS213AppV1.26.hex to DFU disk. 5.Restart DS213.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/gabonator/DS203/issues/44#issuecomment-653632663, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJ4SO3RG3GODWJOUDDQXIC3RZYJR7ANCNFSM4GSSHJPQ .
There is an update now (2020.06.30) in the minidso forum. Nothing to write home about.
APP V1.26: Automatically call the corresponding parameter table according to the ADC string in DFU The problem of using U disk to set parameters. Increase the gear when the channel A and channel B probe attenuation is 10 times Fixed an issue where the SaveBuf and SaveCSV options in the menu would occasionally freeze.
Thread: http://www.minidso.com/forum.php?mod=viewthread&tid=3357&extra=page%3D1%26filter%3Dtypeid%26typeid%3D154 Direct link: http://www.minidso.com/forumdownload/DS213%20APP%201.26%20FPGA018.zip
How to:
1.Enter DS213 DFU mode. (turn on device while holding play pause button) 2.Copy FPGA_CFG.ADR to DFU disk, Then the DFU disk will restart. 3.Copy STMU_213_018.bin to DFU disk, Then the DFU disk will restart. 4.Copy DS213AppV1.26.hex to DFU disk. 5.Restart DS213.
Thank you for the response. I followed your instructions and the device still wont retain the information. I even created a folder for the files and when i reset the device the folder and the files are gone from the device. Still in limbo....lol
Craig
@cyphrsphyr you have to copy the files one by one and wait for the device to restart in between. All in the indicated order. It worked perfectly for me. Maybe try a different computer?
Any compatibility with the DS213?
http://www.miniware.com.cn/product/ds213-mini-oscilloscope/
Other sketchy sources (ebay, banggood.com, etc.) say this has 15MHz Analog Bandwidth. From main website: (link above)
CPU: ARM Cortex M3
FIFO & Control: FPGA
ADC: HWD9288-100
Analog Channels: 2([CH_A] [CH_B])
Digital Channels: 2([CH_C] [CH_D])
Operation Channel: INV [CH_A], INV [CH_B], [CH_A]+[CH_B]、 [CH_A]-[CH_B]、[CH_C]&[CH_D]、[CH_C] | [CH_D]
Vertical Sensitivity: 10mV-10V/div (1-2-5 STEP) (using X1 probe)
Vertical Resolution: 8 bits
Sample Memory Depth: 4 channels, 4*4K
Coupling: DC, AC
Max Input Voltage: ±40Vpp (using X1 probe)
Trigger Types: Ascend/Descend Edge Trigger Mode, Positive/Negative Pulse Trigger, Logic Trigger
Trigger Mode: Auto, Normal, Single, Slow
Trigger Source: [CH_A] [CH_B] [CH_C] [CH_D]
Signal Source: Square Wave: 10Hz to 8MHz, in total 20 shifts and 3 Vpp Signal Sources;
Sine/Triangle/Sawtooth Wave: 10Hz to 20MHz, in total 11 shifts and 3 Vpp Signal Sources
Storage: built in 8M USB disk
File Types: BMP、BUF、CSV
Auto Measurement Types: Signal sequence/cycle/duty ratio, peak voltage/virtual value/max value/min value/average
Cursor Measurement: Time value, Amplitude value
Display Modes: 4 wave lines: Line 1: [CH_A], HIDE
Line 2: [CH_B], HIDE
Line 3: [CH_C], REC_1, REC _2, REC _3, REC _4, HIDE
Line 4: [CH_D], [CH_A]+[CH_B], [CH_A]-[CH_B], [CH_C]&[CH_D], [CH_C] | [CH_D], HIDE
Sampling Mode: Real-time Sampling
Sampling Rate: 100M Sa/s
Battery: 1000mAh
Size: 99.5mmx58.5mmx13.5mm
Weight: 129g (with battery)
Certificate: CE, FCC