• State
  • Locked Locked
  • Replies 15 replies
  • Subscribers 53 subscribers
  • Views 2170 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.

2650 newbie help

Tony Asaro
Prodigy 150 points
Other Parts Discussed in Thread: CC2650

I purchased the 2650 sensortag a few weeks back & at that time, I didn't buy the sensortag + debug_devpack combo. :(

I poked around the forums but, couldn't resolve my questions so, here they are:.

1) I've managed to compile the sample projects via the cloud tools & also on my PC w/ local CCS. The android app seems to have  option for uploading firmware. Is it possible to take the output of the compiled projects and send them OTA to the 2650. Or, is it mandatory to use a CC-DEVPACK-DEBUG. If yes, I'd appreciate a pointer to the details. 

2) The store shows that the DEVPACK DEBUG is available (in stock) but, it doesn't show up in my cart when I select it. Is it no longer being sold as a separate item? Other products - e.g. sensortag + devpack, WATCH, LED packs - do show up on the cart. I've checked non-Ti sites & they show out-of-stock. 

3) The store also  advertises a WATCH devpack - it's $4 more than the DEBUG devpack (which is $15). Are these equivalent in terms of debug + firmware uploading but, w/ an LCD panel or would someone need a DEBUG devpack as a minimum. 

 

 

  • 0
    Guru 735685 points
    CC-DEVPACK-DEBBUG is not in stock until next year as I know. DEVPACK watch is different to CC-DEVPACK-DEBBUG and it cannot function as CC-DEVPACK-DEBBUG. The alternative is to use SmartRF06 as debugger or buy a 3rd party XDS100V3 debugger.
  • 0
    TI__Guru** 105180 points
    Hello Tony,

    Unfortunately, the DevPack Debugger ( CC-DEVPACK-DEBBUG ) is out of stock. Since you really need debug capability, I would do as YK suggests and use a 3rd party debugger or one of the TI XDS200 or XDS100v3 debuggers. I apologize for the inconvenience with the non-available inventory

    Best wishes
  • 0 in reply to JXS
    Prodigy 150 points
    Hi JXS,

    I will investigate the debugger options you listed ...

    In the meantime, is it possible to send the compiled output (== firmware?) of cloud tools or CCS on my PC to the sensortag?
    I ask `cause the android app has an option to load firmware over-the-air.
    If so, how does one go about doing that and how can I restore the old firmware should I need to do that.

    Thanks,
    --Antonio
  • 0 in reply to Tony Asaro
    TI__Mastermind 33460 points
    Hi Tony,

    We do have an OAD profile allows you to download program images over the air. You can see more information in the sensortag getting started wiki
    processors.wiki.ti.com/.../CC2650_SensorTag_User's_Guide

    However, this is a fairly limited form of programming your device as it doesn't allow you to set breakpoints or change all of the flash pages. Until your debugger arrives it would be useful to learn our OAD system as it is a popular feature to add to your BLE product.
  • 0 in reply to Sean2
    Prodigy 150 points

    Thanks Sean but, I'm stuck again. :(

    Here's where things stand:
    I imported the BIM_Extflash, SensorTag + SensorTagStack projects into my workspace.
    I modified the BIM settings to produce a hex file.
    I modified the SensorTag post-build steps with the following: "${CG_TOOL_HEX}" -order MS --memwidth=8 --romwidth=8 --intel -o "${ProjName}.hex" "${ProjName}.out";python "C:/Python27/Scripts/hexmerge.py" -o "${PROJECT_LOC}/FlashOnlyOAD/OAD_IMAGE_FULL.hex" -r "000:1FFFF" --overlap=error "${PROJECT_LOC}/FlashOnlyOAD/${ProjName}.hex":0000:1EFFF "${PROJECT_LOC}/../${ProjName}Stack/FlashROM/${ProjName}Stack.hex" "${PROJECT_LOC}/../BIM_extflash/FlashOnly/BIM_ExtFlash.hex":1F000:1FFFF;

    That all works & I get a combined hex file.
    I copied the OAD_IMAGE_FULL.hex file generated over to my android phone.
    It ends up in the Download directory.
    I start up the TI BLE app on my addroid, scroll down to the firmware upload section and select that.
    The android app indicates no firmware images are available for upload. :(
    Poked around some more and I believe I need some sort of bin file.

    Instead of the back & forth, mind explaining the steps get a viable image I can send over-the-air to the CC2650?
    All I've done so far is change the SensorTag.c file such that the devInfoModelNumber has my name in the string and hoping to see it on the android app. Baby steps. :)

    Thanks for the help.

  • 0 in reply to Tony Asaro
    Prodigy 150 points
    Ping.
    Looking for the step-by-step process to generate a .bin file that I can upload over-the-air via the android app to my 2650 while I wait for DEVPACK_DEBUG units to be available. I think I'm most of the way there, just need those last steps. Any help appreciated.
  • 0 in reply to Tony Asaro
    TI__Mastermind 33460 points
    Hi Tony,

    Will update the sensortag user's guide to make the OAD process clear. Check back there within a couple of hours.
  • 0 in reply to Sean2
    TI__Mastermind 33460 points
    Note that you are correct that .bin files will need to be used, but BIM is not included in an OAD image as it is permanently resident on the device.

    The section that you are referring to is for generating a super hex to flash using flash programmer 2. This will be explained on the page as mentioned above.
  • 0 in reply to Sean2
    Prodigy 150 points
    Thanks Sean.
    Send me a note when you're done & I'll give it a go.
    Please also specify the guide + section to refer to.
  • 0 in reply to Tony Asaro
    TI__Mastermind 33460 points
    Tony,

    processors.wiki.ti.com/.../CC2650_SensorTag_User's_Guide is now updated. Didn't have an android app to get any screengrabs for you but the process should be the same as iOS.
  • 0 in reply to Sean2
    Prodigy 150 points
    Hi Sean,

    I'm not having any luck. :(
    I copied what I thought were your updated changes for an OAD .bin (1st part below) and got a bunch of errors (2nd part below).
    Steps so far ...
    1) I imported the SensorTag project: C:\ti\simplelink\ble_cc26xx_2_01_00_44423\Projects\ble\SensorTag
    2) I selected both the SensorTag + SensorTagStack projects
    3) I added the post build steps
    4) I did a "clean" which automatically runs a "build all"
    Build throws errors (on the SensorTag project).
    Again, my goal is to simply create a .bin for uploading thru the android app.
    Appreciate if you could start from scratch & reply with the exact steps.

    Thanks,
    --Antonio

    ====================================================================
    CCS
    Right click on project > properties > Build > steps > post build steps
    Add these lines:
    "${CCS_INSTALL_ROOT}/utils/tiobj2bin/tiobj2bin" "${BuildArtifactFileName}" "${BuildArtifactFileBaseName}.bin"
    "${CG_TOOL_ROOT}/bin/armofd" "${CG_TOOL_ROOT}/bin/armhex" "${CCS_INSTALL_ROOT}/utils/tiobj2bin/mkhex4bin"

    ====================================================================
    "C:/ti/ccsv6/utils/tiobj2bin/tiobj2bin" "SensorTag.out" "SensorTag.bin"
    tiobj2bin.bat failed on ofd470
    Please see processors.wiki.ti.com/.../Tiobj2bin_Failed
    tiobj2bin.bat failed on hex470
    Please see processors.wiki.ti.com/.../Tiobj2bin_Failed
    'C:\Users\antonio\Documents\GitHub\TiProjects\SensorTag\FlashOnlyOAD\armofd' is not recognized as an internal or external command,
    operable program or batch file.
    'mkhex4bin' is not recognized as an internal or external command,
    operable program or batch file.
    mkhex4bin failure occurred. Giving up.
    "C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.6/bin/armofd" "C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.6/bin/armhex" "C:/ti/ccsv6/utils/tiobj2bin/mkhex4bin"
    error: failed to read "C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.6/bin/armhex"
    error: failed to read "C:/ti/ccsv6/utils/tiobj2bin/mkhex4bin"
    gmake[1]: [post-build] Error 1 (ignored)
    ' '

    **** Build Finished ****
  • 0 in reply to Tony Asaro
    Prodigy 150 points
    D'oh!! The CCS build steps need to be on the same line. Builds now.
    Gonna try the .hex file on my android phone - crossing fingers.
  • 0 in reply to Tony Asaro
    Prodigy 150 points
    Uploaded the .bin via the android app.
    After some time, app reported successful upload.
    The app suggested the sensortag would reboot itself + start flashing its LED.
    I waited and no response - no flashing, dead Jim :(

    I disassembled the sensortag & pulled out + re-inserted the battery.
    Its flashing again.
    I see the sensortag in the android app but when I attempt to connect, it says "Service Discovery Failed".
    I guess its running a default image.

    Very disappointed. Didn't expect it to be sooo hard to basically do nothing.
  • 0 in reply to Tony Asaro
    Prodigy 150 points

    Any help? My sensortag is not happy.

    Since the DEBUG DEVPACK is out of stock 'til next year, can you recommend an inexpensive alternative that works w/ CCS (local + cloud). 

    I'm just a hobbyist trying to keep costs of toys to a min. :)

  • 0 in reply to Tony Asaro
    TI__Mastermind 33460 points
    Hi Tony,

    Sorry to hear about your SensorTag. It can be remedied with a debugger and SmartRF Flash Programmer 2. I understand the other debuggers are higher cost, but you can use any of the ones recommended here: e2e.ti.com/.../471908

    XDS100 will likely be the cheapest, and will be a good investment as many other TI processors support it.