From 918da684d8513e4903935fa5984c09d674a5ce36 Mon Sep 17 00:00:00 2001 From: Nicholas Herriot Date: Wed, 17 Jul 2019 17:52:01 +0100 Subject: [PATCH] Updated Building Micropython Binaries (markdown) --- Building-Micropython-Binaries.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Building-Micropython-Binaries.md b/Building-Micropython-Binaries.md index be2c383..9b4e87d 100644 --- a/Building-Micropython-Binaries.md +++ b/Building-Micropython-Binaries.md @@ -5,7 +5,6 @@ Prerequisites to this are setting up your build environment. You can [get starte 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 * flashing onto micropython hardware ## Directory Structure @@ -48,13 +47,16 @@ And for the SF6 it would be: ### Compiling Your Own Python Code Into Firmware To make a firmware build with a python file that you have created, simply place in the **/modules** directory the python file you wish to be available in your firmware build. Hence if you wanted to have a **hello_world.py** compiled into your firmware image do: - place the **hello_world.py** into your /ports/stm32/modules directory -- do your buld with the command **FROZEN_MPY_DIR=modules +- do your build with the command **FROZEN_MPY_DIR=modules e.g. ```bash /> make BOARD=PYBD_SF2 FROZEN_MPY_DIR=modules ``` +## Flashing Onto Micropython Hardware +[Flashing onto is described here](https://github.com/micropython/micropython/wiki/Pyboard-Firmware-Update) +