• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 181 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.

Original question:

LP-CC2652R7: restore orignial firmware

LP-CC2652R7: Trouble getting started with Launchpad

Kent Hauser
Prodigy 40 points
Part Number: LP-CC2652R7
Other Parts Discussed in Thread: CCSTUDIO, CC2652R7, UNIFLASH,

Tool/software:

I am having trouble getting started with the LaunchPad board. I am trying to port an application I have written for another (non-ti) part to the device, but am having all kinds of trouble getting my footing with the development tools and the SDKs. I am new to the TI tools, but have decades of experience with embedded development and Bluetooth.

What I am hoping for is a "state of the development environment" as of July 2024 so that I know what should work and which tools I should be using. I am trying to develop on both ARM and Motorola Macs.

I first downloaded and tested the iPhone "Simplelink Started" app & successfully tested the lights & switches functions of the app with the factory software in the LaunchPad.

I then tried to compile and install the "project_zero" software so that I could validate I had a working development environment. 

I tried installing the CCStudio IDE (Theia Framework), but could not locate the proper SDK to allow me to develop with the CC2652R7. Found many broken links in the documentation so I don't know if I just couldn't find the proper SDK or if it's not supported. The documentation said "most targets" are supported by the "newer Theia" framework, but of course I only care about the CC2652R7 and I found no indication one way or the other.

I then tried installing the (classic) Eclipse CCStudio IDE (Version: 12.7.1.00001) and found an SDK for the CC2652R7 (ie simplelink_cc13xx_cc26xx_sdk_7_41_00_17). I copied the examples to my "Project Explorer", and used the "Build" links as described in getting started to build the "bim" and "project_zero" targets. A copy of the project explorer is shown below.

I then used the "Debug As" link to install software and had both "bim" and "project_zero" stop at break. However, when I restarted the software only the Left button (BTN-1) would be displayed on the the iPhone App. The LED buttons on the iPhone app also no longer controlled the lights on the LP -- the lights stay off. I didn't fire up any debug tools (eg WireShark) to decode what was going on as I was just trying to debug development environment, not the software.

I then tried to follow the instructions at LP-CC2652R7: restore orignial firmware using the cloud UNIFLASH installer. I could not find exact matching hex file names (ie there was not file name ending in "_oad.bin". I used the  following command to look for files in the SDK. I used the Release/bim_offchip.hex and project_zero_unsecure_app.hex, but got same result as before. Most likely I failed to program anything using the cloud programmer.

% cd ~/ti/simplelink_cc13xx_cc26xx_sdk_7_40_00_77
% find examples -name \*.hex | grep -i cc2652r7
examples/nortos/LP_CC2652R7/bim/hexfiles/bim_dual_onchip/Release/bim_dual_onchip.hex
examples/nortos/LP_CC2652R7/bim/hexfiles/bim_dual_onchip/Debug/bim_dual_onchip.hex
examples/nortos/LP_CC2652R7/bim/hexfiles/bim_offchip/Release_unsecure/bim_offchip.hex
examples/nortos/LP_CC2652R7/bim/hexfiles/bim_offchip/Debug_unsecure/bim_offchip.hex
examples/nortos/LP_CC2652R7/bim/hexfiles/bim_offchip/Release/bim_offchip.hex
examples/nortos/LP_CC2652R7/bim/hexfiles/bim_offchip/Debug/bim_offchip.hex
examples/nortos/LP_CC2652R7/bim/hexfiles/bim_onchip/Release_unsecure/bim_onchip.hex
examples/nortos/LP_CC2652R7/bim/hexfiles/bim_onchip/Debug_unsecure/bim_onchip.hex
examples/nortos/LP_CC2652R7/bim/hexfiles/bim_onchip/Release/bim_onchip.hex
examples/nortos/LP_CC2652R7/bim/hexfiles/bim_onchip/Debug/bim_onchip.hex
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/offChipOad/erase_storage_offchip_cc13x2lp.hex
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/offChipOad/ticlang/rfOADClientExtFlash_LP_CC2652R7_app_v2.hex
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/offChipOad/ticlang/rfOADClientExtFlash_LP_CC2652R7_app_v1.hex
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/offChipOad/ticlang/rfOADClientExtFlash_LP_CC2652R7_all_v1.hex
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/offChipOad/bim_offchip.hex
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/onChipOad/bim_onchip.hex
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/onChipOad/ticlang/rfOADClientIntFlashUApp_LP_CC2652R7_app_v2.hex
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/onChipOad/ticlang/rfOADClientIntFlashPApp_LP_CC2652R7_all.hex
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/onChipOad/ticlang/rfOADClientIntFlashUApp_LP_CC2652R7_app_v1.hex
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/onChipOad/ticlang/rfOADClientIntFlashPApp_LP_CC2652R7.hex
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/MCUBootOad/ticlang/rfOADClient_LP_CC2652R7_app_v1.hex
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/MCUBootOad/ticlang/rfOADClient_LP_CC2652R7_app_v2.hex
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/MCUBootOad/ticlang/rfOADClient_LP_CC2652R7_all_v1.hex
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/MCUBootOad/mcuboot_LP_CC2652R7.hex
examples/rtos/LP_CC2652R7/ble5stack/hexfiles/simple_central_app.hex
examples/rtos/LP_CC2652R7/ble5stack/hexfiles/simple_peripheral_app.hex
examples/rtos/LP_CC2652R7/ble5stack/hexfiles/project_zero_unsecure_app.hex
examples/rtos/LP_CC2652R7/ble5stack/hexfiles/host_test_app.hex
% find examples -name \*.bin | grep -i cc2652r7
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/offChipOad/ticlang/rfOADClientExtFlash_LP_CC2652R7_app_v1.bin
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/offChipOad/ticlang/rfOADClientExtFlash_LP_CC2652R7_app_v2.bin
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/onChipOad/ticlang/rfOADClientIntFlashUApp_LP_CC2652R7_app_v1.bin
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/onChipOad/ticlang/rfOADClientIntFlashUApp_LP_CC2652R7_app_v2.bin
examples/rtos/LP_CC2652R7/prop_rf/hexfiles/onChipOad/ticlang/rfOADClientIntFlashPApp_LP_CC2652R7.bin

I then installed the "cloud" version using the Chrome browser on the M1 Mac. A screen shot of the environment is shown below.

When I tried to select "build", I got repeated error messages "Trouble Halting Target CPU: (Error -2064 @ 0)".

When I tried to follow the "Getting started guide" I got this: 

Obviously, I'm flailing. If you could point me to the best supported environment, with complete URLs (as of July 2024) I'd appreciate it. I would also like instructions for how to restore the LP-CC2652R7 firmware to it's original state as well.

Sorry for the long post, but I wanted to show what I'd done so it would be obvious to someone who knows what they are doing what I've done wrong.

Thanks.

  • 0
    TI__Mastermind 33640 points

    Hi,

    Thank you for reaching out! I truly apologize you have run into issues during the setup of your dev board and development system. To clarify, you should be able to use either the original CCS or the Theia version with the LP-CC2652R7. The latest SDK for this device would be the 7.41 (https://www.ti.com/tool/download/SIMPLELINK-LOWPOWER-F2-SDK) which is the one you have.

    I see you are having issues debugging/flashing the project zero project. I expect the issue here is that project zero is an OAD project which must be flashed in a specific way (through Uniflash with the BIM at the base address and the actual app at a certain offset). This is only necessary for OAD projects, if you were to debug a non-oad enabled project such as simple_central or simple_peripheral, then you should be able to debug these easily through CCS via the debug button.

    I would highly recommend reference our SimpleLink Academie which provide a lot of hands-on knowledge and theory on our devices, sdk, and technology. The SimpleLink Academy is a set of labs/modules which cover a wide variety of topics to learn how to use your device. These labs may be found here: https://dev.ti.com/tirex/explore/node?node=A__AEW1O8IFGp0P7hUJIZnV4A__com.ti.SIMPLELINK_ACADEMY_CC13XX_CC26XX_SDK__AfkT0vQ__LATEST

    I would suggest starting with the Bluetooth Low Energy 5 Fundamentals to get started and then work through the labs that cover topics that are relevant to your project. We do have two OAD labs that discuss how to use OAD and flash it using our devices. These labs are called the BLE Enhanced OAD Fundamentals & BLE Enhanced OAD Advanced labs.

    If you have any issues with these labs or with debugging/flashing while following the instructions contained in the lab, then please let me know and I would be more than happy to help.

    Best Regards,

    Jan

  • 0 in reply to Jan
    Prodigy 40 points

    Thanks for your advice regarding CCS Theia. When I had trouble with the Theia version I saw in the release notes "Code Composer Studio Theia v1.4.1 is recommended for production development with MSPM0, and MSP430 devices.  CCS Theia includes optional support for Wireless connectivity (not WiFi)", so I figured wireless support was WIP.

    And sorry I buried the lead on my ProjectZero troubles. My real problem was with missing files and the ProjectZero not working as expected when I compiled and installed it.

    When I tried to follow instructions from Restore Original Firmware, the "Out-of-Box experience" tab said to flash "ble5_project_zero_cc13x2r1lp_app_FlashROM_Release.hex". The corresponding CC2652R7 "project zero" directory in the SDK does not contain a "FlashROM" file, though it is mentioned in the README file in the project directory. 

    I also mentioned I built the BIM_OFFCHIP & ProjectZero examples from the SDK. After I flashed the projects (BIM then ProjectZero as oad.bin & later hex) the LED function of Project Zero stopped working. Also button 1 was registering as button 2, and button 2 not registering at all. To me that means I was successfully flashing new firmware (because LP was behaving differently), but there is some bug in example (because LP was behaving differently). 

    As to the BLE Fundamentals, I would note that he Links to "BLE fundamentals" on the CC2652R7 product pages are broken. Google search picks up something for CC26x0. Another google hit is for CC26x2, which maybe applies to CC2652R7. It is not clear to someone new to Ti parts which digits are important to match. Seems CC13xx & CC26xx use same software, but CCxxx0 and CCxxx2 are very different. Hard to tell about CC2652 & CC2652R1. I notice the the "magic number" (initial bytes in binary file) for the CC2652R7 binaries begins with "C,C,2,6,5,2,R,1", so I guess the ...R1 & ...R7 parts are close.

    So to summarize:

    1) thanks for the info on the Theia Code Composer.

    2) I'd like a pointer to the appropriate "FlashROM_Release.hex" file for the LP-CC2652R7 as described above.

    3) I'd appreciate it if someone could try the ProjectZero example from "simplelink_cc13xx_cc26xx_sdk_7_41_00_17" on an LP-CC2652R7 to see if it functions correctly. If not, a pointer to a working version in a different SDK would be appreciated.

    Thanks, Kent

  • 0 in reply to Kent Hauser
    TI__Mastermind 33640 points

    Hi Kent,

    My apologies, the documentation seems to be a bit out of date. The FLASHROM reference was from a much older SDK, so this name is not accurate.

    Regarding the buttons not working as expected, could you take a picture of your LaunchPad and include the revision of the launchpad? That behavior is definitely not expected. It would also be helpful to obtain a picture of the markings on the IC itself.

    The broken links probably broke after a naming change, but I can confirm that the lab provided does work for the CC2652R7. I do not have an R7 board with me right now, but I will source one soon. In the meantime, can you provide the images requested to see what might be going on?

    Best Regards,

    Jan

  • 0 in reply to Jan
    Prodigy 40 points

    As requested, here are front/back views of the LP-CC2652R7. I couldn't read anything off the chip, but can send any internal registers you need. I tried to resize the image down, but the preview doesn't work for me??? If you're looking for info from back it reads: BOM Rev: A, FW: SDK5.30, 2214. The date code on the PCB itself if 2134. I bought it directly from TI last month.

    As a side note, I was trying to follow the Academy Custom Profile tutorial, but with the SimplePeripheral demo. I found that the "Example Service Generator" did nothing when I typed "generate". I tried it in Safari, then Chrome (both on M1 Mac), then on a Win11 machine. I then found this link in the E2E archive LAUNCHXL-CC1352R1: SimpleLink Academy BLE custom profile - custom profile generator produces no output. When I tried the older version linked there, my custom service was generated, but wouldn't compile. I'm using 128-bit UUIDs for service & characteristic and the generated code treats them as 16-bit. 

    At least at this point, my existing mobile app talks nicely with the LaunchPad. I guess I just need to figure out the iCall mechanisms to graft my application code in.

    Thanks for your help.

    FroneBack

  • 0 in reply to Kent Hauser
    TI__Mastermind 33640 points

    Hello,

    It seems the images did not go through with the image. Could you try to reattach them? Based on the info provided, it does seem like the board itself should be okay.

    Regarding the custom profile generator, I apologize for the inconvenience, we were very recently made aware that it was not working as intended and we are looking to fix it soon. In the meantime, you can change the simplelink academy version in TI Resource Explorer to be an older version which should work. Can you share the errors that you are getting during compile time?

    I am glad to hear that you were able to get the app set up with the launchpad! :) To learn more about iCall, I suggest reading through the user's guide's section on icall and referencing the code within simple_peripheral to get a feel for how its used. If you have any specific questions about iCall, then I would be more than happy to help there as well.

    Best Regards,

    Jan