mirror
/
micropython
kopia lustrzana https://github.com/micropython/micropython
1
0
Forkuj 0
Kod Zgłoszenia Projekty Wydania Wiki Aktywność

Updated Building Micropython Binaries (markdown)

master
Nicholas Herriot 2019-07-17 17:46:21 +01:00
rodzic d11170d59a
commit d4aa5e1890
1 zmienionych plików z 2 dodań i 2 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

4
Building-Micropython-Binaries.md

@ -2,7 +2,7 @@ This describes the basics on building micropython binaries for different boards.
Prerequisites to this are setting up your build environment. You can [get started and setup your build environment on Linux Mint 18.0 here](https://github.com/micropython/micropython/wiki/Getting-Started---Compiling-Micropython-for-Ubuntu-16.04)
Assuming that you have a working environment and you can run **make** to make a build for Linux we can now:
Assuming that you have a working environment and you can run **make** to make a build for Linux we can now explain the:
* directory structure
* making a build for an architecture
* identify the firmware builds
@ -24,7 +24,7 @@ Within each platform directory there is build<name> directory e.g.
/ports/stm32/build-PYBD_SF2
/ports/stm32/build-PYBD_SF6
```
When a build is complete the firmware builds are placed in the relevant directory. Within a build directory there are two main build files that are used to flash onto a board. Which are named **firmware.hex** and **firmware.dfu*. The *dfu* file is the file that has to be flashed onto your microcontroller.
When a build is complete the firmware builds are placed in the relevant directory. Within a build directory there are two main build files that are used to flash onto a board. Which are named **firmware.hex** and **firmware.dfu**. The *dfu* file is the file that has to be flashed onto your microcontroller.
Within the stm32 directory there is a **modules** directory. This is used to compile your own modules into a firmware build. This is explained later.