Difference: IPaddressAssignment (5 vs. 6)

Revision 608 May 2013 - CharlieHill

Line: 1 to 1

META TOPICPARENT	name="HcalDTC"

Changed:

<
< The AMC13 has three distinct PCB Tongues, each carrying its own functionality. Speicifically, 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.

>
>

AMC13 IP Address Assignment

The AMC13 has three PCB Tongues, each its own entity. Specifically, 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: 11 to 12

Final Byte for Spartan Chip = 254 - 2*SN
Final Byte for Virtex/Kintex Chip = 255 - 2*SN

2. Via MMC SPI EEPROM

Changed:

<
<

In 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. The format of this packet is below:

00           #AMC13 Slot Number
ff ff 00 00  #Net Mask
c0 a8 01 64  #IP Address
00 00        #Boot Vector

The serial number is etched on the front of the card. It can be discovered using the python program 'find_ver_serial_no.py' or by reading the upper eight bits from register 0x0 on either chip

>
>

In 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

3. Dynamically at runtime

This can be done using raw IPMITool commands which set the IP address of its slaves (in this case, T1, T2, and T3). Commands are yet to come

-- JimRohlf - 26 May 2012

View topic | History: r26 < r25 < r24 < r23 | More topic actions...