RFSoC Data Converter Evaluation Tool User Guide 52
UG1287 (v2018.2) October 1, 2018 www.xilinx.com
Chapter 7: Protocol Specification
1. Depending on the memory type, select BRAM/DDR and set GPIOs. (If it is BRAM, the
hardware loops back the data; if it is DDR, DMA loops back the data.)
2. Map the memory, copy content, and trigger DMA.
3. Book-keep the memory type and addresses used for every pipeline for future use.
readdatafrommemory <tile_id> <block_id> <Number_of_bytes> <il_pair> <BRAM/DDR>
Check on the data length request based on mem_type. If it is BRAM, the size limit is
128K. If it is DDR, the limit is 128 MB.
For example, to send 1024-byte samples to firmware, the following command is used:
writedatatomemory 0 1 1024 0
Output return format:
• If an input command is not recognized, the parser errors out and sends
ERROR: CMD: Invalid Command\n.
• If an input command is recognized, the parser checks the number of arguments, and
sends
ERROR: CMD: Invalid Number of Arguments\n
• If the argument count is correct, it passes the command and parameters to the
execute state.
• If execution succeeds, the result is returned
CMD param1 param2 ... paramX value1 value2 ... valueY\n
• Commands that are not expected to return values return their name if execution
succeeds: [CMD]
• CMD and values are separated by a space.
• Values are the same as returned by the RFSOC driver.
• End of a line is \n
• If execution fails (e.g., in case of XRFdc driver failure), an error is returned
ERROR: CMD: Execution\n
• Any log or messages from metal-log can be returned via the getlog command.
°
\r\n characters are replaced from any log messages with "|" and a single \n
appended at the end.
To Next Page
Loading...