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.

CC2640 Timestamp help

Other Parts Discussed in Thread: CC2640, CC2650, BLE-STACK

Hello everyone,

I'm attempting to profile some code on my custom CC2640 board that relies on really tight timing (and I've previously posted about Clock_getTicks() reyling on the 32kHz RTC) and was attempting to find a way to profile my code. The 'profiling' options in the CCS debugger are all grayed out, so I was hoping to use the Timestamp_getXX() functions to help me. 

I've searched the forums here, and have found a few posts on this topic, but not one single complete example that can help me get this working. (The best help I found was here -

The SYS/BIOS User Guide makes it sound trivial to get it working, but following the example in there, I get tons of compiler errors. My code is based on the SimpleBLEPeripheral, and makes use of the GPTimer/PWM driver. I need to profile code that relies on single 1uS differences - therefore I need a way to profile at 48Mhz clock ticks.

I can't find the example ClockApp or SensorTag UART examples that others have mentioned in my C:\ti\ folder.

I've checked the wiki, and although it explains how to enable the profiler in the debugging perspective, all the options are grayed out (as I mentioned before.)

Does anyone have any suggestion as to where I can look to find a concrete example that works on the CC2640/CC2650 to profile code? I'm really begging to get frustrated with the disjointed documentation and support for this particular TI processor. I've had great success on the past in developing on the MSP430 because i was able to write directly to registers and forego the use of any middleware. This CC26xx setup is really confusing me.

Thanks in advance everyone,

-Ben

  • Hi Ben,

    You should be able to use the examples for the CC2650 with some minor modifications. To do this you can go to the Resource Center found at the View menu in CCS. There you will find various examples for the 2650, you can click on whichever one you need and then click on Import the example project into CCS in the window that comes up. Then you want to go into the Project properties for the imported project and change the device to the CC2640. And lastly you would want to check your Board file to make sure the project is not using any pins that don’t exist on your device.

    Thanks,
    Gerardo

  • Thanks Gerardo,


    I didn't know you could use the View Menu to access examples like that - pretty useful.

    However, I tried both the UART and Clock examples that were recommended in other posts (using the method you mentioned) pertaining to using the Timestamping features, and didn't see anywhere that they made use of them. However, they do use the Logging feature that allows you to enable the Profiling in the debugger, but all the features beyond enabling it were still grayed out.

    Can you recommend an example for either the 2640 or 2650 that uses timestamping? I have both my custom board based on the 2640 as well as a SensorTag board laying around to test on. I'm anxious to be able to use the timestamps to check my codes timing.

    Again, thanks for the pointer and I'll continue to keep looking into it, but for now I'm still stuck without a concrete example or bit of documentation that covers this.

    Thanks,

    -Ben

  • Hi Ben,

    The Benchmark example has some Timestamp features, it may help you get an idea of what you need to do.

    I see you said you were looking at the SYS/BIOS user guide previously, have you looked at the TimestampProvider section on the BIOS API? It can be found under ti->sysbios->family->arm->cc26xx->TimestampProvider. This may help you fix some of those errors you mentioned you were getting previously. If you continue to get compilation errors after looking at the API please post them here.

    Thanks,
    Gerardo
  • Hello again Gerardo,

    I looked through the examples again, and didn't see the Benchmark example you were talking about. This is what I see when I look at the examples:

    I've looked through the ti->sysbios->family->arm->cc26xx->TimestampProvider documentation, but didn't have any luck. I still get compilation errors.

    I have one more thing I want to try, and if it doesn't work, I'll post my appBLE.cfg here, as well as the errors I get.

    Thanks again,

    -Ben

  • Hi Ben,

    Could you also tell me what version of TI-RTOS you are using?

    Thanks,
    Gerardo
  • Hello again Gerard,

    Sorry it took me so long to get back to you, but my house (in Baltimore) has been without power for a few days :/

    Anyways, here I'm attaching my appBLE.cfg as well as an image showing my version of TI-RTOS that I have installed. I still haven't been able to understand the compiler errors I'm getting, so if you can lend any insight after looking at my .cfg and RTOS version, I'd really appreciate it.

    Thanks again,

    -Ben

    6787.appBLE.cfg

  • Hi Ben,

    So it looks like that example is not in your version of TI-RTOS, so if you wanted to look at it you would have to update your TI-RTOS.

    As for your compile errors, you forgot to post the errors you are getting, could you please post those.

    Thanks,
    Gerardo

  • Hello again Gerard,

    Sorry for posting incomplete information. I end  up having to do end-user troubleshooting and know how frustrating it cant be to not have the full picture when attempt to help.

    Anyways, when I change my appBLE.cfg as follows to enable the Timestamping, I get the following errors:

    7674.appBLE (1).cfg

    In my application, I attempt to use the following include to access the timestamp provider:

    #include <ti/sysbios/family/arm/m3/TimestampProvider.h>

    ...with no luck.

    I really can't upgrade to the latest BLE-Stack, or TI-RTOS, as I've been developing our project for over a year, and worry about the other things it might break - just in case you were going to suggest that.

    If you can suggest anything further (now that you have all my information) I'd appreciate it.

    Thanks!

    -Ben

  • Hi Ben,

    So two things that I believe should help you, first add this to your .cfg file:

    var Timestamp = xdc.useModule('xdc.runtime.Timestamp');
    Timestamp.SupportProxy =
        xdc.useModule('ti.sysbios.family.arm.m3.TimestampProvider');

    Then use the following to include Timestamp:

    #include <xdc/runtime/Timestamp.h>

    Thanks,
    Gerardo

  • Thanks for the suggestions Gerardo,


    However, after making your changes I get a whole bunch of errors now. I'm attaching them here:

    Description	Resource	Path	Location	Type
    #10010 errors encountered during linking; "SimpleBLEPeripheral.out" not built	SimpleBLEPeripheral		 	C/C++ Problem
    <a href="file:/c:/ti/ccsv6/tools/compiler/dmed/HTML/10234.html">#10234-D</a>  unresolved symbols remain	SimpleBLEPeripheral		 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_cc26xx_Power_auxISR__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_cc26xx_Power_defaultClockFunc__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_cc26xx_Power_initiateCalibration__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_cc26xx_Power_LF_clockFunc__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_cc26xx_Power_Module_startup__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_cc26xx_Power_notify__I' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_cc26xx_Power_startFirstMeasurement__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_cc26xx_Timer_dynamicStub__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_cc26xx_Timer_Module_startup__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_m3_Hwi_disableFxn__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_m3_Hwi_enableFxn__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_m3_Hwi_excHandlerAsm__I' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_m3_Hwi_initNVIC__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_m3_Hwi_Instance_init__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_m3_Hwi_Module_startup__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_m3_Hwi_pendSV__I' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_m3_Hwi_restoreFxn__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_m3_Timer_Module_startup__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_m3_Timer_periodicStub__I' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_m3_TimestampProvider_Module_startup__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_m3_TimestampProvider_rolloverFunc__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_family_arm_m3_TimestampProvider_startTimer__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_gates_GateHwi_enter__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_gates_GateHwi_Instance_init__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_gates_GateHwi_leave__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_gates_GateHwi_query__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_hal_Hwi_Instance_init__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_hal_Hwi_Module_startup__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_heaps_HeapMem_alloc__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_heaps_HeapMem_free__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_heaps_HeapMem_getStats__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_heaps_HeapMem_init__I' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_heaps_HeapMem_Instance_init__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_heaps_HeapMem_isBlocking__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_knl_Clock_Instance_init__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_knl_Clock_logTick__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_knl_Clock_Module_startup__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_knl_Clock_setTimeout__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_knl_Clock_start__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_knl_Clock_stop__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_knl_Clock_workFuncDynamic__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_knl_Idle_loop__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_knl_Queue_Instance_init__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_knl_Semaphore_Instance_init__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_knl_Swi_Module_startup__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_knl_Swi_post__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_knl_Task_disable__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_knl_Task_Instance_init__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_knl_Task_Module_startup__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    Undefined reference to 'ti_sysbios_knl_Task_restore__E' in file C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	.xdchelp	/SimpleBLEPeripheral	 	C/C++ Problem
    unresolved symbol ti_sysbios_BIOS_getCpuFreq__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_BIOS_getThreadType__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_BIOS_start__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_family_arm_cc26xx_Boot_trimDevice, first referenced in C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_family_arm_cc26xx_Power_getTransitionState__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_family_arm_cc26xx_Power_getXoscStartupTime__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_family_arm_cc26xx_Power_isStableXOSC_HF__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_family_arm_cc26xx_Power_registerNotify__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_family_arm_cc26xx_Power_releaseConstraint__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_family_arm_cc26xx_Power_releaseDependency__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_family_arm_cc26xx_Power_setConstraint__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_family_arm_cc26xx_Power_setDependency__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_family_arm_cc26xx_Power_switchXOSC_HF__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_hal_Hwi_disableInterrupt__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_hal_Hwi_enableInterrupt__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_hal_Hwi_initStack, first referenced in C:\Users\flecko\workspace_v6_1\SimpleBLEPeripheral\FlashROM\configPkg\package\cfg\appBLE_pem3.oem3	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_knl_Clock_getTicks__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_knl_Clock_isActive__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_knl_Queue_dequeue__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_knl_Queue_empty__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_knl_Queue_enqueue__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_knl_Semaphore_pend__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_knl_Semaphore_post__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_knl_Task_enable__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    unresolved symbol ti_sysbios_knl_Task_self__E, first referenced in <whole-program>	SimpleBLEPeripheral		 	C/C++ Problem
    XDC runtime error: xdc.runtime.Timestamp: no element named 'logsEnabled'	appBLE.cfg	/SimpleBLEPeripheral/TOOLS	Configuration Validation	XDCTools Configuration Marker
    

    However, to make things easier on both of us, is there any example I can download without upgrading my TI-RTOS version that has timestamping enabled? I can't believe this can be this hard to get something like this working.

    Let me know when you get a chance.

    And again - thank you for the help!

    -Ben

  • Hi Ben,

    There doesn't appear to be any examples with timestamps on 2.14.

    Did you make any other changes to the code after your last successful compilation?

    Thanks,
    Gerardo
  • I ended up giving up on getting timestamping to work, because I was able to fix the section of code that I wanted to measure.

    Thanks for the pointers, but until I upgrade (if ever) to the new version of the TI-RTOS/BLE-STACK, I'll just assume that I can't use timestamping.

    -Ben

  • Hi Ben,

    Sorry we couldn't get this working, but glad to hear you were able to get your code to work without it.

    Thanks,
    Gerardo