| 36 | * For WARPLab 7.6.0 and above, the trigger input / output IDs from the trigger manager are as follows: |
| 37 | {{{ |
| 38 | Trigger Output D0 == EXT_OUT_P0 |
| 39 | Trigger Output D1 == EXT_OUT_P1 |
| 40 | Trigger Output D2 == EXT_OUT_P2 |
| 41 | Trigger Output D3 == EXT_OUT_P3 |
| 42 | Trigger Input D0 == EXT_IN_P0 |
| 43 | Trigger Input D1 == EXT_IN_P1 |
| 44 | Trigger Input D2 == EXT_IN_P2 |
| 45 | Trigger Input D3 == EXT_IN_P3 |
| 46 | }}} |
55 | | The CM-MMCX is capable of sourcing and/or sinking a clock referenced used to discipline a PLL on each node. This clock module can be used in a daisy chain configuration, where a single primary node shares its clock reference with a chain of secondary nodes that adopt and forward the clock reference. The role of each node is configured via the 6-position SIP switch on the CM-PLL, according to the figure below. |
| 66 | The CM-PLL is capable of sourcing and/or sinking a clock referenced used to discipline a PLL on each node. This clock module can be used in a daisy chain configuration, where a single primary node shares its clock reference with a chain of secondary nodes that adopt and forward the clock reference. The role of each node is configured via the 6-position SIP switch on the CM-PLL, according to the figure below. |
| 67 | |
| 68 | * The CM-PLL also carries the four trigger inputs and four trigger outputs between nodes. The trigger inputs are ORed with the trigger inputs from the debug header. The trigger outputs are replicated versions of the debug header trigger outputs.[[BR]] |
| 69 | [[Image(wiki:GettingStarted/files:important.png,nolink,valign=middle)]] In WARPLab 7.5.x, there is a bug in the mapping of trigger outputs in the CM-PLL connection: EXT_OUT_P0 is swapped with EXT_OUT_P2. See [http://warpproject.org/forums/viewtopic.php?pid=13893#p13893 this forum post] for more information. |