• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 78 subscribers
  • Views 388 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.

target type identification in the C code

Antoine ROBINET
Prodigy 50 points

hello,

I have searched information on MSP430 target type identification in the forum but I can't find what I need:

http://e2e.ti.com/support/microcontrollers/msp430/f/166/p/206507/732240.aspx#732240

http://e2e.ti.com/support/microcontrollers/msp430/f/166/p/87094/300954.aspx#300954

I would like to identify my target in my code to be able to have one version of the code running on several target and PCB.

is it possible to identify the target? (for me, it is between F2619 and F2618).

I checked the memory on 0x0FF0 zone like explained on several topics, I have exactly the same value for both target type. and the code is not explained.

the FET debugger is able to know which target is present  so it should be possible to it also in the code.

thanks for your help.

  • 0
    Guru 33653 points

    Antoine ROBINET said:

    is it possible to identify the target? (for me, it is between F2619 and F2618).

    I checked the memory on 0x0FF0 zone like explained on several topics, I have exactly the same value for both target type. and the code is not explained.

    the FET debugger is able to know which target is present  so it should be possible to it also in the code.

    TI FET is open source, so you can check how it is done there (http://processors.wiki.ti.com/index.php/MSPDS_Open_Source_Package).

    F2618/F2619 have different flash / RAM size, and probably with some write / read can be recognized target device.

  • 0 in reply to zrno soli
    Prodigy 50 points

    hello

    thanks for this advice, I'll check on the FET code, but it can be a little hard to find!

    I am very surprised  there are no applications notes on how to identifiy the target on the texas documentations.

    I can imagine many applications where knowing the target is essential, even revision of the same chip may be an issue.

    There should be a simple way to do it!

**Attention** This is a public forum