Release Note
C0FE0031_xxxx.sff
MPI Version |
FPGA Version |
03.03.00
Production Release |
C0FE0031_0346 |
03.02.00
Production Release |
C0FE0031_0341 |
C0FE0031_0346
| |
Modications to gpioPinConfigReg |
| |
|
Reference Number: FP 336 |
| |
|
Type: General Change |
| |
|
FPGA Version: 0x0346 |
| |
|
Problem/Cause:
Prior to FPGA version x0346, gpio pins that were configured as an "output" did not resume "output" direction after an ioAbort event. Also, during the ioAbort event, if a service channel write to the gpio configuration register occurred, the gpio "output" pins would be set to "output" mode momentarily (and then cleared to "input" mode by the ioAbort event). After the ioAbort event was cleared, the gpio pin state would remain as in "input" mode unless software restored the gpio configuration register again. |
| |
|
Fix/Solution:
In FPGA version x0346 and later, an ioAbort event still forces gpio "output" pins to "input" mode, which allows external resistors to pull pins from either high or low for a "safe" state. The resistors may or may not be present depending on the PCB assembly. However, during an ioAbort event, service writes to the gpio configuration register no longer cause momentary "output" direction. After the ioAbort event is cleared, gpio pins will resume their previous "output" state without software intervention.
|
| |
Intermittent Dual String Discovery Failure |
| |
|
Reference Number: FP 332 |
| |
|
Type: Bug Fix |
| |
|
FPGA Version: 0x0346 |
| |
|
Problem/Cause:
Probe, resetRequest, and resetComplete were repeated on the wrong port (OUT port) when using the OUT port as the primary port during SynqNet node discovery. As a result, SynqNet node discovery may have failed. This problem was caused by the probe, resetRequest, and resetComplete being repeated on the wrong port. This issue existed in all FPGA versions prior to x0346. |
| |
|
Fix/Solution:
The FPGA code was corrected in version x0346 and later releases. This fix is required for systems using the Dual String or IN Port String topologies. This fix is NOT required for systems using normal OUT Port String or Ring topologies.
|
| |
sqMac - 0x00 will be read for dataType NULL |
| |
|
Reference Number: FP 323 |
| |
|
Type: New Feature |
| |
|
FPGA Version: 0x0346 |
| |
|
Description:
0x00 will be read for dataType NULL in the status and feedback packets.
|
| |
Intermittent Fault Recovery failures |
| |
|
Reference Number: FP 315 |
| |
|
Type: Bug Fix |
| |
|
FPGA Version: 0x0346 |
| |
|
Problem/Cause:
Some nodes may have intermittently failed to recover from a fault in some network configurations. If a node failed to recover, it exited cyclic operation and correctly triggered ioAbort logic (forcing outputs into "safe" states). Any nodes "downstream" of the failing node (after it switched ports) were also likely to exit cyclic operation. For any given node, there was only a small schedule window where this error may have occurred. There were two causes of the problem. The rcvMiiBuffer did not clear itself after an overflow in some situations. Also, a packet fragment generated by the fault recovery that happened to have valid CRC (but no data) would confuse the packetFifo, and corrupt internal node configuration bits. The first issue existed in FPGA build versions x0341 through x0345 and their branches (MPI release 03.02.00). The second issue existed in all FPGA versions prior to x0346. |
| |
|
Fix/Solution:
The fault recovery problems was corrected in FPGA build versions x0346 and later. The rcvMiiBuffer will correctly clear itself after an overflow. The xmitMiiReg will release xmitHoldRcvBuf within 8 clocks after a fault, preventing an rcvMiiBuffer overflow. 8 clocks will guarantee that there is minimum packet spacing between the packets. sqPll will ignore the second SYNQ packet after fault recovery (in case packet delays were effected in the cycle where fault recovery occurred). The rcvMii will correctly handle a valid packet with data length of 0. No software changes are required.
|
| |
Support for big and little endian bytes |
| |
|
Reference Number: FP 301 |
| |
|
Type: New Feature |
| |
|
FPGA Version: 0x0346 |
| |
|
Description:
Support has been added for big endian or little endian byte ordering in the driveParallel interface.
|
C0FE0031_0341
| |
sqMac rxMiiBuffer multiple packets |
| |
|
Reference Number: FP 263 |
| |
|
Type: General Change |
| |
|
FPGA Version: 0x0341 |
| |
|
Description:
Add support for multiple packets to the rxMiiBuffer. This improves tolerance to network jitter. Prior to version x0341, the rxMiiBuffer could absorb up to 32 clocks (1.28 µS) of delay for a single packet, but only 8 clocks for multiple packets with minimum spacing. This change is required to meet theoretical worst-case network jitter in large networks (32 nodes). The improvement may also help at network startup, since the node's PLL phase error is larger than normal (as the PLL pulls into nominal lock). No software changes are required.
|
C0FE0031_0340
| |
New BranchRev Register |
| |
|
Reference Number: FP 231 |
| |
|
Type: New Feature |
| |
|
FPGA Version: 0x0340 |
| |
|
Description:
Add BranchRev register. This extends the existing 16 bits of FPGA version number with 8 bits of branch and 8 bits of revision ID.
|
|
