Datasheet 搜索 > 微控制器 > Microchip（微芯） > PIC18F26K20-I/SO 数据手册 > PIC18F26K20-I/SO 开发手册 4/18 页
器件3D模型￥ 20.522
PIC18F26K20-I/SO 开发手册 - Microchip（微芯）
制造商:
Microchip（微芯）
分类:
微控制器
封装:
SOIC-28
描述:
MICROCHIP PIC18F26K20-I/SO 微控制器, 8位, 闪存, AEC-Q100, PIC18FxxKxx, 64 MHz, 64 KB, 3.84 KB, 28 引脚, SOIC
Pictures:
3D模型
符号图
焊盘图
引脚图
产品图
页面导航:
应用领域在P1P5P15
导航目录
PIC18F26K20-I/SO数据手册
Page:
of 18 Go
若手册格式错乱，请下载阅览PDF原文件
AN1095
DS01095D-page 4 © 2011 Microchip Technology Inc.
Status Flags
Status flags have been provided to indicate whether an
error or warning condition occurs during the emulation
process. These indicators are accessed in the Data
EEPROM Flags register; all flags are active-high.
The status bits and return values are defined as
follows:
• addrNotFound(0xFF/0xFFFF) – A read operation
occurred on a previously unwritten data EEPROM
address.
• expiredPage(0x1) – The program memory erase/
write cycle count has exceeded the user-defined
limit. The algorithm will attempt to execute the
write operation.
• packBeforePageFull(0x2) – The pack routine was
called before the currently active page was full.
The routine will attempt to move the latest data
EEPROM information to the packed page even
though the active page is not full.
• packBeforeInit(0x3) – The pack routine was
executed before the initialization routine. The
pack operation was aborted.
• packSkipped(0x4) – A page was written beyond
the page boundary. This may be a result of the
pack routine not being executed properly. The
pack operation was aborted.
• illegalAddress(0x5) – There was an attempt to
write/read with a data EEPROM address equal to
or greater than the size of data EEPROM. The
read/write operation was aborted.
• pageCorrupt(0x6) – The page status information
was corrupted. The current operation was
aborted.
• writeError(0x7) – The information that was written
into program memory failed the verification. The
current operation was aborted.
The status flags differ in severity and how they are
serviced. The informational status flags are expected to
occur during normal processing and are serviced by
simply clearing the flag with the associated macro.
These include: addrNotFound, packBeforePageFull
and illegalAddress flags.
Warning status flags indicate a condition has been
exceeded but processing will continue. This includes
the expiredPage status flag. With this flag set, the
algorithm will attempt to process read and write
requests, but the flag will be set after each operation.
The most severe flags are the system error status flags.
These imply either the integrity of the data EEPROM
information has been compromised and/or the algorithm
cannot continue until the offending condition has been
resolved. These include packBeforeInit, pageCorrupt
and writeError flags.
To avoid a packBeforeInit event, ensure the
initialization routine, DataEEInit, is called before
performing any other emulation routine. Since this
routine accesses the current state of the emulation
process, it will take action only if it is required.
Therefore, it can be called at any time during data
EEPROM emulation.
The pageCorrupt and writeError flags indicate that a
write operation failed to verify and the current operation
was aborted. If this occurs, the integrity of the data
EEPROM information has been compromised. No
further emulation operations should be attempted. The
only recourse is to erase all of the pages of program
memory reserved for data EEPROM emulation and
attempt to reinitialize them.
Macros are available to retrieve and clear the status
flag values. Status flags are cleared only by the user.
No operation is affected by the value of any flag, but the
flag’s value will indicate whether an operation has
completed successfully.
EXAMPLE 1: MACROS NAMING
CONVENTION EXAMPLE
All of the flags can be read or cleared in a single
operation using the 8-bit character, dataEEFlags.val.
Note: All EEPROM banks affect the same status
flags.
Macros: “Getx” “Setx y”
x = Flag name
y = Value assigned to flag
器件 Datasheet 文档搜索
AiEMA 数据库涵盖高达 72,405,303 个元件的数据手册，每天更新 5,000 多个 PDF 文件
