• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 82 subscribers
  • Views 418 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.

When are Boot Rom IPC Commands active

Rob Barton
Expert 2220 points

Other Parts Discussed in Thread: CONTROLSUITE

In section 3.18 of

It shows various BOOT mode commands.

When are these IPC boot mode commands active, and when do they fall out of scope?

If I am writing an application, do these IPC commands stay available to me?  Or after boot up, does it stop responding to them?

I guess the question is:

1.  At what point do these IPC commands become available in the boot process, and at what point do they no longer apply.  How is this synchronized across the two processors so the set of commands is active on both at the appropriate time.

2.  How do I write my own custom command, and how to remain compatible with the built in BOOT commands so no conflict occurs.

  • 0
    TI__Mastermind 30255 points
    Rob,

    For CPU2 to CPU1 IPC commands, these are only available when CPU1 is in wait boot and IPC is set to be enabled by using the OTP boot configuration word (see section 3.16).

    For CPU1 to CPU2 IPC commands, these are available once CPU1 boots and branches to application. If you look at the simple dual core blinky example in controlSUITE, you'll see the use of the IPC library command "IPCBootCPU2" which is making use of the IPC interrupt commands setup on CPU2. Once the CPU2 application starts running, the PieVectTable is re-inititialized and the IPC boot ROM handler is no longer being used.

    Best Regards
    Chris