• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 333 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.

CC1310: ROM vs CC1312

Nicholas Carley
Genius 9975 points
Part Number: CC1310
Other Parts Discussed in Thread: CC1312R

Hello,

The CC1312 datasheet specifies 256kB of ROM in the CC1312 but no mention of the amount in the CC1310 datasheet.

  • How much ROM is in the CC1310?
  • If a customer migrates from CC1310 to CC1312 do they need to be aware of any changes in relations to the ROM?
  • Did we move more of the code from the SDK into ROM so that it no longer needs to be included in a customer's application FW builds? 

Thanks,
Nick

  • 0
    TI__Guru**** 317180 points

    The ROM provides preprogrammed, embedded TI-RTOS kernel and Driverlib. The ROM also contains a bootloader that can be used to reprogram the device using SPI or UART.

    If we find out that an function have bugs and/ or need different functionality we can patch the ROM code and run from flash instead. On the CC1310 we currently have more patches than on CC1312R since some of the bugs where fixed in the CC1312R ROM code. But this is details a user does not have to worry about. The important detail is to use the overrides provided in SmartRF Studio to ensure that the code is run from the correct memory. 

    For migration: The application code is copy/ paste from CC1310 to CC1312R. Use the correct overrides and a customer doesn't need to know what is stored in ROM or not.