AM2634-Q1: Core0 and core1 boot process

Part Number: AM2634-Q1
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi experts,

I ask this for my customer.

My customer have two team to develop the project, one is responsible for bootloader that run in core0 and another is responsible for application control that run in core1.

Now they have core1 code ready and don't have core0 project.

And for saving the devleopment time, they want to use core1 project to debug firstly.

So I suggest them use devboot and download this project to core1 directly.

The process is show in below: load the ccxml, connect the core0 but don't program the code to core0 and then connect the core1 and download the project to core1. and then reset the core1 and run

1. Why it need to connect the core0 firstly?

2. Why it needs reset after the download to core1? I aks this because if I don't reset it, it will run into illeage interrupt

3. Why it can't watch the variable refresh?

  • Apologies for the delay,

    My current understanding is that you have to connect to core 0 and then core 1 to get your example to load correctly. 
    Most likely this is caused by a combination of your CCXML and the gel files being used. Most of our base applications run from core 0. A key point is that the cores in use need to be unhalted.

    Are you using a specific board? Like the ControlCard or LaunchPad? 

    Are they using makefiles or CCS+SysConfig?

    Understanding what tools are being used will help me explain what steps need to be taken to resolve this issue.

    For the variable refresh, it looks like the core is halted, preventing you from reading the variables. 

    In addition, here are some good references for multicore setup and usage that can help with your end application:

    I would recommend using a multicore example project (such as ipc_notify_echo) as a starting point, even for your beginning testing.
    Regards,
    Susan
  • Hi Susan,

    Thanks for your reply!

    Nikhil help me also.

    It is because of the ccxml file: in default ccxml, it will init chip when it connects to core0,

    if you want to init chip when it connects to core1, you need to add gel file to CS_DAP, then you can connect to core1 directly.

    BRs

    Shuqing