Hi,
I'm working on TI CC2642 chipset now, everything is working fine with TI XDS110 debugger. Now, we need to switch to JLINK because of new hardware design, but when I connected JLINK and started debugging, there are more 60% chance that the board will be stuck in exception, I did some trace with OZone, and also talked to TI support engineer, the conclusion is the reset with JLINK not fully cold reset which causes some timer, uart interrupt not be cleared up completely. I also tried to toggle the reset pin of CC2642, then attach the JLINK to device, it's working fine. I'm not very family with the JLINK script, so my question is if there is any way to use OZone to debug this with togging ResetPIN for resetting device?
Any response will be appreciated.
I'm working on TI CC2642 chipset now, everything is working fine with TI XDS110 debugger. Now, we need to switch to JLINK because of new hardware design, but when I connected JLINK and started debugging, there are more 60% chance that the board will be stuck in exception, I did some trace with OZone, and also talked to TI support engineer, the conclusion is the reset with JLINK not fully cold reset which causes some timer, uart interrupt not be cleared up completely. I also tried to toggle the reset pin of CC2642, then attach the JLINK to device, it's working fine. I'm not very family with the JLINK script, so my question is if there is any way to use OZone to debug this with togging ResetPIN for resetting device?
Any response will be appreciated.