Can I configure GPIOTE to debug my signals?

RE: Can I configure GPIOTE to debug my signals?

endnode — Wed, 16 Aug 2017 08:30:32 GMT

HAL means Hardware Abstraction Layer, typically the lowest layer of any C/C++ API or SDK. Basically every driver is using it. I would say slow down, take blinky example, you wanted to blink with LEDs so spend some time with it until you are sure what are you doing.

RE: Can I configure GPIOTE to debug my signals?

ndarkness — Wed, 16 Aug 2017 08:16:54 GMT

@endnode thanks again, I take a look to the blinky example and GPIOTE example. Is HAL example also relevant for the GPIO? I cannot find any example of HAL on SDK12.2, where can I find that?

RE: Can I configure GPIOTE to debug my signals?

endnode — Tue, 15 Aug 2017 09:25:20 GMT

Sure, i use that for signalling with LEDs or just for reading with Logical analyzer/oscilloscope as well. There are all functions available in \components\drivers_nrf\hal\nrf_gpio.h header file (first configure the PIN as output and then use set/clear functions to set it LOW or HIGH.) There are also HAL and blinky examples in nRF5 SDK, have you searched any?

RE: Can I configure GPIOTE to debug my signals?

ndarkness — Tue, 15 Aug 2017 09:20:09 GMT

@endnode, thanks for your clarification. I would like to have at least one of the signal(that varies between 1/0) out to check how it since I will eventually use it for toggling orther device. Couldn't I even in that case set the signals out the pins?

RE: Can I configure GPIOTE to debug my signals?

endnode — Tue, 15 Aug 2017 09:13:59 GMT

Are you sure you are using right module? GPIOTE (as shortcut suggests) means General Purpose IO Tasks and Events, how you would like to utilize it for debug? You can either signal something with GPIO pulses (simple setting digital LOW/HIGH values on PINs you like), that has nothing to do with Task and Event functionality (that's useful if you want to detect some GPIO input change (= that's Event part) and do some action upon this trigger (= that's the Task part)).

But simple GPIO low/high won't output any "value" (not speaking about "float" type;))) unless you design some protocol on top of simple digital GPIO (low/high values). Serial data output over UART is typical example but you can use other things like SEGGER RTT... then again question is why you don't use these logging/debugging modules built into Nordic SDK examples and bother with GPIO(TE)???