CCS/TMS320F28388D: CPU2 BOOT from CPU1 Status

Hello

What behavior are you seeing? Is your CPU1 boot mode set correctly via the boot GPIOs? Is your CPU2 application entry address (code_start) at the 0x80000 address?

Put an LED blink in each so you can see if they are reaching their applications.

Best regards

Chris

hello Chris,

Yes i have used a led blinky patter to understand the flow, what I observed is when only single core is selected the controller is getting a reset. 

i.e after executing the statement in CPU1.

Device_bootCPU2(BOOTMODE_BOOT_TO_FLASH_SECTOR0);

Can you let me know why it could  get a reset, any suggestions to debug ?

thanks,

Nagesh 

Hello

Are you disabling the watchdog? This gets enabled coming out of boot and will be disabled when connected via CCS.

Best regards

Chris

Hi Chris,

Yes, the Watchdog is disabled, I tried to simulate the behavior in one of the example code and I could see a similar behavior trying to figure out why it's getting a reset.

The situation is, the output file should be loaded only on CPU1. I have keet different led blinking pattern before booting CPU2 and after booting CPU2.

I am using the example code provided in c28x_dual for F2838xD, i was not able to attach the complete project here hence attaching the updated code for the same.

I have commented on some of the IPC as it was not required here for the example code. and highlighted the new code with BOLD. FLASH is selected.

// FILE:   ipc_ex1_basic_c28x1.c

int gu16ApplicationType = DUAL_CORE;
void main(void)
{
    int i;
    int k = 0;
    // Initialize device clock and peripherals
    Device_init();

    Device_initGPIO();
    GPIO_setPadConfig(DEVICE_GPIO_PIN_LED1, GPIO_PIN_TYPE_STD);
    GPIO_setDirectionMode(DEVICE_GPIO_PIN_LED1, GPIO_DIR_MODE_OUT);

    for(k=0;k<20;k++)
    {
        // Turn on LED
        GPIO_writePin(DEVICE_GPIO_PIN_LED1, 0);
        DEVICE_DELAY_US(100000);
        GPIO_writePin(DEVICE_GPIO_PIN_LED1, 1);
        DEVICE_DELAY_US(100000);
    }
    // Boot CPU2 core
#ifdef _FLASH
    Device_bootCPU2(BOOTMODE_BOOT_TO_FLASH_SECTOR0);
#else
    Device_bootCPU2(BOOTMODE_BOOT_TO_M0RAM);
#endif

    // Clear any IPC flags if set already
    IPC_clearFlagLtoR(IPC_CPU1_L_CPU2_R, IPC_FLAG_ALL);
    if( DUAL_CORE == gu16ApplicationType )
    {
       GPIO_setPadConfig(DEVICE_GPIO_PIN_LED2, GPIO_PIN_TYPE_STD);
       GPIO_setDirectionMode(DEVICE_GPIO_PIN_LED2, GPIO_DIR_MODE_OUT);
       // Configure CPU2 to control the LED GPIO
       GPIO_setMasterCore(DEVICE_GPIO_PIN_LED2, GPIO_CORE_CPU2);
    }
    for(;;)
    {
        // Turn on LED
        GPIO_writePin(DEVICE_GPIO_PIN_LED1, 0);
        DEVICE_DELAY_US(500000);
        GPIO_writePin(DEVICE_GPIO_PIN_LED1, 1);
        DEVICE_DELAY_US(500000);
    }

}

Hello Chris,

I have one more observation from debugging further.

I would like to know under what circumstances the CPU2 can cause a reset on the controller (F28388D) including CPU1.

this happens only when the control card is not connected to CCS.

Secifically it happens after executing "Device_bootCPU2(BOOTMODE_BOOT_TO_FLASH_SECTOR0);" 

Thanks,

Nagesh

Nagesh,

I will try to replicate and get back to you on that by end of day tomorrow.

Currently I can only think of CPU2 having a watchdog reset which triggers an NMI on CPU2. Otherwise CPU2 isn't able to reset the whole device. If CPU1 isn't getting reset, then there is a couple different CPU2 reset sources. Look at the TRM chapter "C28x System Control"->"Resets".

I also recommend after running standalone to reconnect to device with target config that has GEL removed. In the target config, go to the advanced tab, select CPU1, CPU2, etc and clear the path for the GEL. This way when you connect it won't reset the device and then you can load symbols to see where in code it currently is. You can also observe the IPC status register and other registers that can provide more debugging info.

Best regards

Chris

Hello Chris, 

I found out where exactly its getting a reset, I am reusing the function 'void SysCtl_controlCPU2Reset(SysCtl_CoreReset control)' from the example code.

under that 

    if(control != 0x0U)
    {

    }
    else
    {
  
        EALLOW;
        clearvalue = HWREG(DEVCFG_BASE + SYSCTL_O_CPU2RESCTL);
        clearvalue &= ~SYSCTL_CPU2RESCTL_RESET;


        HWREG(DEVCFG_BASE + SYSCTL_O_CPU2RESCTL) = (SYSCTL_REG_KEY &
                SYSCTL_CPU2RESCTL_KEY_M) | clearvalue; // Causing reset after this macro, trying to understand the functionality of this macro, can i replace this 
                                                                                               //will a register

        for(i=10;i>0;i--)
        {
            strGpioDataRegs.GPATOGGLE.bit.GPIO31 = 1;
            DGenerateMicroSecDelay(65535);
            DGenerateMicroSecDelay(65535);
            DGenerateMicroSecDelay(65535);
        }

        EDIS;
    }

thanks

Nagesh

hello, 

Thank you for your analysis. 

I am trying to update the NMI handler as you suggested and using the example code from TI provided in C2000Ware_3_03_00_00_Software

C:\ti\C2000Ware_3_03_00_00_Software\driverlib\f2838x\examples\c28x_dual\nmi

I have updated the nmi_isr to send the CPU2 back to reset as below, but I do not see it to be working as expected.

I have not loaded any application on CPU2, just by booting by CPU2 without an application in it i am expecting nmi interrupt and in that interrupt sending the CPU2 back to reset in CPU1. Can you also check if possible if what I am doing is correct?

void main(void)
{
    Device_init();
    Interrupt_initModule();
    Interrupt_initVectorTable();
    SysCtl_clearAllNMIFlags();
    Interrupt_register(INT_NMI, &nmi_isr);
    SysCtl_enableNMIGlobalInterrupt();
    Interrupt_enable(INT_NMI);
    EINT;
    ERTM;
    Device_bootCPU2(BOOTMODE_BOOT_TO_FLASH_SECTOR0);
    while(1)
    {
        while(nmi_isr_called != 1);
        if(nmiflagstatus != (SYSCTL_NMI_CPU2WDRSN | SYSCTL_NMI_NMIINT))        {            ESTOP0;        }
        nmi_isr_called = 0;
        nmi_isr_count++;   
    }
}

interrupt void nmi_isr(void)
{
    nmi_isr_called = 1;
    unsigned long int counter = 0;
    unsigned long int i = 0;
//Added to observe LED blinky if it enters nmi interrupt, but not observing the LED blinky pattern
    while(counter < 5)
    {
        counter = counter + 1;
        GPIO_togglePin(DEVICE_GPIO_PIN_LED1);
        for(i = 0; i < 100000; i++)
            asm(" RPT #255 || NOP");
    }    

     nmiflagstatus = SysCtl_getNMIFlagStatus();
    nmisdflagstatus = SysCtl_getNMIShadowFlagStatus();

    SysCtl_clearAllNMIFlags();

    Device_bootCPU2(0x00);

}
thanks,
Nagesh