diff options
author | Kevin O'Connor <kevin@koconnor.net> | 2019-04-01 21:32:33 -0400 |
---|---|---|
committer | Kevin O'Connor <kevin@koconnor.net> | 2019-04-01 21:41:33 -0400 |
commit | c30a6f2e6b9fd44e14345d0a44fe8ea9bd65d653 (patch) | |
tree | 8a43ef0837ef58ad0a2a34458ff5bf769cb633e7 /docs/Protocol.md | |
parent | 2c851e1621ab6f49f8501ef7805adeb4fc202e98 (diff) | |
download | kutter-c30a6f2e6b9fd44e14345d0a44fe8ea9bd65d653.tar.gz kutter-c30a6f2e6b9fd44e14345d0a44fe8ea9bd65d653.tar.xz kutter-c30a6f2e6b9fd44e14345d0a44fe8ea9bd65d653.zip |
docs: Update Protocol documentation with enumerations
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
Diffstat (limited to 'docs/Protocol.md')
-rw-r--r-- | docs/Protocol.md | 52 |
1 files changed, 33 insertions, 19 deletions
diff --git a/docs/Protocol.md b/docs/Protocol.md index f73a195a..d10a1186 100644 --- a/docs/Protocol.md +++ b/docs/Protocol.md @@ -109,6 +109,30 @@ output("The value of %u is %s with size %u.", x, buf, buf_len); The output() function is similar in usage to printf() - it is intended to generate and format arbitrary messages for human consumption. +Declaring enumerations +---------------------- + +Enumerations allow the host code to use string identifiers for +parameters that the micro-controller handles as integers. They are +declared in the micro-controller code - for example: + +``` +DECL_ENUMERATION("spi_bus", "spi", 0); + +DECL_ENUMERATION_RANGE("pin", "PC0", 16, 8); +``` + +If the first example, the DECL_ENUMERATION() macro defines an +enumeration for any command/response message with a parameter name of +"spi_bus" or parameter name with a suffix of "_spi_bus". For those +parameters the string "spi" is a valid value and it will be +transmitted with an integer value of zero. + +It's also possible to declare an enumeration range. In the second +example, a "pin" parameter (or any parameter with a suffix of "_pin") +would accept PC0, PC1, PC2, ..., PC7 as valid values. The strings will +be transmitted with integers 16, 17, 18, ..., 23. + Declaring constants ------------------- @@ -119,7 +143,12 @@ DECL_CONSTANT("SERIAL_BAUD", 250000); ``` would export a constant named "SERIAL_BAUD" with a value of 250000 -from the micro-controller to the host. +from the micro-controller to the host. It is also possible to declare +a constant that is a string - for example: + +``` +DECL_CONSTANT_STR("MCU", "pru"); +``` Low-level message encoding ========================== @@ -277,24 +306,9 @@ dictionary. Once all chunks are obtained the host will assemble the chunks, uncompress the data, and parse the contents. In addition to information on the communication protocol, the data -dictionary also contains the software version, constants (as defined -by DECL_CONSTANT), and static strings. - -Static Strings --------------- - -To reduce bandwidth the data dictionary also contains a set of static -strings known to the micro-controller. This is useful when sending -messages from micro-controller to host. For example, if the -micro-controller were to run: - -``` -shutdown("Unable to handle command"); -``` - -The error message would be encoded and sent using a single VLQ. The -host uses the data dictionary to resolve VLQ encoded static string ids -to their associated human-readable strings. +dictionary also contains the software version, enumerations (as +defined by DECL_ENUMERATION), and constants (as defined by +DECL_CONSTANT). Message flow ============ |