• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 440 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.

CCS/MSP430F5529: Porting an 8051 C program to MSP430 pin names come from?

Stephan K Sagmiller
Prodigy 240 points
Part Number: MSP430F5529

Tool/software: Code Composer Studio

Hello,

I've a project started for the EXPMSP430F5529LP board and have run the examples perfect first time, Thanks.  I've now copied a project written in C originally done for an 8051 part.  First task is changing all the pin definitions to those in the MSP430.H header file.  Where can I find the documentation that describes how to use the header file naming convention?

Oh, Boss says I need this completed today.  Would you verify that the naming given in the msp430F5529 datasheet for signal definitions and in the FIG 4-1 are those used in the .H file? 

Have any suggestions for making the changes?  Perhaps a conversion header file??

Thanks

Stephan

  • 0
    TI__Mastermind 29105 points

    Hey Stephan,

    I'm not sure how complex the firmware you are porting is, but I wouldn't be surprised if the porting effort is more than just an afternoon.

    There are 2 main ways to reference the pins and registers in the MSP430F5529. You can address them at a register level or using TI's Driver Library.

    Register Level:
    This is basic #defines pointing to the different registers and bit masks. Naming should be very similar to those listed in the datasheet, but may not be identical. Register level example software for all the different peripherals can be found here: dev.ti.com/.../

    All the register names are defined in msp430f5529.h. This will be included in your CCS example project under ${CCS_BASE_ROOT]/msp430/include.

    Driver Lib:
    This is a more abstracted library with powerful functions to set up and operate the peripherals. You give up a bit of direct control, for higher levels of readability and useability.

    The API programmer's Guide defines all the functions and parameters available for each peripheral. All the Driverlib examples can be found here: dev.ti.com/.../


    Regards,
    JD

  • 0
    Guru 26200 points
    Hello,
    is your project related to digital I/O pin functions or other resources like timers, dma channels, uarts, etc.?