Difference between revisions of "Toshiba TMPM4K"
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | The '''Toshiba TMPM4K''' are Cortex-M4 based microprocessors. |
+ | The '''Toshiba TMPM4K''' are Cortex-M4 based microprocessors.<br> |
| + | They belong to the M4K group of the TXZ+4A series. |
||
__TOC__ |
__TOC__ |
||
| Line 12: | Line 13: | ||
| Data Flash || 0x30000000 || 32 KB || style="text-align:center;"| {{YES}} |
| Data Flash || 0x30000000 || 32 KB || style="text-align:center;"| {{YES}} |
||
|} |
|} |
||
| − | |||
| − | ====ECC Flash [OPTIONAL]==== |
||
| − | *Describe ECC Flash restriction here. |
||
| − | |||
| − | ===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== |
||
| − | *The |
+ | *The Watchdog is disabled during flash programming. |
| − | *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. |
||
| + | ==Device Specific Handling== |
||
| − | ==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=== |
||
===Reset=== |
===Reset=== |
||
*The device uses normal Cortex-M reset, no special handling necessary, like described [[J-Link_Reset_Strategies#Type_0:_Normal | here]]. |
*The device uses normal Cortex-M reset, no special handling necessary, like described [[J-Link_Reset_Strategies#Type_0:_Normal | here]]. |
||
| − | *The device uses Cortex-M Core reset, no special handling necessary, like described [[J-Link_Reset_Strategies#Type_1:_Core | here]]. |
||
| − | *The device uses Cortex-M Rest Pin, no special handling necessary, like described [[J-Link_Reset_Strategies#Type_2:_ResetPin | here]]. |
||
| − | *The device uses Cortex-A reset, no special handling necessary, like described [[J-Link_Reset_Strategies#Strategies for Cortex-A devices | here]]. |
||
| − | *The device uses Cortex-R reset, no special handling necessary, like described [[J-Link_Reset_Strategies#Strategies for Cortex-R devices | here]]. |
||
| − | *The device uses ARMv8-A reset, no special handling necessary, like described [[J-Link_Reset_Strategies#Strategies for ARMv8-A devices | here]]. |
||
| − | *The device uses ARMv8-R reset, no special handling necessary, like described [[J-Link_Reset_Strategies#Strategies for ARMv8-R devices | 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== |
==Evaluation Boards== |
||
| + | *[[Toshiba_SBK-M4KN | Toshiba SBK-M4KN]] |
||
| − | *[[WikiTemplateEvalBoard|[SiliconVendor] [EvalBoardName]]] |
||
==Example Application== |
==Example Application== |
||
| − | *[[ |
+ | *[[Toshiba_SBK-M4KN#Example_Project | Toshiba SBK-M4KN]] |
| + | --!> |
||
Latest revision as of 17:18, 10 January 2024
The Toshiba TMPM4K are Cortex-M4 based microprocessors.
They belong to the M4K group of the TXZ+4A series.
Flash Banks
Internal Flash
| Flash Bank | Base address | Size | J-Link Support |
|---|---|---|---|
| Code Flash | 0x00000000 | Up to 512 KB | 
|
| Data Flash | 0x30000000 | 32 KB |
|
Watchdog Handling
- The Watchdog is disabled during flash programming.
Device Specific Handling
Reset
- The device uses normal Cortex-M reset, no special handling necessary, like described here.
