Problem with call stack CCS 5.3

iluvator

Other Parts Discussed in Thread: MSP430F6736, MSP430F5528

Hello
I have problem with call stack tree when my code is located above 64k address. I don't see call stack tree, current function:

When code is located <64k everything is OK:

This is my project settings:
Compiler
-vmspx --abi=eabi --code_model=large --data_model=small -Ooff --opt_for_speed=0 -g --include_path="C:/TI/ccsv5/ccs_base/msp430/include" --include_path="C:/__Projekty/MacR6/MacR6_Program" --include_path="C:/__Projekty/MacR6/MacR6_Program/inc" --include_path="C:/TI/ccsv5/tools/compiler/msp430_4.1.2/include" --gcc --define=__MSP430F6736__ --diag_warning=225 --display_error_number --silicon_errata=CPU21 --silicon_errata=CPU22 --silicon_errata=CPU40 --printf_support=nofloat

Linker
-vmspx --abi=eabi --code_model=large --data_model=small -Ooff --opt_for_speed=0 -g --gcc --define=__MSP430F6736__ --diag_warning=225 --display_error_number --silicon_errata=CPU21 --silicon_errata=CPU22 --silicon_errata=CPU40 --printf_support=nofloat -z --stack_size=200 -m"MacR6_Program.map" --heap_size=0 --use_hw_mpy=F5 -i"C:/TI/ccsv5/ccs_base/msp430/include" -i"C:/__Projekty/MacR6/MacR6_Program" -i"C:/__Projekty/MacR6/MacR6_Program/src" -i"C:/__Projekty/MacR6/MacR6_Program/inc" -i"C:/TI/ccsv5/tools/compiler/msp430_4.1.2/lib" -i"C:/TI/ccsv5/tools/compiler/msp430_4.1.2/include" --reread_libs --display_error_number --rom_model

I use MSP-FET430UIF firmware 3.02.05.004.

Is there any solution to show all call stack?

over 12 years ago

0 Chester Gillon over 12 years ago

Guru 92251 points

I have repeated the problem on a MSP430F5528 with CCS 5.4.0.00091, MSP430.dll v3.3.0.6 and MSP-FET430UIF v1.4a.

What seems to be happening is the address of the currently executing function is correctly handled as 20 bits, but the address of the calling function is truncated to 16 bits and thus the callstack is truncated. e.g. in the following example func_a should be shown as being called from main at main.c:34 0x010838:

Howewver, the return address is truncated to 0x000838 which means the return address can't be resolved and the call stack stops.

I guess the error is in how CCS traces the call stack in memory. To get the call stack correct does CCS need to enhanced to detect if the currently executing function was called with either CALL (a 16 bit return address on the stack) or CALLA (a 20 bit return address on the stack)?