欢迎访问ic37.com |
会员登录 免费注册
发布采购

F87EHHD 参数 Datasheet PDF下载

F87EHHD图片预览
型号: F87EHHD
PDF下载: 下载PDF文件 查看货源
内容描述: [FXTH87E, Family of Tire Pressure Monitor Sensors]
分类和应用:
文件页数/大小: 183 页 / 1700 K
品牌: NXP [ NXP ]
 浏览型号F87EHHD的Datasheet PDF文件第34页浏览型号F87EHHD的Datasheet PDF文件第35页浏览型号F87EHHD的Datasheet PDF文件第36页浏览型号F87EHHD的Datasheet PDF文件第37页浏览型号F87EHHD的Datasheet PDF文件第39页浏览型号F87EHHD的Datasheet PDF文件第40页浏览型号F87EHHD的Datasheet PDF文件第41页浏览型号F87EHHD的Datasheet PDF文件第42页  
NXP Semiconductors  
FXTH87E  
FXTH87E, Family of Tire Pressure Monitor Sensors  
Table 30.ꢀSIMTST register field descriptions  
Field  
Description  
7
Reserved Bit — These bits are reserved for factory trim and should not be altered by the user.  
reserved  
6:4  
Temperature Restart High threshold — Binary coded from 0x00 to 0x07; recommend applications overwrite  
to 0x06 at each wakeup cycle.  
TRH  
3:1  
Reserved Bit — These bits are reserved for factory trim and should not be altered by the user.  
Temperature Restart Outside  
reserved  
1ꢀTR module is outside the TREARM temperature range and will restart the MCU if the TRE bit is set and  
temperature falls back within the TRESET temperature range.  
0
TRO  
0ꢀTR module is within the TRESET temperature range and the MCU cannot be armed to restart when  
temperature falls back to the TRESET range. The TRE bit cannot be set.  
7.5 Interrupts  
Interrupts provide a way to save the current CPU status and registers, execute an  
interrupt service routine (ISR), and then restore the CPU status so processing resumes  
where it left off before the interrupt. Other than the software interrupt (SWI), which is a  
program instruction, interrupts are caused by hardware events. The debug module can  
also generate an SWI under certain circumstances.  
If an event occurs in an enabled interrupt source, an associated read-only status flag  
will become set. The CPU will not respond until and unless the local interrupt enable is a  
logic 1 to enable the interrupt. The I bit in the CCR must be a logic 0 to allow interrupts.  
The global interrupt mask (I bit) in the CCR is initially set after reset which masks  
(prevents) all maskable interrupt sources. The user program initializes the stack pointer  
and performs other system setup before clearing the I bit to allow the CPU to respond to  
interrupts. When the CPU receives a qualified interrupt request, it completes the current  
instruction before responding to the interrupt. The interrupt sequence follows the same  
cycle-by-cycle sequence as the SWI instruction and consists of:  
Saving the CPU registers on the stack  
Setting the I bit in the CCR to mask further interrupts  
Fetching the interrupt vector for the highest-priority interrupt that is currently pending  
Filling the instruction queue with the first three bytes of program information starting  
from the address fetched from the interrupt vector locations  
While the CPU is responding to the interrupt, the I bit is automatically set to avoid  
the possibility of another interrupt interrupting the ISR itself (this is called nesting of  
interrupts). Normally, the I bit is restored to 0 when the CCR is restored from the value  
stacked on entry to the ISR. In rare cases, the I bit may be cleared inside an ISR  
(after clearing the status flag that generated the interrupt) so that other interrupts can  
be serviced without waiting for the first service routine to finish. This practice is not  
recommended for anyone other than the most experienced programmers because it can  
lead to subtle program errors that are difficult to debug.  
The interrupt service routine ends with a return-from-interrupt (RTI) instruction which  
restores the CCR, A, X, and PC registers to their pre interrupt values by reading the  
previously saved information off the stack.  
When two or more interrupts are pending when the I bit is cleared, the highest priority  
source is serviced first.  
FXTH87ERM  
All information provided in this document is subject to legal disclaimers.  
© NXP B.V. 2019. All rights reserved.  
Reference manual  
Rev. 5.0 — 4 February 2019  
38 / 183  
 
 
 复制成功!