On Sun, Sep 13, 2026 at 4:19 AM Travis Siegel via fpc-pascal <
Show quoted text 17 lines
wrote:
On 9/11/2026 4:15 PM, Christo Crause via fpc-pascal wrote:
> Here are some thoughts on two types of boards (there are many
> different boards of course):
> - Arduino Uno R4 (esp32-s3 module): Wifi + USB + 1x serial + CAN,
> higher power consumption, limited FPC support in trunk (workable but
> not straight forward).
I wasn't aware any of the arduino boards were supported by FPC, I was
actually tempted to mention to the op that FPC might not be a good
development platform, due to lack of support for arduino boards, but
since I hadn't checked to be 100 percent sure, I left that part out of
my reply.
FPC supports just about all of the AVR controllers used in many of the Arduino boards:
Uno Rev1 - 3, Nano, Pro Mini (atmega328p)
Leonardo, Micro, Pro Micro (atmega32U4)
Nano Every, Uno Wifi rev2 (atmega4809)
Mega (atmega2560)
Show quoted text 6 lines
Good to know such support is present, that might make some of my
projects more accessible to more platforms.
Where does one find the (limited) arduino support that is present in
FPC? I'd be curious if any of the boards I have are directly supported.
FPC supports the AVR controllers but does not provide much in terms of libraries.
Note that FPC supports the microcontrollers, not the boards as such. Some third party libraries/code example:
https://github.com/ackarwow/unolib - Pascal version of some of Arduino's libraries
https://github.com/ccrause/fpc-avr - Pascal examples and libraries
Show quoted text 7 lines
I realize the difference between arduino boards isn't all that
significant, so support for one is at least partially accessible to
other arduino boards. How would one (possibly) contribute to increasing
the number of boards supported?
From a compiler perspective the differences between Arduino boards can be
massive.
The controller could be based on AVR, ARM, RISC-V, xtensa or other architecture.
The Arduino ecosystem hides this detail behind lots of abstraction. Board support is an Arduino ecosystem concept, FPC can define an alias for a
board that maps to a controller it supports, but it is not the same thing.
To reproduce the Arduino experience on top of FPC I suggest expanding the Unolib project.
I have probably half a dozen arduino boards here, along with the same
Show quoted text 10 lines
number of raspberry pies, as well as micro:bit and propeller/basic stamp
boards from parallax. I'm now beginning to wonder if FPC could be
adapted to work with the parallax propeller boards, since they aren't
(functionally) all that different from arduinos, just been around a
whole lot longer, and have more processors (in most cases)
This is probably a discussion better directed to the fpc-devel list, but
I'm just curious how difficult (or easy) it would be to support other
boards.
Yes, best to enquire on fpc-devel.