smith84 wrote on Tuesday, May 07, 2013:
I have just double-checked the linker script and all appears well, certainly the memory sizes are correct. (I have used the unmodified EFM32LGxxx series linker file from Energy Micro.)
I am now not certain that all is well when the new timer call is not included after doing some more detailed analysis. At this stage I have commented out the offending module’s Init function so there may be a memory size influence, but there should certainly be no new code running.
I have done some step-by-step debugging to try and understand what is going on during the OS startup through the prvPortStartFirstTask and vPortSVCHandler calls, and would like to ask the following (possibly silly) question:
Should the port.c code initialise the priority of the SVCall Exception? I see that it sets the priority of the PendSV and SysTick (though it probably shouldn’t do SysTick if tickless idle is active), but could not see anything for SVCall and so its priority remains at 0 (highest). Although I guess if my reading is correct it is only used to set up the first task and so would probably not make a difference.