|
|
FreeRTOS Interactive
|
Hi,
I have been woriking on this port for the EXP430F5529 Launchpad using the GCC toolchain now included in Code Composer Studio v6 (No size limit).
Its a very basic project with just two task implementing a Led blink and a Serial Port Echo for the Application UART of the Board.
I have only tested the large memory model.
I upload it here, just in case someone finds it useful,
Regards,
Jose
Update 30/11/2014 FreeRTOS v8.1.2 and CCS with GCC v 4.9.1
New version with some problems corrected and inproved efficiency. Please note that MSP430X large memory model is experimental in GCC. We have found some problems when exiting low power modes from a ISR in this memory model (and GCC 4.8.0 ). We have added some workarrounds to avoid them.
I forgot to add the workarrounds to the serial port ISR. I upload a new version including them here. Sorry.
Hi Jose - I'm having a terrible time with GCC for MSP430 from TI (and using the FreeRTOS port).
Can you help with any of the problems I've seen?
See the TI support forum: http://e2e.ti.com/support/microcontrollers/msp430/f/166/t/361064.aspx
Thanks!
Best Regards, Dave
HI,
Are you using our port or one of your own. If using ours, please note it have been tested mainly for the large memory model, so you have to add -mlarge as flag in the "miscellaneous" compiler options of the project. Also, you should define GCC_MSP430X as symbol.
I have seen that in your build linker is complaining about undefined symbol "vApplicationSetupTimerInterrupt". Please find that function on our main.c and add it to your project (it setups the timer that provides the RTOS tick).
Regarding your problems with Flash usage, it is true, GCC for MSP430X and large memory model is still experimental, and have some problems. One of them is that it does not deal properly with the Flash Memory gap in the 430X architecture (i. e. the space reserved for the interrupt vectors). Also, we have found that gcc does not calculate properly the stack frame for interrupts routines when using the large memory model (i.e. it get confused by the PC+SR compact stacking in the 430X interrupts) , resulting in intrinsics like __bic_SR_register_on_exit (necesary to exit low power) catastrophicaly modifying the PC instead of the SR (we include a workarround for this in our example, please see lines 209 and 213 in file serial.c of our last example project).
If you want to place functions beyond the first 64K of flash, you have to add this to the linker file:
.far_rom :
{
. = ALIGN(2);
PROVIDE (_start = .);
KEEP (*(SORT(.crt_*)))
*(.lowtext .text .stub .text.* .gnu.linkonce.t.* .text:*)
KEEP (*(.text.*personality*))
/* .gnu.warning sections are handled specially by elf32.em. */
*(.gnu.warning)
*(.interp .hash .dynsym .dynstr .gnu.version*)
PROVIDE (__etext = .);
PROVIDE (_etext = .);
PROVIDE (etext = .);
. = ALIGN(2);
KEEP (*(.init))
KEEP (*(.fini))
KEEP (*(.tm_clone_table))
} > FAR_ROM
And for thoes functions you want to send to the far ron region, you have to add this: "__attribute__ ((section(".far_rom"))) " (see the function initPort in hal.c in our example, this was the one we used to test this). Also note this only works for the large memory model, so you have to add the "-mlarge" flag as commented before.
I will leave some more comments to your post on the TI forum.
Regards,
Jose