diff options
4 files changed, 25 insertions, 7 deletions
diff --git a/ports/mimxrt/boards/ADAFRUIT_METRO_M7/deploy_metro_m7.md b/ports/mimxrt/boards/ADAFRUIT_METRO_M7/deploy_metro_m7.md index c5bfd1a28..a2d6f5c82 100644 --- a/ports/mimxrt/boards/ADAFRUIT_METRO_M7/deploy_metro_m7.md +++ b/ports/mimxrt/boards/ADAFRUIT_METRO_M7/deploy_metro_m7.md @@ -8,4 +8,8 @@ here: https://learn.adafruit.com/adafruit-metro-m7-microsd/installing-the-bootlo Once the bootloader is installed and started, you can install MicroPython by copying the .uf2 version of the firmware file to the bootloader -drive. When the firmware is installed, the drive will disappear. +drive. A LED on the board will start flickering, indicating that the +upload is ongoing. Once the upload is complete, the drive icon will +disappear. Wait until the LED stops flickering. In rare cases there +may be an error message coming up, especially when there are only few +or no changes in the firmware file. Then just repeat the upload.
\ No newline at end of file diff --git a/ports/mimxrt/boards/MAKERDIARY_RT1011_NANO_KIT/deploy_makerdiary.md b/ports/mimxrt/boards/MAKERDIARY_RT1011_NANO_KIT/deploy_makerdiary.md index fde338159..49922183b 100644 --- a/ports/mimxrt/boards/MAKERDIARY_RT1011_NANO_KIT/deploy_makerdiary.md +++ b/ports/mimxrt/boards/MAKERDIARY_RT1011_NANO_KIT/deploy_makerdiary.md @@ -31,4 +31,9 @@ sudo ./sdphost -u 0x1fc9,0x0145 -- jump-address 0x20207000 ``` Wait until a drive icon appears on the computer (or mount it explicitly). At this point the bootloader is installed. You can now copy the -MicroPython .uf2 file to the board. +MicroPython .uf2 file to the board to start the firmware upload. +A LED on the board will start flickering, indicating that the +upload is ongoing. Once the upload is complete, the drive icon will +disappear. Wait until the LED stops flickering. In rare cases there +may be an error message coming up, especially when there are only few +or no changes in the firmware file. Then just repeat the upload. diff --git a/ports/mimxrt/boards/OLIMEX_RT1010/deploy_olimex.md b/ports/mimxrt/boards/OLIMEX_RT1010/deploy_olimex.md index 7abba784b..4db0b6f61 100644 --- a/ports/mimxrt/boards/OLIMEX_RT1010/deploy_olimex.md +++ b/ports/mimxrt/boards/OLIMEX_RT1010/deploy_olimex.md @@ -33,10 +33,16 @@ and you will not need it for Windows. 4. Once the upload of the bootloader is finished, push Reset twice. -The bootloader should start and show a drive icon. Copy the .uf2 version of MicroPython -to this drive to install or update MicroPython. +The bootloader should start and show a drive icon. -Once the UF2 bootloader is installed, only step 4 is required to deploy MicroPython. If +5. Copy the .uf2 version of MicroPython to this drive to install or update MicroPython. + +A LED on the board will start flickering, indicating that the upload is ongoing. Once the upload +is complete, the drive icon will disappear. Wait until the LED stops flickering. In rare cases there +may be an error message coming up, especially when there are only few or no changes in +the firmware file. Then just repeat the copy. + +Once the UF2 bootloader is installed, only steps 4 and 5 are required to deploy MicroPython. If MicroPython is already installed, the bootloader can as well be invoked by calling `machine.bootloader()`. diff --git a/ports/mimxrt/boards/deploy_mimxrt.md b/ports/mimxrt/boards/deploy_mimxrt.md index 7ad21fe64..2c7f35009 100644 --- a/ports/mimxrt/boards/deploy_mimxrt.md +++ b/ports/mimxrt/boards/deploy_mimxrt.md @@ -41,5 +41,8 @@ installed. If there is no valid Firmware on the device, the bootloader will start automatically. Once it's started, a drive ICON will appear. The MicroPython firmware file with .uf2 -extension must then be copied to that drive. When the file is copied and MicroPython -is installed, the drive disappears and MicroPython starts. +extension must then be copied to that drive. A LED on the board may start flickering, +indicating that the upload is ongoing. Once the upload is complete, the drive icon +will disappear. Wait until the LED stops flickering. In rare cases there +may be an error message coming up, especially when there are only few or +no changes in the firmware file. Then just repeat the copy. |
