• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 475 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.

TM4C129x MEM#17 Errata

Aaron Geier
Intellectual 600 points

Hello,

I have a question with regard to the new MEM#17 errata.  I am not familiar with the BOOTCFG register, and don't have any code to explicitly do anything with it.  Do I need to be concerned about this errata

  • 0
    TI__Guru**** 244400 points
    Hello Aaron

    If not using the BOOTCFG register, then you do not need to be concerned about the errata,

    Regards
    Amit
  • 0 in reply to Amit Ashara
    Guru 117855 points

    Amit Ashara said:
    If not using the BOOTCFG register, then you do not need to be concerned about the errata...  

    Thanks for this clarification - appreciated.

    Might you (also) list the most typical "use cases" - for employing the BOOTCFG Register - so that we/others may adequately "gauge" this restriction?      Thanks.

  • 0 in reply to cb1_mobile
    TI__Guru**** 244400 points
    Hello cb1

    Indeed. There are 4 main functions in the BOOTCFG register

    1. Bits 1-0 control the Debug Port. If the value is changed from the default 10 and committed then JTAG debugger access are inhibited for further access.
    2. Bit 4 controls the KEY value for commit operations. Default value of 1 means a Key of 0xA442 while a value of 0 means the user can have a custom key in the FLPEKEY register for any Flash Program/Erase or commit operations
    3. Bits 15-8 are used for BOOT Pin Configuration. Only one Port-Pin can be selected for forcing the device to ROM Boot loader on a Power On /Pad Reset even if there is a valid Application code resides at location 0x0. This allows for OTA updates when a custom boot loader is not required
    4. Bit-31 when 1 means the register is not committed and can be used by the application to decide if the change is temporary or permanent.

    The reserved bits shall be maintained as 1. If any bits is changed from 1 to 0 and committed then only a Debug Unlock Sequence can turn the register back to its POR value.

    Regards
    Amit