| ... | @@ -223,3 +223,6 @@ To see what Hashpipe is doing it will be useful to check specific control values |
... | @@ -223,3 +223,6 @@ To see what Hashpipe is doing it will be useful to check specific control values |
|
|
watch -n 1 "./hashpipe_check_status -I 0 -v | fold -w 80"
|
|
watch -n 1 "./hashpipe_check_status -I 0 -v | fold -w 80"
|
|
|
|
|
|
|
|
```
|
|
```
|
|
|
|
|
|
|
|
### Hashpipe Outputs
|
|
|
|
Hashpipe will write a binary file containing all of the ADC samples and packets meta-data. Provided is the file parse_bits.m which can be used to parse that binary file into time samples from each ADC. It can also be used as reference as to how the network packets are formatted. Each "chunk" as described in the parse bits file consists of 1024 time samples from each ADC and you can specify how many chunks to read at a time by changing the num_chunks variable. |
|
|
|
\ No newline at end of file |
