RT1176 SDK v2.12.1 bug: FlexRAM ECC support

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

RT1176 SDK v2.12.1 bug: FlexRAM ECC support

Jump to solution
878 Views
raddeh
Contributor III

Upgrading to SDK v2.12.1 for the RT1176, i've discovered that similar bugs as reported for v2.12.0 in a previous ticket still exist:

  1. In file MIMXRT1176_cm7_features.h line 430: The define FSL_FEATURE_FLEXRAM_HAS_ECC should be set to 1, not 0. The RT1176 FlexRAM does support ECC. Having the define set to 0 does break previous code that uses the ECC support, as the corresponding access functions in fsl_flexram.c won't be compiled..
  2. When fixing 1. (setting FSL_FEATURE_FLEXRAM_HAS_ECC to 1) the compilation of fsl_flexram.c does fail. The defines used in function FLEXRAM_ErrorInjection() do not exist. The function also tries to access a register, that according to the i.MX RT1170 Processor Reference Manual Rev.1 does not exist on that processor.

 

This is a major bug, that was already reported for v2.12.0 of the SDK. The workaround is to set the define FSL_FEATURE_FLEXRAM_HAS_ECC manually to 1 and to remove the function FLEXRAM_ErrorInjection() from fsl_flexram.c.

Tags (2)
0 Kudos
1 Solution
866 Views
jay_heng
NXP Employee
NXP Employee

I have created internal ticket for it. It should be fixed in SDK 2.12.2

https://jira.sw.nxp.com/browse/MCUX-54294

View solution in original post

0 Kudos
3 Replies
867 Views
jay_heng
NXP Employee
NXP Employee

I have created internal ticket for it. It should be fixed in SDK 2.12.2

https://jira.sw.nxp.com/browse/MCUX-54294

0 Kudos
746 Views
raddeh
Contributor III

@jay_heng This bug persists to be present in the latest SDK version 2.13.1

 

  • In file SDK_2_13_1_MIMXRT1170-EVK/devices/MIMXRT1176/MIMXRT1176_cm7_features.h the define FSL_FEATURE_FLEXRAM_HAS_ECC should be 1
  • In File SDK_2_13_1_MIMXRT1170-EVK/devices/MIMXRT1176/drivers/fsl_flexram.c the function FLEXRAM_ErrorInjection() should not exist or should not be compiled for the RT1176
0 Kudos
722 Views
jay_heng
NXP Employee
NXP Employee

Yes, it was not fixed yet, as the ticket is still open

0 Kudos