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.

CC2650: simple_peripheral_cc2650lp_app example Hwi Exception | CC2650F128RGZx

Part Number: CC2650


Hi,

I have the same problem as original post, wondering if the problem was resolved or not? actually my case is slightly different as i am using (Buy CC2650 CC2650F128RGZx Core Board Wireless Module M3 TI-TROS IDE IOT Development ARM Cortex-M3 2.54mm 48pin for Smart ZigBee Online at Low Prices in India - Amazon.in) this board with SDK examples, I have tried simple peripheral example of both lp, em and bp boards, all of them get stuck at the same point:

I wonder, since i am using a different board do i need to make any changes to the board.c file, and what changes should i make since i don't have any schematic of this board. Please let me know if anybody can help me with this problem.

Thanks,

Najeeb Uddin

  • Hey Najeeb,

    Have you tried this on a launchpad? This can very likely be due to a hardware issue so you will need to have the schematic before making any changes to the board.c file. Once you have this, do a quick diff of our Launchpad's schematic to note any major differences, as there may be an issue there.

    You can try to read the HWI exception code that is returned, but the first thing I would do is double check the hardware works.

  • Hi, I found out that it get stuck in an exception handler, I decoded the exception in the image below

    I don't have the board schematic. from this exception decoding, can you tell me what might be causing this problem ?

    PS: I am running the sensortag example in the image above.

    Thanks,

    Najeeb Uddin

  • As a sanity check, did you also flash the stack project?

    Here's a link to a guide (designed for CC2640R2 but the concepts still apply):

    Running the SDK on custom hardware:

    Debug CPU exceptions:

    Look through the "Running the sdk on custom hardware" to make sure the pins are mapped out to your custom board, along with the other points in the guide. You may need to do some translation to the CC2650 equivalents of the references in the CC2640R2 guide. There's not enough information in the image, but if you are using an modified SDK example I would not debug this as a "memory issue".

    Unfortunately I cannot assist much further without a schematic. I suspect the issue is either a hardware issue or a mismatch between the example project's pin assignments. You will need to modify the project to match your custom hardware.

  • As a sanity check, did you also flash the stack project?

    I am not sure I did that (sorry I am new to the CC2650, although I did read the SDK docs and that does not clearly specify how to run their examples). I imported both the app and stack project to the workspace and pressed the debug button on the app project, I thought that's all you have to do!

    Thanks for the help.

  • No worries! Let me know if that ends up being the issue :)

  • So, first I pressed debug button on the stack project and then I the stopped the project and then pressed the debug button on the app project. Now it does not get stuck in Hwi, the exception in Hwi(ROV) shows "No data to dispaly". Now when I pause it, it seems to get stuck at some other address but ccs cannot find the source, as shown in the image below:

    Although the task tab (ROV) does show idle task is running. it is possible that it is stuck at idle loop in idle task. Anyways the Simplelink Starter app on my phone shows SimpleBLEPeripheral but it comes and goes and when I try to connect, it does not connect. After 5 tries of the connection the SimpleBLEPeripheral disappears from the BLE device list.

    So what do you say? is it still the hardware issue or I am getting something wrong?

    Thanks,

    Najeeb

  • Hey Najeeb,

    Glad to hear we're making good progress. Seeing the peripheral on your phone is a great sign. What phone are you using to test? I can try to do a quick test on a LaunchPad to see if I'm also able to reproduce this issue.

    The custom hardware section sheds light on the potential issues that can occur if a device running on different hardware is not properly configured. A quick example is related to sleep clock accuracy. If the device uses a different crystal, the BLE stack needs to be configured for the crystal's accuracy if it's different than our LaunchPads.

  • Hi Ammar,

    Yeah it worked, it seemed to be a crystal issue, I used crystal less mode in simple_peripheral_cc2650em project, following the instruction in section 6.6 in swru393 document and now simplelink starter app successfully connected to the SimpleBLEPeripheral.

    Thanks a lot Ammar, it would not have been possible without your help.

    Thanks agian,

    Najeeb Uddin