I don’t think there’s a way to profile/debug patches on device directly. OWL is running on baremetal hardware with an RTOS, patches themselves have separate stack and are loaded to memory at runtime. So patch code is not visible with a debug build of firmare. It’s impressive that Martin made it work in first place, but unfortunately patch contents is a black box for normal tools that are used to debugging firmware.
If you want to profile performance specifically, it might be possible to read MCU cycles counter from memory directly. This is the register that is used by firmware for measuring CPU load, so you could try reading a 32bit unsigned int from 0xE0001004 before/after function call (haven’t tried it myself). Also, https://godbolt.org has support for gcc-arm, I’ve used that for checking how different end up compiled a few times.
Also, I was told this may be useful with native builds - gdbplotlib · PyPI (haven’t tried it myself too!)