Difference between revisions of "Multi-Core Debugging"
| Line 1: | Line 1: | ||
==Terminologies== |
==Terminologies== |
||
Basically, there are two two different approaches when it comes to multi-core setups: |
Basically, there are two two different approaches when it comes to multi-core setups: |
||
| − | ===SMP ( |
+ | ===SMP (Symmetrical multiprocessing)=== |
TBD |
TBD |
||
===AMP (Asymmetrical multiprocessing)=== |
===AMP (Asymmetrical multiprocessing)=== |
||
TBD |
TBD |
||
| + | ==J-Link Debug Support== |
||
| + | The J-Link support both approaches: SMP and AMP and of course hybrid solutions. Unfortunately, multi-core debugging is not as straight forward or as simple as it sounds. Why? Customer requirements highly depend on the actual use case and on the available multi-core debug related features provided by the chosen SoC such as individual reset functionality of the different cores. Those requirements make it difficult to provide a out-of-the-box solution, which covers all use cases. For that reason, the J-Link supports the most common use cases by default. This behavior should be well documented on the corresponding device family page. Other scenarios can be also supported but may require some custom configurations. Please feel free to get in touch with SEGGER in such cases. |
||
Revision as of 15:10, 30 January 2023
Contents
Terminologies
Basically, there are two two different approaches when it comes to multi-core setups:
SMP (Symmetrical multiprocessing)
TBD
AMP (Asymmetrical multiprocessing)
TBD
J-Link Debug Support
The J-Link support both approaches: SMP and AMP and of course hybrid solutions. Unfortunately, multi-core debugging is not as straight forward or as simple as it sounds. Why? Customer requirements highly depend on the actual use case and on the available multi-core debug related features provided by the chosen SoC such as individual reset functionality of the different cores. Those requirements make it difficult to provide a out-of-the-box solution, which covers all use cases. For that reason, the J-Link supports the most common use cases by default. This behavior should be well documented on the corresponding device family page. Other scenarios can be also supported but may require some custom configurations. Please feel free to get in touch with SEGGER in such cases.
