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.

Linux/CC3200-LAUNCHXL: Simplelink CC3200 SDK libtirtos.a

Part Number: CC3200-LAUNCHXL
Other Parts Discussed in Thread: CC3200, SYSBIOS, CC3220S

Tool/software: Linux

Hi, I'm using the CC3200 Simplelink SDK from www.ti.com/.../cc3200sdk along with swru376d.pdf (3.3: Option 3: gcc) to set up my development environment.

Everything works ok until as per section 3.3.5 (Target Connection and Debugging (GDB)) step 5 I run: "arm-none-eabi-gdb -x gdbinit wlan_station.axf". If I type continue I get this error:

Breakpoint 1, main () at ../main.c:946
946        long lRetVal = -1;
(gdb) continue
Continuing.
cc3200.cpu -- clearing lockup after double fault

Program received signal SIGINT, Interrupt.
0x2000a184 in prvPortStartFirstTask () at ../../third_party/FreeRTOS/source/portable/GCC/ARM_CM4/port.c:259
259        __asm volatile(

Serial output from board is only the title of the application:

                 *************************************************
                           CC3200 WLAN STATION Application       
                 *************************************************

Any ideas how to fix this error ?

I've tried switching to TIRTOS but am getting other errors related to some absolute paths in libtirtos.a so I rebuilt it. The SDK for CC3200 downloaded from www.ti.com/.../cc3200sdk contains some absolute paths in the tirtos compiler options (ti_rtos/ti_rtos_config/gcc/configPkg/compiler.opt).  Changing the compiler options and the makefile after downloading tirtos sdk for simplelink, I've managed to build libtirtos.a but using this to make the example (getting_started_with_wlan_station) throws the errors (now with the amended absolute paths).

LD    exe/wlan_station.axf
../../../oslib/gcc/exe/libtirtos.a(osi_tirtos.obj): In function `ti_sysbios_family_arm_m3_Hwi_Params_init':
/ti/tirtos_simplelink_2_13_01_09/products/bios_6_42_00_08/packages/ti/sysbios/family/arm/m3/Hwi.h:1089: undefined reference to `ti_sysbios_family_arm_m3_Hwi_Params__init(void) static'
../../../oslib/gcc/exe/libtirtos.a(osi_tirtos.obj): In function `ti_sysbios_knl_Task_Params_init':
/ti/tirtos_simplelink_2_13_01_09/products/bios_6_42_00_08/packages/ti/sysbios/knl/Task.h:815: undefined reference to `ti_sysbios_knl_Task_Params__init(void) static'
../../../oslib/gcc/exe/libtirtos.a(osi_tirtos.obj): In function `ti_sysbios_knl_Semaphore_Params_init':
/ti/tirtos_simplelink_2_13_01_09/products/bios_6_42_00_08/packages/ti/sysbios/knl/Semaphore.h:419: undefined reference to `ti_sysbios_knl_Semaphore_Params__init(void) static'

and other similar errors.

 

  • Sridhar,

    Let me try to find someone who can help you with these issues.

    Regards,
    VR
  • Sridhar,

    Have you tried this on a Windows PC?

    VR

  • Hi Vincent, thanks for the response. I haven't tried on a Windows machine yet. The instructions for Windows in swru376d.pdf use Cygwin, so I'm assuming it works on Linux - and it mostly does as expected.
  • Happy new year!

    I'm still keen on resolving this error with the getting_started_with_wlan_station example using FreeRTOS w CC3200 on Linux.

    I've tried to debug the problem some more and have the following questions:

    1. Where in the application is the choice of pvPortMalloc() implementation made ? There seem to be multiple implementations of pvPortMalloc() in FreeRTOS and it's not yet clear to me where in the application settings this choice is made.

    2. Separately, is it possible that this error has something to do with the way the debug tools (arm-none-eabi-gdb) take control of the board for debugging - particularly if there's something in flash which is getting run before the debugger connects. Perhaps that's causing an unexpected interrupt while the FreeRTOS task scheduler starts ?

    Any pointers greatly appreciated. I'm going to investigate this for another few hours before I give up and move onto the CC3220S with which I've got further.

  • Hi,

    I assume you have already found a solution for this one so I'm closing this thread.
    If the issue is still relevant, please open a new thread.

    br,
    Kobi