Maxim MAXQ612 Errata Sheet

This document describes two errors of MAXQ612 revision B1 chip. The first error is that when the internal oscillator (PLL) is used in divide-by-4 mode as system clock, the watchdog timer reset will lock the IC, and a power cycle is required to recover. The second error is that flash word programming and page erase operations do not complete successfully when invoked with clock divide-by-2, divide-by-4, or divide-by-8 modes active.


Maxim MAXQ612 Errata Sheet - cover page
Brand
Maxim
Category
Other Electronics
Document type
Application Note
Language
English
Pages
4
File format
PDF
File size
37 KB
Published
21 March, 2012
Updated
30 September, 2023
MD5 checksum
CC9B274F41A1B8E7D0CC5EEBD03CFB21

About this manual

The errata sheet documents several functional discrepancies observed in MAXQ612 revision B1 devices and offers recommended workarounds. It applies only to components marked with the B1 revision code on the package.

Key issues include watchdog timer reset locking the IC, flash programming failures in clock‑divided modes, inadvertent erasure of system code when memory protection is enabled, and problems with certain instructions and interrupt priorities. The document also provides a revision history for reference.

What's inside

  • WATCHDOG TIMER RESET LOCKS THE IC IN RESET
  • FLASH PROGRAM/ERASE OPERATIONS FAIL IN CLOCK‑DIVIDED MODE
  • SYSTEM CODE IS INADVERTENTLY ERASED
  • MEMORY PROTECTION FAULT ASSERTED
  • PUSH INSTRUCTION CAUSES CODE EXECUTION ERROR
  • USE OF INTERRUPT PRIORITY FEATURE CAN CAUSE INCORRECT PROCESSING OF INTERRUPTS
  • °C PERIPHERAL DOES NOT FUNCTION CORRECTLY
  • REVISION HISTORY

Frequently asked questions

What happens when the watchdog timer reset occurs in divide‑by‑4 mode?

The watchdog timer reset locks the IC in reset, requiring a power cycle to recover.

Why do flash program/erase operations fail in clock‑divided modes?

Flash word programming and page erase operations do not complete successfully when the system clock is divided; the workaround is to set the clock to divide‑by‑1 before performing these operations.

What is the cause of a memory fault when debugging upper memory?

Entering debug mode in upper memory causes the debug engine to drop the privilege level, generating a memory fault upon return from the debug code.

Download PDF (37 KB)

More Maxim Manuals


View all Maxim manuals →