… I’ll let people familiar with embedded dev to address your remarks ;-)
Maybe you can generate it all from the CubeMX files? If you have installed it, take a look at C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeMX\db\mcu, all clear text XML files with all the differences. Of course, the best would be to have just another target, "Ada", in the CubeMX settings, much like there is a target for TrueStudio, MDK-ARM etc. Unfortunately looks like CubeMX is not open source, and might be difficult to add an Ada target, because I assume there are lots of hardcoded C stuff in it.
For the Ada_Drivers_Library library itself you should be able to use the support available in the srm32f4_disco
When I use the runtime ravenscar-full-stm32f4, the line "delay until Clock + Microseconds (200);" in stm32-board.adb hangs, but looks like it works for STM32F407_Discovery'Runtime ("Ada");. Unfortunately I can't use the latter, because I need streams, exceptions etc. Am I using the right runtime for full ravenscare? Or any idea how to fix it or where I can look to fix it myself?
This is quite strange, what board do you have?
I described how to compile it here: https://github.com/FrankBuss/Ada_Synth
Everything is in github, it is reproducable
Everything is in github, it is reproducable
when I comment all delay until lines I discovered by debugging in single step mode, and then uncomment the line https://github.com/FrankBuss/Ada_Synth/blob/master/ada/discovery/ada_synth.adb#L69 again, it works, I can here a sine wave then
Btw, the debugger doesn't work well on my PC (Debian Linux 64 bit). Very slow, like 10 seconds to load all the symbols on start, 1-2 seconds for single steps, and crashes sometimes, together with GPS.
I have a 4 GHz Intel I7, 32 GB RAM, not much else running, other programs are very fast, like the Keil uVision debugger for the same board, even inside a Windows VM.
It's not a CPU or RAM problem. The slow binary load comes from the st-link probe and driver. My guess is that there's a bottle neck in the USB communication, but since ST is not very open about the st-link probes firmware and all we have is a reverse engineered driver for it, I don't see how to improve the situation.
On the other hand they do provide the st-link probe effectively for free which is nice.
It comes from here:
Integer_16 (I * 432452) + Int_Sample;
strange, it doesn't work here when I use the delays, maybe something wrong how I compiled it? I clicked the "Build Target Build All" button in GPS
I can see the exection kind of in the st-util window, 2 characters per line, how do so see this nice output?
and thanks for extending the deadline, maybe after all I can still get a first working version done until Monday :-)
BTW, do you know about my sample/synthesizer project? https://hackaday.io/project/19326-wee-noise-maker
image how much easier it is to play your noise maker with a real piano :-)
The ST-Link doesn't support SWO, it uses semihosting, which happen to be very slow, so basically the advice is that don't use for code that is time sensitive and in short it sucks. The idea would be to upgrade the ST-Link with Segger which is now possible but I am not sure if it can use SWO since it needs the physical pin to output the serial data. If you want to solve at least the ugly output use openocd instead of st-link debugger. Also the debugger of gps suffer when you start inspecting variables and memory, suddenly hangs or even needs a reset . BY the way I am not seeing where it's stated that the deadline has been moved!
MIDI-in is working now:
https://github.com/FrankBuss/Ada_Synth
@Fabien-Chouteau if you have a digital 3 V MIDI signal and a MIDI piano, you could now play music on it. But I added a nice automatic startup chord at reset as well :-)
Tomorrow the fun part starts, implementing polyphonic audio, changing the generator parameters with the knobs etc.
https://github.com/FrankBuss/Ada_Synth
@Fabien-Chouteau if you have a digital 3 V MIDI signal and a MIDI piano, you could now play music on it. But I added a nice automatic startup chord at reset as well :-)
Tomorrow the fun part starts, implementing polyphonic audio, changing the generator parameters with the knobs etc.
@miabbate_twitter did you make progress on the filesystem?
@miabbate_twitter do you have a link to your project page? My MIDI synthesizer is now done, still missing polyphonic sound, but this should be easy to implement
http://www.makewithada.org/entry/midisynthesizer
http://www.makewithada.org/entry/midisynthesizer
Are there many entries for this competition? I think it is a bit rough for newbies like me to learn Ada, learn how to use the IDE, learn the STM32 libraries API etc. A full tutorial might be useful.