M core boot A53 core for different S32G Board Version Rev

[learnx]

HI,

I operate according to the AN13750 documentation, but there are different result for different Board version

For S32G274Ardb2 Board Version Rev.D, this part of the code will execute normally, but for S32G274Ardb2  Board Version Rev.E it will block in an endless loop.

The guidance in the AN13750 documentation is specific to which version of the board？

Board Version Rev.C、Board Version Rev.D 、Board Version Rev.E？

[Daniel-Aguirre]

Hi,

Rev E of RDB2 uses the silicon revision v2.1, while Rev C/D uses the v2.0 revision.

Since AN13750 is intended to be used with HSE v0.1.0.5, we understand that the specific version was released prior to the new silicon revision (S32G2 v2.1), hence the guide was verified with v2.0 silicon revision. If we look into the HSE v0.1.0.5 release notes, we see the following is stated:

The first HSE version that supports v2.1 silicon should be HSE v0.1.0.9, in which the release notes state the following:

Since we understand that your board is being stuck under the HSE verification routine, we assume the issue is due to the HSE version being used under AN13750 is the v0.1.0.5, since it does not support v2.1 silicon revision.

Have you verified the HSE DEMO_APP with the Rev E board? Where you able to get a successful outcome? 

Please, let us know.

[learnx]

Is there any guidance document on booting the A core from the M core of the Rev 2.1 board?

[Daniel-Aguirre · Accepted solution]

Hi,

As far as we can see, there is no update for AN13750 on regards of silicon revision.

If not using HSE, we can use the same scheme as the AN13750 proposes, under the same packages and bootloader version. We have confirmed this from our side.

If you want to use HSE, v1.9.0 is required and RTD v4.0.0 P3 is the one compatible with it. All other packages then take RTD as a base package, hence they need to be selected for the same RTD version to be compatible.

Aside from this, if you require a specific document, help us contacting your local NXP FAE/representative, for they to help on this regard. We do apologize.

Please, let us know.

[learnx]

Thank you.