This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Marketing docs differ from product spec re nRF52810 count of RTC's: RTC2 is absent?

The Nordic nRF52810 Product Brochure and a module manufacturer Raytac's documents say the nRF52810 has three RTC's.

This post by a Nordic employee says the nRF52810 has just two RTC's:   https://devzone.nordicsemi.com/f/nordic-q-a/29071/main-differences-between-52810-and-52832/115283#115283

Also, files in the 14,2 SDK such as device/nrf52810_peripherals.h define RTC_COUNT equal to 2.

Which is correct?

This bit me because I was developing for the nrf52810 on the 52DK, using RTC2, and it seemed to work.  Probably I was not using the correct compiler defines (maybe I was using -DNRF52 instead of -DNRF52810_XXAA and -DDEVELOP_IN_NRF52832.)  When I switched to more correct compiler defines for some but not all of my code, it seemed to compile, but stopped working, with a hardfault.  I would stress that using the newer SDK,  a developer must define a very specific chip such as -DNRF52810_XXAA (and not just -DNR52 or -DNRF52810) and the developer must do so for ALL their code, including libraries that might reference RTC2 or other peripherals that are absent from the 52810.

Parents
  • The writer encountered an issue while developing code for a specific device called the nrf52810 on a development board called 52DK, using a module called RTC2. Initially, the code seemed to work, but it later stopped working with a "hardfault" error. The writer believes the issue may be due to using incorrect compiler defines. Specifically, they may have been using -DNRF52 instead of the more specific -DNRF52810_XXAA and -DDEVELOP_IN_NRF52832. The writer emphasizes that when using the newer SDK, it is crucial to define the specific chip being used (e.g., -DNRF52810_XXAA) for all code, including libraries that may reference peripherals such as RTC2 that are not present on the 52810.

Reply
  • The writer encountered an issue while developing code for a specific device called the nrf52810 on a development board called 52DK, using a module called RTC2. Initially, the code seemed to work, but it later stopped working with a "hardfault" error. The writer believes the issue may be due to using incorrect compiler defines. Specifically, they may have been using -DNRF52 instead of the more specific -DNRF52810_XXAA and -DDEVELOP_IN_NRF52832. The writer emphasizes that when using the newer SDK, it is crucial to define the specific chip being used (e.g., -DNRF52810_XXAA) for all code, including libraries that may reference peripherals such as RTC2 that are not present on the 52810.

Children
No Data
Related