• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 53 subscribers
  • Views 1149 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LM3S9B96 : Error conencting to the target

roberta
Prodigy 230 points


I am trying to port from Code Red to Code Composer. I can download my original project on our custom board, which uses the same eval board FTDI design, & debug fine in Code Red.

I have imported the uart_echo example, commented out all graphics calls, and built the code just fine for the lm3S9B96 processor.

However when I try to Debug the Active project I get "CORTEX_M3_0: Error connecting to the target".  I have searched what little documentation exists and found nothing to give me a clue as to what might be the problem.

Ideas?

Here is the target config file:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<configurations XML_version="1.2" id="configurations_0">

<configuration XML_version="1.2" id="Stellaris In-Circuit Debug Interface_0">

<instance XML_version="1.2" desc="Stellaris In-Circuit Debug Interface_0" href="connections\Stellaris_ICDI_Connection.xml" id="Stellaris In-Circuit Debug Interface_0" xml="Stellaris_ICDI_Connection.xml" xmlpath="connections"/>

<connection XML_version="1.2" id="Stellaris In-Circuit Debug Interface_0">

<instance XML_version="1.2" href="drivers\stellaris_cs_dap.xml" id="drivers" xml="stellaris_cs_dap.xml" xmlpath="drivers"/>

<instance XML_version="1.2" href="drivers\stellaris_cortex_m3.xml" id="drivers" xml="stellaris_cortex_m3.xml" xmlpath="drivers"/>

<platform XML_version="1.2" id="platform_0">

<instance XML_version="1.2" desc="Stellaris LM3S9B96_0" href="Devices\lm3s9b96.xml" id="Stellaris LM3S9B96_0" xml="lm3s9b96.xml" xmlpath="Devices"/>

<device HW_revision="1" XML_version="1.2" description="" id="Stellaris LM3S9B96_0" partnum="LM3S9B96">

<router HW_revision="1.0" XML_version="1.2" description="CS_DAP Router" id="CS_DAP_0" isa="CS_DAP">

<subpath id="subpath_0">

<cpu HW_revision="1.0" XML_version="1.2" description="Cortex M3 CPU" id="CORTEX_M3_0" isa="CORTEX_M3">

<property Type="choicelist" Value="0" id="Slave Processor"/>

<property Type="choicelist" Value="0" id="bypass"/>

</cpu>

</subpath>

</router>

</device>

</platform>

</connection>

</configuration>

</configurations>

 

 

 

  • 0
    TI__Guru**** 171224 points

    Roberta,

    I am not entirely sure what is happening in your case, but I have a few hints:

    - Your custom board may use an old ICDI firmware revision. I recall a while ago that some of the older boards had compatibility issues with CCS - something that was corrected at later releases, but that could explain why it works with CodeRed but fails to connect to CCS.

    - If the error message mentions anything about licensing, you may be running the  CCS free limited license which does not allow using ICDI outside of the development board. In this case, you can use an XDS100 emulator which fully supports all targets and does not require purchasing a CCS license. Check this other post for some additional comments about the ICDI usage.

    - Bad or invalid device drivers for the ICDI. You can check this post for the placement of the ICDI installer shipped with CCS.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 230 points

    Rafael,

    Sorry Rafael, I have read the posts you recommended, but I am not finding any answers there.

    First I should note that the Help says that I am licensed to use Code Composer, and I was able to download the hello example to an MSP430 just after I installed the software. I am only having problems with the LM3S9B96 project.

    I have tried reinstalling ccs4.2.4.00033, since that is what one of your posts did, and I am still get an "error connecting" message. However, it is also saying "frequency is out of range". I do not know what that means.

    I downloaded the LM flash programmer, and tried it. The options are different from the old Flash Programmer so I wasn't sure what options to pick. I tried several and I every time I tried to erase flash it said "unable to find target" I tried several options & nothing worked. I am trying to see if my boss can find an old version of the flash programmer, as I know it worked with this board at one time. Also, I tried the "update ICDI driver" and it said it wasn't installed.

    I worked on this code for two years, and this is the first time I have heard the term ICDI mentioned or a reference to a driver for it. We always thought of the interface as an FTDI serial driver with the debugger using the SWD interface. You talk about old ICDI firmware revisions and ICDI device drivers. Is there anywhere that documents what this ICDI driver is and how it works with the FTDI driver. What is its name. Where is it installed? When is it installed? What are its versions & what versions are required for what processor revisions.

    Our current boards use C3 parts. For a while, every time a new uP came out we had to upgrade our Code Red software. I am not sure what part is currently on our old canabalized development boards. (I am working contract from home now). We probably upgraded them from B1 to C3 at some point. I will try and get one so that I can see if it works. I really think there is just something wrong with the configuration on my system & not the production board.

    Roberta

  • 0 in reply to roberta
    Prodigy 230 points

    Hmm, I have done some more googling/reading

    The following  http://processors.wiki.ti.com/index.php/Stellaris-ICDI_Programming , IMPLIES that the FTDI chip has to be reprogramed to work with the CCS? It refers lcdi.zip which I can download.  It does not mention if my Code Red setup will work after I reflash the FTDI chip or how to restore the FTDI chip to its original flash if things go wrong.  I really don't want to try this unless I am sure it is the proper thing to do and I am sure I can still use the Code Red tools after it is done.  Since I am porting two years of work from Code Red to Code Composer, I need to be able to swap between the two development tools until I get all of the bugs out of the Composer development.

    Is there a complete story behind this, the need for it, what exactly it corrects, and if this new version is compatible with Code Red? The hardware guys really hate me when I tell them I need a part replaced on the board. I'll keep googling, but right now I am to scared to try it.

    Roberta

  • 0 in reply to roberta
    TI__Guru**** 171224 points

    Roberta,

    Unfortunately I don't have the whole story, therefore I will have to get some help from the Stellaris experts here as they are more knowledge about the CodeRed tool than I.

    However please check some comments below:

    roberta said:

    First I should note that the Help says that I am licensed to use Code Composer, and I was able to download the hello example to an MSP430 just after I installed the software. I am only having problems with the LM3S9B96 project.

    Good to know. It means you have a valid CCS license and it can connect to a target.

    roberta said:

    I have tried reinstalling ccs4.2.4.00033, since that is what one of your posts did, and I am still get an "error connecting" message. However, it is also saying "frequency is out of range". I do not know what that means.

    I downloaded the LM flash programmer, and tried it. The options are different from the old Flash Programmer so I wasn't sure what options to pick. I tried several and I every time I tried to erase flash it said "unable to find target" I tried several options & nothing worked. I am trying to see if my boss can find an old version of the flash programmer, as I know it worked with this board at one time. Also, I tried the "update ICDI driver" and it said it wasn't installed.

    The "frequency out of range" message can be caused by several issues related to the JTAG connection or even to locked devices. However, the fact that LMFlash is not working indicates something else may be wrong - maybe a hardware or a device driver issue.

    roberta said:

    I worked on this code for two years, and this is the first time I have heard the term ICDI mentioned or a reference to a driver for it. We always thought of the interface as an FTDI serial driver with the debugger using the SWD interface. You talk about old ICDI firmware revisions and ICDI device drivers. Is there anywhere that documents what this ICDI driver is and how it works with the FTDI driver. What is its name. Where is it installed? When is it installed? What are its versions & what versions are required for what processor revisions.

    I mentioned the ICDI as I imagine you are using a standalone JTAG debugger for your custom board, but you are correct in saying it uses the standard FTDI device drivers (sorry for misleading you). However, the ICDI emulator I have here (that works with CCS) has the same settings shown in the page you referenced, notably the VID/PID (0x0403/0xBCDA) and the Product Description (Luminary Micro ICDI Board).

    Can you run FTProg and compare the settings for your board? That could be one detail that is preventing the debug procedure.

    Also, FTProg can save the current settings to a XML file (the option Save As Template), thus allowing you to return to your original settings.

    Regards,

    Rafael

  • 0 in reply to desouza
    Prodigy 230 points

    Ok, I'll check out the FTprog tomorrow & see what information it gives me. Maybe that will help me understand how things are workin. I am going to pickup an old 2009  eval/development board to experiment with also. It won't be so bad if I mess it up instead of our custom board. 

  • 0 in reply to roberta
    Prodigy 230 points

    Ok, Rafael things are working well now. I was totally confused with your first post but after enough searching in that area, I now realize that the FTDI requires that it be programmed in order for all of the tools to work properly.

    FYI

    The FTDI on our custom board was blank. The FTDI on our old eval board was not. The LM Programmer debugger interface worked with the eval, but not the custom board. Plus a lot of memories from two years back were surfacing. I had a lot of problems getting things to work as soon as I started working with the custom board. We worked with an FAE for a long time trying to figure out what was wrong with the board, but found nothing wrong. Nothing was ever mentioned about programming the FTDI. At some point I figured out a way to do what I needed with Code Red and meet our deadlines, but I never really got the LM Programmer to work the way I remembered, and it seemed that Code Red didn't work as well as it used to, but I blamed it on all of the new processor revs and Code Red Revs & didn't have time to investigate. 

    Hopefully this will clear up a lot of other problems we were having as well.

    Thank You, Roberta

  • 0 in reply to roberta
    TI__Guru**** 171224 points

    Roberta,

    I am glad the board is working well, and thanks for reporting back the results of your work.

    I recall at some point we had to incorporate an additional device identification mechanism in CCS to avoid it getting confused by USB-to-serial adapters based on the FTDI chip. I imagine that some releases of CodeRed work with the default settings of the FTDI device, but not CCS (nor the LMFlash programmer).

    Regards,

    Rafael