• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 272 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.

Original question:

CC2640R2F: cc2640 custom board reset problem.

CC2640R2F: Code working on LAUNCHXL-CC2640R2 eval board but not on custom Hardware CC2640R2L

Sarthak Tanwani
Intellectual 340 points
Part Number: CC2640R2F
Other Parts Discussed in Thread: LAUNCHXL-CC2640R2, CC2640R2L

Hi,

My problem is very similar to the related e2e thread. I have a custom hardware based on CC2640R2L MCU. I program the custom hardware via the debugger on LAUNCHXL-CC2640R2. When I program the custom hardware, for example with the pinStandby example code, it works perfectly well during and after debug, when I programmed the MCU. As soon as I reset the MCU, it stops working completely.

The program stops at the first call to sleep() functions and then never proceeds further. As it is here on line 72.

I am using Simplelink sdk version 4.40 and TI compiler version 20.2.3.

Kindly let me know how to solve this issue. Thanks.

  • 0 in reply to FI
    Intellectual 340 points

    No, I went through both the e2e threads and those issues are different. I didn't face my issue when I programmed the device with adcsinglechannel example code. It means flashing code is not causing the problem, flashing certain example codes is(like the pinStandby and pinShutdown example code).

    I am facing an issue because of the sleep() function.

    When I am using the device with BLE Stack, the advertising works perfectly as I can see it on my phone. But as soon as I try to connect, the device does not respond.

    As I have read, The power policy automatically tries to put the device in lowest power consumption state at each time. When the power policy tries to put the device in sleep after I try to connect, the device stops responding. It is showing the same behaviour with the pinStandby function. As I am not able to debug this issue, (during debug the debugger does not let the device go to the sleep state) I used an LED to indicate that after line #72 the device stops responding.

    I am actually using custom hardware, so in order to limit any hardware limitation, I implemented internal RCOSC on basic simple_peripheral example code. I performed the following steps from this link: Developing a Bluetooth Low Energy Application — Bluetooth Low Energy Software Developer's Guide 3.00.01 documentation

    But still the bluetooth connection is unstable. The only change I observed is that I am now able to connect to the device. After I read some values, or simply after some time the device disconnects automatically.

    I am not facing any such issue with the LAUNCHXL-CC2640R2 eval board.

    I can observe the difference when I try to connect to my custom hardware with and without internal RCOSC configuration. In both cases, the advertisement is working. But when I try to connect and internal RCOSC is not configured, I am not even able to connect. With the internal RCOSC cofigured, I am able to connect to the device but the connection is unstable and disconnects after some time.

  • 0 in reply to Sarthak Tanwani
    Expert 2160 points

    It sounds like you have some design issues, most likely poor layout. You 32 kHz crystal oscillator is probably not tuned correct also. Refer to this application note: https://www.ti.com/lit/pdf/swra640 and submit your design for a review.