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

TMS320F28P650DK: dual core booting and debugging

ranjith reddy
Prodigy 130 points
Part Number: TMS320F28P650DK
Other Parts Discussed in Thread: C2000WARE

Tool/software:

Hi TI Experts,

I'm working with the TMS320F28P650D dual-core device and looking debug both cores(CPU1 and CPU2).

My questions are:

  1. what are the necessasary initializations should be done

  2. do i need to externally define any predefined symbols if so what are they
  3. what are the things that i need to done in CPU1 
  4. what are the things that i need to done in CPU2
  5. while debugging does cpu1 need to boot cpu2 or cpu2 directly boots itself
  6. Facing issues while runnig in flash but not facing any issues while running from ram
  7. do i need to do any thing related to boot modes to fun flash on power on. 

Any guidance, documentation links, or example projects would be greatly appreciated.

Thanks in advance!

  • 0
    TI__Mastermind 38830 points

    Hi Ranjith,

    These questions are best answered by running the examples in C2000Ware.  You can start with the led_ex1_blinky example under f28p65x/examples/c28x_dual/led.  This example demonstrates how  memories are allocated to CPU2 from CPU1 and behavior of CPU2 boot (either from RAM of FLASH) as defined in CPU1 as CPU2 cannot boot by itself.  Peripheral setup for clock gating and configuration is done in CPU1 but can be controlled in CPU2.  The led blinky example configures the GPIOs used to drive the LEDs via CPU1 but the toggling can be controlled by CPU2 as defined in CPU1.  Similar configuration assignment and control applies to the different peripherals where CPU1 defines the configuration and control or ownership of the module (by default CPU1 or CPU2 when configured by CPU1).

    Regards,

    Joseph