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
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>
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.
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.
If you have the time and opportunity point me where to look for ranges of horizontal scanning 1S … 0.1 uS. The idea is to add a range of 0.05uS and automatic switching between the range of the horizontal sweep.
I would like to get involved in improving the software.
