From 9f95ff5b6ba01db09552b84a0ab79607060a2666 Mon Sep 17 00:00:00 2001 From: Ali Labbene Date: Wed, 11 Dec 2019 08:59:21 +0100 Subject: Official ARM version: v5.4.0 Add CMSIS V5.4.0, please refer to index.html available under \docs folder. Note: content of \CMSIS\Core\Include has been copied under \Include to keep the same structure used in existing projects, and thus avoid projects mass update Note: the following components have been removed from ARM original delivery (as not used in ST packages) - CMSIS_EW2018.pdf - .gitattributes - .gitignore - \Device - \CMSIS - \CoreValidation - \DAP - \Documentation - \DoxyGen - \Driver - \Pack - \RTOS\CMSIS_RTOS_Tutorial.pdf - \RTOS\RTX - \RTOS\Template - \RTOS2\RTX - \Utilities - All ARM/GCC projects files are deleted from \DSP, \RTOS and \RTOS2 Change-Id: Ia026c3f0f0d016627a4fb5a9032852c33d24b4d3 --- docs/DAP/html/group__DAP__SWO__Baudrate.html | 149 +++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 docs/DAP/html/group__DAP__SWO__Baudrate.html (limited to 'docs/DAP/html/group__DAP__SWO__Baudrate.html') diff --git a/docs/DAP/html/group__DAP__SWO__Baudrate.html b/docs/DAP/html/group__DAP__SWO__Baudrate.html new file mode 100644 index 0000000..0a316d1 --- /dev/null +++ b/docs/DAP/html/group__DAP__SWO__Baudrate.html @@ -0,0 +1,149 @@ + + + + + +DAP_SWO_Baudrate +CMSIS-DAP: DAP_SWO_Baudrate + + + + + + + + + + + + + + +
+
+ + + + + + + +
+
CMSIS-DAP +  Version 2.0.0 +
+
Interface Firmware for CoreSight Debug Access Port
+
+
+ +
+
    + +
+
+ + + +
+
+ +
+
+
+ +
+ + + + +
+ +
+ +
+
+
DAP_SWO_Baudrate
SWO Commands
+
+
+ +

Set SWO baudrate. +More...

+

Set SWO baudrate.

+

DAP_SWO_Baudrate (0x19):

+

Sets the baudrate for capturing SWO trace data. Can be called iteratively to determine supported baudrates.

+

DAP_SWO_Baudrate Request:

+
| BYTE | WORD |
+
> 0x19 | Baudrate |
+
|******|**********|
+
    +
  • Baudrate: Requested baudrate
    • +
+

DAP_SWO_Baudrate Response:

+
| BYTE | WORD |
+
< 0x19 | Baudrate |
+
|******|**********|
+
    +
  • Baudrate: Actual baudrate or 0 (baudrate not configured) When requested baudrate is not achievable the closest configured baudrate can be returned or 0 which indicates that baudrate was not configured.
    • +
+
Note
When Manchester Mode is used and if decoder is implemented with clock recovery then baudrate is not required since clock is automatically decoded. However such decoders are harder to implement (especially for high frequencies) and the clock recovery might not be implemented. Therefore the baudrate should be provided also for Manchester mode.
+
+
+ + + + -- cgit