Skip to content

Add Decoder for the DAC8552 SPI protocol - #1106

Open
dj-bauer wants to merge 1 commit into
ngscopeclient:masterfrom
dj-bauer:dac8552
Open

Add Decoder for the DAC8552 SPI protocol#1106
dj-bauer wants to merge 1 commit into
ngscopeclient:masterfrom
dj-bauer:dac8552

Conversation

@dj-bauer

Copy link
Copy Markdown
Contributor

DAC8552 is a 16-bit dual-channel SPI-controlled DAC. It's message consists of 24 bit.
The first byte is a control-header specifying what register to update and what register contents to push out to the DAC. The second and third byte are the 16-bit value to be loaded into either register.

The implementation of the Decoder is basically identical to the ADL5205Decoder. I am thinking of merging the 2 into children of a general CPUSPIByteDecoder class as it seems to me that more decoders that just decode SPI-Traffic are to come. The only things, which are fundamentally different is the state machine, that loops over all SPISymbol and GetText()-Method.

This is most definetly to be merged after v0.2 this goes hand in hand with #1105 as this DAC requires CPHA=1

DAC8552 is a 16-bit dual-channel SPI-controlled DAC.
It's message consists of 24 bit.
The first byte is a control-header specifying what register to update
and what register contents to push out to the DAC.
The second and third byte are the 16-bit value to be loaded into either
register.

The implementation of the Decoder is basically identical to the `ADL5205Decoder`.
I am thinking of merging the 2 into children of a general CPUSPIByteDecoder
class as it seems to me that more decoders that just decode SPI-Traffic are to come.
The only things, which are fundamentally different is the state machine,
that loops over all `SPISymbol` and `GetText()`-Method.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant