I’m trying to confirm that the ECC on the SDRAM is enabled for the Apalis IMX8X module. Is there a way to confirm this in linux or uboot?
Hi @mim747 there is not a simple way to verify this. No utilities exist that will confirm this. Potentially you could dig through the memory controller registers to figure it out but I don’t know of anything that will do that for you.
Thanks for responding Drew!
I’ll do some digging in the datasheet to see which registers can confirm this. Do you know if the latest yocto based image from Toradex has enabled ECC on the SDRAM or other memories for the latest Apalis module? I believe the one we purchased has support for ECC. I haven’t been able to find any documentation or code to tell me that it has been enabled on this module. Any guidance is appreciated and thanks!
Some variants of the Apalis i.MX8X family have ECC enabled. If that is the SKU you ordered, you should be in good shape.
Perfect, thank! We did order that SKU, so we should be set. I was trying to find how I could disable the ECC via uboot/linux menuconfig, but could not find the setting. Do you know if it’s possible to disable ECC via yocto before bulding a new image?
Which version of the BSP are you building? You’ll need to patch the SCFW to do this. I’m getting the details from our BSP team but the specifics will depend on the version of the BSP.
Attached is a patch which should disable ECC. This patch is against the current HEAD of the dunfell-5.x.y branch of meta-toradex-nxp.
Here’s my build configuration. Not sure where to find the BSP version, but I am using the latest toradex version 5.2 (dunfell). Would I be able to get that patch and build the SCFW myself?
Build Configuration: BB_VERSION = "1.46.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "aarch64-tdx-linux" MACHINE = "apalis-imx8x" DISTRO = "tdx-xwayland" DISTRO_VERSION = "5.2.0-devel-20210504151046+build.0" TUNE_FEATURES = "aarch64" TARGET_FPU = "" meta-toradex-nxp = "HEAD:048c2fbf26bcb19392fddcceecee0e7b18e19dd2" meta-freescale = "HEAD:0545b1ed2e02a6aadad3ce5b1af1593d6c61c157" meta-freescale-3rdparty = "HEAD:058316a502cdba7fad02df8c857c72e218b7bc45" meta-toradex-tegra = "HEAD:a0f00032e59ea7db45e46eea35a221ede499aefd" meta-toradex-bsp-common = "HEAD:02ee9a4f47d195a3b47a31b8db439e1b7bb78539" meta-oe meta-filesystems meta-gnome meta-xfce meta-initramfs meta-networking meta-multimedia meta-python = "HEAD:346681e7bf9c78008a845fc89031be4fd4ceb3a1" meta-freescale-distro = "HEAD:5d882cdf079b3bde0bd9869ce3ca3db411acbf3b" meta-toradex-demos = "HEAD:bf1bc67f2de9f0245da66a3a15d5c439ee7462d7" meta-qt5 = "HEAD:0d8eb956015acdea7e77cd6672d08dce18061510" meta-toradex-distro = "HEAD:2561e4a6cc6d5a8f6badb32ed3ead6eb4b536519" meta-poky = "HEAD:7ae5d508ddbdd7986a3100885befda460450ef34" meta = "HEAD:a8debddd6cbdd70db74e096d72f97fbee008ee63" workspace = "<unknown>:<unknown>"
The patch I posted earlier today should work for you here. It can be applied against meta-toradex-nxp.