Skip to content

F
FPGA Device ID
Commit 86954390 authored by Javier Serrano's avatar Javier Serrano
1 Browse files
Options

Clarify that one of the two devices in the example is actually the top level

parent e32306af
Hide whitespace changes
Inline Side-by-side
Showing with 9 additions and 2 deletions
device-structure.rst
View file @ 86954390
......@@ -73,8 +73,8 @@ Observation 02.02.01
the application-specific part. In the example in :numref:`spec_diagram` we
have two devices: one which takes care of the basic functionality of the SPEC
board (e.g. I2C bus to identify the FMC, temperature, interrupt management...)
and one specifically designed to turn the combination of SPEC and ADC
mezzanine into a digitiser.
and one (the top level) specifically designed to turn the combination of SPEC
and ADC mezzanine into a digitiser.
.. _`rule 02.03.00`:
......@@ -180,6 +180,13 @@ Observation 03.05.02
register. Users are then free to continue using the convention in other
devices if they deem it useful.
Note also that gateware and software don't need to follow the same
hierarchical structure. In our example gateware design, the WRTD ADC device is
the top-level, and that device contains a SPEC BASE device. So far as the
software is concerned, the two drivers are at the same hierarchical level. The
SPEC BASE device is discovered first and managed by the SPEC driver. Then the
WRTD ADC device is discovered and the WRTD ADC driver starts managing it.
Version
'''''''
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment