DSO203 GCC APP - Community Edition (2.51+SmTech1.8+Fixes)

End-Of-Life Products & Services DSO
#214

Thanks very much for this and thanks to Wildcat for the material merged in.



Loaded up and running OK.

#215

Hi PMOS,



WOW! What a tremendous amount of work you’ve put into this! Thank you soooo much for making this scope so much better.



Dan

#216



Nice one!

I notice channel B is still noisier than A. Maybe there’s a bug in the PCB.



Another thing! I can’t find how to enable and change manual trigger threshold in this version. Can you explain me how to do it? Thanks!

#217

Thanks Jack,

I finally had some free time that I could spend with this. All thanks to Wildcat though. He did a tremendous job.



To change to manual trigger adjustment:

  • press: Button 2 (square) for 1 to 2 seconds - You’ll see the trigger menu indicator change to manual.

    (short press changes auto trigger levels and extra long press (>3 seconds) goes into calibration mode)



    I’ll update the first post with the new readme. It’s all there.
#218

[code]
v1.28

  • RAM usage optimization
  • Channel 4 source change turnaround fix (move trigger source to last selected ch)
  • auto switch to full buffer mode when enabling FFT/Spectrograms
    [/code]
    Latest download: https://github.com/pmos69/dso203_gcc/zipball/master

    If you just want the APP, get it here: http://pmos69.net/dso203/APP_G251.hex



    Tested with:
  • SYS 1.50 1.6 from Marco Sinatti ( http://pmos69.net/dso203/SYS25116.hex ) - NEEDED FOR CORRECT GENERATOR FREQUENCIES
  • FPGA 2.61 ( http://pmos69.net/dso203/FPGA261.zip )
  • HW 2.6
#219

[code]
v1.29

  • Big Display Meters (METER) - Accessible from the Channel 4 menu.
    • Corresponding meter/measurement indicated by marker.
    • Change the indicated meter as usual - The Big meter will reflect the change (Any channel, any measurement).
      [/code]
      Latest download: https://github.com/pmos69/dso203_gcc/zipball/master

      If you just want the APP, get it here: http://pmos69.net/dso203/APP_G251.hex



      Tested with:
  • SYS 1.50 1.6 from Marco Sinatti ( http://pmos69.net/dso203/SYS25116.hex ) - NEEDED FOR CORRECT GENERATOR FREQUENCIES
  • FPGA 2.61 ( http://pmos69.net/dso203/FPGA261.zip )
  • HW 2.6
#220

Hi,



I tried to upgrade my firmware, for the first time.

The hardware is v2.6.



I followed this wiki:

<LINK_TEXT text=“http://www.seeedstudio.com/wiki/DSO_Qua … g_Firmware”>http://www.seeedstudio.com/wiki/DSO_Quad:Upgrading_Firmware</LINK_TEXT>



I downloaded this files:

http://pmos69.net/dso203/

(SYS25116.hex, APP_G251.hex, FPGA261.zip)



wget http://www.seeedstudio.com/wiki/images/3/31/Dso.img.zip



I go to the upgrade mode (>|| button holding while powering up).

I copied SYS25116.hex to /mnt/dso (linux), I powered off an on again the dso (slide-switch), the file was renamed to .RDY. I have not unplugged the mini-usb cable.



Then I copied APP_G251.hex, the file has been disappeared, after on-off cycle, instead of renamed to APP_G251.rdy.

Before upgrading the FPGA, I tried to power on the device and see the new app in action.



I powered on, and the dso quad stuck at the INIT SCREEN.



I see this:
[code]
DSO QUAD

Hardware Ver 2.6 Serial No: E9A0B87E
DS203 Mini DSO SYS Ver 1.31
GCC v1.29 APP Community Edition
[/code]

After I did copied the FPGA files too (CFG_FPGA.ADR, power cycle, V261FPGA.BIN).

Still no luck.



When I plug into computer (while this init screen is showing), the computer does not recognize it.

So I could not copy Dso.img.zip file with dd command to the device.

I tried to dd the Dso.img.zip while in DFU mode, I got this:
</s><i> </i># bunzip2 Dso.img.zip --stdout | dd of=/dev/sdb dd: writing to: ”/dev/sdb”: No more space left on device 1025+0 records in 1024+0 records out 524288 bytes (524 kB) copied, 2,03603 s, 258 kB/s <e>

Any helping hands?

#221

Ok, before power cycle, I can do a umount/mount cycle, and check of the upgrade result:



SYS25116.hex -> SYS25116.RDY

APP_G251.hex -> APP_G251.RDY

CFG_FPGA.ADR -> CFG_FPGA.ERR



Dunno, should I proceed with V261FPGA.BIN too?

Why the error?



Ok, I proceeded:

V261FPGA.BIN -> V261FPGA.NOT



Any hint?



Some more tries:

downloaded FPGA_v222:

http://garden.seeedstudio.com/images/2/23/FPGA_V222.rar



CFG_FPGA.ADR -> CFG_FPGA.SET

V222FPGA.BIN -> V222FPGA.NOT



downloaded FPGA_V25:

http://garden.seeedstudio.com/images/1/12/FPGA_V25.rar

CFG_FPGA.ADR -> CFG_FPGA.SET

FPGA_V25.BIN -> FPGA_V25.NOT



Ok, I really stuck.



Maybe the firmware upgrade is too old?

I see this:
[code]
DSO QUAD

Device Firmware Upgrade V3.10
Please copy .Hex/.Bin file to
DFU virtual USB disk.
[/code]

Best,

Laszlo

#222

Reading the wiki one more time, I got the idea, what if I reupload an older sys, app, fpga firmwares in that order, and maybe the fpga down the line success.



So, downloaded:

http://garden.seeedstudio.com/images/c/c4/SYS_B134.rar

http://garden.seeedstudio.com/images/f/f9/APP_B232.rar

http://garden.seeedstudio.com/images/2/23/FPGA_V222.rar



And uploaded to the devices, one by one:

SYS_B134.hex -> SYS_B134.RDY

APP_B232.hex -> APP_B232.RDY

CFG_FPGA.ADR -> CFG_FPGA.SET

V222FPGA.BIN -> V222FPGA.NOT



Also tried these too:

Sys_151: <LINK_TEXT text=“http://www.seeedstudio.com/forum/downlo … php?id=857”>http://www.seeedstudio.com/forum/download/file.php?id=857</LINK_TEXT>

App_252: <LINK_TEXT text=“http://www.seeedstudio.com/forum/downlo … php?id=856”>http://www.seeedstudio.com/forum/download/file.php?id=856</LINK_TEXT>

FPGA261: <LINK_TEXT text=“http://www.seeedstudio.com/forum/downlo … php?id=858”>http://www.seeedstudio.com/forum/download/file.php?id=858</LINK_TEXT>



SYS_B151.hex -> SYS_B151.RDY

AP1_B252.hex -> AP1_B252.RDY

CFG_FPGA.ADR -> CFG_FPGA.SET

V261FPGA.BIN -> V261FPGA.NOT



Still no luck. Any more ideas?



Best,

Laszlo

#223

Bravo to the authors for the great work.

When can we expect a new version.

Regards, Peter!

#224

Available time has been quite rare, so I can’t really say. :confused:

I have a few things in the development ToDo, but haven’t been able to get anything done.



(unless more code contributions come in, and in that case I’ll have to find the time)

#225

This DSO203 GCC APP works with hardware 2.7 ?

#226

pmos69, thanks for the great work and fast response.

If I can give some suggestions:

  1. Is it possible to start by changing the color of the testimony in FFT mode from red to yellow or green. Red is fuzzy.
  2. To add to the ranges of horizontal scanning 50nS/del.
  3. Automatic switching between the range of the horizontal sweep.



    As with Chip’s APP.

    Regards !

    Peter
#227

Works perfectly.

#228

HW: 2.70, Sys: 1.52, GCC App: 2.51 (http://pmos69.net/dso203/APP_G251.hex).

Bug: actual generator frequency is 2 times lower than selected in all modes except PWM.

#229

I have downloaded: https://github.com/pmos69/dso203_gcc/zipball/master

compiled, updated firmware. DSO shows initial screen with version and hangs.

I noticed that http://pmos69.net/dso203/APP_G251.hex is not compiled from this source.

What is wrong?

My toolchain version:

arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.7.3 20130312 (release) [ARM/embedded-4_7-branch revision 196615]

GNU assembler (GNU Tools for ARM Embedded Processors) 2.22.0.20130312

#230

You are absolutely right counterpart. Software is great, but I want some finishing and supplements.

Also not working properly vertical scanning ranges of volts / div.

#231

I think you have the wrong sys file loaded to get that bug. Check OP and use the linked sys25116

#232

Hello,

I want to ask some of the authors of the software to show me where exactly are configured ranges Horizontal scanning: 1S …0,1uS.

The idea is to add a range of 0.05uS.

Thanks in advance!



P.S: Time for v1.30!

#233

First off, thanks to pmos and all the devs that have turned the Quad into something much more than when I first got it a year and a half ago.



I was wondering if it would be possible get multiple binaries for this community edition, packaged for alternate slots? With several great firmwares available, it would be nice to be able organize them into different slots without having to reflash to run a different firmware.



I built a hex 1.29 locally compiled for slot two, but it crashes (freezes at loadup screen and beeps constantly). The binary I downloaded for 1.29 run’s fine(in slot one). I used the 2013q1 arm-eabi-none toolchain from Launchpad, but I manually “installed”(unzipped) it to a temp folder and hacked up the built script and environment to avoid interfering with some other gcc toolchains I have installed. So it’s entirely possible I goofed it up somewhere. From reading some of the other forums, I’m a little worried I’m going to hose my bootloader with a bad build.



Thanks again,



Jon