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.)
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.
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.
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.
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.
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)
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 . I was expecting to debug it using an Rlink and Ride (similar to ST link).
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 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?
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.
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.
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.