DS203 quad user interface design

Products & Technology DSO Quad
#5

Hi Gabonator1

I too am a fan of the quad. However, I am sure the original authors must be busy with something else. Otherwise, it seems to me a brilliant idea to have a pocket scope that can do so much. In fact I loved the Nano so much, I blindly purchased the quad and sold my nano to a client. Now I realise it wasn’t a smart move.

I like what you’re doing with the UI and I wish I can help. I wish I can help in some way. I am used to coding a few types of processors and Arm7 is one of them. I haven’t really had the time to indulge in the hacking of this scope, but your idea looks promising.

Let me know if you need any specific help and I’ll try to assist whichever way I can. I cannot promise much because I am pretty loaded at the moment.

I sure hope to have some of the following

  • better / reliable triggering
  • better calibration procedures
  • a better DSO quad.

Regards
Jerson
jerson.co.in

#6

Hi everyone!

I really appreciate your interest. The progress of this project is highly dependent on my free time, which is currently very precious. What you see is what have I done mostly during nights when I returned from work :slight_smile:. My plan was to design a powerful and easy to read/write C++ framework for developing custom exensions for ds203. After implementing all the basic functions, it shoud be quite simple for everyone to change/implement new features with the basic knowledge of C/C++. The reason I released the early preview application is to find more people who would like to involve in this project. They don’t need to be programmers, after some time when the application will be more or less working, we will need testers and people with good ideas to improve functions of the ds203.

Currently I am looking for someone from the hardware/software designers of ds203 (maybe some seeedstudio stuff?), I am having some stupid problems with configuring stm32’s peripherals and I can’t move forward…
It would be nice to have some experienced FPGA designer for developing advanced triggering algorithms.

My application can be compiled for two platforms - ArmM3 and for Win32, the project file “ds203.sln” can be opened with Visual Studio 2005. All the development and testing was made in Windows environment and Visual Studio. And when I thought it is working well, I compiled it with batch file “ds203ui/OnArmM3/makefile.bat” which automatically loads the compiled .hex file onto ds203 device. So even if this is reading someone who doesn’t have ds203 scope, can try to compile and run the project to get the basic overview of the firmware features.

I am planning these features for the new firmware:

  • Advanced signal generator (I need it for my current project)
    • more types of waveforms and better resolution than 36 points importable from the 2MB disk
    • simple AM/FM modulation
    • transferring waves from scope view into generator (you will record some wave form at first and then the dso will synthetize it - simple recorder/player)
  • Realtime USB transfer of sampled data (2nd planned feature)
  • Realtime Uart decoder with automatic baud rate calculator
  • True RMS voltmeter (I found many posts about the low accurancy of ds203, but I believe it is a simple task to calibrate it)
  • Export to WAV (Windows PCM), SVG http://gabonator.yweb.sk/sim/download/sources/Owon%20PDS5022S%20driver/samples/nice.svghttp://valky.eu/?data/news/owon.txt, TEXT file
  • FFT (I don’t know whether this feature can be used for anything meaningful, but it looks good)

I am sick of all the expensive oscilloscopes that have a full range of nice features, but their architecture is closed and does not offer any way of implementing new features. I am happy that I found ds203, maybe it does not have input circuits or frequency range as normal oscilloscopes, but for visualizing and analysing signals it’s a perfect tool.
At least it can be considered as development board with 32 bit microcontroller + fpga + display, a nice toy for everyone who want to start learning how to work with these devices and don’t want to spend money on some dev-board and JTAG programmer.

Here is my current problem:
I cannot change the number of samples for the generator. It does not work by calling __Set(ANALOG_CNT, xxx), nor by settings the DMA values directly (*((vu32 *)(0x40020400+0x48))) = xxx. I can change the pointer for source data (DMA2_CMAR4), but it always sythesize only the first 36 values. Any idea?

#7

If you look at the DS0Quad_SourceCode/SYS_V1.50/source directory from github, in the file Config.c on line 425 you will see the offending code DMA2_CNDTR4 = 36 // DMA2_CH4 number of data(*2 Bytes) In theory, if you call __Set(ANALOG_CNT, XXX) it should reset this value to the specified value. I haven’t looked at the ARM spec, but my guess is that you cannot change the value of the CNDTR4 register unless you first stop the DMA. You should be able to stop it by:

DMA2_CCR4 &= ~1;

and restart by

DMA2_CCR4 |= 1;

#8

Gabonator,

I was trying to compile your code in Linux to see if I could add some stuff but it doesn’t have a Makefile. I tried to make one but there are lots of microsoft specific things that I didn’t want to invest in fixing without having a way to check them back in. Two issues so far: it seems that filenames and how they are included are not consistent in term of upper/lower case (windows doesn’t seem to care), and there seems to be references to include files that are probably microsoft only (like windows.h). Also, I think you build both the arm version and a windows version, but I’m not sure which files go with which version. Right now all the top level files need a windows.h file. It would be nice at a minimum the arm code could build without window, and better if even the debug version could build in a cross-platform way.

#9

relavak, try this:
http://pub.valky.eu/ds203ui_preview2.zip

I tried to use correct names of files in includes, also I put there simple makefile for linux, but I didn’t try it. Please tell me if you succeed building it for linux, or what steps were necessary to successfully build the code on linux machinue. For better cooperation, I would like to place this project on sourceforge or github. Which one do you prefer (svn/git) ?

#10

I tried to compile in linux and found some problems. The first problem is that I didn’t have instructions on how you expected to compile the code so I did this:

cd Build/arm_linux make

which is not what I think you did, but anyway that is what I eventually got to work. Unfortunately I had to change quite a bit of stuff including:

mv Source/HwLayer/bios.h Source/HwLayer/Bios.h mv Source/Core/design.h Source/Core/Design.h mv Source/Gui/toolbar.h Source/Core/Toolbar.h in Source/HwLayer/ArmM3/src/interrupt.c use interrupt.h not Interrupt.h in Source/HwLayer/ArmM3/src/startup.c use interrupt.h not Interrupt.h in Source/HwLayer/ArmM3/src/cbios.cpp use BIOS.h not bios.h (line 5)

You also need new versions of the common/build.mk and arm_linux/Makefile files. You can see I changed quite a bit of stuff especially in build.mk.

I prefer github mainly because I’m trying to learn to use git. I hate svn but like cvs.

UPDATE: I found a way to eliminate the need to change the .lds files. New updates2.zip file.
updates2.zip (1.39 KB)

#11

Hey all, I’m definitely interested in helping out where I can. I’m familiar with C/C++, but mostly for pc. I’ve never worked with ARM before, but am interested in learning.

@gabonator1, two things: First, GREAT WORK! :slight_smile: It looks pretty sweet compared to stock, and secont: for what it’s worth, I vote Git, though as a newcomer I know my vote may not mean much.

#12

Hi guys,

I am really very happy that there are more people that would like to participate in this project. Here is a github repository where is a little improved version of the firmware:
https://github.com/gabonator/DS203

I was having really hard time to configure everything - this was for me the first time to make a git repository, most problems I was having with rsa keys… But now it seems that it is working, so I hope you will enjoy it :slight_smile:

unfortunatelly, I didn’t have time to implement new features, I spent all my time preparing for a medical conference that was in Boston (IEEE AMA), where I was demonstrating a wireless ECG system with visualization on android phone. For more informations see the last PDF link on this page http://ama-ieee.embs.org/program/final-program/. For demonstrating this device I have used the DS203 oscilloscope for generating ECG waveforms. Oscilloscope was connected through resistor divider to the ECG electrodes. Everyone on the conference liked this project very much :slight_smile: Maybe I will later write some report to my blog

#13

Thank you for trying to make something useful from the DSO Quad.

Also I think this thread would be more visible for other DSO Quad users if you reference it from the Tech Support -> DSO Quad section.

Regards.

#14

Good idea cex, I put there link to this discussion.

#15

I downloaded APP_G251.hex from github to my new DSO QUAD. The DFU came back with an extension of .err, and it does not appear to have loaded. I tried booting each button on top.

I have the Frequency response application in the 4th button, and I have upgraded the official firmware. So it appears I can change the firmware’s. Can some one offer some insight into what went wrong?

I upgraded the default firmware first thing when I got it. I now have 1.52 and 2.52 released on 2011-11-15. Could there be an issue with this Oct 28th firmware being older than the latest firmware I have? I have upgrade firmware 3.10, which is what it came with. Perhaps that is a newer firmware. I just got the Quad yesterday evening.

Your GUI looks great, I can’t wait to try it out.

#16

I got the same ERR. I tried downgrading to FPGA 2.5 and sys 1.5 first and it still failed.

#17

Try renaming it to APP.HEX

–EDIT–
It still doesn’t work…

#18

HEX load SOLVED, I got it to install and boot. I did a git clone, instead of web page download. The file I got from the git clone was 76KB, while the web download claimed to be 227KB. Once I got the correct file, it worked just fine.

#19

The 227KB download file is a web page. Thanks for finding this!

Even with the HEX load, I don’t get the error but I don’t get a change in the scope app either.

I tried both APP_G251.hex and copying it as APP.hex.
I tried Linux and Windows both. Do I need to downgrade the FPGA and SYS code for this?
Does it install as the default app or is it on another startup button? I tried buttons 2-3-4 and get no app.

#20

I have the most recent FPGA according to the firmware wiki page. So that’s probably not the issue. I upload my firmware from an XP box, I couldn’t get it quite right with Ubuntu.

Did it come back with a file after you uploaded the firmware? Have you been successful in uploading another firmware? I used the name found in the git repo. Did you obtain your file via git, or by web page? Is your firmware about 76KB?

#21

I just did a diff between the correctly downloaded hex file via web page raw, and via git download. The diff claimed the text for each line to be the same, however the line end character is not. I also noticed the file size as claimed by XP is 75KB for the web copy, and 76KB for the git copy.

The web page raw download produced an .err when I tried to load it. The git copy worked great. Perhaps a zip copy of the original source file would be handy, this would ensure data integrity, as it appears the github web page is modifying the files before sending them for download. Git was intended to be for source code, not binary files, I suspect that’s one reason why this didn’t work as one would expect.

#22

A quick review of the current alt GUI.

I like it much much. I see the grey features, implying they are planned, but not implemented yet. Those look really interesting.

Things I like include,
– Better contract of the text, the flashing text and odd contract of the original gui was some times a bit hard to read for those with less than perfect eye sight.
– Not using the push button of the selector switch, I find them hard to press, especially if I have gloves on.
– I find the gui just plain easier and more intuitive to navigate. Options are near each other, the selector doesn’t jump around the screen, it flows from one selection to the next.

Things that would be really cool to see include,
– Save primary setting such that they are kept when I turn it off, then back on. Things like channel 1 amplitude, trigger setting, time base, ect.
– HEX file that can be loaded into slot 2 or 3 instead of 1. Perhaps noted in the name like APP_G251_slot1.hex APP_G251_slot2.hex, ect.
– Custom wave form uploaded via USB for generator.

All in all, it’s a great start, I wish I were a better programmer and could help. Keep up the good work, I’m eager to see what you come up with next.

#23

I tried to compile under wine, but with out luck. I used “wine cmd” to get into a windows command prompt, but get this message. [code]C:\DS203\Build\arm_win32>makefile.bat
DS203 Build tool by valky.eu
Target slot: !APP!
DFU Drive: !TARGET!

Your current path contains spaces, it can cause some problems…
Press Return key to continue:
Compiler not found !

C:\DS203\Build\arm_win32>
[/code] I changed the makefile.bat like this set CBASE=C:\arm-2011.03\bin\ I would guess there is a space in a step of the compile process that doesn’t match the wine expectations. I don’t know where that might be though. Any thoughts about how to find it or them?[code]C:\DS203\Build\arm_win32>cd C:\arm-2011.03\bin\

C:\arm-2011.03\bin>dir
Volume in drive C is
Volume Serial Number is 0000-0000

Directory of C:\arm-2011.03\bin

12/5/2011 6:20 AM .
12/5/2011 6:20 AM …
4/20/2011 4:34 PM 380,928 arm-none-eabi-abiactel.dll
4/20/2011 4:34 PM 592,896 arm-none-eabi-addr2line.exe
4/20/2011 4:34 PM 611,328 arm-none-eabi-ar.exe
4/20/2011 4:34 PM 1,072,640 arm-none-eabi-as.exe
4/20/2011 4:34 PM 229,888 arm-none-eabi-c++.exe
4/20/2011 4:34 PM 591,872 arm-none-eabi-c++filt.exe
4/20/2011 4:34 PM 228,864 arm-none-eabi-cpp.exe
4/20/2011 4:34 PM 55,808 arm-none-eabi-elfedit.exe
4/20/2011 4:34 PM 229,888 arm-none-eabi-g++.exe
4/20/2011 4:34 PM 226,816 arm-none-eabi-gcc.exe
4/20/2011 4:34 PM 226,816 arm-none-eabi-gcc-4.5.2.exe
4/20/2011 4:34 PM 44,563 arm-none-eabi-gcov.exe
4/20/2011 4:34 PM 4,233,728 arm-none-eabi-gdb.exe
4/20/2011 4:34 PM 656,384 arm-none-eabi-gprof.exe
4/20/2011 4:34 PM 868,864 arm-none-eabi-ld.exe
4/20/2011 4:34 PM 602,624 arm-none-eabi-nm.exe
4/20/2011 4:34 PM 744,448 arm-none-eabi-objcopy.exe
4/20/2011 4:34 PM 888,320 arm-none-eabi-objdump.exe
4/20/2011 4:34 PM 611,328 arm-none-eabi-ranlib.exe
4/20/2011 4:34 PM 373,248 arm-none-eabi-readelf.exe
4/20/2011 4:34 PM 792,064 arm-none-eabi-run.exe
4/20/2011 4:34 PM 593,920 arm-none-eabi-size.exe
4/20/2011 4:34 PM 455,680 arm-none-eabi-sprite.exe
4/20/2011 4:34 PM 593,920 arm-none-eabi-strings.exe
4/20/2011 4:34 PM 744,960 arm-none-eabi-strip.exe
4/20/2011 4:34 PM 166,400 cs-make.exe
4/20/2011 4:34 PM 38,912 cs-rm.exe
27 files 16,857,107 bytes
2 directories 31,728,070,656 bytes free

C:\arm-2011.03\bin>
[/code]
Also I plan to have a Doxygen file available shortly. I’m downloading and installing Doxygen now. That should make some nice call graphs and such things to make it a bit easier to study your code.

#24

I wanted to try it out (and maybe even help to improve it if I like it - I’m a programmer), but couldn’t.

First, I cloned the git repository. Then I copied .hex file to my DS203, it was renamed to .rdy. But nothing happened. That is, current firmware in the device was not overwritten: everything works like I did not try to update the device with completely different firmware. Very strange. I tried many times of course. With all other firmware (standard, marcosin’s, and my own) everything works correctly, and always updates perfectly.

Then I tried to compile:

% cd Build/arm_linux % make make: *** No rule to make target `BIOS.o', needed by `all'. Stop.
Obviously, I’m using Linux.

So, what am I doing wrong?