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

ROM_ or not to ROM_?

Nicolas Göddel
Intellectual 795 points

Hi there,

I want to know the differences between ROM_ functions their equivalent without ROM_. What are the differences? At the moment there seems to be no difference at all. Both variations are working as expected.

Thank you!

  • 0
    Guru 20670 points

    Both should do the same thing. The difference is that normally you program the TivaWare function into the flash and then call them in the code.

    Tiva MCUs come witht the TivaWare in the ROM. If you use ROM_ it just calls them from the ROM. It should be a bit faster also to call functions from the ROM

    Just to add more questions, you know that there is also MAP_?  I don't quite remember this one well but i think it does the same as ROM, but if there is a error it uses the functions uploaded into the FLASH. 

  • 0 in reply to Luis Afonso
    TI__Guru**** 244450 points

    Hello user1597705,

    Thanks Luis. One important information on the MAP_ as mentioned by Luis is that if there is an issue with the ROM_ version of the API, the next TivaWare release may deprecate it, and thus the Flash version will be used allowing for a seamless transition between working and non-working codes. This was the case on the TM4C129 Rev-1 device which was then fixed on Rev-2 device.

    Regards

    Amit