Wiki
Sidebar
ds:projects:lassie:ifcsystem
Table of Contents
Lasa: IFC System
| Module | Slot | Address |
|---|---|---|
| CPU | 1 | |
| Vetar 2a | 2 | |
| VDIO | 4 | 0xa0000000 |
| VDIO | 5 | 0xa1000000 |
| VDIO | 6 | 0xa2000000 |
| VDIO | 7 | 0xa3000000 |
| VDIO | 8 | 0xa4000000 |
| VDIO | 9 | 0xa5000000 |
| VDIO | 10 | 0xa6000000 |
| VDIO | 11 | 0xa7000000 |
| VDIO | 12 | 0xa8000000 |
| VDIO | 13 | 0xa9000000 |
| VDIO | 14 | 0xaa000000 |
| VDIO | 15 | 0xab000000 |
| Scaler SIS3820 | 18 | 0x04000000 |
| Scaler SIS3820 | 19 | 0x05000000 |
| Clock SIS3807 | 21 | 0x03000000 |
Implementation Details
- Due to the limited number of VME windows for the Tundra chip, the memory space for all VDIO modules is mapped in one block. All other modules are mapped separately.
- Range settings are send on each CMD_SEQ_START and/or CMD_BP_START
Notes
- The time between the CMD_SEQ_START/CMD_BP_START event and the acceptance of new range settings for the second IFC is around 5ms. Approximately 2ms are the result of the communication from the FTRN to the Lasa class via d-bus and saftlib. No significant change in the time delay has been observed for the last IFC (last VDIO module).
ds/projects/lassie/ifcsystem.txt · Last modified: 2017/06/06 18:43 by haraldbraeuning
