- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Hi,
I'm having a very weird problem here, I'll try to explain as detailed as possible:
I'm developing quite a big application using both cores of the Concerto F28M35H52C1 (using the DIMM 100 USB dock) and everything is working fine until I power down my board for the whole night.
I mean, I can flash both cores, run both cores with the JTAG, I can power off the board flip the dip-switches on it and boot again without the JTAG, but when I go home and power everything off for the night and come back on the other day C28 does not boot properly. So it seems. Let me go through the boot up of my code.
M3 starts and setups the clock
// Sets up PLL, M3 running at 100MHz and C28 running at 100MHz
SysCtlClockConfigSet(SYSCTL_USE_PLL | (SYSCTL_SPLLIMULT_M & 0xA) | SYSCTL_SYSDIV_1 | SYSCTL_M3SSDIV_1 | SYSCTL_XCLKDIV_4);
Initialises all peripherals (SysCtlPeripheralEnable) setup the GPIO pins and its initial values, setups the UART port, setup the I2C bus, read the EEPROM, copy time critical code to RAM, call FlashInit(), setup the shared RAM by giving C28 access to its writable areas, give C28 GPIO access
// give GPIO access to C28
GPIOPinConfigureCoreSelect(GPIO_PORTA_BASE, (GPIO_PIN_2 | GPIO_PIN_3 | GPIO_PIN_4 | GPIO_PIN_5), GPIO_PIN_C_CORE_SELECT); // PWM pins
GPIOPinConfigureCoreSelect(GPIO_PORTC_BASE, GPIO_PIN_6, GPIO_PIN_C_CORE_SELECT); // LED pin
ask for C28 to boot and WAIT FOR IT TO BOOT:
// Send boot command to allow the C28 application to begin execution
IPCMtoCBootControlSystem(CBROM_MTOC_BOOTMODE_BOOT_FROM_FLASH);
// Lock M3 until C28 is ready
while (!IPCCtoMFlagBusy(IPC_FLAG17)) { }
IPCCtoMFlagAcknowledge(IPC_FLAG17);
then, and only then, it setups the Timed interruptions and the ethernet!
On the 500ms timed interruption it's simply blinking one of the LEDs (M3_LED) and sending some update info to the LCD screen via UART1.
---------------------------------------------------------------------------------------------------------------------------------------------
Now through the C28 boot code it (among other stuff) make C28_LED pin an output
EALLOW;
GpioG1CtrlRegs.GPCDIR.bit.GPIO70 = 1; // make it an output pin
EDIS;
initialise and start the 500ms timed interruption, turn on C28_LED, tells M3 that it's all setup and ready to go:
// Flag to M3 that the variables are ready in MSG RAM
IPCCtoMFlagSet(IPC_FLAG17);
and at the end enables global and higher priority real-time debug events.
---------------------------------------------------------------------------------------------------------------------------------------------
So the problem is:
with JTAG connected, flashing the code on both cores, resetting the cores, resetting the system, restart C28 (it goes to run), restart M3 (it goes to int main() ), run M3, M3 starts C28 and it stops on int main(), M3 stops waiting for C28, I start C28 core, it flags for M3 and both execute as expected. Blinking LEDs, updating LCD info, I can send ethernet commands that write to the eeprom and triggers an IPC on C28 to read the new data from the shared RAM... all working! On that part the control card switches are: SW1 and SW3 all up (closer to the ethernet connector).
without the JTAG: the above was running and I power off the board on the USB switch and remove the mini-USB from the side and flip SW1 all down (boot from flash) and SW3-pin1 down (no JTAG). I power the board on again and I see everything is working just as before. The board boots, both LEDs blinking, info on the LCD being updated, ethernet commands work. Even thou I can't connect the JTAG in this mode to see what C28 is doing, because both LEDs are blinking I'm assuming that C28 boot properly, initiated the timers and flagged M3 to run.
the next day: same setup from above, didn't change not even one switch, didn't flash any other code, didn't touch it. Turn off my PC, go home, have a night of sleep, the next day come to work again and..... M3_LED blinks, LCD info updated, ethernet commands apparently working (because I can't connect JTAG I can't confirm that it's doing what is supposed to) but C28_LED is not blinking.
And that makes no sense, if C28 didn't boot, it wouldn't allow M3 to boot neither. But M3 seems to be booting and C28 does not. On the other hand, even thou M3 seems to be booting fine, I tried send ethernet commands that would write the EEPROM, but it seems that it's not writing anything at all.
So it seems that after long power down the board is booting up to some weird limbo state that some stuff works and some doesn't.
Attached are my 2 Linker files which are copies from the generic_flash_wshared_M3 and generic_flash_wshared_C28;
