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

Moderators: lily.li, violet, jeremy882, crail.lyu969

fflan
Pre-kindergarten
Pre-kindergarten
Posts: 10
Joined: Tue Dec 03, 2013 12:21 am

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

Post by fflan » Tue Dec 03, 2013 1:12 am

Hi there,
I got the last version from ebay, 2.72 too, HW v2.7b and tried many things to get a better app because of really bad accuracy regarding tensions. (zero and Abs values)
The selling brand is different than seedstudio -it wasn't available here when I purchased it.

I tried the community app with all the resource required : it worked, but can't save parameters (was discovering 8m Flash memory)
I reinstalled the SYS_B160.hex system, and the app had problems (graphical and functional, sorry I didn't remind exactly what, but i can make another test).
So I tried Gabonator version, with the 2.61 fgpa but kept my Sys_B160 fmw, and it worked partially, I can save parameters and (better) calibration settings, but failed to save data (bmp, dat, csv) and corrupts seriously the memory if I try.

So, actually I have it on slot 1, reinstalled my original V110 app on slot 3 working on a mixed system :
Fgpa 2.61, SysB160, gabonator (can't save bmp), and original app V110 (not community) which works well despite the bad accuracy.

I tried altbios04 : Can't install it, tried altbios03 : memory chip corrupted.
It costed me a lot of time to calibrate these applications, but Gabonator gave me really better results.
Really sad I can't use the community app, I saw in the release notes a better calibration handling and all others good stuffs...
Can I help more ?
Thanks.

fflan
Pre-kindergarten
Pre-kindergarten
Posts: 10
Joined: Tue Dec 03, 2013 12:21 am

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

Post by fflan » Tue Dec 03, 2013 1:28 am

I forgot to mention Quadpawn to jpa: (great work really impressive, thanks a lot!)
It works, but the process to install it is not conventionnal, because when I drop the hex file on the virtual disk, I don' t get another instance with the .rdy extension, it just became busy while copying the file.
But If I power off/on, the application is ok with my configuration, it is able to write calibration.

flochechx
Pre-kindergarten
Pre-kindergarten
Posts: 2
Joined: Tue Dec 03, 2013 6:50 am

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

Post by flochechx » Tue Dec 03, 2013 6:58 am

Hello all,

I just bought a DSO and right now I am really happy with it. The finishing and the hardware is very great for such a low price.

Anyway, I would like to participate in the software developpment, I really like to code and this project is challenging.
My questions are, could anyone summarize to me which firmware/APP/FPGA are the 'best' and the most used by developpers here ?
From my reading on this forum, which is from my side a bit messy, I believe that the best firmware is the one from Marco => Where can I find the latest source code ? I am not sure if the one I got is the right one.
For the APP it seems this one from Gabonator is the one to use. Right ?
What about the FPGA ?

Thanks a lot everyone !

Flo

myankele
Pre-kindergarten
Pre-kindergarten
Posts: 5
Joined: Thu Nov 28, 2013 7:21 am

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

Post by myankele » Tue Dec 03, 2013 3:27 pm

Flo: It seems that we are trying to figure out what can be ran on the new 8MB 2.72HW units. (BTW: Don't go above 35V)

fflan: I tried to install QuadPawn as well. My setup is not modified at all: Stock everything from the store.
It has HW version 2.72, SYS 1.60, App (PLUS A1) 1.10.
I held button 4, starting copying PAWN_011.HEX. It set for a while and then said that USB Drive disconnected.
I turned it on and off and QuadPawn came up. So, so far, same results as you (no .rdy file)
Howewer, I don't see calibration.ini file after running the Calibration app.

Looking at the Calibration app, save_calibration() should create this file. Do you have it ?
EDIT: I see CALIBRAT.INI now. I needed to unplug the cable and replug it.

In early November, Petteri Aimonen, made a few changes related to 8M devices. Some of the comments were:
"Upgrade to AlterBIOS 0.4 to make it work on 8M devices." and "Add support for 8M flash chip"

So, it is strange that you can't get this bios to work. Although, I didn't try.
Last edited by myankele on Wed Dec 04, 2013 6:20 am, edited 1 time in total.

fflan
Pre-kindergarten
Pre-kindergarten
Posts: 10
Joined: Tue Dec 03, 2013 12:21 am

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

Post by fflan » Tue Dec 03, 2013 10:11 pm

Howewer, I don't see calibration.ini file after running the Calibration app.
Looking at the Calibration app, save_calibration() should create this file. Do you have it ?
Yes, pawn is ok for me too !
I have two files : CALIB.DAT and CALIBRAT.INI (which I saved elsewhere)
I think they are for APP110 and Pawn when I have it (APP110 is now installed on slot 3 and it uses slot 3/4, so I don't have pawn working anymore : not surprising.)
In early November, Petteri Aimonen, made a few changes related to 8M devices. Some of the comments were:
"Upgrade to AlterBIOS 0.4 to make it work on 8M devices." and "Add support for 8M flash chip"
My problem is actually with SYS1.6, alterbios seems to not install anything. (How to be sure it is installed ?)
I have tried Sys1.52 and the community app wasn't saving anything...
I don't remember if I tried at this moment AlterBios, but I think I did.

Pehaps the good combination is the older SYS, alterbios0.4 and the community app : to be tried...

My other concern is gabonator, really good and working with sys 1.6 (I can save parameters, but others files corrupts the memory, and I lose calibration, and because It is not stored on the flash memory, I can't restore it.
http://www.seeedstudio.com/forum/viewto ... 441#p18441

An ideal configuration would be (for me) : Gabonator and the community APP fully working, with or without Pawn
OR
Gabonator and Pawn
OR
Community APP and Pawn
The main fault on the origina APP is tension and zero V accuracy, ridiculous...and well adressed by the two others;..

Thanks for your help

bobtidey
Elementary-1
Elementary-1
Posts: 174
Joined: Sun May 13, 2012 9:39 am
Are you a staff member of seeedstudio?: no
Which products/projects are your favorite?: DSO Quad

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

Post by bobtidey » Tue Dec 03, 2013 11:21 pm

Thanks to recent posters for running the tests on the 8MB hardware which do show that there are problems with running the alternative software on this model. I, for one, am keen we get this resolved as I don't want to get stuck with the supplied software on the second 8MB model I am getting when my existing 2MB model can run all the alternate apps without problems.

Here is my attempt at a summary of software sources to be considered. Please correct, add as needed.

There are 4 main apps plus the Pawn scripting apps.

Standard APP as supplied by manufacturer

Gabonator, Different UI approach, source at https://github.com/gabonator/DS203

Community App, many improvements, source at https://github.com/pmos69/dso203_gcc

Wildcat - Branch of Community App, not all features but some nice improvements, Zip of code is in post here http://www.seeedstudio.com/forum/viewto ... cat#p18218

Then there are 3 main current versions of SYS

SYS1.50 as supplied by manufacturer 2MB support, can be used with Wildcat, source at https://github.com/Seeed-Studio/DSOQuad_SourceCode

SYS252116 small modification to standard SYS (2MB) to support more signal gen range, used by Community App, source is in this post http://www.seeedstudio.com/forum/viewto ... 116#p16851 although it is labelled as 1.6

SYS1.6 as supplied by manufacturer and supports only 8MB, source is http://kapsi.fi/~jpa/stuff/other/dso_qu ... ources.rar

SYS1.6 and 1.5 mainly differ around the ExtFlash support. Logically the API looks the same which is why I thought that the alternate apps might have worked. My current theory is that because the 1.6 SYS has much bigger Flash buffers then there may be a problem with the RAM memory footprint of the SYS and the APPs overlapping because of that. I don't know at the moment what sets the memory base addresses of the app and the SYS to see if the apps can be adjusted to avoid any conflict.

It is possible that Alterbios could be used with the older SYS but I can't find any good explanation of Alterbios operation other than it can take over the standard Bios calls, but there was a comment that the App also has to be adjusted to use this.

rapp.chr
Pre-kindergarten
Pre-kindergarten
Posts: 2
Joined: Wed Dec 04, 2013 3:57 am

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

Post by rapp.chr » Wed Dec 04, 2013 4:00 am

bobtidey wrote:Thanks to recent posters for running the tests on the 8MB hardware which do show that there are problems with running the alternative software on this model. I, for one, am keen we get this resolved as I don't want to get stuck with the supplied software on the second 8MB model I am getting when my existing 2MB model can run all the alternate apps without problems....
And which of these will work with latest Hardware revision 2.72 and 8M flash? The list itself is not new, we need to know which of these support the hardware, or are working on supporting it.

fflan
Pre-kindergarten
Pre-kindergarten
Posts: 10
Joined: Tue Dec 03, 2013 12:21 am

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

Post by fflan » Wed Dec 04, 2013 5:01 am

@bobtidey : Good summarize...
I've seen a source code managing the two memory chipset, but I don't remember which app it was.

I have just tried that (the community pack) :
SYS 1.50 1.6 from Marco Sinatti ( http://pmos69.net/dso203/SYS25116.hex )
APP_G251.hex
FPGA 2.61
The device is recognized like having a 2Mo, you can't format, you can't access or save, but the app starts.
Alterbios 0.4 does not install (or I don't know how, because it kept copying for ever)

So actually we need Sys1.6 on this device.
I put SYS_B160 and restart with community app : "parameter record not found" before starting.
But now I can format and I can save calibration parameters (dummy test)
I get a file 9222D88A.WPT.
I succeed to save ONE BMP of 47k and ONE BUF, but after that, the next files are 0 ko, I get ERR with all the next trials.
After a new quick format I can save another bitmap (you must disconnect/reconnect usb to see it)
In either case, the bitmap is readable but not... nice, for the less...
I can't access to the timing under AUTO triggering : the field is empty
I can't access to frequency above 50khz in square mode...
...
So, it's useless like that...

I can try the Wildcat version under Sys1.6, but I'm sceptic. Edit: Confirmed, it is worse, when saving the second bitmap, it crashes.

@rapp.chr : read my previous post, APP110 (original for v2.7, the only one good for saving bmp etc), gabonator (with the restiction of saving wav, bmp...) and quadpawn are working with system 1.6 on my quad.

edit : Forgot to mention the dfu version v3.12c, and I miss a logo (grey frame)

rapp.chr
Pre-kindergarten
Pre-kindergarten
Posts: 2
Joined: Wed Dec 04, 2013 3:57 am

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

Post by rapp.chr » Wed Dec 04, 2013 3:58 pm

fflan wrote: @rapp.chr : read my previous post, APP110 (original for v2.7, the only one good for saving bmp etc), gabonator (with the restiction of saving wav, bmp...) and quadpawn are working with system 1.6 on my quad.
Thanks, I must have missed that :)

flochechx
Pre-kindergarten
Pre-kindergarten
Posts: 2
Joined: Tue Dec 03, 2013 6:50 am

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

Post by flochechx » Fri Dec 06, 2013 3:43 am

Hello everyone,

Thanks for the summarize, it helps!

I am looking at the source code, and I think I will work on the SYS to start with the basics, and after on the community APP. The Gabonator one does not seem to need any improvment :).
For the 2MB/8MB story, I guess you mean the external flash ? I saw on the schematic that the ext flash is a 16MB. Even if I guess few MB are used to load the FPGA (normally less than 1mb should be enough), to what needs are the left ones?

However I saw with disappointment that the JTAG port on the STM32 is used by other stuff and is not available for debug :cry: . I was expecting to debug it using an Rlink and Ride (similar to ST link).

Thanks!

Post Reply