The Arm CoreSight SDC-600 Secure Debug Channel, provides a dedicated path to a debugged system for authenticating debug accesses. Key benefits include:
- A standardized communication protocol
- The first layer of protection against debug access attacks
- Robust security solution with Arm Security IP
|Conventional Secure JTAG Controller||CoreSight SDC-600|
|Need for external JTAG pins exposure||Functional IO/JTAG pins|
|Simple key-based authentication||Certificate and key-based authentication|
|No / lack of cryptographic involvement||Fully interoperable with Crypto IP|
|Customized communication protocol||Standard and open communication protocol|
Start designing now
Arm Flexible Access gives you quick and easy access to this IP, relevant tools and models, and valuable support. You can evaluate and design solutions before committing to production, and only pay when you’re ready to manufacture.
Authenticated debug through an always-on communication channel
CoreSight SDC-600 addresses the security needs of modern day devices, by allowing silicon and tool vendors to enforce protection and to police debug accesses into the system. This is achieved through a debug certificate, exchanged through a dedicated communication path of CoreSight SDC-600.
Complete end-to-end security solution
CoreSight SDC-600 is intended to work closely with Cryptographic elements, to provide a robust security solution through debug certificate authentication. Arm ensures that CoreSight SDC-600 is designed and tested, to work efficiently with Arm CoreSight IP and Arm Security IP. This provides the most reliable and predictable security implementation for authenticating debug accesses.
Promoting efficient ecosystem adoption
CoreSight SDC-600 implements the Arm recommended communication protocol, which enables efficient handshake communication between an external agent and target system.
|Not answered||CMSIS: Storage interface vs Flash interface - what's the difference ?||0 votes||37 views||0 replies||Started 11 hours ago by ranchu||Answer this|
|Suggested answer||What SBCs I need to choose?||0 votes||71 views||1 replies||Latest yesterday by Andy Neil||Answer this|
|Not answered||Does anyone knows why a documentation as ARM DSU 0030 is only available for licensees||0 votes||37 views||0 replies||Started yesterday by JaWa||Answer this|
|Suggested answer||The meanings of AxCACHE||0 votes||202 views||1 replies||Latest 4 days ago by Christopher Tory||Answer this|
|Suggested answer||CoreLink NIC-400 Interconnect gives an extra request||0 votes||275 views||1 replies||Latest 4 days ago by Christopher Tory||Answer this|
|Suggested answer||Is there a limit for AXI4 outstanding transaction?||0 votes||190 views||1 replies||Latest 4 days ago by Christopher Tory||Answer this|
|Not answered||CMSIS: Storage interface vs Flash interface - what's the difference ? Started 11 hours ago by ranchu||0 replies 37 views|
|Suggested answer||What SBCs I need to choose? Latest yesterday by Andy Neil||1 replies 71 views|
|Not answered||Does anyone knows why a documentation as ARM DSU 0030 is only available for licensees Started yesterday by JaWa||0 replies 37 views|
|Suggested answer||The meanings of AxCACHE Latest 4 days ago by Christopher Tory||1 replies 202 views|
|Suggested answer||CoreLink NIC-400 Interconnect gives an extra request Latest 4 days ago by Christopher Tory||1 replies 275 views|
|Suggested answer||Is there a limit for AXI4 outstanding transaction? Latest 4 days ago by Christopher Tory||1 replies 190 views|