Categories

{{ selectedCategory.name }}

{{ topic.Title }} {{ topic.Ddate | formatDate }}

{{ topic.Content }}

No topics found!

Arm Cortex-M: Error 304: Check Debug Adapter

10-Jun-2024

Error 304 means the BlueBox fails to connect and establish debug session with the Cortex-M-based target CPU.


Possible solutions

Use the Reset debug command

When troubleshooting the initial debug connection to the target CPU, it's recommended to use the CPU Reset debug command instead of the Download debug command. 


Check Debug Adapter

Check if the BlueBox is properly connected to the target debug connector through the usage of proper BlueBox Debug Adapter (iC5000, iC5700).

Check the pinout of the target debug connector

Double-check that the pinout of the target debug connector matches with the one from the debug adapter. Pinouts can be found in the Debug Adapters User Manual

If a wrong debug adapter is used, the debug connection to the target CPU will fail and in the worst case the hardware can get damaged too.


Cortex-M-based target typically provides 10-pin or 20-pin target debug connector featuring  CoreSight 10 or CoreSight 20 pinout. Some Cortex-M targets may also provide 20-pin 2.54 mm target debug connector. Be careful with this one since it can have either CoreSight 20 pinout or Arm pinout.

Was this answer helpful?

Sorry this article didn't answer your question, we'd love to hear how we can improve it.
Note: This form won't submit a case. We'll just use it to make this article better.

Similar topics

{{ topic.Title }} {{ topic.Ddate | formatDate }}

{{ topic.Content }}

No similar topics found!

Other topics in the same category

{{ topic.Title }} {{ topic.Ddate | formatDate }}

{{ topic.Content }}

No topics found!