Thanks for the report. That sounds promising.
Take care with calibration on the higher ranges as the changed voltage overload protection on hw 2.72 means that input voltage should be kept below 30V.
There was a missing changed source file from the previous zip. This didn’t affect the hex files.
Attached here has the missing file plus rebuilt hexes incorporating a recent small Gabonator change persisting some more settings.
I have also forked the source on Github so any further updates will be on there.
https://github.com/roberttidey/DS203
GabonatorDS203Mods.zip (659 KB)
Wildcat3.1 does not work on my HW2.72…
i just get an black screen after starting the slot 3 in my case…
Can you say exactly which Wildcat 3.1 Hex you are trying and also what other stuff you have loaded in the other slots?
i use the one from the page before…
i had no other slots used on first try …
no the slots have following in it…
2nd Slot is Gabonator
4th Slot is QuadPawn
I’ve got the wildcat on slot 1 now… this works…
maybe the hex for slot 3 has some issue??
I have been looking at the alempert Fourpack versions of the Apps which takes an interesting approach in splitting the 2 slot Apps so they only occupy 1 slot and using the extra ROM space to hold the rest of the code. These are set up for 2MB devices so I was thinking of trying out 8MB support in there. However, it extracted AlterBios out of Pawn and instead uses the patching version. When that is installed it affects all the apps. That caused me to look more closely at the 8MB support in that version and if I understand it correctly then the method used so far to get Community and Wildcat working is in conflict.
So far the changes made to get Community and Wildcat working were to change the apps to deal with the BIOS ReadFileSec and ProgFileSec calls working with 4096 buffers on a 8MB device rather than 512 on a 2MB. It looks to me that when the AlterBios is used then the patched versions of these calls continue to use 512 byte buffers and the read and write of 4096 is hidden inside the fat fs in Alterbios. If this is correct then it seems that one should be able to use the original unmodified versions of the Apps together with AlterBios to achieve the same result.
Gabonator is different in that it uses its own internal fat fs so I think that does need the sector size changes that I have done.
I think what would be nice to get to would be to use the 1 slot split approach as used in Fourpack together with full 2MB/8MB compatibility. Merging the sector size change into the Fourpack Gabonator is straightforward. If my thought on Alterbios is correct then it should be a matter of making sure the RAM allocation maps are compatible.
OK good news on slot 1. I’ll check out slot 3 version anyway despite my previosu post on a possible different approach to compatibility.
Just re-reading your mail. You said you have pawn in slot 4. That isn’t going to work as the main scope Apps like stock, community and Wildcat take up 2 slots. So if you put Pawn on after Wildcat then it would have wiped out half of Wildcat.
This is what is interesting about the Fourpack approach it splits up larger apps so they only use up 1 start up slot and put the rest of the code in spare ROM capacity in the background.
thx for that explanation…
this declares maybe, why wildcat in slot 1 crashes (hangs) if i put gabonator on slot 2…
to bad… i thought i can have all 4 slots filled…
1 wildcat
2 gabonator
3 logic analyer
4 quadpawn
…
The fourpack technique will allow 4 apps but to get there it needs the 8M capabiliy added in and different slot versions of the scope apps to be produced.
Thanks so much for this. I haven’t tested thoroughly but it installs at least.
I hope the community will continue to develop for the 2.72 hardware.
Hello there,
One year ago I returned my quad (wich was already 8M version) because of a failure on one channel.
Looking at the work done about the 8M version, I ordered another one and had another try.
Sys 1.62, Fw 2.72, APP v112 stock.
I installed the forked 8M Gabonator version from roberttidey on slot1, Wilddcat3.3 for 8M devices in slot 2, and quadpawn in slot 4.
They work, and I managed to save valid bmp/wav with gabonator. I c’ant before, so I was enthousiast.
But, after having played with gabonator calibration, Quad calibration etc, Im sorry to say I finally got the famous Assertion Failed while restarting gabonator (and lost calibration like before) : code 460 shortly and 464 source/core/settings/cpp before starting the app.
And I don’t remember how to recover from this (reinstalling Gabonator App ?)
So what do you think about that ? I’m not sure if this is an app saving conflict, or only gabonator not perfectly patched, but the 8M problem while saving seems always here.
I didn’t try to write something with Wildcat app for now.
Is there someone today who has at least one application working perfecly on 8M devices ?
Edit : I have just repaired the FAT with chsdsk /f
I did a few tests with gabonator. This is not a side effect from others slots and apps.
I succed to record several files without problems while restarting : Calib data, settings, bitmaps, wav, csv… but after a moment, they appear not readable, and finally the app corrupt the entire FAT. It is not constant, but sooner or later this happens.
I think that the corruption of CALIB.DAT is fatal.
About wildcat33 : All seems right, CFG (prepared per the manual), bmp… so perhaps the only way to go for stablity ?
Pawn is ok too.
Thanks for your comments
It might be worth trying Wildcat in 1 (+2) and Gabonator in 3 as other users have reported success with that config.
If that still causes problems with Gabonator I’ll try to check out further at the weekend.
Personally, I tend to use Wildcat most of the time. Gabonator has nice UI and plugins etc., but I like the functionality of Wildcat and once one is familiar with the controls then it is very quick to navigate around.
I can try that, but … I think the problem concern essentialy multiples bitmaps files, not just one.
Perhaps the fat space reservation like recommended by Wildcat (whith dummy files created just after formating the FAt) is a good workaround.
We all agree for gabonator I thnik, the Ui is far more intuitive or at least it does’nt require to rebember shot/medium/long clicks especially when you do not use it often.
Can you summerize what functionality of wildcat out-performs those from Gabonator ? (I’m a newby in the DSO world so I missed the most advanced parts) ?
Thank you for your work on these 8M version, a great improvement without a doubt.
Unfortunately the “Wildcat” version sometimes still corrupts the 8MB usb disk when saving screen dumps.
Try to solve, but the BIOS::DSK::SectorSize() function doesn’t always return the same value.
So I moved to a fixed 8MB version and removed some of the “user applications” to get some extra RAM available.
Managed to get a stable working version.
On the way fixed some overflow problems in the “Spectrum analyzer” that sometimes crashed the application.
Also implemented the “probe gain” (1x,10x,100x,1000x) into the “measurements” and “cursor” screen.
Attached the updated files. miniDSO_8MB_2015_apr_V1.01b.zip (183 KB)
(Note: this is only for 8MB versions!)
It doesn’t work on HW v2.81 like all the gabonator versions i tested. It corrupts the FPGA.