and then a custom board with MK26FN2 (256kram 2Mflash USB*2 stdPerip+SDcard++) .
I'm really impressed with @dhylands's port to Teensy as its something I know about and working through it - though the overall micropython/STMHAL blows my mind and for its great ideas. Wow thanks for open sourcing it.
I'm looking at uPy for its customizing capability for scientists (and citizen scientists/makers) interfacing to outdoor environmental sensors
so having low power, powered by battery/solar is critical - the reason for Kinetis processor and that I have a board already.
The core of the python is to be be able to easily process ASCII command strings over the serial ports (USB and UART/RS232) and some local port control,
however it also needs to have an OS - probably FreeRTOS - with apps for managing the core realworld events.
I was thinking of starting from the teensy3/MK20DX256 code, creating a minimal machine and then adding back in the functions.
The KDS3 (Kinetis Design Studio3 / Eclipse - http://mcuoneclipse.com) is comprehensive for HAL interfaces -
protoyping access to peripherals and low power clock management framework.
- the microPython make structure works for multiprocessor projects, so I was thinking of a directory structure
Code: Select all
py
stmhal
teensy
kinetis-<processor>
-<board eg FRDM-K64F>
-<OS eg FreeRTOS>
-<customApps invoked from board startup>
<OS FreeRTOS> really belongs at an equal level to Kinetis but is more custom.
The make would be initiated at the <board> and it could have an option for including the CustomApps/FreeRtos.
I was wondering if there where any thoughts on file structures and what might be usefull for possible acceptance back to the main tree.