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.

CC1352R: False GPIO interrupt flag is set after Reset and enabled DCDC converter

Part Number: CC1352R


Tool/software:

Hello,

 We are developing a new device based on CC1352R, CCS V12.7.1 and the latest SDK V7_41_00_17.

The device has 3 buttons connected with external pull-ups 100kOhm and debouncing capacitors 22nF. The default configuration is "Input with Falling edge detection".

Only the first button is with configuration "Output, state Low". After the initialization of all peripheral modules, its configuration is changed to be "Input with Falling edge detection and enabled interrupt".

Since the software Watchdog is enabled, we noticed that very often after POR, manual Reset or Software Reset, the Watchdog is activated. The reason for this behavior was a bug in our code, which is already fixed.

But the main reason was that the ISR for the first button is activated almost immediately after the new configuration of the pin "Input with Falling edge detection" is applied.

What we checked:

1. Signal from the button - perfect. Long rising time because of the external debouncing capacitor t=RC=2.2ms. After 3t, this signal riches almost the maximum value of VDDS. No glitches, voltage drops or transitions between Low and High state .

2. This happens ONLY after Reset. We didn't reproduce the issue changing the configuration of the pin periodically (e.g., every 1s).

3. This issue exists ONLY if the internal DCDC converter is enabled. We didn't reproduce the issue using the GLDO.

4. I doesn't depend on the SDK. Tested with 2-3 SDKs.

5. The issue also exists if we use the example project from the SDK "gpiointerrupt". Of course, the project was modified a little bit to correspond to our project.

6. The issue was reproduced using the Lanchpad and adding additional deboucing capacitors to the buttons (22-100nF) to correspond to our project.

We already have a workaround, BUT the main questions are:

1. Why this issue (false event flag) exists ONLY after Reset?

2. Why this issue exists ONLY when the DCDC converter is enabled? If we simulate the behavior of the MCU (execution time) with delay in Standby mode, the false event flag doesn't exist.

Our concern is IF one independent flag could be set during the execution of the code ONLY because the DCDC converter is enable, how to rely on this product.

If you need I can give you the SDK example project prepared by use for test purposes.

Thank you very much in advance for your response.