This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

66AK2H14: Single Lane HyperLink Configuration Settings

Part Number: 66AK2H14

Are there any specific configuration steps that must be taken to configure HyperLink for a single channel?

I am using CCSV7.1 with PDK_K2HK_4_0_4. I have the example application hyplnk_K2HC66DevLibBiosExample running on two EVMK2Hx development boards that are connected via a custom backplane. The example application executes successfully when executed with hyplnk_EXAMPLE_ALLOW_4_LANES defined but when this is not defined and I only have hyplnk_EXAMPLE_ALLOW_1_LANE defined then the application hangs on both boards. I have tried running the application with hyplnk_EXAMPLE_ALLOW_0_LANES defined and not defined. Neither case seems to make any difference. Are there other settings that need to be made to support a single channel configuration? I appears that there may be some low level initialization that relies on all four channels.

Thanks for your support, 

Sincerely, 

Jack

  • Hi,

    I've notified the sw team. Their feedback will be posted here.

    Best Regards,
    Yordan
  • Hi,

    Hyperlink must have to start in four lane mode. You must have all four lane connected to the remote side. In our EVM this is not a problem. In your own designed board, even you just want to use one lane, you still have all 4-lane connected to the remote side.

    If you defined 1-lane or 0-lane configuration, then below Serdes code only has 1-lane and will not work.
    serdes_lane_enable_params.num_lanes = hyplnk_EXAMPLE_MAX_LANES;

    After Hyperlink starts in 4-lane mode, the HW automatically manages the power, see user guide 2.5.3 Power Management. It can enter 1-lane or 0-lane mode. This is controlled by Lane Power Management Control Register (Base Address + 0x44).

    Regards, Eric