nRF52832, ports/GPIOs x internal peripherals, ports/GPIOs x wakeup from sleep, plus general HW doubts

RE: nRF52832, ports/GPIOs x internal peripherals, ports/GPIOs x wakeup from sleep, plus general HW doubts

Simonr — Thu, 12 Jan 2023 06:52:58 GMT

Yes, by configuring your application to use the internal LF crystal, this should also work with the internal RC oscillator, but as you say, it's not as accurate as an external one would be, so you need to calibrate at some points.

Best regards,

Simon

RE: nRF52832, ports/GPIOs x internal peripherals, ports/GPIOs x wakeup from sleep, plus general HW doubts

Abomin3v3l — Wed, 11 Jan 2023 20:39:25 GMT

Hi.

Is there any way, would it be possible? To make such function using the internal low frequency crystal? Because our hardware does not have the external low frequency crystal.

Regards.

RE: nRF52832, ports/GPIOs x internal peripherals, ports/GPIOs x wakeup from sleep, plus general HW doubts

Simonr — Wed, 11 Jan 2023 06:49:56 GMT

Yes, this should be possible. We already have the nRF Calendar example available in our unofficial GitHub that does just this. Note that it uses the external LF crystal by default though.

Best regards,

Simon

RE: nRF52832, ports/GPIOs x internal peripherals, ports/GPIOs x wakeup from sleep, plus general HW doubts

Abomin3v3l — Mon, 09 Jan 2023 20:04:18 GMT

Hi Simon.

The nRF52832 have 3x RTC (real-time counter).

Is it possible to implement a basic RTC (real-time 'clock') making a basic horary/calendar function? In the case of our first project with the 52832 we will use the internal 32.768KHz crystal oscillator.

Do you know that time scheme that count seconds passed since the start of 1970? How about if the nRF52832 receives via BLE such number of seconds, and activates a timer that generates an interrupt every 1 second, and then increment in 1 the value of seconds since the start of 1970? Consider that with some frequency the MCU would receive an updated value via BLE, because as the clock that runs the timer is not so accurate, with time there would be a lag.

Regards.

RE: nRF52832, ports/GPIOs x internal peripherals, ports/GPIOs x wakeup from sleep, plus general HW doubts

Simonr — Mon, 05 Dec 2022 06:48:14 GMT

Hi Jeferson

Yes, any of the pins marked as GPIOs, or "Px.xx" can be used to for example generate interrupts from logic level changes.

Best regards,

Simon

RE: nRF52832, ports/GPIOs x internal peripherals, ports/GPIOs x wakeup from sleep, plus general HW doubts

Abomin3v3l — Fri, 02 Dec 2022 16:24:48 GMT

Hello Simon.

Thank you very much.

Another question.

(9) Which GPIOs of nRF52832 can be used to generate interrupts through logic level change on the pin? ('0' to '1' or '1' to '0'). Any GPIO?

Regards.

Jeferson Pehls.

RE: nRF52832, ports/GPIOs x internal peripherals, ports/GPIOs x wakeup from sleep, plus general HW doubts

Simonr — Mon, 24 Oct 2022 13:59:30 GMT

Hi Jeferson

1. Yes, but please note that some of the GPIOs are configured for other usage by default, like the P0.09 and P0.10 are configured as NFCT pins, and P0.21 is configured as a RESET pin. However these can be configured as GPIOs as well if you'd like.

2. Yes, you can also configure any GPIO as the wake-up pin.

3. The number of each peripheral instance on the nRF52832 are listed in the product specification. I also attached them below:

And yes, some of them are shared. This can be found in section 15.2 Peripherals with shared ID in the product specifciation.

4. Yes, what I can see of your schematic looks okay.

5. Indeed, no problem there. These pins can be used at higher frequencies too, just not at the same time as the radio is running.

7. Again, please refer to the product specification section 37 SAADC.

8. Indeed, it has an internal RC oscillator that is fine for most uses, but you will get higher accuracy and lower current consumption by including an external 32.768 kHz crystal in your design. It is not needed for using any of the peripherals or features specifically AFAIK.

Best regards,

Simon