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.

Project Zero CC2650 Launchpad problems with SmartRF Flash Programmer

Other Parts Discussed in Thread: CC2650

Hi everybody,

I am starting with the CC2650 device, concretely I'm using the CC2650 Launchpad.

First I followed the instructions at the CC2650 LaunchPad User's Guide for Bluetooth Smart. Secondly I followed the steps to Redirect LCD writes to UART. All of this has been applied to the LAUNCHXL Project Zero, and it runs ok at the Code Composer. However, If I write this project (App and Stack) with the SmartRF Flash Programmer 2, although the writting finish succesfully, the program not runs (No Uart prints, no leds,..). What could be happening?  It will be something about project configuration? Or rather about Flash Programmer?

Thanks.

  • Can you try to read back the flash image program by CCS and Flash programmer?
  • I test ProjectZero from CCS cloud and it works fine. I would suggest you to use CCS cloud to test it.
  • Thanks Yikai.

    The problem is not the CCS. In fact, the program runs ok at CCS, in their classical software version too.


    Thanks.

  • Thanks Christin,

    How can I read back the flash image with CCS?
  • I have a CC2650 Launchpad Rev 1.1. and according to this link, at the "Important note on versions" section, there are some things that is not possible to do with this launchpad version. It will be related with my problem?

  • What I meant is program with CCS and read back the flash content from flash programmer 2.

    Then used the generated hex files, programmed with flash programmer 2, and read back from flash programmer 2.

    Compare the content from both readout.
  • Thanks Christin,

    I get it now. I've just do it, and after generate the files, I put it the contents in Excel sheet. I use "EXACT" function in order to know if there are some differences. Left column is the bytes readed after program the system with CCS, and right column is the read values after program the system with the hex files. The result are these:


    I have 4 bytes different at the page 12:



    Page 29 and 30, all bytes are different. (Although I don't know if there is a real mistake, because it's a 0x00 vs. 0xFF value):

  • Hi Dav,

    I am not sure what contributes to the change on pg12, but since ProjZero uses OSAL_SNV=2 the difference you are seeing starting at 0x1D00 is caused by the fact that the image pulled from the device has already initialized the SNV region (the stack does this at start).

    A couple things for you to try:
    1. How are you merging app and stack? Can you try using the hexmerge tool within the IntelHex module pypi.python.org/.../IntelHex
    2. Download app with Flash Programmer 2, attach to running target in CCS and see the state of the proc?
  • Hi Sean2,

    Thanks for your help. I tried the first option and I have some questions about your proposals.

    1. Answering your question, I could say that until now I not merge the hex files, I flashed it with the multiple option of Flash Programmer. After merge with python, I get a new hex file (330k) using App hex file (125k) and Stack hex file (159k). After merge I flash the merged file with the "single" option of Flash Programmer, but nothing occurs. The system doesn't start.

    2. What do you mean? If I download the App with Flash Programmer and after this I lunch the program with CCS, this overlap the app, don't you?