![nrf segger embedded studio nrf segger embedded studio](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/285344/5e2c7640-b41d-2756-1970-987de98dd28c.jpeg)
Depending of the setting in the TRACECONFIG register, this value can get divided down even further.
![nrf segger embedded studio nrf segger embedded studio](https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-01677ea924e041179cb27de31f1e00c9/pastedimage1590135754450v1.png)
So when the MCU Clock is set to maximum 64 MHz the SWO clock is only maximum half of that which is 32 MHz.
![nrf segger embedded studio nrf segger embedded studio](https://jimmywongbluetooth.files.wordpress.com/2020/10/image-2.png)
However on these devices, the SWO clock has an additional fixed divider. This is also the case for the nRF52 series devices. However, a few device specifics apply which are described in the following section.įor most devices, the SWO clock is derived from the current MCU clock. On the nRF52 series devices from Nordic Semiconductor, SWO is supported. Note: There is no backdoor or similar implemented on this device to bypass the ACL for debugging purposes. modifying flash contents during a debug session via the memory window)
Nrf segger embedded studio code#
Single stepping code in read-protected regions.The following operations will no longer work in case the ACL is used: As the ACL registers are write-once after reset, it is highly recommended that the ACL is not used during debug as this limits the debugging capabilities. The nRF52 series incorporate a so called access control list (ACL) peripheral which can be configured at runtime to inhibit reading from certain flash ranges (not to be confused with the device's readout protection feature) as well as reprogramming them. 5 Monitor Mode Debugging on Nordic nRF52.