From 8cd14cb22efd07e72d76c9bba5ed94e60720f312 Mon Sep 17 00:00:00 2001 From: Tom Nisbet Date: Mon, 24 Jun 2019 16:25:47 -0400 Subject: [PATCH] List devices in 28C readme --- README-28C.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README-28C.md b/README-28C.md index 5b3b16e..93f1fc1 100644 --- a/README-28C.md +++ b/README-28C.md @@ -11,13 +11,15 @@ In practice, the Xicor chips seem very forgiving of the timing, doing successful # Solution -The TommyProm programmer uses direct port access to control the data bus and addressing shift register. This is much faster than doing individual DigitalWrite calls and allows the unlock and page write code to run comfortably with the tBLC constraints. It has been successfully tested with the following 28C256 chips: +The TommyProm programmer uses direct port access on the Arduino to control the data bus and addressing shift register. This is much faster than doing individual DigitalWrite calls and allows the unlock and page write code to run comfortably within the tBLC constraints. It has been successfully tested with the following 28C256 chips: * Atmel AT28C256-15PU * Catalyst/ON Semi CSI CAT28C256P-12 * Xicor X28C256P-15 * Xicor X28C256P-25 +The Atmel chips tested included a batch from eBay that may not have been genuine, but they were unlocked and burned successfully with the TommyProm code. + The capture below shows an unlock command sequence where the tBLC us within 80us for each byte. ![Unlock Timing](docs/Unlock-Timing.png)