Jump to content
43oh

schweini

Members
  • Content Count

    5
  • Joined

  • Last visited

Posts posted by schweini

  1. When you make a new ccs project you need to make sure you select the correct chip you are using, such as the 2211 or 2231. Also, you must realize that the 2211 doesn't have a built in thermometer, so using the 2231 demo code on it won't work right.

     

    yea - the temperature program flashed and runs perfectly on the 2231 now, but that isn't really my issue.

     

    My problem is, that if i double click that ccxml thingy on the left, and change the target to the chip i am actually using, CCS refuses to see the chip. If I leave it exactly like it is right in the example project (which has a 'wrong' chip selected) it detects a target mismatch, but at least sees the chip, and then flashes it.

     

    But it just seems wrong using the wrong configuration, even if it works. But any other target makes CCS go blind. On two seperate PCs.

     

    hmmm....come to think of it - maybe it's not the bad configuration per se, but the clciking on the 'save' button that screws things up. because if i change it back to the initial, wrong selection, CCS still refuses to detect the chip. I will try to change the XML by hand, to see what happens.

  2. Hi, again, and thanks for the suggestions!

     

    I was following the instructions at:

    http://www.msp430launchpad.com/2010/07/ ... arted.html

     

    which seem to be straight-forward enough.

    Yet, i got the error I described in my last post - but if I simply use the example project, without ANY modifications, and click on 'debug', after a while i get the error:

    -------------------

    MSP430: Error connecting to the target: The target setup (F20x2_G2x2x_G2x3x) does not match the actual target type (F20x1_G2x0x_G2x1x)

    -------------------

    ....which i then 'ignore', and CCS happily flashes my MSP430. When I click on 'run', the leds start blinking again. The program doesn't seem to run, though (i guess because of that target mismatch).

    If I use exactly the same project, and simply change the target from the pre-defined 'MSP430F2012' to the chip i am actually using (the 2211, in this case but i also tried it with the 2231), i get the message mentioned in the other comment, again, an nothing works at all.

     

    The EXACT same thing happens on another computer with a different USB cable.

     

    I did update the firmware of the launchpad before even starting to try all this, so maybe it has something to do with that.

     

    Anyone?

  3. I have had the drivers installed (although i do think TI is wrong to include them in those gigantic downloads of IVR and CCS!), so that can't be the issue in this case.

     

    The temperature demo program was working ok before - serial communication and all. Although that program isnt there anymore since my (failed?) IVR WorkBench flash. This flash is what tells me that the LP itself should be working fine, since the IVR program did detect the MSP, and said things like 'erasing memory....'. It's just that I cant get CCS to do this, and all tutorial are CCS based.

     

     

    M.

  4. Hi!

     

    I can't get the flashing/downloading/running part to work. I always

    get the error message:

     

    ------------------------

    Failed to load program MSP-EXP430G2-Launchpad.out' on any of the

    targets.

     

    Reason:

     

    The target 'TI MSP430 USB1/MSP430' could not be found.

    ------------------------

     

    So I (randomly) fiddled around with the IAR WorbBench, and (although i

    did get some error warnings about hardware mismatches), it did seem to

    do something, and at the very least deleted the temperature-sensing

    demo program (although the blinking program isnt working, now). Thus,

    i'd guess that the Launchpad board is communicating in some form with

    the MSP.

     

    Any pointers on how to get this (or anything at all!) to work with

    CCS? I really want to climb this admittedly steep learning curve, but

    can't even get over the first hurdle! :(

     

    Is there a 'raw' way (CLI) of flashing the chip? Just to test whether

    maybe my eclipse config is screwed up, or to check whether the board

    is fried?

×
×
  • Create New...