Part Number: MSP432E401Y
Tool/software: TI-RTOS
Hi,
I'm working on a MSP432E401Y with TI RTOS and the SDK 2.10.00.17. I succesfully tested the aes_example without the RTOS.
In RTOS project it seems that these clock configuration APIs generate problems in debug:
/* Disable clock to CCM0 and reset the module from system control and then
enable the clock. */
MAP_SysCtlPeripheralDisable(SYSCTL_PERIPH_CCM0);
MAP_SysCtlPeripheralReset(SYSCTL_PERIPH_CCM0);
MAP_SysCtlPeripheralEnable(SYSCTL_PERIPH_CCM0);
/* Wait for the peripheral to be ready. */
while(!MAP_SysCtlPeripheralReady(SYSCTL_PERIPH_CCM0))
{
}
I tryed to insert them in startup but nothing change:
var Startup = xdc.useModule('xdc.runtime.Startup');
/*
* Default value is family dependent. For example, Linux systems often only
* support a minimum period of 10000 us and multiples of 10000 us.
* TI platforms have a default of 1000 us.
*/
Clock.tickPeriod = 1000;
/* install a "first function" */
Startup.firstFxns[Startup.firstFxns.length++] = '&AES_Init_First';
any idea ?
thank you,
Tommaso