K2H MCSDK 3.1.2.5 Serdes config updating

Hi,

I think MCSDK 3.0.4 (PDK 2.3.00.04.18) is a earlier release for keystone II devices. I don't have this revision MCSDK package to reproduce your issue.

I have tested the SRIO transfer on MCSDK 3.01.x (MCSDK 3.1.3.6 and MCSDK 3.1.1.4) release example, it is working fine. Better to use latest MCSDK source code for your testing.

Thanks,

Ganapathi-san,

Thank you for your help.
I have an additional question. Could you let me know?

We would like to use MCSDK v3.1.2.5 in our production. Is it been tested?

How can I know it has been tested or not?
Where does it describe? (I can not notice as it is an Early release.)

Best regards, RY

Ganapathi-san,
Thanks!
I will proceed our production by MCSDK v3.1.2.5.
I refer release note but there is no explanation if it is "early release" or not.

In my assuming,
It is internal information if "early release" or not. It is not disclosed.
Is my understanding right?

Best regards, RY

Hi,

No. Refer section "9 Releases" on latest MCSDK release notes document. Latest MCSDK 03.01.03.06 revision is a maintenance update to on the R3.1 release stream of the Multicore SDK. The baseline for this release is R3.1.2.

Thanks,

Ganapathi-san,

Thanks for your comment! I understand MCSDK 03.01.03.06 has tested.
Anyway, I need to clarify if following issue was improved or not.

SRIO transfer occasionally failed in our system using CSL of MCSDK 3.0.4 (PDK 2.3.00.04.18).
But, there is no problem using newer CSL of MCSDK 3.1.3 (PDK 2.3.01.03.06) .

So, my question is:
Have you heard issue regarding above in previous MCSDK version?

Best regards, RY