Error 304 means that the BlueBox fails to connect respectively fails to establish debug session with the Cortex-M based target CPU.
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 if the BlueBox is properly connected to the target debug connector
through the usage of proper BlueBox Debug Adapter (iC5000, iC5700).
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 worst case the hardware can get damaged too.
Cortex-M based embedded target typically provides 10-pin 1.27 mm or 20-pin 1.27 mm target debug connector featuring CoreSight 10 respectively 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.
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.
{{ topic.Content }}