Difference between revisions of "NXP RW61x"
| Line 3: | Line 3: | ||
==Flash Banks== |
==Flash Banks== |
||
| − | ===External Flash=== |
+ | ===External QSPI Flash=== |
{| class="seggertable" |
{| class="seggertable" |
||
|- |
|- |
||
| Line 11: | Line 11: | ||
|} |
|} |
||
| + | QSPI flash programming requires special handling compared to internal flash. For more information about this, please see the [[QSPI Flash Programming Support | |
||
| − | |||
| + | Device has only one pin configuration. |
||
| − | ===QSPI Flash=== |
||
| − | QSPI flash programming requires special handling compared to internal flash. For more information about this, please see the [[QSPI Flash Programming Support | QSPI Flash Programming Support article]].<br> |
||
| − | J-Link supports multiple pin configurations for [DEVICE]. The default loader is marked in '''bold'''. |
||
| − | {| class="seggertable" |
||
| − | |- |
||
| − | ! Device !! Base address !! Maximum size !! Supported pin configuration |
||
| − | |- |
||
| − | | [DEVICE]|| [BANK_BASE_ADDRESS] || [MAX_SPI_FLASH_SIZE] MB || |
||
| − | *'''[LOADER_NAME]''' |
||
| − | *[LOADER_NAME] |
||
| − | *[LOADER_NAME] |
||
| − | |} |
||
| − | |||
| − | ==ECC RAM [OPTIONAL]== |
||
| − | *Describe ECC RAM restriction here. |
||
| − | |||
| − | ==Vector Table Remap [OPTIONAL]== |
||
| − | *Describe Vector Table Remap here.. |
||
==Watchdog Handling== |
==Watchdog Handling== |
||
| + | *No Watchdog handling |
||
| − | *The device does not have a watchdog. |
||
| − | *The device has a watchdog [WATCHDOGNAME]. |
||
| − | *The watchdog is fed during flash programming. |
||
| − | *If the watchdog is enabled, it is turned off during flash programming and turned back on afterwards. |
||
| − | |||
| − | ==Multi-Core Support [OPTIONAL]== |
||
| − | Before proceeding with this article, please check out the generic article regarding Multi-Core debugging [[Multi-Core_Debugging | here]].<br> |
||
| − | The [DeviceFamily]family comes with a variety of multi-core options.<br> |
||
| − | Some devices from this family feature a secondary core which is disabled after reset / by default.<br> |
||
| − | Some of the are available with enabled ''lockstep'' mode, only. <br> |
||
| − | In below, the debug related multi-core behavior of the J-Link is described for each core: |
||
| − | ===Main core=== |
||
| − | ====Init/Setup==== |
||
| − | *Initializes the ECC RAM, see [[XXX | XXX]] |
||
| − | *Enables debugging |
||
| − | ====Reset==== |
||
| − | *Device specific reset is performed, see [[XXX | XXX]] |
||
| − | ====Attach==== |
||
| − | *Attach is not supported because the J-Link initializes certain RAM regions by default |
||
| − | ===Secondary core(s)=== |
||
| − | ====Init/Setup==== |
||
| − | *If the main core session has not been started / debugging is not enabled yet, the secondary core executes the enable debug sequence. |
||
| − | *If the secondary core is not enabled yet, it will be enabled / release from reset |
||
| − | ====Reset==== |
||
| − | No reset is performed. |
||
| − | ====Attach==== |
||
| − | *Attach is supported / desired |
||
| − | + | =Device Specific Handling== |
|
===Connect=== |
===Connect=== |
||
===Reset=== |
===Reset=== |
||
Revision as of 15:30, 24 August 2023
The NXP RW61x are Cortex_M33 based Wireless MCUs with Integrated Radio: 1x1 Wi-Fi® 6 + Bluetooth® Low Energy 5.3.
Contents
Flash Banks
External QSPI Flash
| Flash Bank | Base address | Size | J-Link Support |
|---|---|---|---|
| QSPI | 0x08000000 | Up to 128MB | 
|
QSPI flash programming requires special handling compared to internal flash. For more information about this, please see the [[QSPI Flash Programming Support | Device has only one pin configuration.
Watchdog Handling
- No Watchdog handling
Device Specific Handling=
Connect
Reset
- The devices uses normal Cortex-M reset, no special handling necessary, like described here.
- The devices uses Cortex-M Core reset, no special handling necessary, like described here.
- The devices uses Cortex-M Rest Pin, no special handling necessary, like described here.
- The devices uses Cortex-A reset, no special handling necessary, like described here.
- The devices uses Cortex-R reset, no special handling necessary, like described here.
- The devices uses ARMv8-A reset, no special handling necessary, like described here.
- The devices uses ARMv8-R reset, no special handling necessary, like described here.
- The device uses custom reset:.....
Limitations
Dual Core Support
Some XXX devices feature a second core. Right now, the J-Link software does support the main core, only. Support for the second core is planned for future versions.
Attach
Attach is not supported by default because the J-Link initializes certain RAM regions by default.
Security
Evaluation Boards
- [SiliconVendor] [EvalBoardName] evaluation board: http://techwiki.segger.local/WikiTemplateEvalBoard
Example Application
- [SiliconVendor] [EvalBoardName] evaluation board: http://techwiki.segger.local/WikiTemplateEvalBoard#Example_Project
