RapidIO MegaCore Function User Guide Does Not Clarify that Migration from SOPC Builder to Qsys Changes Port Names

Description

When you migrate an SOPC Builder system that contains a RapidIO MegaCore function to a Qsys system, many of the RapidIO MegaCore function signal names change. Signal names that have the _<variation> suffix in the SOPC Builder system, instead have the suffix _from_the_<variation> or _to_the_<variation> in the Qsys system. The suffix for each signal depends on the signal direction.

In a Qsys system, you can control the name of any exported signal. However, the issue should be documented in the RapidIO MegaCore Function User Guide.

The following signals are affected: arxwlevel, atxovf, atxwlevel, buf_av0, buf_av1, buf_av2, buf_av3, char_err, ef_ptr, error_capture_destination_id, error_capture_ftype, error_capture_letter, error_capture_mbox, error_capture_msgseg_or_xmbox, error_capture_source_id, error_capture_ttype, error_detect_illegal_transaction_decode, error_detect_illegal_transaction_target, error_detect_message_error_response, error_detect_message_format_error, error_detect_message_request_timeout, error_detect_packet_response_timeout, error_detect_unsolicited_response, error_detect_unsupported_transaction, gxb_powerdown, gxbpll_locked, master_enable, multicast_event_rx, multicast_event_tx, packet_accepted, packet_cancelled, packet_crc_error, packet_not_accepted, packet_retry, packet_transmitted, port_error, port_initialized, rd, reconfig_clk, reconfig_fromgxb, reconfig_togxb, rx_errdetect, rx_packet_dropped, rxclk, rxgxbclk, symbol_error, td, txclk.

Clock and reset signal renaming depends on the conduit names you provide in Qsys following the migration.

This issue affects all RapidIO variations generated with the SOPC Builder flow and migrated to the Qsys system integration tool.

Resolution

This issue has no workaround.

This issue is fixed in version 11.0 of the RapidIO MegaCore Function User Guide.