• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 369 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.

IWR1843BOOST: IWR1843BOOST

Alan Milne
Intellectual 285 points
Part Number: IWR1843BOOST
Other Parts Discussed in Thread: IWR1843, UNIFLASH

Hi,

maybe hardware failure?

All working OK, developing & debugging in CCS 11 (update to 12 ... same error).  Suddenly get this error:

Error connecting to the target:
(Error -151 @ 0x0)
One of the FTDI driver functions used during the connect
returned bad status or an error. The cause may be one or
more of: no XDS100 is plugged in, invalid XDS100 serial number,
blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the XDS100 can be located.
(Emulation package 9.6.0.00172)

XDS110 ports X2 appear in device manager, mmwStudio works fine (recently re-installed to fix problem loading DCA1000, but CCS was OK after this), uniFlash7 OK - ccsdebug download.

So - tools seem happy & working, except CCS.  Any suggestions of what to look at next?

many thanks

Alan Milne

  • 0
    TI__Expert 8802 points

    Hi Alan,

    Have you tried googling the error? There are a handful of other posts on E2E that seem to be dealing with this or similar issues.

    Also, you could try using the XDS utility software to try and reset the XDS - it should be located in your CCS install under ccs\ccs_base\common\uscif\xds110

    Regards,

    Tim

  • 0 in reply to Tim Henderson
    Intellectual 285 points

    Hi Tim,

    googling just gave millions of links to windows problems.  Searching the error number of TI didn't seem to give much much either - lots if suggestions, but mostly for other devices.  If I include IWR1843, the only relevant link - was this one.

    Sorting errors at this level is not my area of expertise, so safer to ask.  I've tried the XDS110reset - doesn't seem to have changed anything.

    Is this something which has failed on the board;? Hard error (buy a new one) or soft (may be able to recover)?  Is it something to do with flash memory (as mentioned in the readme) being corrupted, or loosing contents?

    All other things (e.g. mmwavwestudio & uniflash) still seem to work - is this just around the JTAG-via-USB interface, for CCS debug?  Interestingly, doing a TEST CONNECTION in ccs passes OK.

    many thanks

    Alan

  • 0 in reply to Alan Milne
    TI__Expert 8802 points

    Hi Alan,

    So you tried the XDS utility and a reset didn't work? If so, then the next thing I might try would be to uninstall and reinstall the XDS drivers.

    Additionally, can you confirm if flashing a demo from the radar toolbox (such as the out of box or people counting) and then running the visualizer all works?

    Can you describe where in the debugging process it throws the error? Are you able to connect to the board at all before uploading your program via CCS?

    Any more detail you can provide would be great. Also, do you have another board OR another PC you can test with? This could help us tell if it's a CCS or board bug.

    Regards,

    Tim

  • 0 in reply to Tim Henderson
    Intellectual 285 points

    Hi Tim,

    yes, uniflash with ccsdebug seems OK, and mmwStudio also works.  Reset didn't seem do anything.

    However, something else "interesting" is going on here....

    I tried another PC (stucioCLI) - this works OK, so seems like the USB & board are OK.

    I then tried stuiodCLI (or at least a version with my add-ons) on the original PC - works fine.  So does oob.

    So - it looks like there's something gone wrong in the specific CCS project.  I get the same error using CCS12 rather than 11: I didn't download 12 until after this fault, so it's not any issue caused by that - and I took a copy of the project, so I didn't cross-contaminate between versions of the tool.

    Also, I may have noticed something important  it was there in the error message I sent, but I didn't actually recognise it till today.  On the ccs console (and on the error report, but in the title text, so it didn't get included in what I copied into the original question), it says:

    IcePick_M_0: Error connecting to the target: (Error -151 @ 0x0) One of the FTDI driver

    Note IcePick, and it also says XDS100 ... but I'm using XDS110 - this is what everything in the project i.e. ccxml says.  Is this the problem? Somehow, just in this project, now, it's started trying to use the wrong debugger interface??  I have no idea if/how this is possible, but it at least seems a significant clue.

    Of course, I can't tell you what the other working ccs projects say, because they don't give me an error message to look at.  The various build & start debug boxes go by too fast to see if there's anything in them to help.

    hope that helps track it down.

    thanks

    Alan

  • 0 in reply to Alan Milne
    TI__Expert 8802 points

    Hi Alan,

    Can you send your target configuration .ccxml?

    Regards,

    Tim

  • 0 in reply to Tim Henderson
    Intellectual 285 points

    Hi Tim,

    I don't think I'd give anything away by doing so - I seem to have one in each of DSS & MSS.  The error occurs just as you get going with debug, it's done the compile bits, then presumably its as it starts to talk to the h/w.

    ..OK, it always seems difficult to attach file to here, so I'll have to paste them as text:

    DSS

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <configurations XML_version="1.2" id="configurations_0">

    <configuration XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
    <instance XML_version="1.2" desc="Texas Instruments XDS110 USB Debug Probe_0" href="connections/TIXDS110_Connection.xml" id="Texas Instruments XDS110 USB Debug Probe_0" xml="TIXDS110_Connection.xml" xmlpath="connections"/>
    <connection XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
    <instance XML_version="1.2" href="drivers/tixds510debugssm.xml" id="drivers" xml="tixds510debugssm.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds510cs_dap.xml" id="drivers" xml="tixds510cs_dap.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds510cortexR.xml" id="drivers" xml="tixds510cortexR.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds510cs_child.xml" id="drivers" xml="tixds510cs_child.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds510etbcs.xml" id="drivers" xml="tixds510etbcs.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds510icepick_m.xml" id="drivers" xml="tixds510icepick_m.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds510c674x.xml" id="drivers" xml="tixds510c674x.xml" xmlpath="drivers"/>
    <platform XML_version="1.2" id="platform_0">
    <instance XML_version="1.2" desc="IWR1843_0" href="devices/iwr1843.xml" id="IWR1843_0" xml="iwr1843.xml" xmlpath="devices"/>
    </platform>
    </connection>
    </configuration>
    </configurations>

    MSS

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <configurations XML_version="1.2" id="configurations_0">

    <configuration XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
    <instance XML_version="1.2" desc="Texas Instruments XDS110 USB Debug Probe_0" href="connections/TIXDS110_Connection.xml" id="Texas Instruments XDS110 USB Debug Probe_0" xml="TIXDS110_Connection.xml" xmlpath="connections"/>
    <connection XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
    <instance XML_version="1.2" href="drivers/tixds510debugssm.xml" id="drivers" xml="tixds510debugssm.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds510cs_dap.xml" id="drivers" xml="tixds510cs_dap.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds510cortexR.xml" id="drivers" xml="tixds510cortexR.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds510cs_child.xml" id="drivers" xml="tixds510cs_child.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds510etbcs.xml" id="drivers" xml="tixds510etbcs.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds510icepick_m.xml" id="drivers" xml="tixds510icepick_m.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds510c674x.xml" id="drivers" xml="tixds510c674x.xml" xmlpath="drivers"/>
    <platform XML_version="1.2" id="platform_0">
    <instance XML_version="1.2" desc="IWR1843_0" href="devices/iwr1843.xml" id="IWR1843_0" xml="iwr1843.xml" xmlpath="devices"/>
    </platform>
    </connection>
    </configuration>
    </configurations>

    hope that's all there - and tells you something about the problem.  It does look like its calling up XDS110.  I wasn't aware of having done anything different to cause whatever has gone wrong - in debug session, added next bit of code to test, went into debug, got the failure.

    thanks

    Alan

  • 0 in reply to Alan Milne
    TI__Expert 8802 points

    Hi Alan,

    Can you try creating new target configurations in CCS? Also, have you tried reverting that portion of code you mentioned you changed before you got the failure?

    It's unclear from your previous comment, but you can debug a different program in CCS debug with this board correct?

    I would highly suspect some property/setting got changed in your program or target configuration that is causing it to fail. I am asking around internally to see if we have seen this before.

    Regards,

    Tim

  • 0 in reply to Tim Henderson
    Intellectual 285 points

    Hi Tim,

    yes, change was a simple un-comment the call to the next bit of code, tried reversing ... no change.

    Also yes, in ALL other projects I tried, they could all debug - well, at least to the extent of correctly going through the debug start up processes, downloading the code, and it runs on the h/w.

    I have tried a new debug configuration: I opened the existing (non working) one i.e. used "debug configurations", and simply renamed it, then APPLY.  Unfortunately this has indeed just renamed it, rather than giving me a new one, as I intended, and the original still existing, to compare with. 

    However - this new configuration - simply the non-working one renamed & APPLYed ... works OK!  I didn't change any parameters in the config editor.

    So its looking like something in or around CCS managed to corrupt something (NOT including the parameters in config editor, they still looked OK, and I didn't change them), and the APPLY has re-written what ever it was with the  now correct info.  On the grounds that the problem persisted - including after windows re-start - it must be something written to disk.  Something between the debug config editor, and the info the debugger uses to start the session?

    Right - on the face of it, this solves my problem - I now know about this issue and have a fix (this time, at least).  However, that still leaves the question of how/what has actually happened to cause the issue - CCS bug?

    I'll leave this open - in case there's anything else you want to ask or I can help with evidence for, to try to see if this is something in CCS.  After that, I can close this question.

    many thanks

    Alan

  • 0 in reply to Alan Milne
    TI__Expert 8802 points

    Hi Alan,

    Glad it is working now. If our CCS experts have any additional comments I will post them here. I will close the issue for now though. Somehow the .ccxml must've just been corrupted somehow.

  • 0 in reply to Tim Henderson
    Intellectual 285 points

    Hi Tim,

    thanks.  As far as I could see (no expert in its contents), the ccxml did look OK i.e. seemed to be calling up XDS110, so maybe there's another file, produced by CCS along the way to debug, and that went wrong?  As said, I got the same error in CCS12 - having copied the project to keep the original in tact, so obviously whatever has gone wrong also got copied with the project.

    Thanks for your help

    Alan