Good day,
I've recently updated firmware of my J-link Pro to ver 6.88 from J-link Configurator V6.88, upgrade process passed without any problem but CCS rejected to connect to MCU and I got message (please see pic1).
I updated CC Studio from download.segger.com/J-Link/JLink_TI_CCS_plugin_unified with latest driver for JLINK, and could not connect to the target mcu as as well, with error message showed on pic. 3. I though that problem was in Segger Link settings (pic. 6), but all looks OK, I check all paths and files, all looks good, and made one more test and found that J-Link could connect to target mcu by J-Link Commander ( pics 5 and 6), so all hw is in working condition.
My question is : what else I can check or test for resolve such kind of problem ? Because do not want return back ti xds100 after work with j-link.
small update, I tried to use software package 6.88a with JLink, and got same story as above. I suppose that problem somewhere in around JLinksctipt file, because randomly got couple success connections with mcu, but what was reason, I can't explain, may be because MCU was in some spacial state after manipulation from JLink Commander
.
May be someone can advice how to make log of JLink activity when it busy with CCS debugging, because logging from from CCS does not work? It should give us idea what to do next.
I did not have such kind of problem before, all project setup process was quite simple and user friendly, but I could not "roll back" to some working stage , because on download.segger.com/J-Link/JLink_TI_CCS_plugin_unified is version 6.88.0 only.
I've recently updated firmware of my J-link Pro to ver 6.88 from J-link Configurator V6.88, upgrade process passed without any problem but CCS rejected to connect to MCU and I got message (please see pic1).
I updated CC Studio from download.segger.com/J-Link/JLink_TI_CCS_plugin_unified with latest driver for JLINK, and could not connect to the target mcu as as well, with error message showed on pic. 3. I though that problem was in Segger Link settings (pic. 6), but all looks OK, I check all paths and files, all looks good, and made one more test and found that J-Link could connect to target mcu by J-Link Commander ( pics 5 and 6), so all hw is in working condition.
My question is : what else I can check or test for resolve such kind of problem ? Because do not want return back ti xds100 after work with j-link.
small update, I tried to use software package 6.88a with JLink, and got same story as above. I suppose that problem somewhere in around JLinksctipt file, because randomly got couple success connections with mcu, but what was reason, I can't explain, may be because MCU was in some spacial state after manipulation from JLink Commander
.
May be someone can advice how to make log of JLink activity when it busy with CCS debugging, because logging from from CCS does not work? It should give us idea what to do next.
I did not have such kind of problem before, all project setup process was quite simple and user friendly, but I could not "roll back" to some working stage , because on download.segger.com/J-Link/JLink_TI_CCS_plugin_unified is version 6.88.0 only.
The post was edited 2 times, last by KGA ().