Opcode 0x0004 (OTEST)
Output Words0:0001 0002 0004 0008 0010 0020 0040 0080 0100 0200 0400 0800
10002000 4000 8000
Opcode 0x0005 (SNOISE)
Input Words
0:0000 0000
Opcode 0x0009 (GPARM)
Output Words
0:2000 0064 0960 9DCF 0110 0DD0 0000 0000 0000 5284 0000 0000 0040
D472 0000 0000
16:0000 0603 020D 5DC0 012C 1D4C 1770 0BB8 8421 0210 2EE0 2EE0 0000
0000 042E 07AE
32:000D FE20 0066 0050 FE70 0000 0000 0000 0000 0000 0001 0011 0000
0011 0000 0DD0
48:0000 0000 00E8 01C0 03E8 04B0 0303 0000 0037 30CB 0003 0000 0000
0000 0000 0000
When the OTEST opcode is received, it is parsed by RVP9/Main HostCmds thread, which
also generates the exposeIO printout. The opcode is shown in both numerical and
mnemonic form, followed by the 16-word walking-ones pattern that results from it. The
SNOISE command arrives, along with the two input words, which are expected by that
opcode.
No output words are generated by SNOISE. The GPARM opcode is received and the 64
output words that it produces are displayed.
Watching the opcode-level activity of the signal processor is helpful when debugging both
custom driver code and custom opcode handlers that you might write for RVP.
C.3.2
Showing Live Acquired Pulse Information: -showAQ
The (I,Q) data computed by the FIR filters are transferred to CPU memory using direct
memory access (DMA) bus cycles initiated by RVP9/Main threads.
The radar data arrive in discrete chunks and the TimeSeries API is updated accordingly.
To show live acquired pulse information for debugging, include the -showAQ command
option in the RVP startup command line.
The following example shows the output (I,Q) bus activity for a dual polarization system in
which 3 UDP packets were sent to transfer the data.
UDP column
Record ID that increments each time a pulse is sent.
Frags column
Shows the number of UDP packets sent to transfer the last pulse of data.
Bins column
Number of bins requested multiplied by two, because this is a dual polarization
system.
Appendix C – RVP900 Developer Notes
375
To Next Page
Loading...