TI LaunchPad 120XL BSP issue.

Karel Gardas karel.gardas at centrum.cz
Sun Aug 11 18:42:12 UTC 2013


Hello,

I'm adopting LM369xx BSP to work on LM4F120XL Lanchpad board. The board 
does have Cortex-M4F CPU with 256 kB flash, 32 kB RAM and 2 kB EEPROM. 
I've successfully run RTEMS hello world on it already so now I'm on 
ticker.exe hacking. I'm debugging it since it always fails with 
following backtrace:

(gdb) where
#0  _Workspace_Handler_initialization (areas=0x200010c8, area_count=1, 
extend=0x0 <bsp_start_vector_table_begin>) at 
/export/home/karel/vcs/rtems/c/src/../../cpukit/score/src/wkspace.c:89
#1  0x00001180 in bsp_work_area_initialize_default 
(area_begin=0x20002938, area_size=22216) at 
../../../../../.././lm4f120/lib/include/bsp/bootcard.h:176
#2  0x000011d0 in bsp_work_area_initialize () at 
/export/home/karel/vcs/rtems/c/src/lib/libbsp/arm/lm3s69xx/../../shared/bspgetworkarea.c:57
#3  0x00001122 in boot_card (cmdline=0x0 <bsp_start_vector_table_begin>) 
at 
/export/home/karel/vcs/rtems/c/src/lib/libbsp/arm/lm3s69xx/../../shared/bootcard.c:101
#4  0x00000116 in bsp_start_hook_0_done () at 
/export/home/karel/vcs/rtems/c/src/lib/libbsp/arm/lm3s69xx/../shared/start/start.S:311
#5  0x00000116 in bsp_start_hook_0_done () at 
/export/home/karel/vcs/rtems/c/src/lib/libbsp/arm/lm3s69xx/../shared/start/start.S:311
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)


I don't know workspace manager at all so I'm curious what's so big 
problem that there is probably some remaining unallocated RAM? I.e. 
remaining is > 0 ? At least I hope I interpret this well...

Thanks!
Karel

PS: I've configured rtems with --enable-posix --enable-samples 
--disable-itron --target=arm-rtemseabi --disable-networking 
--enable-rtemsbsp=lm4f120 -- and I'm curious if 32 kB RAM is not enough 
for POSIX?

PPS: I'm using RTEMS HEAD as of Friday last week and of course one I get 
this working I'll submit my changes for inclusion as the TI LaunchPad is 
really nice and cheap board to experiment with RTEMS.

PPPS: linkcmds.lm4f120 looks:

/**
  * @file
  *
  * @brief Memory map.
  */

MEMORY {
	RAM_INT (AIW) : ORIGIN = 0x20000000, LENGTH = 32K
	ROM_INT (RX)  : ORIGIN = 0x00000000, LENGTH = 256K
}

REGION_ALIAS ("REGION_START", ROM_INT);
REGION_ALIAS ("REGION_VECTOR", RAM_INT);
REGION_ALIAS ("REGION_TEXT", ROM_INT);
REGION_ALIAS ("REGION_TEXT_LOAD", ROM_INT);
REGION_ALIAS ("REGION_RODATA", ROM_INT);
REGION_ALIAS ("REGION_RODATA_LOAD", ROM_INT);
REGION_ALIAS ("REGION_DATA", RAM_INT);
REGION_ALIAS ("REGION_DATA_LOAD", ROM_INT);
REGION_ALIAS ("REGION_FAST_TEXT", RAM_INT);
REGION_ALIAS ("REGION_FAST_TEXT_LOAD", ROM_INT);
REGION_ALIAS ("REGION_FAST_DATA", RAM_INT);
REGION_ALIAS ("REGION_FAST_DATA_LOAD", ROM_INT);
REGION_ALIAS ("REGION_BSS", RAM_INT);
REGION_ALIAS ("REGION_WORK", RAM_INT);
REGION_ALIAS ("REGION_STACK", RAM_INT);

INCLUDE linkcmds.armv7m




More information about the devel mailing list