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.

LAUNCHXL-CC2650: Problem with my SNP

Part Number: LAUNCHXL-CC2650
Other Parts Discussed in Thread: CC2650, EK-TM4C123GXL

Hello,

I burned a hex file on my CC2650 to implement the BLE stack in the form of the simple network processor (SNP). However, I am not receiving the expected result. My output is (on the TExaS display):

Application Processor - TM4C123-CC2650

Reset CC2650
LP->SNP FE,03,00,55,04,1D,FC,01,B2
from SNP fail
Get Status
LP->SNP FE,00,00,55,06,53
from SNP fail
Get Version
LP->SNP FE,00,00,35,03,36
from SNP fail
Add service
LP->SNP FE,03,00,35,81,0
Add service
LP->SNP FE,03,00,35,81,01,F0,FF,B9
from SNP fail
Add CharValue
LP->SNP FE,08,00,35,82,03,0A,00,00,00,02,F1,FF,BA
from SNP fail
Add CharValue
LP->SNP FE,08,00,35,82,01,02,00,00,00,02,F2,FF,B3
from SNP fail
Add CharValue
LP->SNP FE,08,00,35,82,02,08,00,00,00,02,F3,FF,BB
from SNP fail
Add Notify CharValue
LP->SNP FE,08,00,35,82,00,10,00,00,00,02,F4,FF,A6
from SNP fail
Add Notify CharValue
LP->SNP FE,08,00,35,82,00,10,00,00,00,02,F5,FF,A7
from SNP fail
Register service
LP->SNP FE,00,00,35,84,B1
from SNP fail
Set Device name
LP->SNP FE,16,00,35,8C,01,00,00,53,68,61,70,65,20,74,68,65,20,57,6F,72,6C,64,20,30,30,31,CB
from SNP fail
SetAdvertisement1
LP->SNP FE,0B,00,55,43,01,02,01,06,06,FF,0D,00,03,00,00,EE
from SNP fail
SetAdvertisement Data
LP->SNP FE,1F,00,55,43,00,14,09,53,68,61,70,65,20,74,68,65,20,57,6F,72,6C,64,20,30,30,31,05,12,50,00,20,03,02,0A,00,1D
from SNP fail
StartAdvertisement
LP->SNP FE,0E,00,55,42,00,00,00,64,00,00,00,00,01,00,00,00,C5,02,BB
from SNP fail
Get Status
LP->SNP FE,00,00,55,06,53
from SNP fail

Any thoughts?

  • Hello Ariel,

    I am working to find the appropriate expert to help you. This may take some time to reach the right person depending on availability. Please expect an update by 7/28. I appreciate your patience.

    In the meantime, can you please clarify what SDK version you are using?

    Regards,

    Luis

  • Hello Luis,

    I think that is irrelevant since the problem lies in programming the CC2650 with a custom SNP, or even with the .hex image supplied from factory, using the SmartRF Flash Programmer.

  • I see. Thanks for the clarification.

    Can you please elaborate a little bit further? A detailed setup and steps to duplicate your issue would help greatly. In particular, something that is not clear is if your hex file is custom (made by you) or anything we provide. Also, it is not clear where you are observing this textual output.

    Looking forward to hear from you.

    -Luis

  • The instructions I followed:

    Step 1) Search TI.com for “Smartrf flash programmer”. Download and unzip a file called flash-programmer-2-1.7.4.zip. In administrator mode, install the application, Setup_SmartRF_Flash_Programmer_2-1.7.4.exe

    Step 2) Download and unzip hex files from this web link ble_2_02_simple_np_setup.exe These hex files (object code) implement the BLE stack in the form of the simple network processor (SNP). This download creates two directories: one with files for the BoosterPack (cc2650bp) and one with files for the LaunchPad (cc2650lp).

    Step 3) Find this hex file on your computer: simple_np_cc2650lp_uart_pm_xsbl_mooc.hex Notice the letters lp (for LaunchPad) and mooc.

    Step 4) Use the Flash Programmer to burn this hex file onto your CC2650 LaunchPad

    The textual output is displayed on the TExaSdisplay application.

    Please note I have already discussed this thoroughly with my professors however the conclusion was that it is most likely a hardware issue.

    Thank you for your time.

  • Ariel,

    Did you draw any conclusions on your problem? Did you find out the root cause?

    If not, please let me know and I can try to help.

    -Luis

  • No, please try to find the root cause. If you are unsuccessful please begin a replacement process for the part.

    Ariel

  • Ariel,

    I'd be glad to help more.

    There's a lot more information that I need to get from you in order to be able to help you. Especially, about what happens between step 4 and when the error occurs.

    You've only have mentioned CC2650, in the form of a LaunchPad, acting as a network processor.

    So, let me ask you a few questions:

    1. Did the programming of the hex file complete successfully? It should look like this. I used v1.8.1 and programmed the hex with no issues.
    2. Before we continue, please tell me about the TExaS display that you've mentioned. I'm not familiar with it. 
    3. Please describe your setup.
      1. What is the other board that communicates with the CC2650? You mentioned the TM4C123 processor. Is it EK-TM4C123GXL? I can't get enough details from the video you posted.
      2. How do the two boards connect? Have you verified that all the connections are valid and correct?
      3. Have you attempted to connect your CC2650 LaunchPad to another instance of the application processor? (if available). We're trying to find if the SNP is the problem, or the App processor is the problem (or the connection, which I mentioned in last step). 
    4. What firmware does your application processor have? What steps did you take to verify that the problem does not lie in the app processor and not in the SNP?
    5. What other steps have you taken to troubleshoot the hardware? Used any oscilloscopes, DMM, etc?

    If you decide to go that route, please go to https://ticsc.service-now.com/ in order to request a replacement.

    Looking fw to hear from you.

    Thanks,

    Luis

  • 1. Yes the hex file programmed successfully.

    2. TExaSdisplay provides interaction with your serial port software running on the LaunchPad. TExaSdisplay is like HyperTerminal or PuTTy but much simpler, it also emulates a graphics display (Nokia display).

    3. The other board is the EK-TM4C123GXL. The boards appear to connect properly (I connect the TM4C123 to my laptop and the connected CC2650 gets powered as well, is there are another way to check the connection?). I have not attempted connecting to another application processor for I only have the TM4C123.

    4. I’m not sure what you mean by application processor may you please elaborate.

    5. I have only used the TExaSdisplay Text I/O to troubleshoot which provided me with the output I pasted in my original post.

    Thanks,

    Ariel

  • Ariel,

    Thanks for your answers. 

    On #4, I meant that the application processor is the TM4C123. On #3, I meant that if you have access to another  EK-TM4C123GXL, you could check if the problem is the EK or the CC2650.

    Please go to https://ticsc.service-now.com/ in order to request a replacement.

    -Luis