• Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 913 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.

xxyyz CCS

JOHN CARRARA
Intellectual 485 points
Other Parts Discussed in Thread: MSP430G2131, MSP430G2231

Customer has been successful building and programming his chips using CCS 5.1.1

Customer is unsuccessful using CCS 6.0.0

Customer is getting Jtag communication errors.

 

The chips he is using are the MSP430G2131, MSP430G2231

 

  • Guru 192875 points
    Hi John,

    Can you share the error window?

    Regards,
    Gautam
  • in reply to Gautam Iyer
    Intellectual 485 points

    Unresolved symbol _bis_SR_register

    Note: this starts with a single underscore rather than a double underscore.

  • in reply to JOHN CARRARA
    TI__Guru**** 173310 points

    JOHN CARRARA said:
    Unresolved symbol _bis_SR_register

    This sounds like a build error, but in the previous message you said they were getting JTAG communication errors. Are these two separate independent issues?

    For the unresolved symbol error please copy the CCS build console to a text file and attach it here.
    http://processors.wiki.ti.com/index.php/Build_Errors_in_CCS#General_Tips

    If there are also JTAG issues, please post more details about the target board (is it a TI board or custom board) and exact error message, preferably with a screenshot. Does the same board connect with CCS 5.x but not with CCS 6.x?

  • in reply to AartiG
    Intellectual 485 points

    Let's assume it's only a build error and that's why the customer can't program the parts.

    Even the path is confidential. Below is scrubbed.

    There are three errors.

     #10010 errors encountered in linking;"filename.out"not built

    #10234-D unresolved symbols remain

    unresolved symbol _bis_SR_register first referenced in c:\....\workspace_v6_1\....

    Customer has included main.h but I'm wondering if they need a IN430.h for the pre-processor substitutions from _bis... to __bis...

    Or tie the path to the 5.1.1 workspace.

  • in reply to JOHN CARRARA
    TI__Guru**** 171224 points
    Hi,

    The thread below explains a bit about the intrinsic in question (with double underscores).
    e2e.ti.com/.../199558

    Therefore, as suggested by you it seems there was either a compatibility layer on a header file (perhaps to convert from IAR or other compiler) or something changed on the MSP compiler shipped with CCSv5.1.1 and the newest one - I can't find evidence of this last issue, though.

    Searching around on the internet for in430.h brings quite a few hits - thus making it difficult to pinpoint what would be a suitable one.

    Hope this helps,
    Rafael