TRACECLK and CPU clock

[eblot]

Hi,

I'm running a nRF52832 connected through TRACE port to a Segger J-Trace Pro.

Some traces seem to be lost, and Segger support team tells me it is possible as nRF52832 runs @ 64MHz, while the traceport runs @ 16MHz, which can therefore only output data @ 32MHz. Segger suggest to decrese the CPU clock speed @ 32 MHz so that no overflow occurs.

* Is is possible and how to do that with nRF52832 running SDK 15.2 and S132 6.1.1?

* If if is not possible, how to make the TRACE port reliable?

Thanks,

Emmanuel.

[eblot]

Ok.

Is it something that will be fixed in the next iteration of the nRF52, because the ETM may be used, among other needs, to debug performance issues *without* altering the normal behaviour of the CPU, and it looks like the implementation of the ETM port by Nordic defeats this very purpose. It seems quite paradoxal to me.

Thanks

[Kenneth]

Yes, I expect this will be addressed, but I can't comment on when and how etc.

Best regards,
Kenneth

[Guilherme de Paula]

Wow.  This is a big problem for us.  The nRF52840 has this limitation too.  Our problem is even more complicated, as the J-Trace Pro that we bought are only supported by IAR in "Sampling" mode and not in "Streaming" mode.  We are considering switching to SES (Segger Embedded Studio).

[Guilherme de Paula]

But this link from Segger says it is fine.  Maybe there is a way to make it work.

https://wiki.segger.com/Tracing_on_Nordic_Semiconductor_nRF52832