Professional Documents
Culture Documents
PIC16(L)F1454/1455/1459 Family
Silicon Errata and Data Sheet Clarification
The PIC16(L)F1454/1455/1459 family devices that you For example, to identify the silicon revision level
have received conform functionally to the current using MPLAB IDE in conjunction with a hardware
Device Data Sheet (DS40001639B), except for the debugger:
anomalies described in this document. 1. Using the appropriate interface, connect the
The silicon issues discussed in the following pages are device to the hardware debugger.
for silicon revisions with the Device and Revision IDs 2. Open an MPLAB IDE project.
listed in Table 1. The silicon issues are summarized in 3. Configure the MPLAB IDE project for the
Table 2. appropriate device and hardware debugger.
The errata described in this document will be addressed 4. Based on the version of MPLAB IDE you are
in future revisions of the PIC16(L)F1454/1455/1459 using, do one of the following:
silicon. a) For MPLAB IDE 8, select Programmer >
Note: This document summarizes all silicon Reconnect.
errata issues from all revisions of silicon, b) For MPLAB X IDE, select Window >
previous as well as current. Only the Dashboard and click the Refresh Debug
issues indicated in the last column of Tool Status icon ( ).
Table 2 apply to the current silicon 5. Depending on the development tool used, the
revision (A6). part number and Device Revision ID value
Data Sheet clarifications and corrections start on page appear in the Output window.
5, following the discussion of silicon issues. Note: If you are unable to extract the silicon
The silicon revision level can be identified using the revision level, please contact your local
current version of MPLAB® IDE and Microchip’s Microchip sales office for assistance.
programmers, debuggers, and emulation tools, which The DEVREV values for the various PIC16(L)F1454/
are available at the Microchip corporate web site 1455/1459 silicon revisions are shown in Table 1.
(www.microchip.com).
Note: This document summarizes all silicon 2.1 Gain Amplifier Output
errata issues from all revisions of silicon, When using the FVR module, if the gain amplifier
previous as well as current. Only the outputs are set via the CDAFVR or ADFVR bits in
issues indicated by the shaded column in FVRCON while the module is disabled (FVREN =
the following tables apply to the current 0), the internal oscillator frequency may shift, the
silicon revision (A6). device current consumption can increase, and a
Brown-out Reset may occur.
1. Module: Oscillator Work around
1.1 OSCSTAT bits: HFIOFR and HFIOFS Set the FVREN bit of FVRCON to enable the
When HFINTOSC is selected, the HFIOFR and module prior to adjusting the amplifier output
HFIOFS bits will become set when the oscillator selections with the CDAFVR and ADFVR bits. If
becomes ready and stable. Once these bits are set switching from the 4x output setting to the 1x
they become “stuck”, indicating that HFINTOSC is output setting, select the 2x output setting as an
always ready and stable. If the HFINTOSC is intermediary step. Always set the amplifier output
disabled, the bits fail to be cleared. selections to off (’00’) before disabling the FVR
module.
Work around
Affected Silicon Revisions
None.
A2 A5 A6
Affected Silicon Revisions
X
A2 A5 A6
X 3. Module: Program Flash Memory (PFM)
1.2 Oscillator Start-up Timer (OST) bit 3.1 PFM Self Write
During the Two-Speed Start-up sequence, the Writes to the PFM will not execute if the device’s
OST is enabled to count 1024 clock cycles. After clock source is HS or ECH, or if the internal
the count is reached, the OSTS bit is set, and the oscillator is at either 8 MHz or 16 MHz. The DFM
system clock is held low until the next falling edge is unaffected.
of the external crystal (LP, XT or HS mode), before
switching to the external clock source. Work around
When an external oscillator is configured as To write to the PFM, the clock source must have
primary clock and Fail-Safe Clock mode is enabled one of the following settings: internal oscillator set
(FCMEN = 1), any of the following conditions will to 4 MHz or lower, ECM, ECL, XT, External RC, LP
result in the Oscillator Start-up Timer (OST) failing or T1OSC.
to restart: Affected Silicon Revisions
• MCLR Reset
• Wake from Sleep A2 A5 A6
• Clock change from INTOSC to Primary Clock X
This anomaly will manifest itself as a clock failure
condition for external oscillators which take longer 4. Module: CPU
than the clock failure time-out period to start.
4.1 BRA/BRW
Work around If a BRA or BRW instruction is executed
None. concurrently with an interrupt event, the ISR
routine can restore the PC to an incorrect value.
Affected Silicon Revisionss
Work around
A2 A5 A6
Use the GOTO instruction rather than the BRA or
X X BRW instruction.
Affected Silicon Revisions
A2 A5 A6
X X
A2 A5 A6
X X X
• Microchip believes that its family of products is one of the most secure families of its kind on the market today, when used in the
intended manner and under normal conditions.
• There are dishonest and possibly illegal methods used to breach the code protection feature. All of these methods, to our
knowledge, require using the Microchip products in a manner outside the operating specifications contained in Microchip’s Data
Sheets. Most likely, the person doing so is engaged in theft of intellectual property.
• Microchip is willing to work with the customer who is concerned about the integrity of their code.
• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code protection does not
mean that we are guaranteeing the product as “unbreakable.”
Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protection features of our
products. Attempts to break Microchip’s code protection feature may be a violation of the Digital Millennium Copyright Act. If such acts
allow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that Act.
QUALITY MANAGEMENT SYSTEM Microchip received ISO/TS-16949:2009 certification for its worldwide
headquarters, design and wafer fabrication facilities in Chandler and
CERTIFIED BY DNV Tempe, Arizona; Gresham, Oregon and design centers in California
and India. The Company’s quality system processes and procedures
== ISO/TS 16949 ==
are for its PIC® MCUs and dsPIC® DSCs, KEELOQ® code hopping
devices, Serial EEPROMs, microperipherals, nonvolatile memory and
analog products. In addition, Microchip’s quality system for the design
and manufacture of development systems is ISO 9001:2000 certified.