• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 54 subscribers
  • Views 4202 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS 4.1.1.00014 - strange error message when debugging MSP430F1132

Joerg Quinten
Guru 17650 points
Other Parts Discussed in Thread: MSP430F1132, MSP430F1232, MSP430F2232, MSP430F2274, MSP430F1122, MSP430F1222

Hi,

in my latest project I'm working with an MSP430F1132. Now I'm facing a strange problem when I try to debug my code! An error message shows up before download saying my target setup doesn't match my current target (see below). When I ignore the message downloading and debugging my app works fine.

Can anybody pls tell me what the problem is? I've included the msp430f1132.h and I'm using the default lnk_msp430f1132.cmd. Mounted on the target is a MSP430F1132DW Rev E micro. I'm using MSP-FET430UIF flashed with the latest firmware for download/debugging.

Thanks for answering, rgds
aBUGSworstnightmare

  • 0
    TI__Genius 14520 points

    My guess would be that your projects device selection is out of synch with your target. I.e. your project was created for a different device. You can check it by right clicking on the project and selecting properties. Then select CCS Build category and check what the device variant is set to. You may need to adjust Device Variant setting to match the HW. If you need to switch it, then you will get a migration dialog to convert your project from device to another.

     

    Martin

     

  • 0 in reply to MartinS
    Guru 17650 points

    Hi MartinS,

    thanks for your guess, but this is not the answer! pls see my build settings below:

    I've also made a complete new project, added my files too, tried to download it and it showed up with the same error message. So my guess is, there's a problem with CCS in this case.

    Rgds
    aBUGSworstnightmare 

  • 0 in reply to Joerg Quinten
    TI__Genius 14520 points

    Hi, 

    In your project there should be a file with .ccxml extension. If you have switched devices in the same project (using above project properties page), then you may have more than one. Could you open(double click on the file) .ccxml file that has [Active] annotation beside it and let me know whether it has the same device as the device that is connected? 

    If yes, then could you try clicking on the arrow beside Debug toolbar button, this should open a menu. Towards the bottom there should be a menu called "Debug ...", please click on it, a dialog called "Debug' should appear. On left side there should be a node called "Project Debug Session" there should be some entries below that node. Select them all and delete. They will be re-created when you start debugger next time. This is where custom debugger options are stored (among with CPU used to start debugger), thus when you delete them you may need to re-set debugger options or flash options if you changed them from defaults. 

    Martin

     

     

  • 0 in reply to MartinS
    Guru 17650 points

    Hi Martin,

    I did all the steps from your latest post but the problem wasn't fixed!

    The .ccxml file I'm using is for MSP430F1132. (see screenshot below):

    I also had a look at the source of this file and there's an entry saying partnum="MSP430F12x2/11x2"; what is this used for? I had a look on other .ccxml-files (i.e. MSP430F1232, MSP430F2274 and MSP430F2232) and couldn't find such a statement!

    I the re-opened the .ccxml file from my current project and now it looked different than before!

    So, can anybody tell me what's going on?

    Kind regards
    aBUGSworstnightmare 

  • 0 in reply to Joerg Quinten
    Guru 17650 points

    Hi,

    nobody here who can answer this?

    aBUGSworstnightmare

  • 0 in reply to Joerg Quinten
    TI__Guru**** 168267 points

    Hi,

    I hit the same issue using a similar setup. I worked around this issue by modifying the device XML file <MSP430F1132.xml> inherited by the target configuration file.

    The first line of this file reads:

    <device HW_revision="1.0" XML_version="1.0" description="MSP430F1132" id="MSP430F1132" partnum="MSP430F12x2/F11x2">

    I changed it to

    <device HW_revision="1.0" XML_version="1.0" description="MSP430F1132" id="MSP430F1132" partnum="MSP430F1132">

    And it worked fine on my system.

    This issue affects four Device XML files (located in C:\Program Files (x86)\Texas Instruments\ccsv4\common\targetdb\Devices)

    <MSP430F1122.xml>

    <MSP430F1222.xml>

    <MSP430F1132.xml>

    <MSP430F1232.xml>

    If you want to modify the files yourself, make sure you also delete the target configuration cache files located in the following places:

    file <targetdb.dat> typically located at C:\Program Files\Texas Instruments\ccsv4\common\targetdb
    file <targetdb.cache> typically located at C:\Program Files\Texas Instruments\ccsv4\DebugServer\bin\win32
    cache file located in the same directory as the target configuration file (.ccxml) - typically located in the project directory in the workspace

    I am still investigating the correct contact person to modify the scripts that generate these files, therefore I don't yet have a bug number. I will let you know as soon as I get a closure to this, ok?

    I imagine the presence of the partnum directive in your original configuration was due to an inherited file from a previous CCSv4 version, but I can't tell for sure as I could not generate a similar file here.

    Hope this helps,

    Rafael

     

  • 0 in reply to desouza
    TI__Guru**** 168267 points

    Hi,

    Thank you for reporting this; I filed the bug SDSCM00035879. Please check its status in the SDOWP link in my signature below.

    Please apologize for the inconvenience,

    Rafael

  • 0 in reply to desouza
    Guru 17650 points

    Hi Rafael,

    thanks for your help and support! The Workaround will be fine for me but it's good the have this issue fixed in later editions.

    Rgds
    aBUGSworstnightmare