TRAVEO™ T2G

excuse me, i can't find TRAVEO II chip 's  silk screen printing  in datasheet.

can you tell me which document introduce this. thanks!

参考 https://community.infineon.com/t5/Knowledge-Base-Articles/Debug-and-Program-Traveo-II-MCU-with-J-Link-KBA228450/ta-p/263278 所述，在CYTVII-B-E-1M-SK 上验证Jlink功能；

发现使用Jlink调试时，可以启动debug，但没办法进入中断函数(void Tc_Handler(void))；附件是使用的CM4 测试代码；

通过CYTVII-B-E-1M-SK  提供的MIPI接口来实现Jlink调试；

芯片供电电压通过外部直接电源供电(3.3V)

基于相同代码，把Debugger Driver换成CMSIS DAP，debug下可以正常进入中断服务函数；

请问，使用Jlink调试TraveoII，是不是有其他限制或需要额外辅助设置？

Hello, 

We are having serious problems connecting to a CYT2B95CAC part using SWD and a JLink segger.
This is the message displayed on j-flash
Can you help please?
Thanks

Message : 

Connecting ...
- Connecting via USB to probe/ programmer device 0
- Probe/ Programmer firmware: J-Link V11 compiled Dec 7 2021 08:37:18
- Device "CYT2B95CAC_M0" selected.
- ConfigTargetSettings() start
- Disabling flash programming optimizations: Compare, SkipBlankDataOnProg and flash breakpoints
- J-Link script: ConfigTargetSettings()
- ConfigTargetSettings() end
- ConfigTargetSettings() start
- Disabling flash programming optimizations: Compare, SkipBlankDataOnProg and flash breakpoints
- J-Link script: ConfigTargetSettings()
- ConfigTargetSettings() end
- Target interface speed: 200 kHz (Auto)
- VTarget = 3.354V
- ConfigTargetSettings() start
- Disabling flash programming optimizations: Compare, SkipBlankDataOnProg and flash breakpoints
- J-Link script: ConfigTargetSettings()
- ConfigTargetSettings() end
- ConfigTargetSettings() start
- Disabling flash programming optimizations: Compare, SkipBlankDataOnProg and flash breakpoints
- J-Link script: ConfigTargetSettings()
- ConfigTargetSettings() end
- ERROR: Failed to connect.
Could not establish a connection to target.

Regards,

Abdelhadi

According to TRAVEO™ T2G Automotive Body Controller Entry Family Architecture Technical Reference Manual (TRM) 20.6 Debug Mode, Table 20-5. Debug Modes: When configure DEBUG_RUN to 0 and DEBUG_TRIGGER_ENABLE to 1, watchdog counter is stopped only when a debugger is connected and the CPU is halted during a breakpoint.

However, the watchdog counter does not stop when a debugger is connected and the CPU is halted during a breakpoint.

It seems that to pause at a breakpoint while debugging, need configure the trigger matrix to connect the related CPU halted signal to the trigger input for the related watchdog timer:

Could you kindly help to share how to configure the trigger matrix to connect the related CPU halted signal to the trigger input for the related watchdog timer?

Thanks very much!

Hi,

MCU CYT2B75

If the global for ADC unit settings "DIAG_EN" and "EPASS_MMIO.PASS_CTL.REFBUF_EN" are set for diagnostic purposes, are those settings affect on all ADC groups (channels). For example I want to use only two channels per unit for diagnostic purposes.

Best rgeards,