All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tudor Ambarus <tudor.ambarus@microchip.com>
To: u-boot@lists.denx.de
Subject: [PATCH 3/4] sama5d3: Fix Galois Field Table offsets
Date: Fri, 8 Jan 2021 14:40:19 +0200	[thread overview]
Message-ID: <20210108124020.823844-4-tudor.ambarus@microchip.com> (raw)
In-Reply-To: <20210108124020.823844-1-tudor.ambarus@microchip.com>

Offsets are described in the datasheet at section:
"11.4.4.2 NAND Flash Boot: PMECC Error Detection and Correction".

For testing I "injected" bit flips into u-boot NAND memory area,
and then read back. PMECC could not correct the errors. With the
offsets updated everything is fine.

Fixes: 3225f34e5c ("ARM: atmel: add sama5d3xek support")
Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
---
 arch/arm/mach-at91/include/mach/sama5d3.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/mach-at91/include/mach/sama5d3.h b/arch/arm/mach-at91/include/mach/sama5d3.h
index 83f18a8148..f4f05676f7 100644
--- a/arch/arm/mach-at91/include/mach/sama5d3.h
+++ b/arch/arm/mach-at91/include/mach/sama5d3.h
@@ -190,8 +190,8 @@
 /*
  * PMECC table in ROM
  */
-#define ATMEL_PMECC_INDEX_OFFSET_512	0x10000
-#define ATMEL_PMECC_INDEX_OFFSET_1024	0x18000
+#define ATMEL_PMECC_INDEX_OFFSET_512	0x8000
+#define ATMEL_PMECC_INDEX_OFFSET_1024	0x10000
 
 /*
  * SAMA5D3 specific prototypes
-- 
2.25.1

  parent reply	other threads:[~2021-01-08 12:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 12:40 [PATCH 0/4] at91: Fix NAND PMECC on various SoCs/boards Tudor Ambarus
2021-01-08 12:40 ` [PATCH 1/4] configs: at91: Fix the involuntarily disablement of NAND PMECC Tudor Ambarus
2021-01-08 12:40 ` [PATCH 2/4] configs: at91: Fix wrong definitions for CONFIG_PMECC_CAP Tudor Ambarus
2021-01-08 12:40 ` Tudor Ambarus [this message]
2021-01-08 12:40 ` [PATCH 4/4] sam9x60.h: Fix Galois Field Table offsets Tudor Ambarus
2021-01-25 18:33 ` [PATCH 0/4] at91: Fix NAND PMECC on various SoCs/boards Eugen.Hristev at microchip.com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210108124020.823844-4-tudor.ambarus@microchip.com \
    --to=tudor.ambarus@microchip.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.