With the nRF52, is the RTT functional when APPROTECT
is enabled?
I would expect not since the RTT relies on memory accesses which should be disabled with APPROTECT
With the nRF52, is the RTT functional when APPROTECT
is enabled?
I would expect not since the RTT relies on memory accesses which should be disabled with APPROTECT
A ran a quick experiment and confirmed that the RTT is not functional when APPROTECT
is enabled.
Just checking here, but short version, if I have RTT writes in my program, I'm debugging and getting everything as it should and do a production build - It's OK, Questionable Pactice, or BAD to just leave those RTT() calls in the code? Do they just immediately return when built for production?
Just checking here, but short version, if I have RTT writes in my program, I'm debugging and getting everything as it should and do a production build - It's OK, Questionable Pactice, or BAD to just leave those RTT() calls in the code? Do they just immediately return when built for production?