Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
AMC13 IP Address Assignment | ||||||||
Changed: | ||||||||
< < | The AMC13 has three PCB Tongues. Tongue 1 (T1) and Tongue 2 (T2) each has their own FPGA (Virtex6/Kintex7 for T1, Spartan6 for T2) and therefore each has their own IP address. | |||||||
> > | The AMC13 has two PCB Tongues. Tongue 1 (T1) and Tongue 2 (T2) each has their own FPGA (Virtex6/Kintex7 for T1, Spartan6 for T2) and therefore each has their own IP address. | |||||||
There are several schemes in the midst of being implemented when it comes to AMC13 IP Address assignment. The following procedures are those which I know of at the moment. | ||||||||
Line: 13 to 13 | ||||||||
2. Via MMC SPI EEPROMIn this scheme, the MMC sends a configuration packet which contains the IP address to be assigned from non-volitile EEPROM to the Spartan and Virtex chips at powerup. For information on how to load new configuration information into the SPI, see the MMC software page | ||||||||
Added: | ||||||||
> > | 3. RARP from a software daemon. This is not yet implemented (until we update our IPBus firmware) but may be come the preferred scheme. | |||||||
Changed: | ||||||||
< < | -- JimRohlf - 26 May 2012 | |||||||
> > | -- EricHazen - 12 Mar 2014 | |||||||
\ No newline at end of file |