• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 2391 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/LAUNCHXL-CC2650: CC2650

Azim Malik Abdul Aziz
Expert 1030 points
Part Number: LAUNCHXL-CC2650
Other Parts Discussed in Thread: CC2650, CC3200

Tool/software: Code Composer Studio

Hi There,

I was trying out Lab 2 of the Tutorial and on building the project these are the errors:


**** Build of configuration Debug for project blink_target_CCS ****

"C:\\CCS8\\ccsv8\\utils\\bin\\gmake" -k -j 4 all -O

Building file: "../main.c"
Invoking: ARM Compiler
"C:/CCS8/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/bin/armcl" -mv7M3 --code_state=16 -me --include_path="C:/TI_RTOS/TI_RTOS_LAB_SOLS/TM4C/Labs/Lab_02/Project" --include_path="C:/ti/tirtos_cc13xx_cc26xx_2_21_00_06/products/cc26xxware_2_24_03_17272" --include_path="C:/CCS8/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include" -g --diag_warning=225 --diag_wrap=off --display_error_number --abi=eabi --preproc_with_compile --preproc_dependency="main.d_raw" "../main.c"

>> Compilation failure
subdir_rules.mk:9: recipe for target 'main.obj' failed
"../main.c", line 19: fatal error #1965: cannot open source file "driverlib/sysctl.h"
1 catastrophic error detected in the compilation of "../main.c".
Compilation terminated.
gmake: *** [main.obj] Error 1
gmake: Target 'all' not remade because of errors.

**** Build Finished ****

I installed the driver library not of the platforms listed in the tutorial, but of CC2650 Launchpad.

Here's a screeshot for your reference:

Best,

A

  • 0
    Expert 1030 points

    Is this because the header files are associated with TivaC or any other. I thought the project files could be used on any platform, citing this from the tutorial: "For CC3200, CC26xx/CC13xx devices, users can run their labs on the Cortex M4 platform (Tiva-C) - and again, everything covered in the workshop is 100% applicable to these devices because almost all material/labs focus on TI-RTOS, not architecture."

    I changed the header file "sysctl" to "sys_ctrl" based on what I see in the driver libraries for CC2650.
    Now I get the following errors:


    **** Build of configuration Debug for project blink_target_CCS ****

    "C:\\CCS8\\ccsv8\\utils\\bin\\gmake" -k -j 4 all -O

    Building file: "../main.c"
    Invoking: ARM Compiler
    "C:/CCS8/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/bin/armcl" -mv7M3 --code_state=16 -me --include_path="C:/TI_RTOS/TI_RTOS_LAB_SOLS/TM4C/Labs/Lab_02/Project" --include_path="C:/ti/tirtos_cc13xx_cc26xx_2_21_00_06/products/cc26xxware_2_24_03_17272" --include_path="C:/CCS8/ccsv8/tools/compiler/ti-cgt-arm_18.1.1.LTS/include" -g --diag_warning=225 --diag_wrap=off --display_error_number --abi=eabi --preproc_with_compile --preproc_dependency="main.d_raw" "../main.c"

    >> Compilation failure
    subdir_rules.mk:9: recipe for target 'main.obj' failed
    "../main.c", line 69: warning #225-D: function "SysCtlClockSet" declared implicitly
    "../main.c", line 69: error #20: identifier "SYSCTL_SYSDIV_5" is undefined
    "../main.c", line 69: error #20: identifier "SYSCTL_USE_PLL" is undefined
    "../main.c", line 69: error #20: identifier "SYSCTL_XTAL_16MHZ" is undefined
    "../main.c", line 69: error #20: identifier "SYSCTL_OSC_MAIN" is undefined
    "../main.c", line 72: warning #225-D: function "SysCtlPeripheralEnable" declared implicitly
    "../main.c", line 72: error #20: identifier "SYSCTL_PERIPH_GPIOF" is undefined
    "../main.c", line 73: warning #225-D: function "GPIOPinTypeGPIOOutput" declared implicitly
    "../main.c", line 73: error #20: identifier "GPIO_PORTF_BASE" is undefined
    "../main.c", line 73: error #20: identifier "GPIO_PIN_1" is undefined
    "../main.c", line 73: error #20: identifier "GPIO_PIN_2" is undefined
    "../main.c", line 73: error #20: identifier "GPIO_PIN_3" is undefined
    "../main.c", line 76: warning #225-D: function "GPIOPinWrite" declared implicitly
    "../main.c", line 89: warning #225-D: function "GPIOPinRead" declared implicitly
    "../main.c", line 89: error #20: identifier "GPIO_PORTF_BASE" is undefined
    "../main.c", line 89: error #20: identifier "GPIO_PIN_2" is undefined
    "../main.c", line 91: warning #225-D: function "GPIOPinWrite" declared implicitly
    "../main.c", line 91: error #20: identifier "GPIO_PIN_1" is undefined
    "../main.c", line 91: error #20: identifier "GPIO_PIN_3" is undefined
    "../main.c", line 95: warning #225-D: function "GPIOPinWrite" declared implicitly
    "../main.c", line 108: warning #225-D: function "SysCtlDelay" declared implicitly
    13 errors detected in the compilation of "../main.c".
    gmake: *** [main.obj] Error 1
    gmake: Target 'all' not remade because of errors.

    **** Build Finished ****


    Thanks,
    A

  • 0 in reply to Azim Malik Abdul Aziz
    TI__Guru**** 467511 points

    Azim Malik Abdul Aziz said:
    Is this because the header files are associated with TivaC or any other. I thought the project files could be used on any platform, citing this from the tutorial: "For CC3200, CC26xx/CC13xx devices, users can run their labs on the Cortex M4 platform (Tiva-C) - and again, everything covered in the workshop is 100% applicable to these devices because almost all material/labs focus on TI-RTOS, not architecture."

    I'm not sure if it is that straightforward. What lab are you following? Can you provide a link?

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1030 points

    Hi Todd,

    Apologies. I thought I had added the link; somehow it didn't show up on here.

    Here's the tutorial link: 

    TI_RTOS_Kernel_Workshop_Lab_Manual_rev4.00.pdf

    I have also attached the lab manual of the tutorial. I am not sure if that helps.

    Best,

    A

  • 0 in reply to Azim Malik Abdul Aziz
    TI__Guru**** 467511 points
    Thanks.
    The workshop relies on some files that is installed in C:\TI_RTOS. Where did you get those files?

    ki
  • 0 in reply to Ki
    Expert 1030 points
    Hi Ki,

    Firstly, please accept my apologies for addressing you as Todd. I was replying to another post at the same time and forgot who I was addressing.
    So, I downloaded those files from the very same tutorial. They are all attached as zip/pdf files. If you scroll down on the Workshop Series 1, you will see them. I had to reinstall CCS8, as I got confused with the entire setup. As of now I only have the CCS8 with no TI-RTOS installed. Should I install it through the Resource explorer or from the TI website? On the TI website under CC2650 Launchpad, it is suggested to install the RTOS through CCS. If that's the case, what RTOS should I download - for SimpleLink Wireless MCU or CC2650? The resource explorer has so many options. I am also worried if any temporary files on my system would affect any of these installations. I did see the CCS8 installation process retreiving something from temp files on my system. Wonder what they were!

    Back to the Folder, TI_RTOS - one is required to create the folder in C, with those unzipped files. My doubt here is, how will these projects run with a target configuration of CC2650? I previously did the same with CC2650 configurations, the target as CC2650 and the examples for Tiva C/TMC4(?)---- Configuration failed ---error. Are there any examples specific to CC2650? Like workshops targeted at CC2650 Launchpad?

    Best,
    A
  • 0 in reply to Azim Malik Abdul Aziz
    TI__Guru**** 467511 points

    Azim
    I assume you where thinking of Todd Mullanix, who one of the TI-RTOS gurus on the forums. This thread many eventually end up being forwarded to him.

    Note that the workshop you are following is a bit dated. That is likely contributing to some of the confusion. Many of your questions I cannot answer definitively since I did not create the workshops.

    I am going to forward this thread to the TI-RTOS experts. They will be more knowledgeable of the workshop and help answer your questions best.

    Thanks
    ki

  • 0 in reply to Ki
    Expert 1030 points
    Hi Ki,
    That would really help.
    Thanks,
    A
  • 0 in reply to Azim Malik Abdul Aziz
    TI__Guru* 96960 points

    Hi Azim,

    Azim Malik Abdul Aziz said:
    almost all material/labs 

    "almost" is the operative word here. Driverlib across the MCU devices is not very portable. That's part of the argument for using TI-RTOS. It's probably best to skip the driverlib parts and go directly to the TI-RTOS solutions.

    Todd

  • 0 in reply to ToddMullanix
    Expert 1030 points
    Hi Todd,
    Ok. Thanks
    Best,
    Azim