Search Results
Search results 1-11 of 11.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
SmartRF06 + CC13xxEM behaves differently than my HWs. I tried various modifications but the only one which helped was using the same RC filter on /RESET signal. When I use 100k-100n as on TI's kit, application is correctly halted at beginning of main (). Using 10k-100n doesn't work. I think that CC13xx starts main () faster than J-Link can prepare break for main (). But I don't understand why J-link behaves this way. CC13xx can stop in ROM waiting for debugger so there should be enough time rega…
-
Dear Niklas, bootloader backdoor is enabled intentionally. This signal contains external 10k pull-down. When no debugger is connected, is runs normally. Then I did tests on more HWs with CC1310 and found that used pull-down is not always working reliably. It probably depends on chip parameter variations. There are two problems with bootloader pin: - TI haven't mentioned using internal pullup for this pin until February (newest RefMan); and this note is not mentioned in revision history so I have…
-
Here are two log files: JLinkLog_502e.txt contains successful start of debug session JLinkLog_614a.txt contains unsuccessful debug session; debugger can't reach main function; I tried to stop execution - MCU is processing loop in ROM code; I guess it could be HIB feature of CC13xx ROM code? Only DLL version is different. Other parts of debug setup are the same (application MCU+HW, code, J-Link FW, Keil)... Is there anything what can I try to successfully use newest DLL version?
-
I used CC13xx debug with J-link in Keil for long time with 5.02e version with more Keil versions. Recently, I have upgraded J-Link to latest version 6.14a. Unfortunately this "broke" Keil debugging. After some time trying to downgrade J-Link I tried downgrading DLL and it helped. The question is which version of DLL should I use to have the newest but also working Other question is what is wrong between Keil and latest DLL... but I have no idea how to trace the root of problem... Behaviour descr…