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
+101-2Lines changed: 101 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,7 @@ This README describes configuration of supported targets.
19
19
*[NXP LPC54xxx](#nxp-lpc54xxx)
20
20
*[NXP LS1028A](#nxp-ls1028a)
21
21
*[NXP MCXA153](#nxp-mcxa153)
22
+
*[NXP MCXW716C](#nxp-mcxw716c)
22
23
*[NXP P1021 PPC](#nxp-qoriq-p1021-ppc)
23
24
*[NXP T1024 PPC](#nxp-qoriq-t1024-ppc)
24
25
*[NXP T2080 PPC](#nxp-qoriq-t2080-ppc)
@@ -2181,7 +2182,15 @@ make
2181
2182
2182
2183
### MCX A: Loading the firmware
2183
2184
2184
-
The NXP Freedom MCX A board debugger comes loaded with MCU Link, but it can be updated to JLink. See https://docs.nxp.com/bundle/UM12012/page/topics/Updating_MCU_Link_firmware.html
2185
+
The NXP Freedom MCX W board debugger comes loaded with MCU Link, but it can be updated to JLink.
2186
+
- Download and install the tool to update MCU Link to support jlink:
2187
+
[@NXP: LinkServer for microcontrollers](https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools-/linkserver-for-microcontrollers:LINKERSERVER#downloads)
2188
+
2189
+
- put the rom bootloader in'dfu' mode by adding a jumper JP8 (ISP_EN)
2190
+
2191
+
- run `scripts/program_JLINK` to update the onboard debugger
2192
+
2193
+
- when the update is complete, remove the jumper in JP8
2185
2194
2186
2195
Use JLinkExe tool to upload the initial firmware: `JLinkExe -if swd -Device MCXA153`
2187
2196
@@ -2241,6 +2250,96 @@ mon reset
2241
2250
c
2242
2251
```
2243
2252
2253
+
## NXP MCXW716
2254
+
2255
+
NXP MCXW716 is a Cortex-M33 microcontroller running at 96MHz.
2256
+
The support has been tested using FRDM-MCXW716 with the onboard MCU-Link configured in JLink mode.
2257
+
2258
+
This requires the MCXW SDK from the NXP MCUXpresso SDK Builder. We tested using [mcux-sdk](https://github.com/nxp-mcuxpresso/mcux-sdk) and [CMSIS_5](https://github.com/nxp-mcuxpresso/CMSIS_5)`
2259
+
placed under "../NXP". Adjust the MCUXPRESSO and MCUXPRESSO_CMSIS variables in your .config file according to your paths.
2260
+
2261
+
### MCX W: Configuring and compiling
2262
+
2263
+
Copy the example configuration file and build with make:
2264
+
2265
+
```sh
2266
+
cp config/examples/mcxw.config .config`
2267
+
make
2268
+
```
2269
+
2270
+
### MCX W: Loading the firmware
2271
+
2272
+
The NXP Freedom MCX W board debugger comes loaded with MCU Link, but it can be updated to JLink.
2273
+
- Download and install the tool to update MCU Link to support jlink:
2274
+
[@NXP: LinkServer for microcontrollers](https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools-/linkserver-for-microcontrollers:LINKERSERVER#downloads)
2275
+
2276
+
- put the rom bootloader in'dfu' mode by adding a jumper in JP5 (ISP_EN)
2277
+
2278
+
- run `scripts/program_JLINK` to update the onboard debugger
2279
+
2280
+
- when the update is complete, remove the jumper in JP5
2281
+
2282
+
Use JLinkExe tool to upload the initial firmware: `JLinkExe -if swd -Device MCXW716`
2283
+
2284
+
At the Jlink prompt, type:
2285
+
2286
+
```
2287
+
loadbin factory.bin 0
2288
+
Downloading file [factory.bin]...
2289
+
J-Link: Flash download: Bank 0 @ 0x00000000: Skipped. Contents already match
2290
+
O.K.
2291
+
```
2292
+
2293
+
Reset or power cycle board.
2294
+
2295
+
The blue led (PA20) will show to indicate version 1 of the firmware has been staged.
2) Create a bin footer with wolfBoot trailer "BOOT" and "p" (ASCII for 0x70 == IMG_STATE_UPDATING):
2307
+
2308
+
```sh
2309
+
echo -n "pBOOT"> trigger_magic.bin
2310
+
```
2311
+
2312
+
3) Assembly new factory update.bin:
2313
+
2314
+
```sh
2315
+
./tools/bin-assemble/bin-assemble \
2316
+
update.bin \
2317
+
0x0 test-app/image_v2_signed.bin \
2318
+
0xAFFB trigger_magic.bin
2319
+
```
2320
+
2321
+
4) Flash update.bin to 0x13000 (`loadbin update.bin 0x13000`).
2322
+
2323
+
Once wolfBoot has performed validation of the partition and staged a firmware with version > 1, the D15 Green LED on PA19 will show.
2324
+
2325
+
Note: For alternate larger scheme flash `update.bin` to `0x14000` and place trigger_magic.bin at `0x9FFB`.
2326
+
2327
+
### MCX W: Debugging
2328
+
2329
+
Debugging with JLink:
2330
+
2331
+
Note: We include a `.gdbinit` in the wolfBoot root that loads the wolfboot and test-app elf files.
2332
+
2333
+
In one terminal: `JLinkGDBServer -if swd -Device MCXW716 -port 3333`
2334
+
2335
+
In another terminal use `gdb`:
2336
+
2337
+
```
2338
+
b main
2339
+
mon reset
2340
+
c
2341
+
```
2342
+
2244
2343
2245
2344
## TI Hercules TMS570LC435
2246
2345
@@ -3224,7 +3323,7 @@ make
3224
3323
3225
3324
After running the above commands, you should find a file named `final_image.bin` in the root folder of the repository. The image can be flashed directly into the board.
3226
3325
By default wolfBoot tries to read a wolfBoot image from the SATA drive.
3227
-
The drive should be partitioned with a GPT table, wolfBoot tries to load an image saved in the 5th or the 6th partition.
3326
+
The drive should be partitioned with a GPT table, wolfBoot tries to load an image saved in the 5th or the 6th partition.
3228
3327
You can find more details in `src/update_disk.c`. wolfBoot doesn't try to read from a filesystem and the images need to be written directly into the partition.
0 commit comments