From c894b6773327479a310341e39cbfc4047c2b96f6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ga=C3=ABtan=20Harter?= <gaetan.harter@fu-berlin.de>
Date: Tue, 12 Feb 2019 16:35:13 +0100
Subject: [PATCH] tests/periph_eeprom: take EEPROM_CLEAR_BYTE into account
After being cleared, the memory can be `0xFF` for `atmega` platforms for
example.
Fix the test to take EEPROM_CLEAR_BYTE into account.
---
tests/periph_eeprom/main.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/tests/periph_eeprom/main.c b/tests/periph_eeprom/main.c
index a9af1709df..2b973f0ff7 100644
--- a/tests/periph_eeprom/main.c
+++ b/tests/periph_eeprom/main.c
@@ -246,7 +246,10 @@ static int cmd_test(int argc, char **argv)
assert(eeprom_read_byte(EEPROM_SIZE / 2) == 'A');
/* clear some bytes */
- const uint8_t cleared[4] = {0, 0, 0, 0,};
+ const uint8_t cleared[4] = {
+ EEPROM_CLEAR_BYTE, EEPROM_CLEAR_BYTE,
+ EEPROM_CLEAR_BYTE, EEPROM_CLEAR_BYTE,
+ };
eeprom_clear(0, 4);
memset(result, 0, 4);
ret = eeprom_read(0, (uint8_t *)result, 4);
--
GitLab