You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Targets.md
+36-29Lines changed: 36 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1379,15 +1379,19 @@ wolfBoot support for iMX-RT1060/iMX-RT1050 has been tested using MCUXpresso SDK
1379
1379
1380
1380
DCP support (hardware acceleration for SHA256 operations) can be enabled by using PKA=1 in the configuration file.
1381
1381
1382
-
Firmware can be directly uploaded to the target by copying `factory.bin` to the virtual USB drive associated to the device, or by loading the image directly into flash using a JTAG/SWD debugger.
1383
-
1384
-
The RT1050 EVKB board comes wired to use the 64MB HyperFlash. If you'd like to use QSPI there is a rework that can be performed (see AN12183). The default onboard QSPI 8MB ISSI IS25WP064A (`CONFIG_FLASH_IS25WP064A`). To use a 64Mbit Winbond W25Q64JV define `CONFIG_FLASH_W25Q64JV` (16Mbit, 32Mbit, 128Mbit, 256Mbit and 512Mbit versions are also available). These options are also available for the RT1042 and RT1061 target.
1385
-
1386
1382
You can also get the SDK and CMSIS bundles using these repositories:
1387
1383
*https://github.com/nxp-mcuxpresso/mcux-sdk
1388
1384
*https://github.com/nxp-mcuxpresso/CMSIS_5
1389
1385
Use MCUXSDK=1 with this option, since the pack paths are different.
On iMX-RT10xx it is possible to load a custom DCD section from an external
@@ -1401,58 +1405,61 @@ section, e.g.:
1401
1405
If an external `.dcd_data` section is provided, the option `NXP_CUSTOM_DCD=1` must
1402
1406
be added to the configuration.
1403
1407
1408
+
### Flashing
1404
1409
1405
-
### Testing Update
1406
-
1407
-
First make the update partition, pre-triggered for update
1410
+
Firmware can be directly uploaded to the target by copying `factory.bin` to the virtual USB drive associated to the device, or by loading the image directly into flash using a JTAG/SWD debugger.
1408
1411
1409
-
```sh
1410
-
tools/scripts/prepare_update.sh
1411
-
```
1412
+
The RT1050 EVKB board comes wired to use the 64MB HyperFlash. If you'd like to use QSPI there is a rework that can be performed (see AN12183). The default onboard QSPI 8MB ISSI IS25WP064A (`CONFIG_FLASH_IS25WP064A`). To use a 64Mbit Winbond W25Q64JV define `CONFIG_FLASH_W25Q64JV` (16Mbit, 32Mbit, 128Mbit, 256Mbit and 512Mbit versions are also available). These options are also available for the RT1042 and RT1061 target.
1412
1413
1413
-
Then connect to the board with JLinkExe, for the rt1040 do:
1414
+
If you have updated the MCULink to use JLink then you can connect to the board with JLinkExe using one of the following commands:
0 commit comments