• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 653 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP430FR6989: Segmentation fault while compiling FreeRTOS Msp430FR5969 demo with TI/msp430-gcc

Fabian Hof
Prodigy 20 points
Part Number: MSP430FR6989
Other Parts Discussed in Thread: MSP430FR5969, MSP430F449

Hi,
I am trying to get FreeRTOS working for my development board MSP430FR6989.
As a starting point, I downloaded the latest CCS (11.1.0.00011) and the latest FreeRTOS code from GitHub (1ce4d784c).

I started by loading the demo (FreeRTOS/Demo/MSP430X_MSP430FR5969_LaunchPad_IAR_CCS) into CCS.

The first problem is that we have to change ParTest.h into partest.h in main.c.

Following that, compilation still fails with the following error:

Fullscreen
1
2
3
4
5
6
7
8
Building file: “/home/fhof/FreeRTOS/FreeRTOS/Source/portable/MemMang/heap_4.c”
Invoking: MSP430 Compiler
"/home/fhof/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/bin/cl430" -vmspx --data_model=large -O0 --opt_for_speed=1 --use_hw_mpy=F5 --include_path="/home/fhof/ti/ccs1110/ccs/ccs_base/msp430/include" --include_path="/home/fhof/FreeRTOS/FreeRTOS/Demo/MSP430X_MSP430FR5969_LaunchPad_IAR_CCS" --include_path="/home/fhof/FreeRTOS/FreeRTOS/Source/include" --include_path="/home/fhof/FreeRTOS/FreeRTOS/Source/portable/CCS/MSP430X" --include_path="/home/fhof/FreeRTOS/FreeRTOS-Plus/Source/FreeRTOS-Plus-CLI" --include_path="/home/fhof/FreeRTOS/FreeRTOS/Demo/Common/include" --include_path="/home/fhof/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include" --include_path="/home/fhof/FreeRTOS/FreeRTOS/Demo/MSP430X_MSP430FR5969_LaunchPad_IAR_CCS/driverlib/MSP430FR5xx_6xx" --define=__MSP430FR5969__ -g --c11 --printf_support=minimal --diag_warning=225 --diag_wrap=off --display_error_number --abi=eabi --silicon_errata=CPU21 --silicon_errata=CPU22 --silicon_errata=CPU40 --preproc_with_compile --preproc_dependency="FreeRTOS_Source/portable/MemMang/heap_4.d_raw" --obj_directory="FreeRTOS_Source/portable/MemMang" "/home/fhof/FreeRTOS/FreeRTOS/Source/portable/MemMang/heap_4.c"
FreeRTOS_Source/portable/MemMang/subdir_rules.mk:7: recipe for target 'FreeRTOS_Source/portable/MemMang/heap_4.obj' failed
abnormal termination of /home/fhof/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/bin/cg430
Segmentation fault (core dumped)
gmake: *** [FreeRTOS_Source/portable/MemMang/heap_4.obj] Error 139
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

The segmentation fault occurs with TI v21.6.0-lts and msp430-gcc v9.3.1.11.

I am on 5.11.0-46-generic #51~20.04.1-Ubuntu if that matters.

Any other advice would be appreciated.
  • 0
    Guru 22825 points

    My experience with FreeRTOS is a bit old (2015) but I don't recall any particular problems.

    There isn't a lot to go on in the error message to tell you where it puked. It does seem to have been working on heap_4.c so that is the first place to look. And at the FreeRTOSConfig.h to make sure it looks reasonable.

  • 0 in reply to David Schultz
    TI__Guru 68011 points

    Hi David,

    Unfortunately, I have not been able to track down anyone that can assist with this issue.  What is your status?

  • 0
    Guru 92251 points

    Since the compiler is crashing, can you try to follow How to Submit a Compiler Test Case

    However, since you reported that the segmentation fault occurs with both TI v21.6.0-lts and msp430-gcc v9.3.1.11 perhaps the cause of the segmentation fault isn't in the compiler.

  • 0 in reply to Chester Gillon
    Guru 22825 points

    Like I said, it has been a while since I downloaded FreeRTOS. So I looked and found this note on the latest version: "The CrossWorks demo has not yet been updated to use CrossWorks V2.0 or later. The GCC demo has not yet been updated to use the latest MSPGCC compiler version."

    The download is large and I have little use for it since what I have works. But I took a look. It still only has low level support for the MSP430F449. (FreeRTOS/Source/portable/GCC/MSP430F449) The file port.c which has the low level task save/ restore code doesn't have any clue about CPUX. You will want to at least use pushm/pullm. For example:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    #ifdef __MSP430_HAS_MSP430XV2_CPU__
    #define portSAVE_CONTEXT() \
    asm volatile ( \
    "pushm #12,r15 \n\t" \
    "mov.w usCriticalNesting, r14 \n\t" \
    "push r14 \n\t" \
    "mov.w pxCurrentTCB, r12 \n\t" \
    "mov.w r1, @r12 \n\t" \
    );
    #else
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to David Schultz
    Guru 22825 points

    I poked around some more and it appears that by latest version it means it hasn't been updated since before TI took over the mspgcc project.

    I also found my first stab at using it by compiling a demo. There appear to be fewer GCC based demo projects now. I compiled again using "make -B" to make sure it compiled everything and other than a lot of NOP needed warnings, it completed just fine.

    The code doesn't use the __eint() and __dint() functions but instead uses asm(" DINT"). One of the things that tells me it hasn't been updated in a long time.

    Oh, the demo makefiles place the objects for the RTOS code within the RTOS directory. Since these depend to some extent on specific project settings (FreeRTOSConfig.h), that is a bad place for them. So keep that in mind if you use multiple targets and use "make -B" to force recompilation of those files.

**Attention** This is a public forum