NRF52832 RTC2

RE: NRF52832 RTC2

ovrebekk — Fri, 25 Mar 2022 09:08:38 GMT

Hi Ben

How do you verify that the interrupt is not entering?

Are you connecting the debugger, or checking if the LED is toggling?

What is the supply voltage on the chip after you have charged?

What about during charging, will the supply voltage change?

[quote user="Ben_iot"]

I burned the rtc after charging, will the temperature damage the internal RC

crystal oscillator?

[/quote]

Do you know how high the temperature could get?

As shown here the nRF52832 should be fine with temperatures up to 125C when it is not in use.

Could you send me a closeup picture of your board?

Best regards
Torbjørn

RE: NRF52832 RTC2

Ben_iot — Thu, 24 Mar 2022 09:24:04 GMT

Hi ovrebekk

This situation happened again, and I used your example, 283288_rtc_test, the rtc interrupt is still

unable to enter, all the rtc can't work, it seems that the internal RC crystal is not working properly. This

board was working before. I burned the rtc after charging, will the temperature damage the internal RC

crystal oscillator?

RE: NRF52832 RTC2

ovrebekk — Fri, 11 Feb 2022 12:43:16 GMT

Hi Ben

No problem, just let me know when you have been able to test my example.

If the interrupt is not firing then the LED will not blink, so it should be very easy to check if the RTC interrupt is OK using that example.

Best regards
Torbjørn

RE: NRF52832 RTC2

Ben_iot — Fri, 11 Feb 2022 02:46:58 GMT

Hello ovrebekk

Thank you very much for your reply. After the RTC error occurred, we tried to burn our own program

and the official RTC example. There was no assert or some other error, but the RTC just couldn't enter the

interrupt. At the same time, the board with RTC exception can be used again。

and we have no way to test your program for the time being. If it comes later, let's test it again

RE: NRF52832 RTC2

ovrebekk — Wed, 09 Feb 2022 14:53:18 GMT

Hi Ben

Is there any chance that you have an assert or some other error condition in the code that could be causing the device to stop behaving properly?

What if you try this very simple example that only toggles P0.17 based on an RTC interrupt?

devzone.nordicsemi.com/.../283288_5F00_rtc_5F00_test.zip

If everything is working correctly you should see the LED turn on and off every second (looking at your schematic it seems you are using P0.17 for the LED).

Best regards
Torbjørn

RE: NRF52832 RTC2

Ben_iot — Wed, 09 Feb 2022 02:35:34 GMT

Hello ovrebekk

For the same board, at the beginning, the RTC was interrupted and could not be entered,

and the ble broadcast did not have a name. After more than ten days, I recharged the device, and

then burned the program, and the RTC function was normal again. So I haven't tested the ble_app_uart

example for now. Our hardware is not connected to a 32K external crystal oscillator

RE: NRF52832 RTC2

ovrebekk — Tue, 08 Feb 2022 12:31:34 GMT

Hi Ben

Would you be able to provide me the hardware schematics, and a picture of the affected board?

On second thought I realized that most of the SDK examples use external 32k crystal by default. Would you be able to run one more test where you make sure that the NRF_SDH_CLOCK_LF_SRC define in sdk_config.h is set to 0?

Best regards
Torbjørn

RE: NRF52832 RTC2

Ben_iot — Mon, 07 Feb 2022 01:55:47 GMT

Sorry for replying to you only now, the custom hardware we use, the ble example doesn't work either, we don't use an external 32k clock, we use an internal 32k clock, so is the internal 32k clock broken?

RE: NRF52832 RTC2

ovrebekk — Fri, 28 Jan 2022 09:07:16 GMT

Hi Ben

You mean to say that out of 20 devices you have one where the RTC doesn't seem to work anymore?

Are you testing this on a nRF52DK, or are you using some custom hardware?

Could you try to flash a standard BLE example into the failing board and see if it works, such as ble_app_uart?

If you can discover and connect to the device without any problems then the 32k clock must be working, since the SoftDevice is not able to function properly without it.

Best regards
Torbjørn