MicroPython
- Awesome MicroPython
- MicroPython: Networking
- Extending MicroPython in C
- Getting Started with MicroPython and LoPy
- https://github.com/troublegum/micropyserver
MicroPyServer is a simple HTTP server for MicroPython projects
MicroPython and OLED display
MicroPython and Bluetooth/BLE
MicroPython on STM32 boards
- Start with Micropython on STM32
- MicroPython for STM32 Discovery B_L475E_IOT01A board
- Source on GitHub: stm32/B_L475E_IOT01A
- Board web page: ST web page
- Esercizi di base con MicroPython
- STM32 Nucleo-F411RE and MicroPython Getting Started
- Micropython on STM32 Nucleo Board in easy steps
- DfuSe USB device firmware upgrade (UM0412)
STSW-STM32080 package contains all binaries and source code for DfuSe USB device firmware upgrade (DFU) software, including the demonstration, debugging GUIs and protocol layers.
It includes the DFU driver compatible with the latest Microsoft OS.
DfuSe utility can be used to interact with the STM32 system memory bootloader or any In-Application Programming (IAP) firmware, running from the user Flash, thus allowing internal memories programming through USB. - UART and AT Command Module
https://forum.micropython.org/viewtopic.php?t=7956
- The .MAP file is a ASCII, nee human-readable, report from the linker about symbols, names, and locations.
- The .ELF is the primary output of the linker, it is an Object File Format, containing your binary code/data, and a lot of metadata about locations and symbols, etc.
- The .HEX file is an ASCII representation of the code/data in memory, it provides address information, can be sparse (have holes, and describe multiple regions of memory), is verbose (about 2.5x larger than necessary) and is in a form that can be emailed.
- The .BIN file is a binary (byte for byte) representation of code/data in memory, these are the values written into the memory and read and processed by the MCU. The address is assumed to be the base of flash, and is a linear/continuous image of memory