I guess the internals of this uses a semaphore aswell to get realtime performance. If you control the semaphore yourself as per my example, you can check the status of the semaphore in the end of the

#api

One possible solution is to create a periodic timer and post to a semaphore in the timer callback. A thread could simply wait on the semaphore in an endless loop. Linux clock_nanosleep (mostly used to

#api

Have you done the initialization by running gpio_pin_configure with GPIO_OUTPUT_ACTIVE as third argument ? Just to be clear, you´re trying to set pin p0.05 ? That´s located on chip pin7 (QFN48 pkg) ?

#gpio #nrf52832

Are you sure that your board boots correctly? ( debug through gdb or just simple serial output ) What version of the SDK are you using? Is MCUBoot activated in your prj.conf?

#gpio #nrf52832