• Locked Locked
  • Replies 30 replies
  • Subscribers 59 subscribers
  • Views 5339 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.

Code Composer Studio v6.1.2 MacOS Beta Release

JohnS
Guru**** 161615 points
Other Parts Discussed in Thread: CC2640, SYSBIOS, CC2650, BLE-STACK, CC2538, CCSTUDIO

There is an updated beta release for CCS MacOS image available here.

This release includes improved support for El Capitan.  Note that we are still working through issues with MSP430 on El Capitan.  It will be a few weeks before those issues are addressed and we can post a patch.  For now we do not recommend using MSP430 with El Capitan.

The installation image posted above is a web installer similar to what we have for windows and linux where it is a small package that you download and then the rest of the content is downloaded on demand depending on your installation selections.  If for some reason you prefer the full installer package it is available here.

We are keeping the release as a beta until we have addressed the remaining El Capitan issues.

John

  • Genius 3205 points
    I'm excited to see support for OS X. Sadly, my installation doesn't work. I downloaded CCS v6.1.2.00014. The application seemed to install correctly. At start up, application center will not load. I get an error message, "We're sorry, we cannot access the app center server." I am able to see a single "hello world" Java project, and I'm not able to edit it. I can't register the "free" version for use with my CC2650EM. I had an older version of Eclipse Java on my Mac which I no longer need. I wonder if there may be some conflict there. Any suggestions as to how to proceed would be appreciated.

    Patrick
  • Genius 3205 points
    I removed all of my projects and downloaded the SimpleBTLEPeripheral & Stack workspace. I found it peculiar that this project would not build right out of the box. I got the following error message:

    Building target: SimpleBLEPeripheralStack.out
    Invoking: ARM Linker
    "@ccs/tools/compiler/ti-cgt-arm_5.2.5/bin/armcl" --cmd_file="@ti-products/cc26xx_bluetooth_smart/cc26xx_bluetooth_smart__2.01.00.44423/Projects/ble/SimpleBLEPeripheral/CC26xx/CCS/Cloud/../../IAR/Stack/CC2640/buildConfig.opt" --cmd_file="@ti-products/simplelink/ble_cc26xx_2_01_00_44423_cloud/Projects/ble/config/buildComponents.opt" -mv7M3 --code_state=16 --abi=eabi -me -O4 --opt_for_speed=0 -g --gcc --define=DEBUG --define=CC26XX --define=CC26XXWARE --define=USE_ICALL --define=DATA= --define=FLASH_ROM_BUILD --define=HALNODEBUG --define=INCLUDE_AES_DECRYPT --define=NEAR_FUNC= --define=OSAL_CBTIMER_NUM_TASKS=1 --define=POWER_SAVING --define=xDEBUG_ENC --define=xDEBUG_GPIO --define=xDEBUG_SW_TRACE --define=xTESTMODES --define=GATT_NO_CLIENT --define=xDEBUG --define=xPM_DISABLE_PWRDOWN --define=xTEST_BLEBOARD --define=ICALL_RAM0_ADDR=0x200043E8 --define=ICALL_STACK0_ADDR=0x0000E000 --define=OSAL_SNV=2 --display_error_number --diag_warning=225 --diag_warning=...(line truncated)...
    <Linking>
    "@ti-products/cc26xx_bluetooth_smart/cc26xx_bluetooth_smart__2.01.00.44423/Projects/ble/common/cc26xx/CCS/cc26xx_ble_stack.cmd", line 89: error #10263: FLASH memory range has already been specified
    "@ti-products/cc26xx_bluetooth_smart/cc26xx_bluetooth_smart__2.01.00.44423/Projects/ble/common/cc26xx/CCS/cc26xx_ble_stack.cmd", line 89: error #10264: FLASH memory range overlaps existing memory range FLASH
    "@ti-products/cc26xx_bluetooth_smart/cc26xx_bluetooth_smart__2.01.00.44423/Projects/ble/common/cc26xx/CCS/cc26xx_ble_stack.cmd", line 97: error #10263: SRAM memory range has already been specified
    "@ti-products/cc26xx_bluetooth_smart/cc26xx_bluetooth_smart__2.01.00.44423/Projects/ble/common/cc26xx/CCS/cc26xx_ble_stack.cmd", line 97: error #10264: SRAM memory range overlaps existing memory range SRAM

    **** Clean-only build of configuration Debug for project SimpleBLEPeripheral ****

    I tried to comment out line 89 & 97 and rebuild. The rebuild did not show the changes to the commented lines and produced the same errors. At the top of the IDE it showed a small alert saying that the project was not saved. When I hovered over the alert, it said that projects are automatically saved - not true. I confirmed that I was logged in. This Beta release needs some work.
  • in reply to PATRICK OHARA
    TI__Guru**** 161615 points

    Patrick,

    If you look at your project are there multiple .cmd files in it?  It looks like it is using one called cc26xx_ble_stack.cmd but I wonder if there is another one in the project that is adding overlapping memory sections.  Might be called cc260xf128.cmd  If that one is there right click on it and exclude it from the build.

    Regards,

    John

  • in reply to JohnS
    Genius 3205 points
    Hi John,
    Thanks for the suggestion, and indeed you are correct. I had two .cmd files in the build. I excluded the cc260xf128.cmd and rebuilt the project. Unfortunately the errors persist. I can't seem to make changes to the project. I tried to comment out the offending lines in the .cmd, but the compiler doesn't recognize the changes. I wonder if there is something more fundamentally wrong with my installation.

    My version of CCS Cloud won't even compile the most basic "Hello World" program as shown below. I created a new project File->New CCS Project and copied this code from my desktop version of CCS running on Windows 10 under Parallels - which works fine. Any other suggestions would be appreciated.

    Patrick

    /*
    * ======== hello.c ========
    * The hello example serves as a basic sanity check program for SYS/BIOS. It
    * demonstrates how to print the string "hello world" to stdout.
    */

    #include <xdc/std.h>
    #include <xdc/runtime/System.h>
    #include <ti/sysbios/BIOS.h>
    #include "Board.h"

    Int main()
    {
    /* Call board init functions */
    Board_initGeneral();

    System_printf("Hello Patrick\n");

    BIOS_exit(0); /* terminates program and dumps SysMin output */
    return(0);
    }
  • in reply to PATRICK OHARA
    TI__Guru**** 161615 points
    Patrick,

    I am out of the office but I will have access to a Mac the day after tomorrow. I will give it a try then. I have tried on the windows machine I have here and everything is working ok for me with the cc2650 examples and CCSv6.1.2. I import them from Resource explorer and don't end up with two cmd files. On Mac they are likely not showing up in Resource Explorer and instead get imported via the project import tool which may behav a little differently. Still works ok on windows that way though.

    Regards,
    John
  • in reply to JohnS
    Genius 3205 points
    HI John,
    Please don't stress over this. I have my Windows based CCS and am using it for now. It would be great if you could take a look when you get back to work and have some time - maybe next week.
    Thanks
  • Mastermind 9055 points
    Hi,

    I have tested v6.1.2 on my EI Capitan. The MSP430 issue is the same as in v6.1.1. When reloading program (or stop debugging and then re-launh debugger again), sometimes, the debugger will be dead. A window will show the error and prompt to try again or give up. I choose to try again, and it works every time. So, I can continue to debug MSP430 without disconnect/connect the USB cable.

    But I found a minor issue. When maximizing CCS main window in EI Captian, it will show in "full screen" mode. This is correct. But when I open another dialog, for example "Show Build Settings", the dialog will expand to full screen. This is wrong. The dialog should keep "windowed", instead of maximized.

    Another question is, I can not find any way to reset CPU. In Windows or Linux, there is usually a speed button on the toolbar for me to do that.

    rcfocus.
  • in reply to PATRICK OHARA
    TI__Guru**** 161615 points

    Patrick,

    Looking at this on the Mac I think we are going to need an app note that explains how to get the BLE SDK CC2650 examples working on Mac.  There are a number of items that need to be done to get it going.  I have been trying it this morning and have found a few but I still don't have the SDK examples building.  I can get TI-RTOS examples to build fine.  I will have someone take a look at this next week when they are back in the office.

    Regards,

    John

  • in reply to JohnS
    TI__Guru**** 451311 points

    Hi Patrick,
    I was able to get the BLE Peripheral examples (App and Stack) building on Mac. I followed the steps documented below:
    processors.wiki.ti.com/.../MacOS_X_CCSv6_Beta

    Let me know if this works for you.

    Thanks
    ki

  • in reply to Ki
    Genius 3205 points
    Hi Ki,
    I think I'll wait for the post beta version. Still very excited about this and wish you guys well with the development.
    P
  • in reply to PATRICK OHARA
    TI__Guru**** 451311 points
    Patrick - Note that the main issue you are running into is that there are no MacOS installer for the BLE-STACK (and dependent software like the version of TI-RTOS for Simplelink used by the BLE-STACK). Even if CCS for MacOS is released, you would run into the same issues unless a MacOS installer for the BLE-STACK is released by the wireless connectivity group.

    Thanks
    ki
  • in reply to PATRICK OHARA
    Genius 3205 points
    The most recent update to the Mac based CCS has solved my problems. I'm now able to run the LCD example & Hello World. I don't see SimpleBLEPeripheral in the examples. I look forward to it being added. I may try to import the version that Ki refers to earlier in this thread.
    Thanks,
    Patrick
  • Expert 1920 points

    Hi,

    After installing the 6.1.2.00014 version on my Mac (El Capitan), I am unable to install any updates. Although, installing a component from the App Center works fine, and it also discovered any "packages" like tirtos_* folders that I copied into it from my previous 6.1.1 installation. It shows me that updates are available, but cannot install them.

    Error message is:

    An error occurred while collecting items to be installed
    session context was:(profile=epp.package.cpp, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
    No repository found containing: org.eclipse.update.feature,com.ti.ccstudio.cc2538.devicesupport.osx,1.32.0.00
    No repository found containing: binary,com.ti.ccstudio.cc2538.devicesupport.osx_root,1.32.0.00
    No repository found containing: org.eclipse.update.feature,com.ti.ccstudio.cc26xx.devicesupport.osx,1.16.0.01
    No repository found containing: binary,com.ti.ccstudio.cc26xx.devicesupport.osx_root,1.16.0.01
    No repository found containing: org.eclipse.update.feature,com.ti.ccstudio.msp430.emu.osx,6.2.1.0
    No repository found containing: binary,com.ti.ccstudio.msp430.emu.osx_root,6.2.1.0
    No repository found containing: org.eclipse.update.feature,com.ti.ccstudio.updatetest.osx,6.1.2.00014
    No repository found containing: binary,com.ti.ccstudio.updatetest.osx_root,6.1.2.00014
    No repository found containing: org.eclipse.update.feature,com.ti.emulation.pack.osx,6.0.83.1
    No repository found containing: binary,com.ti.emulation.pack.osx_root,6.0.83.1
    No repository found containing: org.eclipse.update.feature,jre,1.8.0.66c
    No repository found containing: binary,jre_root,1.8.0.66c

    And, the step #5 from the Wiki of deleting the 2 "cache" directories doesn't seem to help me.

  • in reply to Anup Rajput
    Mastermind 9055 points
    Hi,

    I would like to raise an issue. The CCS development team may always know this.

    I have tried to make the XDS100v3 2nd COM port work under Mac. This is important for SWO input to analyze. For this, I try this to install FTDI VCP driver, but it failed to work due to the PID number is changed. I tried to add a PID number inside the plist file. But, EI Capitan stops the driver from running and request the modified driver to be "re-signed".

    In fact, EI Capitan already builti-in FTDI2232H driver. The issue is TI changed the PID number in XDS100v3. So far, I have to go back to Linux. Hope that the CCS team can come out a solution in the next release for Mac.
  • in reply to JohnS
    Genius 3205 points

    Hi John,

    I'm using CCS 6.1.2.00014 on the Mac and things are working well. I've been able to import and build driver examples - LCD & empty_min. I also imported and built kernel example bigTime.cpp. I have two questions:

    1. I don't see a preprocessor directive to include the C++ complier as I see in Windows. Also a C++ complier is not on the CCS app store. Do I need to do anything special to code in C++ on the mac?

    2. Elsewhere in this thread, Kai points to a wiki that provides instructions to download and run the BLE_Stack. This didn't work for me. Any idea when the SimpleBLEPeripheral example project will be available for the mac CCS beta?

    Thanks

  • in reply to PATRICK OHARA
    TI__Guru**** 161615 points

    Patrick,

    There is nothing special that you need to do to use C++.  There are some options such as the C++ dialect that you can set.   To access those go to the properties for the project and then Build -> ARM Compiler -> Advanced Options -> Language options.  However you shouldn't have to do anything there.  The Preprocessor options are located one group down from the language options.

    On Mac we don't have the compiler updates showing up in the app center yet.  There is a newer compiler available (15.12.0 LTS) that shows up on WIndows and Linux.  We will be updating the App Center shortly to show the compiler updates as well.

    I don't think the team has any short term plans to release a BLE-STACK installer for Mac.  However you can get the existing package to work.  There are instructions here: 

    http://processors.wiki.ti.com/index.php/MacOS_X_CCSv6_Beta#Bluetooth_Low_Energy_Software_Stack_.28BLE-STACK.29

    If you follow those instructions the Simple BLE Peripheral example should work.  Are you hitting issues with that?  If so please go ahead and start a new thread and we can pull in the right people to get you up and running.

    Regards

    John

  • Prodigy 45 points

    Hi! When I opened CCS the other day it wanted to update a few things. When the updates completed, it asked me to relaunch. I clicked yes, but it never started again. Now I cannot open it anymore! The icon appears in the dock and bounces a few times, then disappears. The main uninstaller did the same but I found a folder with a bunch of other uninstallers for different components. I ran all and then removed the ti-folder. I then downloaded the installer again (tried both 6.1.1 and 6.1.2) but it just does the same - bounce a few times, then exits!

    Is this a known issue? Any way to fix it, any logs to check etc?


    Update:

    I found this is the output of  "sudo dmesg | tail" after trying to run the installer, is it related?

    CODE SIGNING: cs_invalid_page(0x126000): p=4210[osx-intel] final status 0x2000000, allowing (remove VALID) page

  • in reply to Albert Skog1
    TI__Mastermind 22060 points

    Hi Albert,

    Can you try running the 6.1.2 installer again and upload the latest bitrock*log file in the /tmp folder so we can take a look.

    Thanks

    Danish

  • in reply to danishinnis
    Prodigy 45 points

    Hi danishinnis,

    Thanks for the tip, this looks interesting, lots of errors referring to libitcl4.0.3.dylib.

    Trying to upload the file as attachment (why does this forum not have a preview button?!):

    bitrock_installer_21406.log

  • in reply to Albert Skog1
    TI__Mastermind 22060 points
    Did you install macports after the first installation of CCS? We've hit some problems with that. Could you accept my friend request, I'll send you a trial version of the installer.
    Danish
  • in reply to danishinnis
    TI__Mastermind 22060 points

    We've confirmed that the macports installation causes problems with the installer. This should be fixed in CCS 6.1.3. In the meanwhile, we can provide a fixed 6.1.2 installer to any one who needs it.

    Danish

  • in reply to PATRICK OHARA
    Mastermind 9055 points
    Hi CCS Team,

    It is March 16 now, is there any update for CCS for Mac?
    As I can see, the serial port driver is an important issue because I can't use the 2nd UART port of XDS100v3 on Mac.
  • in reply to Robert Chen
    TI__Guru**** 161615 points

    rcfocus,

    CCSv6.1.3 which includes MacOS support is looking good for this month.

    I will have to check on the serial port issue.

    Regards,

    John

  • in reply to JohnS
    Mastermind 9055 points
    Hi John,

    I want to use the 2nd UART channel for two purposes:
    (1) As SWO input to Mac. I have designed by my tracer program in Mac by Qt.
    (2) As the flash programming channel for mass-production.

    FTDI has default UID/PID and the Mac USB driver can identify them automatically. But TI has changed the UID/PID number of FTDI chip in XDS100v3 so that it can no longer be detected. If I change the ID values according to FTDI website instruction, then I have to re-certificate the driver. This is very difficult due to new security policy of EI Capitan.

    Hope the issue can be fixed in the coming release.
    I will test CCSv6.1.3 at the first time.
  • Prodigy 105 points
    Hi,

    I'm having problems installing CCS6.1.2.00014_osx.

    I'm running OSX El Capitan Version 10.11.3 (15D21).
    Security set to "Allow apps downloaded from Anywhere"

    When I execute "cc_setup_6.1.2.00014" it just bounces in the dock and then disappears.
    Nothing is installed, no error message is displayed and no error is logged.

    Can you please provide advice to help resolve my problem.

    Thanks,

    David
  • in reply to David Glanville
    Mastermind 9055 points
    Hi David,

    The installation is smooth in my MacBook Pro. I don't know what's happening in your Mac. Maybe the installation file is corrupted. You can try to re-download the installation file and try again.
  • in reply to Robert Chen
    TI__Guru**** 169894 points
    David,

    I just re-tested the same version as you and it worked out fine. One slight difference is that I am running OSX El Capitan version 10.11.4, but I had previously installed it in the same version as yours.

    Unfortunately I am not very experienced in the Mac OS systems, but I found the blog below that mentions how to look for application logs. Perhaps you could see if the installer generated a log that could shed some light on what may be happening?
    bjango.com/.../

    Regards,
    Rafael
  • in reply to desouza
    TI__Mastermind 22060 points
    Hi,
    I'm helping David with his issue on a separate thread.
    Thanks,
    Danish
  • in reply to Robert Chen
    Prodigy 105 points
    Hi.
    Danish has found the cause of the problem and has provided me with a test installer that works.
    Thanks
  • in reply to desouza
    Prodigy 105 points
    Hi.
    Danish has found the cause of the problem and has provided me with a test installer that works.
    Thanks for the advise on the logs and tip on how to attach files.

    Thanks