But it does make me wonder how many other differences there are, between the F4 HAL and the F1 HAL etc
There are some really great pdf documents on the ST chip variant web pages I think I linked to one of these in one of the threads here. I have been working through studying them when I have time. While they do seem to be built with doxygen and duplicate stuff in the header and c code files, having it in one place on the PDF helps.
As far as the port setups, there is a bug in the OS X cube MX, that does not allow the pin functions like the speed to be changed. On the flip side, is the issues you mentioned were from the aborted attempts to adapt the Areoquad core. With using git to control the variants. (each variant can have it's own temporary branch) these differences become moot.
It was not until I went into the demo board configurations, that I realized that all the mouse buttons and modifier keys work in CubeMX. This way pins can be labeled, alternates can be mapped, and IO configured.
stevech » Mon Sep 07, 2015 8:23 pm wrote:That RTOS, done properly for newbies' viewpoint, can eliminate a lot of non-engineer users' frustrations about MCUs.
I wrote a small kernal RTOS for AVR to do MIDI stuff between 2001 and 2005. This was to handle floppy access through a memory map. It took many years to debug. I sure learned a lot.
You are probably correct relating to users accustomed to PCs and RPi/Linux. I learned to program nearly 40 years ago. I noticed that tech workers do not even call them selves programmers any more, they are now coders and API developers.