MPC5744P bootloader

huangchuo — Mon, 21 Aug 2017 04:13:28 GMT

/* Configure FCCU */
FCCU_SetProtocol(FCCU_BI_STABLE); //set Bi-Stable protocol if not in the SAFE mode

/* Init MODE ENTRY module */
MC_MODE_INIT(); /* (pll_init) Setup the MCU clocks and modes */

xcptn_xmpl (); /* Configure and Eable Interrupts */

dcache_disable();

PIT_Init();

PIT_Setup(0,50000000, 0.005);

MC33908_Init();

DSPI_Init(EEROM_DSPI_NB,MASTER,DSPI_CLK,EEROM_DSPI_BR,0);

if(Get_AppValid())
{
__asm__(" e_lis %r3, 0x0104");
__asm__(" e_ori %r3,%r3,0x0000");
__asm__(" se_mtlr %r3");
__asm__(" se_blr");
}

......

The above code runs in the bootloader main () function.

Get_AppValid () detects valid flags for applications in flash. The flags is stored at flash 0x11C0000. When the application download finished , the flags is set to 0x5555AAAA. The Get_AppValid () function check passes through assembly instructions jump to the application.

The application start address is 0x1040000.

Now after the download finished, bootloader reset, restart, run to the Get_AppValid (), jump into the 0x1040000 operation. As a result, IVOR1 interrupts are generated. Single step debugging to see, the program jumped to the 0x1040000, and running 4 instructions, and then into the ivor1 interrupt.

Hope technical support can help solve. Determines whether or not to change the jump mode, or the chip needs to do relevant settings to modify the machine check function.

topic MPC5744P bootloader in MPC5xxx

MPC5744P bootloader