Hey, I was wondering about the compatibility of the spark firmware with other STM32 chips. I am planning on developing a peripheral device for my Electron project that will be based on an STM32 chip, and I was thinking about going with an F0 series chip.
Does it make sense to think about porting spark firmware over to the STM32F0 series?
Particularly if I don’t need anything but the CAN stack, i2c, UART, and GPIO libraries?
Ideally I would develop the product overt time such that eventually it could feature a CAN-enabled bootloader so that I could use the Electron to flash new firmware to the the MCU over the air via CANbus.
The firmware team are busy refactoring the firmware, separating the hardware-dependent code from the hardware-independent code. This should make targeting the F4 much easier!
How did that go? I can’t seem to find anything else in the forum and that thread is now over 2 years old.
I guess when it comes down to it, I’m kinda looking for advice on what will be the “easiest” way to proceed if I’d like to be writing the application for my nucleo board in, say, 2 weeks:
Just use an STM32F2 series controller, and use the spark firmware directly via Eclipse or Keil MDK (~$15 per MCU, total abstraction of firmware)
Use a STM32F103 series controller, and use the code developed by the good folks over at stm32duino.com via Arduino IDE (~$7.50 per MCU)
Adapt necessary spark firmware libraries to a “lesser” microcontroller from the STM32F0 series and develop via Eclipse or Keil MDK (~$5 per MCU, abstraction pretty good, but a patchwork)
Use another ~$5-10 Wiring-based hardware/software product with built-in CAN interface (not sure if there is one out there?)
Stick to the STM32F0 series and use mbed online IDE… hmm this looks tempting
Stick to the STM32F0 series and learn ANSI C, develop my own libraries, get dirty and lose my mind
Clearly choice 6 is the “funnest”, but I need to keep development time down.