🎉 We're happy to announce new public releases 🎉

  • SmartCode v10.4r1 - Take advantage of all the benefits our tools have to offer and build your applications with the latest version
  • TriCore v6.3r1 Inspector v1.0r8 - Save time and detect known issues before they get into your application
Contact us to get access

car engine
Find results that contain at least one of the two words.

"car engine"
Find results that contain the exact phrase 'car engine'.

+car +engine
Find results that contain both words.

car -engine
Find results that contain the word 'car' but not 'engine'.

car*
Partial match. Find results like 'car', 'carneval', 'carousell'.

Arm Cortex Cypress Traveo II: Debug session initialization prerequisites

05-Aug-2024

Traveo II devices require a debug interface operating at a frequency higher than 1500 kHz. This permits the debugger to execute the necessary debug initialization procedures fast enough and within the device start-up time window constraint after the CPU reset line is released by the BlueBox.

winIDEA will report a warning while connecting to the CPU if the debug interface frequency is not configured properly.



When the application is properly linked and programmed into the Flash, the CPU will stop after resetting at the address to which the reset vector points to. If Flash contains no valid code (e.g. empty device), the CPU will stop in the boot code.


On all Cypress Traveo II devices, use the Regular RESET method for reset in initialization operation.


Possible solution

1. Follow the Configure Architecture-specific settings tutorial.

2. If in the debug interface: 

  • SWD Debug Protocol is used - set the SWD clock to 1500 kHz or higher.
  • JTAG Debug Protocol is used - set JTAG Scan Speed to 1500 kHz or higher.


More resources in winIDEA Help

Was this answer helpful?
Similar topics
Load more...