Difference between revisions of "Toshiba TX04"
(8 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
[[Category:Device families]] |
[[Category:Device families]] |
||
− | The '''Toshiba TX04 |
+ | The '''Toshiba TX04''' are motor control microprocessors based on Cortex-M4 |
__TOC__ |
__TOC__ |
||
Line 9: | Line 9: | ||
! Flash Bank !! Base address !! Size !! J-Link Support |
! Flash Bank !! Base address !! Size !! J-Link Support |
||
|- |
|- |
||
− | | |
+ | | Code Flash || 0x00000000 || Up to 1024 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'''. For details on how to select a specific flash loader, please see [[J-Link_Multiple_Flashloader#Selecting_a_specific_flashloader | here]]. |
||
− | {| 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 implemented. |
||
− | *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> |
||
− | {| class="seggertable" |
||
− | |- |
||
− | ! Core || J-Link Support |
||
− | |- |
||
− | | [CORE_NAME] || style="text-align:center;"| {{YES}} / {{NO}} |
||
− | |} |
||
− | |||
− | 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== |
==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== |
||
− | *[[WikiTemplateEvalBoard|[SiliconVendor] [EvalBoardName]]] |
||
==Example Application== |
==Example Application== |
||
− | *[[WikiTemplateEvalBoard#Example_Project | [SiliconVendor] [EvalBoardName]]] |
Latest revision as of 11:02, 2 July 2024
The Toshiba TX04 are motor control microprocessors based on Cortex-M4
Contents
Flash Banks
Internal Flash
Flash Bank | Base address | Size | J-Link Support |
---|---|---|---|
Code Flash | 0x00000000 | Up to 1024 KB | ![]() |
Watchdog Handling
- No watchdog handling implemented.
Device Specific Handling
Reset
- The device uses normal Cortex-M reset, no special handling necessary, like described here.