4 Troubleshooting
This section explains possible issues and the workarounds.
4.1 Connection troubleshooting
Error: Starter kit is not detected on the target system.
• Connect the USB cable that comes with the starter kit. Other USB cables may not connect data lines
• Make sure LED3 is ON (CMSIS-DAP mode). If not, press SW3 to change the KitProg3 device mode
• If LED3 is ON (CMSIS-DAP mode), change the KitProg3 device mode by pressing SW3. Now LED3 is smoothly
blinking. Then try to reconnect the debug session. Then independently if this works or not, stop the debug
session again and switch the KitProg3 device mode to LED3 is always ON (CMSIS-DAP mode)
• Make sure jumper R11 is closed
4.2 Driver troubleshooting
Error: Driver is not detected on the target system or “KitProg3” is not visible
For more information on the supported driver, see the KitProg3 user guide [1].
4.3 Debugger troubleshooting
Error: While programming TRAVEO™ T2G device, CMSIS-DAP device is not found.
Check the USB cable connection and the state of LED3 (LED should be ON for CMSIS-DAP mode).
4.4 Key points
• CM0+ core should be running while debugging with CM4 in single core mode. CM0+ core enables the CM4
core by calling the Cy_SysEnableApplCore() API
• CM4 core workspace (tviibe1m_flash_cm4_mc_template) should be built before building the dual core
workspace (tviibe1m_flash_cm0plus_cm4_template)
To Next Page
Loading...
