Stuck on power down due to GPIO

RE: Stuck on power down due to GPIO

Susheel Nuguru — Fri, 03 Aug 2018 19:33:11 GMT

Thanks for letting us know Gowtham, I will then mark this case closed.

RE: Stuck on power down due to GPIO

TS Gowtham — Thu, 02 Aug 2018 15:41:57 GMT

Hi again, sorry for the delay in replying.

I believe the issue has been solved but I do not know what has fixed it. I realised that the problem was not occurring anymore few weeks ago. The code has been changed quite a few times in between, so I can't find out the solution.

Thanks for your help

RE: Stuck on power down due to GPIO

Susheel Nuguru — Mon, 02 Jul 2018 19:50:08 GMT

Hi Gowtham,

did you manage to solve this issue? I would appreciate it if you can help other forum members by giving a solution so that it can benefit them in future.

RE: Stuck on power down due to GPIO

Susheel Nuguru — Wed, 13 Jun 2018 12:07:06 GMT

SES debugger just stops randomly after 1-2 minutes, this is in itself strange.

Are you sure that your project settings with memory is correct? seems like the debugger does not able to track the stack could be a hint that there is a stack corruption, which would explain why your debugger initially thought that the problem was in nrf_gpio_pin_set

RE: Stuck on power down due to GPIO

TS Gowtham — Mon, 11 Jun 2018 08:49:53 GMT

Sorry for the late reply,

I have been trying to replicate the problem and check the stack call trace but SES debugger just stops randomly within 1~2 minutes without any error. So I'm unable to replicate the problem and check the stack call trace after the problem occurs on SES. Can you suggest any other tool or debugger I can use to check the stack call trace?

RE: Stuck on power down due to GPIO

Susheel Nuguru — Wed, 06 Jun 2018 12:48:55 GMT

it must be stuck somewhere else, not in the gpio_set function. Make sure that the app has not hardfaulted. Using RTT logs to narrow this down will be slow and tedious, start the debugger and run the code for sometime and halt the cpu, check the stack call trace.

RE: Stuck on power down due to GPIO

TS Gowtham — Wed, 06 Jun 2018 12:17:32 GMT

We are facing this issue with Visual Studio with VisualGDB and Segger Embedded Studio. I had placed RTT statements to check this issue.

RE: Stuck on power down due to GPIO

Susheel Nuguru — Wed, 06 Jun 2018 12:10:03 GMT

ah, sorry, I thought they are physically connected.

Problems like this should be easily be detectable when you are running the debugger. But you say that "On debugging the board, the program stops when a nrf_gpio_pin_set(PIN) is called" This should not happen since there is nothing in this functions that could make the CPU loop. Maybe your debugger is not showing the correct call trace? Which IDE and compiler are you using? are you debugging with the code that is compiled with 0 optimizations?

RE: Stuck on power down due to GPIO

TS Gowtham — Wed, 06 Jun 2018 11:56:43 GMT

The issue is occurring on the nRF52, not the nRF51. None of the pins on the nRF51 are used here. The nRF51 is just used to connect to the nRF52 via BLE and get some data. FYI, the nRF 51 and nRF52 are not physically connected.

RE: Stuck on power down due to GPIO

Susheel Nuguru — Wed, 06 Jun 2018 11:29:13 GMT

Since the power toggling works correctly when not connected to nRF51, it seems that this pin on nRF51 is configured with wrong pull. Can you keep the input configuration of this pin on nRF51 side with no pulls.