diff options
| author | robert-hh <robert@hammelrath.com> | 2022-04-24 20:33:47 +0200 |
|---|---|---|
| committer | Damien George <damien@micropython.org> | 2022-05-27 13:23:46 +1000 |
| commit | 1df7678674d0cb4d64afef00c8c6537c729e7b47 (patch) | |
| tree | f2ec5808f65fc09887ef73a0461678853b872e12 | |
| parent | c7accf766606294a9782b946ced20d3718c7632a (diff) | |
mimxrt/boards: Extend the deploy_teensy.md instructions.
| -rw-r--r-- | ports/mimxrt/boards/deploy_teensy.md | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/ports/mimxrt/boards/deploy_teensy.md b/ports/mimxrt/boards/deploy_teensy.md index f48154490..28da09249 100644 --- a/ports/mimxrt/boards/deploy_teensy.md +++ b/ports/mimxrt/boards/deploy_teensy.md @@ -11,4 +11,9 @@ or for Teensy 4.1: teensy_loader_cli --mcu=imxrt1062 -v -w TEENSY41-<date_version_tag>.hex ``` -When loading the firmware the PJRC boot loader will erase the content of the board file system. +Instead of imxrt1062 with the --mcu option, you can as well use the board specic names +TEENSY40, TEENSY41 or TEENSY_MICROMOD. When loading the firmware the PJRC boot loader +will erase the board file system. + +Note: If the Teensy board is equipped with Teensy bootloader v1.07 and up, the first attempt to +upload the firmware may fail. In that case try again. |