Search Results
Search results 1-6 of 6.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Good day, Probably someone has similar problem and will be able to help with quick fix. I have newbuild module with TMS570LS3135 on the board, all supply voltages in the range. JTAG connection was tested from J-Flash with following results: (please see "Good.png") After download simply "LED Blinky" project, it was created in in code composer studio with TI HEL , we got : (please see "Bad.png") and it seems that the MCU is "locked" and stop to run. Does exist way of erase Mcu's memory and return …
-
Thank you, Matthias.
-
Hi Alex, Thank you for update, we'll wait.
-
Hi Alex, Thank you for prompt response. Just small clarification: >> So the fact that the message box shows a version != V6.88 indicates that your CCS installation is *not* using a V6.88 version of the J-Link software Yes, pic. 1 I got when I made upgrade of CSS ver. 10.0.0.xxx to 10.1.1.0004. And as soon as found that Segger stop support Mcu what I had using last 6 months I made decision to upgrade Segger J-link support for CSS as well. and used CCS Install New Software option.Pls. see pic 6. i…
-
Good day Alex, I'm appreciate for prompt response. Probably, my initial explanation was not clear enough and pictures made you confused. But our story is quite simple : 1. We have been using JLink & CCS since for last 8 months , since got it from Element14. 2. Everything worked well for CCS with version below 10.0.x 3. The CCS was updated to latest version approx. 5-6 days before. The JLink drivers for CCS was updated to ver.6.88.0 as well. 4. After we had found unpleasant thing : JLink stop to …
-
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 chec…