ConfigurationFrameAddress row-half and row fields translate directly to
the clock region structure used in 7-series parts. Break these concepts
out into separate classes and encode them as such in Part YAML.
Columns within a row are more complicated. Column indices are relative
to a BlockType. Think of each BlockType as a data bus that terminates at
some particular tile type (e.g. CLB_IO_CLK maps to INT_{L,R} tiles).
Column indices act as addresses of endpoints on the associated BlockType
bus. As the bus is 1 frame (101 words, 404 bytes) wide, each endpoint
feeds frames into multiple tiles simultaneously.
Minor addresses are frame addresses within a BlockType bus endpoint.
These can refer to frames either stored within the endpoint tiles
or in tiles chained behind them.
Note that a given tile can be connected on multiple BlockType buses.
For example, block RAMs appear to be attached both by being chained
behind an INT_{L,R} on the CLB_IO_CLK bus as well as being a direct
endpoint on the BLOCK_RAM bus. Due to this, tiles conceptually belong
to the row rather than a single column.
Signed-off-by: Rick Altherr <kc8apf@kc8apf.net>
_address suffix on accessors is unnecessary and somewhat inaccurate.
The returned values are indices rather than frame addresses.
Signed-off-by: Rick Altherr <kc8apf@kc8apf.net>
Based on Chromium style with the following changes:
- Tabs used for indentation
- Indentation is 8 characters
Signed-off-by: Rick Altherr <kc8apf@kc8apf.net>
Frame addresses are only used in the context of configuration frames.
Remove the prefix to reduce typing that does not improve clarity.
Signed-off-by: Rick Altherr <kc8apf@kc8apf.net>
There seem to be 2 frames of padding between rows in a bitstream. For
single-frame writes, these are parsed as type 0 packets and ignored.
Normal bitstreams use a single FDRI write that apparently includes this
padding and needs to be ignored in the auto-increment handling.
Signed-off-by: Rick Altherr <kc8apf@kc8apf.net>
Normal, debug, and per-frame CRC bitstreams differ in the commands used
to write the frame data but should generate equivalent configurations.
Note that this currently fails as something is wrong with normal
bitstream parsing.
Signed-off-by: Rick Altherr <kc8apf@kc8apf.net>
MemoryMappedFile's data() method returns a void* as it has no idea what
type the contents are. Viewing it as bytes is a very common operation
so add a convience method that wraps the pointer in a Span<uint8_t>.
Signed-off-by: Rick Altherr <kc8apf@kc8apf.net>
Rick Altherr
Tim Ansell
Clifford Wolf
John McMaster
John McMaster