• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 80 subscribers
  • Views 448 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:

RTOS/MSP432E401Y: Question about usb.c

RTOS/MSP432E401Y: How to disable calls to ROM Driverlib implementation

Michael Cress
Expert 1455 points

Part Number: MSP432E401Y

Tool/software: TI-RTOS

Greetings:

I see that there is a header file rom_map.h that maps certain calls to the device ROM rather than the actual implementation. Is there a way to globally unmap these calls, or do I have to comment out all pertinent #define lines individually from rom.h?

Thank you,

Michael Cress

  • 0
    Expert 1455 points
    For now, I have just added a preprocessor conditional compile flag around the macros defined in rom.h to prevent them from being included in the build as defined by rom_map.h.
  • 0
    TI__Expert 8510 points
    Actually, it's simpler than that. If you always want the flash version of the driverlib API code, then simply drop the MAP_ from the name when using those APIs. The purpose of the rom_map.h file is to allow us to use the ROM version whenever possible, but also be able to update selected APIs when needed.
    -Bob L.

**Attention** This is a public forum