• State Resolved
  • Locked Locked
  • Replies 34 replies
  • Subscribers 58 subscribers
  • Views 5502 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.

(ACTIVE) LAUNCHXL-CC2650

jan2809
Mastermind 7850 points
Other Parts Discussed in Thread: LAUNCHXL-CC2650, CC2650, CC3200, CC2640, CC2560

(ACTIVE) LAUNCHXL-CC2650

http://www.ti.com/tool/launchxl-cc2650 but when I click Order Now > Buy from TI it's not there

Is it in stock, yet? If not, when it is expected to be?

Happy New Year!

  • 0
    Guru 735685 points
    I think it is newly listed and not really active by now. I think it should be available soon.
  • 0 in reply to YiKai Chen
    Mastermind 7850 points

    Hi YiKai,

    It's already available, but I don't see any documentation.

    Do you know how to compile Contiki for it?

    Jan

  • 0 in reply to jan2809
    Guru 735685 points
    I don't have this CC2650 LauchPad so I don't know how to compile Contiki for it. However, I guess the build result of SmartRF06+CC2650EM can run on it.
  • 0 in reply to jan2809
    Prodigy 120 points

    I see that it is now available for purchase in the TI Store.  I have placed my order yesterday but it has not been processed yet.

    I also presume that a build for the SmartRF06EB and CC2650 should work.  Hopefully I will be one of the first to receive it and I am eager to get it working.  Will let you know.

  • 0 in reply to Trevor Lynch-Staunton
    Prodigy 120 points

    I have received the Launchpad and it says to update the firmware first using the "Flash Programmer 2". The firmware update went well but the "Simplelink LaunchPad Starter" app for IOS doesn't seem to be released yet. I imagine this is Apple taking some time to release it. Hope it doesn't take too long.  

    I couldn't see it as a discoverable device in the Settings Bluetooth on my phone even though the LED is flashing green. Thought this was strange but I won't condemn it until I have an app as recommended in the pamphlet.

  • 0 in reply to Trevor Lynch-Staunton
    Guru 735685 points
    You can try to use SensorTag App to scan it.
  • 0 in reply to YiKai Chen
    Prodigy 120 points
    Yes, it seems the SensorTag App has all the functionality. Works well. Thanks!
  • 0 in reply to Trevor Lynch-Staunton
    Guru 735685 points
    You are welcome and it good to know it works.
  • 0 in reply to YiKai Chen
    Intellectual 420 points
    I'm having less luck with my new CC2650 LaunchPad.

    Flash Programmer 2 can see the device but errors with "Error occured at addr: 0x00000000, writing 16768 bytes." when trying to flash the new firmware. I just selected the hex file and checked the Program action. Maybe I'm missing something but I couldn't see anything else obvious.

    The SimpleLink Starter app isn't in the Android app store and the SensorTag one can't see the device. It's discoverable via Bluetooth but pairing is refused too.

    Maybe I'll just wait for the tools and documentation to catch up. Looks like a nice board though.
  • 0 in reply to Fred Murphy
    Mastermind 7850 points

    Hi,

    The CC2650 Launchpad rev. 1.1 works OK for me with BLE firmware (updated with Flash Programmer 2 ver.1.7.2)

    using iPhone application. The existing Android "Sensortag" application should work as well, but I haven't tested it.

    What is your Launchpad and Flash Programmer version?

    Jan

  • 0 in reply to jan2809
    Intellectual 420 points
    Same versions as you have. I selected XDS110/CC2650 under connected devices, selected the hex file, checked program, entire source file and when clicking the button with the triangle I get the following output:

    >Initiate access to target: XDS-L1001993.
    >Reading file: C:/Users/fred2/Downloads/CC2650LaunchPad_BLE_All_v0_90.hex.
    >Start flash programming ...
    >Flash loader reported an error (4)
    >Error occured at addr: 0x00000000, writing 16768 bytes.
    >Failed to write 37276 bytes to address 0x00000000.
    >Reset target ...
    >Reset of target successfull.

    Connecting to and reading from the device seem to work OK.
  • 0 in reply to Fred Murphy
    Guru 735685 points
    Try to change a USB cable. Sometimes you will see this trouble with a bad USB cable.
  • 0 in reply to Fred Murphy
    Mastermind 7850 points

    Are you able to program another target?

    What is your OS?

    Have you tried to reinstall the drivers?

  • 0 in reply to Fred Murphy
    Mastermind 7850 points

    before programming flash has to be erased - click all 3 button as you see below:

  • 0 in reply to jan2809
    Intellectual 420 points
    Thanks jan2809, that's probably it - user error. I assumed Erase was if you just wanted to erase the device and that Program would automatically overwrite what's in the flash. I can't check until I get home but I'm sure that selecting all 3 options will do it.
  • 0 in reply to jan2809
    Intellectual 800 points
    I have both the SimpleLink Wi-Fi Starter and the BLE SensorTag apps for Android and neither are picking up the CC2650 Launchpad as a Bluetooth device. I've upgraded the firmware on the CC2650 Using Flash Programming 2 and that seemed to go fine, but the APPs are not picking up the device. I can see the CC2650 in the Bluetooth available devices listing in the Settings on the Tablet, but no luck with the apps. The odd think is that the Wi-Fi Starter App is showing the CC2650 as a CC3200 device and attempts to configure to that. Is it possible I miss a step with the step-up of the device? I followed the Quick Start guide but that did not assist with the issue.
  • 0 in reply to Jon Morss
    Guru 735685 points
    You can try to run SimpleBLEPeripheral example in BLE Stack v 2.1 to your CC2650 LaunchPad.
  • 0 in reply to YiKai Chen
    Intellectual 800 points

    YK,

    I have downloaded and installed the BLE Stack 2.1.1 however the SimpleBLEPeripheral example in there is for a CC2640 device and not a CC2650 device. I have not compiled and installed this since there is a difference between board models. Would this pose an issue?

    Also, how does one get a hold of a CC2650 Launchpad v1.2? I had just recently ordered the CC2650 Launchpad but it is a v1.1 and most of the docs seem to point to either a v1.0 or a v1.2.

    To add to this, I attempted to compile the SimpleBLEPeripheral but I ran into a size limitation with IAR since I have the free version, but with CC V6.1.1 I am getting linking, FLASH and SRAM memory and unresolved symbol ResetISR issues.  I did change the device variant to CC2650F128 since that made more sense rather than the CC2640.

    Did I missing a step here?

  • 0 in reply to Jon Morss
    Guru 735685 points
    CC2650 is a dual mode SOC which can run binary for CC2640 without problem. I have no idea about the differences between CC2650 Launchpad 1.x.
  • 0 in reply to YiKai Chen
    Intellectual 800 points
    Yeah, it won't compile with either CC2650 or CC2640. I was however able to compile the Sensor Tag project and did load this on the board, but that did nothing from what I can tell. I ended up installing CC2650LaunchPad_BLE_All_v0_90.hex back on the board and was able to see the device in the Bluetooth setup on the tablet but the TI apps will not pick up the device as a Bluetooth device.
    Interesting enough, I have the nRF Master Control installed and it was able to identify the CC2560 but it does not seem to know what to do with it and just lists a bunch of undefined options.
    It does show Flags for : LimitedDIscoverable, BrEdNotSupported as well as "Incomplete List of 16-bit Service UUIDs 0xFFED."

    Jon
  • 0 in reply to Jon Morss
    Guru 735685 points
    I try to download prebuilt image C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Accessories/HexFiles/CC2640_SmartRF-7ID_SimpleBLEPeripheral.hex to my CC2650 LaunchPad and My iPhone SensorTag App can see it and pair with it without problem. Can you try it to see if you can get similar result?
  • 0 in reply to YiKai Chen
    Intellectual 800 points
    YK,

    I downloaded the CC2640_SmartRF-7ID_SimpleBLEPeripheral.hex to the launchpad as you suggested but still no luck. However, I down loaded CC2640_SemsorTag.hex to the board and was able to see in the older version of the BLESensorTag app but there doesn't seem to be much I can do with it. The app picks up the CC2650 LP but does list the System ID, Model NO, Firmware rev, Hardware Rev and Manufacture Name, but the serial num and software revision are left N/A. I tried the IBM Quickstart and it does show the device ID as valid but its waiting for the device to send valid data to visualize it.

    The Wi-Fi starter does not pick up the device with any of these bits on it.

    I was able to solve the compile issue I was having though. The issue was that I was changing the processor to CC2650 from CC2640 which it didn't seem to like. Once I removed the project, deleted the folder from the workspace location and then reimported the project in CC I was able to compile it. No luck getting the apps to id the board though.
  • 0 in reply to Jon Morss
    Guru 735685 points
    Try to refer to section 2.5.2.2 in developer's guide ( www.ti.com.cn/.../swru393b.pdf )
  • 0 in reply to YiKai Chen
    Intellectual 800 points
    Uh, that is what I did. However, changing the processor from cc2640F128 to cc2650F128 resulted in errors which I suppose I'll have to track down.
    No thanks, I've wasted enough time on this. I'll just toss the board in the worthless POC pile and try another vendor.
    So much for that out-of-box experience.
  • 0 in reply to Jon Morss
    Guru 735685 points
    I have no idea why it's so difficult for you to make it work. Usually, you only need to download and install BLE Stack v2.1. Then, build example and download it to CC2650 Launchpad to make it work.
  • 0 in reply to YiKai Chen
    Intellectual 800 points

    Yeah, well I have no idea why the TI SmpleLink Android Apps do not work with the CC2650 Launchpad, but I gather from your messages that is something for me to resolve if I wish to continue to pursue using this device.

    Have you tried connecting to the device using the Android version of the Apps; preferably running Android OS version 5.1.1? 

  • 0 in reply to Jon Morss
    Guru 735685 points
    I had tried to connect it to Android SensorTag App but I don't remember if Android OS is version 5.1.1.
  • 0 in reply to YiKai Chen
    Intellectual 800 points
    Considering I can see the device and it's UUIDs via the Nordic nRF Master Control, the device does look like it is functional. From that I can work with the appropriate UUID to send commands to the device to test it to ensure it is working as expected. Perhaps there is something in the newer Android OS that is causing and issue with the Simple Link app; even the older BLE SendorTag app, which is the only one that seems to ID the launchpad if the SensorTag FW is loaded on the CC2560, crashes periodically. I'll keep working at it when I have time and see if I can come up with a solution.
  • 0 in reply to Jon Morss
    Guru 735685 points
    Maybe you can find an iPhone to verify it.
  • 0 in reply to Jon Morss
    Prodigy 10 points

    Hi Jon,


    I can't connect any examples to my andriod sensor tag app, too.

    only thing that is working is the sensortag hex-file, but it is written for the sensortag, so i can't use the leds/buttons on the launchxl board. i used the "project 0" from the following link in the ccs cloud

    http://dev.ti.com/tirex/#/DevTool/CC2650-LAUNCHXL?link=CC26xx%20Bluetooth%20Smart%2FDevelopment%20Tools%2FCC2650-LAUNCHXL%2FExamples%2FProject%20Zero

    and i used the "ble scanner" from following link

    https://play.google.com/store/apps/details?id=com.macdom.ble.blescanner&hl=de

    connect ble scanner to project zero.

    with "r" and "w" you can read/write bytes of the services. if you want to write a status byte you have to choose byte array in the popup-window of the app. i am really not happy with so called out-of-box solutions that aren't working, because it steals all the motivation and a lot of time :/

  • 0 in reply to Adrian Stirn
    Guru 735685 points

    What is your HW? CCC2650DK or CC2650 LaunchPad? By the way, I suggest you to post BLE related issue to BLE E2E forum.

  • 0 in reply to Adrian Stirn
    Intellectual 800 points

    Hey Adrian,

      Yeah, I have been doing a bit of research on this and it depends on how TI implemented their BLE app for Android.  Google shifted from using BlueZ to Bluedroid at Android 4.4 (KitKat) and 5.0/5.1 (Lollipop) so it is possible that something written for 4.3 might not work with the later Android versions.  BlueZ can be added to dev with the later Android versions but it is not something that is there by default.  But I suppose that is a discussion for the BLE section of the forum. 

    However, with regards to getting the code built and loaded on the CC2650 Launchpad, I did find some info in another forum post that pointed to a Wiki dedicated to migrating the sample code to the LAUNCHXL-CC2650.   I followed this which took a bit of work especially removing the references to the LCD which the Launchpad does not have, but I was able to finally compile and load the code on the Launchpad as a true CC2650 device but did not get to implementing the GAT stuff.  I was able to get the LED on the Launchpad to light so I know the code works.   One thing though, in the Wiki, there is a caution about running the sample code on the Launchpad since the sample code is written for another device so the board layouts do not match so you might get some strange behavior if you run it as is.

    This is the link I was referencing:

  • 0 in reply to Jon Morss
    Guru 735685 points
    I remember I had run SampleBLEPeripheral on CC2650 Launchpad without modification of source code so I suggest you can try it.
  • 0 in reply to YiKai Chen
    Intellectual 800 points
    I think we have had this discussion already, but much of the sample code does not pertain to the Launchpad and the processor that is used is not for the CC2560 so why would I used the code as is?