This Answer Record contains the Release Notes for the LogiCORE Fibre Channel Arbitrated Loop v2.2, which was released in 9.2i IP Update 1, and includes the following:
- New Features
- Bug Fixes
- Known Issues
For installation instructions and design tools requirements, see (Xilinx Answer 25222).
New Features
- Support for the ISE 9.2i design tools release has been added.
- In version 2.2 of the core, there are minor updates to the FCMGT files
to align with latest RocketIO Wizard outpus for Virtex-5.
Also, the following fixes and enhancements were made:
CR 439385: Add -pcf option to netgen to get true min/max timing from pcf.
CR 439628: Update core with latest init_controller netlists.
CR 440189: Core reacts incorrectly when detecting LOS in MONITORING, with repeat=1.
CR 440193: Core does not re-tx LIPs in Monitoring State with bypass=true.
CR 438887: LIPs ignored after ALTIME during LISM phase - should restart LISM phase.
CR 438888: RX of various errors in LISM frames results in re-init - should be ignored.
CR 438889: Core can take an ALPA in a LIRP frame when none are available.
CR 438890: Core cannot cope with LIPyx (vendor-specific reset).
CR 438891: Core cannot transmit Old Port PSM prims (OLS, NOS etc) when it should. Similar problems in other states.
CR 438892: Core does not reset ALPA to F7 on entry to Old Port state.
CR 438893: Core can transmit own LIP or LIPF7F7 instead of received LIP.
CR 438894: Core does not react to OLS/NOS after ALTIME of LIPF8 (after Loop failure).
CR 438895: Core does not re-transmit LPB/E while sending LIP after Init Failure.
CR 438896: ALPA for a Master was reset to F7 during the wrong phases of ALPA assignment.
CR 438897: Core does not disregard ARBF0 codes during ALPA assignment phases. It sees ARBF0 as an error.
CR 438898: Core retransmits some codes during ALPA assignment phases.
CR 438899: Core will not send LIPF8 after a Loop Failure.
CR 438900: Core cannot be brought out of Non-Participate mode.
CR 438898: Core retransmits some codes during ALPA assignment phases.
CR 438898: Core retransmits some codes during ALPA assignment phases.
Known Issues in v1.1
-For Virtex-II Pro board designs to avoid BER failures, it is important to ensure that board meets Virtex-II Pro MGT specifications. For more information, see (Xilinx Answer 25035).
- The coding in the example designs for Virtex-5 could cause CRC errors to go undetected 50% of time in hardware. For more information, see (Xilinx Answer 29985).