Great to hear you are looking at this as well. If you are looking on 2.7 schematic the flash is M25PE16-VMW6P which is 16MBit (2Mbyte) which is the previous one. I haven’t found a full schematic for the 2.72 hardware but it should have a 64Mbit (8Mbyte) component.
One strategy might be to understand the memory usage of the SYS and APP as I suspect a greater RAM memory footprint of the 1.6 SYS may be conflicting with the current alternate APPs. The processor is supposed to be 256K ROM and 48K RAM but as has been found out here it seems to actually have the larger memories of a different version with 512K ROM and 64K RAM. AlterBios is one example that is exploiting a bit of the extra capacity.
I can see for example that the RAM usage of the APP in the Community / Wildcat App is set to start at 0x3000 (12K) for constants copied from RAM plus heap variables and the stack set at 0xAAF0. The linker files give the basic set up plus one can get an assembler listing from the .elf file which shows all the memory locations used. The SYS functionality is accessed via a bios jump table and I think uses RAM from 0 upwards. Now the 1.6SYS definitely uses significantly more memory as its EXT Flash buffer is 0x1200 long compared with 0x300 for the 1.5 SYS. This is because the paging in the 8MB Flash is different. I haven’t worked out yet where the top of the 1.6SYS RAM usage is yet. I was hoping to check the memory positioning of the AP110 factory app which does work with SYS1.6 but I can’t find the source for that. I think there is sufficient spare space to maybe reposition the APP RAM a bit to avoid a conflict if there is one.
What dev environment are you intending to use? So far I have only attempted building APPS and I used the CodeSorcery toolchain 2011.03 as linked on the community github. Originally I tried a more recent one but although it built OK the APP wouldn’t execute correctly.
Added Pmos69’s FFT and spectrograph functions:
Added selectable Hamming window or adjacent bin summing, some amplitude compression and screen calibration in decibels. Adjacent bin summing provides flat frequency response at the expense of resolution restricted to every other bin. Provides flat response similar to a flat top window but only expands bandwidth to 2 bins.
Corrected FFT frequency values displays. Also allowed meters to show with FFT on but channel turned off.
Optimized code so still fits within 2 ROM “slots” (barely, beware if recompiling…) - without spilling into the 3rd.
Hello,could you please tell me why cant I download wildcat3 to my device.I have:
HW:2.72
SYS:1.52
APP:2.53
It gives me an error of not enough space on the drive.The available space is 492k and the file is around 2G.Do I have to download all the files in the folder?I have other apps on it too but dont use them.Is that a promlem?
Thank you for your time in advance.
I’m not sure I understand the numbers you quote 492k and 2G. The file you need to install is just APP1.hex (or APP2, APP3 if putting in different slots). This is a 183k file. The rest of the material in the zip is the source code etc.
You start up the DSO with the USB connected and left hand button pressed which puts it in download mode and then just copy the APP1.hex file across.
By the sound of it you may have the latest hardware with 8GB disc. You can check this by looking at drive properties when mounted. If so then this software may not be compatible with this yet as it was built for the previous models with 2GB discs. That is one area I am interested in sorting out. There is no harm in trying as you can restore the original software if you have its hex file.
I guess you are getting a HEX file that is bigger than what it is supposed to be(possibly rendered in HTML format). You should use the right-click save-as option to save the HEX file before you use. Check the HEX file size to be sure you got it correctly.
Three days ago I also got my DSO QUAD. It reports HW ver. 2.72 and the drive size in Win Explorer ist 8MB.
It took me a day to find out about this firmware stuff.
What works:
- Gabonator
- Pawn stuff
What doesn’t work:
- APP_G251
- Wildcat 3
Both install, start and do a lot, but e.g. the time base setting is never displayed and
I can’t fire up the CAL screen. Looking at the code this is wierd, as short/long/extra long
key presses are correctly processed but the cal routine ist probably never called as
one of the first things it would do is blank the screen, but that remains undisturbed.
Thanks to the Gabo package I could set up a dev environment on Win, rebuild his latest app version
and run it as APP4.
@tsipaki7
I find your SYS and APP versions posted somewhat surprizing as I understand the 8M hardware
requires SYS 1.60, mine has that. Also my APP is 1.10 and I’d like to know what 2.53 is.
Try the wildcat3.zip file from the post above yours. If it unpacks with no error then the download is ok.
Then try one of the appX.hex files.
Warning! make sure you have the hex file for the stock firmware before you do anything!
I found that installing something as APP 2-4 often corrupts APP1.
Wilhelm
mr.django, I appear to be in the same boat. I have HW version 2.72 and got the errors you report with APP_251 and Wildcat 3. I was also not able to observe a signal from the signal generator.
I’m going to try Gabonator and Pawn Stuff later and report back.
Is this “Pawn Stuff”? All I could find in a quick search was something called QuadPawn.
https://github.com/PetteriAimonen/QuadPawn
And just to confirm, this is Gabonator?
https://github.com/gabonator/DS203
Re: issues with hardware 2.72:
The code I posted was not tested with and never meant to work with the newer HW2.72/SYS 1.60. File reads/writes
will likely fail with this version as cluster size used is different with the newer 8Mb drive it uses. One of the first things the
program does is read the config file, which will likely corrupt the menus, among other things, if not read properly.
Unfortunately, at this time, I don’t have one of these later 8Mb version devices, so I can’t test any possible
modifications to make it compatible. I just purchased another Quad (NOT from SEEED), but it turned out
to be a 2Mb version (with a sub-standard “clone” ADC that had to be replaced, I might add… Produced nothing
but garbage on one channel at the faster time bases) .
For those with the earlier version, here’s a minor update, bug fix and performance improvement:
CHANGELOG TO VERSION W3.1:
-Fixed color background for FFT values being used from out of bounds array index, producing faint
blue background (or possibly something else if recompiled) instead of black. Also changed FFT
frequencies display to green to match channel D color (provides better visibility than red).
-Fixed inadequate buffer size being used under some conditions when using spectrograph function.
-Fixed a bug where meter readings of one channel would show up on another channel if it was turned
off and FFT turned on.
-Changed triggering selection logic to better integrate with FFT when not displaying trace.
When all channels are off, triggering will be set to FFT displayed channel. Also, trigger selection
shortcut will acknowledge FFT channels, if on, when switching trigger source, rather than channel D.
-Changed V/div shortcut: now if selection is already on V/div, will toggle channel on/off, rather than
going to other analog channel’s V/div and turning that one on, if off. Also if FFT is on with all
channels off, shortcut will go to the FFT’s channel V/div but will not turn it on (long press again
to toggle channel trace on/off if desired).
-Added V2 cursor = db in FFT mode, V2 cursor position added at top of screen. Helps calculate db
readings, particularly near bottom of screen.
-Changed graphics of FFT freq displays so peak trace can be clearly seen through them, providing
better visibility at top of screen.
-Changed most often called for background graphics refresh source from ROM constants to run time
loaded RAM arrays. Provides significant increase in frame refresh rate (specially in single frame
buffer mode) and reduction of ROM size allows program to still fit within 2 “slots” in spite of
increased size/complexity.
-Start/Stop will now pause spectrograph.
-Eliminated needless simultaneous drawing of hidden trace graphics while in spectrograph mode
(speeds up refresh).
-FFT summing mode now engages a bin earlier at the extreme left in the spectrum.
I just installed The Wildcat 3.1 app. (Hardware v2.6, SYS 1.50)
Thank you so much for this, Wildcat!!! 
It’s fantastic!
I just found one issue.
The frequency of the internal signal generator is 4 times higher than indicated.
The internal frequency counter and the FFT display the real frequency. e.g. with the signal gen set at 1 kHz the app displays 4 kHz.
I confirmed with another frequency counter and it also shows 4 kHz when the signal gen is set to 1kHz.
Any idea?
Sorry if this has been addressed before.
Regards,
Markus
Are you using the modified SYS that was designed for the community app? That will cause that effect with the WIldcat APP which is designed to use the standard stock SYS.
So… is there -any- firmware out there that works with HW 2.72? Or am I now stuck with an albatross? 
Thanks for your answer!
Good question :oops:
On my display it says SYS 1.50 SmTech 1.6
Could you please target me to the correct SYS?
Edit: just found everything on page 1 of this thread.
Now that’s embarrassing
Ok found everything on the DSO wiki
Works like a charm now!
HW 2.72 with 8M?
I have HW 2.6
Having a new Quad with 2.72/8M I am wondering what to do about the community software.
Just a thought - would there be any way to reformat the 8M as a 2M and reduce the cluster size so it would not have the software issues? Or, could a small partition be copied onto the device with something like Partition Master?
-Cory
I don’t think one would be able to make the 8M device behave like a 2M one. It’s not about partitioning, it’s more about the fundamental hardware block size used when the device erases and writes new data. That means the routines that do writing have larger buffers.
I think the most fruitful approach is to use the SYS 1.60 which supports the 8M device and then adjust the apps to be compatible with this. The calls made to the SYS are pretty much the same with the main differences being in the memory allocation, so it should be relatively straightforward. This is also evidenced by the gabonator app which largely works with 1.6 except for storing data. I did start to look a this as a family member has a 8M model whereas mine is 2M, but have not had much time to pursue this further recently.
The 2.72 / 8M issues seem to be fixed, please see the last upload in this thread: <LINK_TEXT text=“http://www.seeedstudio.com/forum/viewto … 187#p19187”>http://www.seeedstudio.com/forum/viewtopic.php?f=26&t=5128&p=19187#p19187</LINK_TEXT>
New update:
Tentative support for 8MB devices. Integrated bobtidey’s mods. Note that this has not been tested
on other than 2MB units at this time.
Added persistence and map modes, BMP load, and 30db extra gain to all FFT functions.
Updated spectrograph and XY modes + many minor improvements and bug fixes. See
changelog in README.TXT for complete list and how to use these. Program still fits
within 2 slots.
Persistence mode of RF eye pattern
in RAW data mode
Persistence mode of a video signal
in NORMAL data mode
30db additional FFT gain with
auto scaling
Voice print of person speaking
MAP mode of video frame
XY display of stationary pattern
in persistence mode
I tried this latest on my 8MB 2.72 with 1.6. It seems to work though I don’t understand how to operate it. After bringing up the meters on the right, are you able to change what is displayed as in the original app?
Also, I assumed, maybe incorrectly, that app1, app2, app3 refers to the slot residency? I tried that and it looks like they boot in the correct slot but I get a blank screen.
Anyway, I applaud what everyone has coded and love the little device. I wanted something for on my desk as sometimes the DDS freq generators and other equipment I have won’t start and I can’t figure out what is going on without a scope. After purchasing this little unit, I also bought a larger inexpensive DSO as well so it was ‘scope week’ at my house. Been using an oldy but goody 300mhz tek 2465 for years which had a ton of functions with cursors, etc, but no storage.
So please keep up the good work. I would love to be able to boot wildcat from 2 or 3 keeping the original in 1. I have gabonator’s code in 4 which I like as well.
Jerry.