• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 1195 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.

AWR1642: Boot Process Questions

Barend Ungrodt
Intellectual 1420 points
Part Number: AWR1642
Other Parts Discussed in Thread: IWR1642BOOST

Hi AWR Team,

I have a customer asking a couple questions regarding the boot process. He's read through part of the TRM(p.189), and I've shared the boot-flow document, but there are a few follow up questions.

  • Can the MSS_TCMA_ROM memory space be programmed? The customer is looking know if the boot loader algorithm can be modified, and if there is source code we can share
  • Is ROM eclipsing available for DSS?
  • The datasheet states that the Pre-Eclipse view is in effect after boot. Does this include a warm boot as well as power cycling?
  • If the bootloader code can be re-written, can we define whatever trigger we choose to reload an image from flash/download a new image, thus eliminating the SOP2:0 functionality?

Looking forward to your reply.

Thanks,
Barend

  • 0
    TI__Guru*** 149204 points
    Hi

    Will get back to you on Monday.

    Thank you
    Cesar
  • 0
    TI__Mastermind 21025 points

    Hi Barend, here are the answers I have so far:

    • Can the MSS_TCMA_ROM memory space be programmed? The customer is looking know if the boot loader algorithm can be modified, and if there is source code we can share

    [dave] No, the ROM is not modifiable. Boot loader source code is not available.

    • Is ROM eclipsing available for DSS?

    [dave] No, ROM is in the MSS subsystem, not the DSS (see Figure 2 of SWRA551)

    • The datasheet states that the Pre-Eclipse view is in effect after boot. Does this include a warm boot as well as power cycling?

    [dave] As discussed in this thread: https://e2e.ti.com/support/sensor/mmwave_sensors/f/1023/t/596486?tisearch=e2e-sitesearch&keymatch=awr1642%20bootloader a warm reset resets all logic and restarts the bootloader. So, yes.

    • If the bootloader code can be re-written, can we define whatever trigger we choose to reload an image from flash/download a new image, thus eliminating the SOP2:0 functionality?

    [dave] Not sure what the goal is here. If the customer is looking for additional functionality, most likely an MSS image can be flashed (or downloaded) that performs it.

     

  • 0 in reply to db_woodall
    TI__Intellectual 1420 points
    Hi Dave,

    They want to understand the flashing process on the IWR1642BOOST. The thought is that it has a lot of the functionality that they will have to incorporate into the bootloader for their project.

    In addition to the above questions, do you have any insight on the below?

    • When flashing through the JTAG is the MSS_TCMA_ROM bootloader program accessed to write the binaries to the external serial flash?
    • Is the debugger fetched from the external serial flash similar to a downloaded image?

    Thanks again!
    Barend
  • 0 in reply to Barend Ungrodt
    TI__Mastermind 21025 points
    • When flashing through the JTAG is the MSS_TCMA_ROM bootloader program accessed to write the binaries to the external serial flash?

    [dave] According to Table 1 of SWRA551, the bootloader is spinning in an infinite loop while binaries are being flashed.

    • Is the debugger fetched from the external serial flash similar to a downloaded image?

    [dave] No, no part of the debugger runs on the device. For regular breakpoints, the assembly instruction is replaced at the requested location. For most debugging activities (stepping, breakpoints, etc) the core is placed in an emulation mode.