Mike Dunston

I believe most of the Gpio implementations have already moved off GpioWrapper already.

I can't say for certain on that, it is still used by a handful of target (STM32 being one).

`std::enable_if` is only available in C++14 which is not available by default in arduino-esp32 (possibly other platforms). We will need a fallback option when using C++11 (which is really old!)

Ahh, I landed on a diff page that stated C++14. If we can craft the necessary magic we can certainly go that route.

https://github.com/RobertPHeller/openmrn/blob/LinuxGpio-no-GpioWrapper/src/os/LinuxGpio.hxx#L93 declares the template type as "int". https://github.com/RobertPHeller/openmrn/blob/LinuxGpio-no-GpioWrapper/src/os/LinuxGpio.hxx#L175 defines the type as "gpio_num_t" (define to [unsigned int](https://github.com/RobertPHeller/openmrn/blob/LinuxGpio-no-GpioWrapper/src/os/LinuxGpio.hxx#L79)). I'd suggest drop all usages of `gpio_num_t` and use int or even uint8_t...

also it would be better to use `typedef` instead of `define` for types...

IRAM is very limited and we need to be very selective as to what we tag as that. We shouldn't have any ISRs in OpenMRNLite code for the esp32, except...

Also inside the ISR context, unless data is tagged as DRAM_ATTR it is possible to crash the esp32. If it is tagged it is read-only. The only data that can...

This is possibly why during CDI load I see occasional timeouts being reported. Though, I thought the BG task for executor was also for the CanBridge code? If not, we...

Ping.cpp does not include the header that defines this function, you can alter the library to add the following to fix this likely: ``` #include ```