• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 79 subscribers
  • Views 447 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.

Original question:

CCS/MSP430FR2512: ROM DriverLib access

CCS/MSP430FR2512: ROM Driver Library Routines

Dick Laine1
Prodigy 130 points

Part Number: MSP430FR2512
Other Parts Discussed in Thread: MSP430WARE, MSP430FR2633, MSP430FR2522

Tool/software: Code Composer Studio

Hi

I would like to know precisely which MSP430Ware v3.80.07.00 Driverlib routines are present in ROM in the MSP430FR2512 processor.

Examining the rom_driverlib header file for the FR2512, which directs to rom_driverlib_fr253x_fr263x.h, it would appear that the only routines in ROM are those related to the eUSCI_A and eUSCI_B serial modules.

I cannot believe that 12K of ROM has only this handful of routines.  Why USCI serial routines and not system, clock and power routines?   In any case my understand is that all the CapTIvate routines are in there.

Where can I find a comprehensive list of what is present in the ROM?  There seems to be a total lack of information available on this subject.

Regards

Dick

  • 0
    TI__Guru 71216 points

    Hi Dick,

    The available driverlib ROM functions in the MSP430F2512 are listed in the rom_driverlib_fr253x_fr263x.h.

    The MSP430FR2512 has the same ROM as MSP430FR2522 and MSP430FR2633 family.

    The reason why only USCI modules are in ROM and not other driverlib functions is the Captivate Library uses these primarily for communication with the Captivate design center during development, although there is no reason why the end application could not use them for communication with a host MCU.

    Also, when this family of devices was developed, to keep the cost low, only 12K of ROM was determined to be needed at that time.

    10K of ROM is the CapTIvate Capacitive library function calls.  The remaining 2k is the driverlib functions.

    Does this help answer your questions?

  • 0 in reply to Dennis Lehman
    Prodigy 130 points

    Hi Dennis

    That's fine.  Basically the ROM is just there for CapTIvate, and that was the design intention.  Anyone who wants to use the CapTIvate libraries would clearly want to do so through the Design Center. 

    In that context, it all makes sense.  But the rom_driverlib routines have been written in a generic way, to allow for the next generation of devices with a 64K rom which will hit the shops for Christmas next year!  :-)

    Regards

    Dick

**Attention** This is a public forum