Tongxin THA6 Gen 2: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 78: | Line 78: | ||
In below, the debug related multi-core behavior of the J-Link is described for each core: | In below, the debug related multi-core behavior of the J-Link is described for each core: | ||
== | ===Main core=== | ||
=== | ====Init/Setup==== | ||
*Secure Debug: | *Secure Debug: | ||
**Authentication levels EL1 and EL2 are supported. | **Authentication levels EL1 and EL2 are supported. | ||
**Only the default password (all bytes set to 0xFF) is supported. If you need to unlock the device using a custom password, please contact us through our support ticket system. | **Only the default password (all bytes set to 0xFF) is supported. If you need to unlock the device using a custom password, please contact us through our support ticket system. | ||
* Halt timer configuration: | |||
** Corsight CTI is configured to halt the following timers simultaneously with the R52 cores: STM, IWDT, SAFEWDT, CPUWDTn and BASETIMERn. | |||
====Reset==== | |||
*The device uses custom reset: | |||
**Sets reset catch so that CPU is halted immediately after reset | |||
**Performs reset via EDPRCR register | |||
**Ensures that debug power domain and system power domain are powered up | |||
**Powers core if necessary | |||
**Enables debug mode if necessary | |||
**Clears reset catch | |||
====Attach==== | |||
*Attach is supported | |||
===Reset=== | ===Secondary core(s)=== | ||
====Init/Setup==== | |||
*Secure Debug: | |||
**Authentication levels EL1 and EL2 are supported. | |||
**Only the default password (all bytes set to 0xFF) is supported. If you need to unlock the device using a custom password, please contact us through our support ticket system. | |||
* Halt timer configuration: | |||
** Corsight CTI is configured to halt the following timers simultaneously with the R52 cores: STM, IWDT, SAFEWDT, CPUWDTn and BASETIMERn. | |||
====Reset==== | |||
*The device uses custom reset: | *The device uses custom reset: | ||
**Sets reset catch so that CPU is halted immediately after reset | **Sets reset catch so that CPU is halted immediately after reset | ||
| Line 92: | Line 111: | ||
**Enables debug mode if necessary | **Enables debug mode if necessary | ||
**Clears reset catch | **Clears reset catch | ||
=== | ====Attach==== | ||
* | *Attach is supported | ||
==Evaluation Boards== | ==Evaluation Boards== | ||
Latest revision as of 09:38, 9 July 2025
The Tongxin THA6 Gen 2 device family are Cortex-R52 based microcontrollers.
Flash Banks
| Flash Bank | Base address | J-Link Support | Loader | |
|---|---|---|---|---|
| Name | Size | |||
| PFLASH0[1] | 0x08000000 | 
|
Default | 3 MB |
| PFLASH0 NVR[2] | 0x09800000 |
|
Default | 16 KB |
| PFLASH1[1] | 0x08300000 |
|
Default | 3 MB |
| PFLASH1 NVR[2] | 0x09804000 |
|
Default | 16 KB |
| PFLASH0 (MBUS memory)[2] | 0x40400000 |
|
Default | 3 MB |
| PFLASH0 NVR (MBUS memory)[2] | 0x41C00000 |
|
Default | 16 KB |
| PFLASH1 (MBUS memory)[2] | 0x40700000 |
|
Default | 3 MB |
| PFLASH1 NVR (MBUS memory)[2] | 0x41C04000 |
|
Default | 16 KB |
| DFLASH0 (MBUS memory)[1] | 0x44000000 |
|
Default | 512 KB |
| DFLASH0 NVR (MBUS memory)[2] | 0x44400000 |
|
Default | 32 KB |
| PFLASH0 (MBUS device)[2] | 0x90400000 |
|
Default | 3 MB |
| PFLASH0 NVR (MBUS device)[2] | 0x91C00000 |
|
Default | 16 KB |
| PFLASH1 (MBUS device)[2] | 0x90700000 |
|
Default | 3 MB |
| PFLASH1 NVR (MBUS device)[2] | 0x91C04000 |
|
Default | 16 KB |
| DFLASH0 (MBUS device)[2] | 0x94000000 |
|
Default | 512 KB |
| DFLASH0 NVR (MBUS device)[2] | 0x94400000 |
|
Default | 32 KB |
Watchdog Handling
- The device has a watchdog IWDT.
- The watchdog is fed during flash programming.
Multi-Core Support
Before proceeding with this article, please check out the generic article regarding Multi-Core debugging here.
The THA6 family comes with a Cortex-R52 primary core and up to three Cortex-R52 secondary cores.
| Core | J-Link Support |
|---|---|
| Cortex-R52 CPU0 |
|
| Cortex-R52 CPU1 |
|
| Cortex-R52 CPU2 |
|
| Cortex-R52 CPU3 |
|
In below, the debug related multi-core behavior of the J-Link is described for each core:
Main core
Init/Setup
- Secure Debug:
- Authentication levels EL1 and EL2 are supported.
- Only the default password (all bytes set to 0xFF) is supported. If you need to unlock the device using a custom password, please contact us through our support ticket system.
- Halt timer configuration:
- Corsight CTI is configured to halt the following timers simultaneously with the R52 cores: STM, IWDT, SAFEWDT, CPUWDTn and BASETIMERn.
Reset
- The device uses custom reset:
- Sets reset catch so that CPU is halted immediately after reset
- Performs reset via EDPRCR register
- Ensures that debug power domain and system power domain are powered up
- Powers core if necessary
- Enables debug mode if necessary
- Clears reset catch
Attach
- Attach is supported
Secondary core(s)
Init/Setup
- Secure Debug:
- Authentication levels EL1 and EL2 are supported.
- Only the default password (all bytes set to 0xFF) is supported. If you need to unlock the device using a custom password, please contact us through our support ticket system.
- Halt timer configuration:
- Corsight CTI is configured to halt the following timers simultaneously with the R52 cores: STM, IWDT, SAFEWDT, CPUWDTn and BASETIMERn.
Reset
- The device uses custom reset:
- Sets reset catch so that CPU is halted immediately after reset
- Performs reset via EDPRCR register
- Ensures that debug power domain and system power domain are powered up
- Powers core if necessary
- Enables debug mode if necessary
- Clears reset catch
Attach
- Attach is supported