ARM处理器R1＝0x, R2=0xFF008899，则执行指令AND R0,R1,R2后，寄存器R0＝ _R1= _。具体值怎么算_百度知道
ARM处理器R1＝0x, R2=0xFF008899，则执行指令AND R0,R1,R2后，寄存器R0＝ _R1= _。具体值怎么算
是怎么算出来的，请教一下
MOV R0,R1 LSL#2
左偏移2次乘以2^2，但这样的怎么算呢？
我有更好的答案
你把R1和R2的值换算成2进制，然后按位做AND运算就可以了。
MOV R0,R1 LSL#2
左偏移2次乘以2^2，但这样的怎么算呢？
其他类似问题
为您推荐：
arm处理器的相关知识
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁嵌入式系统考试试卷30
上亿文档资料，等你来发现
嵌入式系统考试试卷30
山东科技大学学年第一学期；《嵌入式系统》测试试卷；班级学号姓名；一、单项选择题（每题1分，共15分）；1、完全把系统软件和硬件部分隔离开来，从而大大提；A.图形用户接口B.驱动映射层C.硬件交互层D.；2、实时操作系统（RTOS）内核与应用程序之间的；A.输入/输出接口B.文件系统C.APID.图形；3、为了提高嵌入式软件的可移植性，应注意
山东科技大学学年第一学期《嵌入式系统》测试试卷班级
姓名一、单项选择题（每题1分，共15分）1、
完全把系统软件和硬件部分隔离开来，从而大大提高了系统的可移植性。A. 图形用户接口
B. 驱动映射层
C. 硬件交互层
D. 硬件抽象层2、实时操作系统（RTOS）内核与应用程序之间的接口称为
。A. 输入/输出接口
B. 文件系统
D. 图形用户接口3、为了提高嵌入式软件的可移植性，应注意提高它的
。A. 易用性
D. 设备无关性4、在ARM处理器中，
寄存器包括全局的中断禁止位，控制中断禁止位就可以打开或者关闭中断。A. CPSR
D. LR5、下面
特性不符合嵌入式操作系统特点。A. 实时性
B. 不可定制
D. 易移植6、在嵌入式系统的存储结构中，存取速度最快的是
B. 寄存器组
D. Cache7、处理机主要由处理器、存储器和总线组成，总线包括
。A. 数据总线、串行总线、逻辑总线、物理总线B. 并行总线、地址总线、逻辑总线、物理总线C. 并行总线、串行总线、全双工总线D. 数据总线、地址总线、控制总线8、若每一条指令都可以分解为取指、分析和执行三步。已知取指时间t取指＝4△t，分析时间t分析＝3△t，执行时间t执行＝5△t。如果按串行方式执行完100条指令需要
△t。A. 1190
D. 12059、如上题，如果按照三级流水线方式执行，执行完100t。A. 504
D. 51010、通常所说的32位微处理器是指A.地址总线的宽度为32位
B. 处理的数据长度只能是32位C. CPU字长为32位
D. 通用寄存器数目为32个11、在CPU和物理内存之间进行地址转换时，
将地址从虚拟地址空间映射到物理地址空间A. TCB
D. DMA12 以下叙述中，不符合RISC指令系统特点的是＿＿＿A 指令长度固定，指令种类小B 寻址方式种类丰富，指令功能尽是增强C
设置大量通用寄存器，访问存储器指令简单D 选择使用频率较高的一些简单指令 13、嵌入式系统应用软件一般在宿主机上开发，在目标机上运行，因此需要一个
环境。A. 交互操作系统
B. 交叉编译
C. 交互平台
D. 分布式计算14、在ARM下列指令中错误的是＿＿A MOV R1，＃128
B MOV R1，0x3f7C LDR R1，=0x1128
D LDR R1，0x3f15、在指令系统的各种寻址方式中，获取操作数最快的方式是＿＿＿。A. 直接寻址
B. 立即寻址
C. 寄存器寻址 D. 间接寻址 二、分析题（共25分）1、已知地址0x814，0x80010中分别存放数据0x01，0x02，0x03其中r0=0x, r1=0x, r2=0x, r3=0x执行指令 LDMIA
r0!, {r1-r3}后，写出r0,r1,r2,r3的值？（5分） 2．将如下的程序代码中的斜体加粗部分用汇编语言代替，实现混合编程(12分) char seg7table[16];*((U8*) 0x) = 0x00;for( ; ; ) { for(i=0;i&0x10;i++)
*((U8*) 0x) = seg7table[i];
}3、取你学号的后两位数，以二进制格式写入如图的第二行中，完成任务就绪表，问：你的学号=？，OSRdyTbl[1]=？(二进制数)，OSRdyGrp=？(十进制数) ，并计算出当前最高优先级的值？（8分） 三、编程题：（25分）针对JXARM9－2410实验箱，在我们所做的外部中断实验中，假设，编译后，文件2410init.s中标号IsrIRQ内存地址为0x，外部中断3的中断服务函数eint3_isr的首地址为0x，且定义.EQU
_ISR_STARTADDRESS, 0x33fffe??,(??是你学号的后两位乘以4后变为十六进制数)，其余代码不变，分析2410init.s代码回答下列问题：①HandleIRQ=？②[HandleIRQ]=? ③外部中断3的中断向量地址=？④外部中断3的中断向量地址中的内容=？⑤表述外部中断3从中断发生到中断服务程序被执行的整个过程。四、问答题（35分）1、在嵌入式系统中，Bootloader有何功能？启动代码功能是什么？两者有何关系？在我们所做的带有中断功能的实验中，能否把启动代码去掉，为什么（10分）2、ARM处理器有几种工作模式？ARM的寄存器组织是怎样的？并说明R13、R14、PC（R15）有何特殊作用（15分）3、什么是嵌入式系统？嵌入式系统的特点是什么？在嵌入式系统中会不会出现象微软和英特尔那样的行业巨头，谈谈你的观点（10分） 包含各类专业文献、高等教育、行业资料、应用写作文书、外语学习资料、幼儿教育、小学教育、嵌入式系统考试试卷30等内容。
　长沙理工大学研究生考试试题课程名称: 课程编号: 考试方式:闭卷 拟题教师: ...实时操作系统 ) 、进 4、从嵌入式操作系统特点可以将嵌入式操作系统分为( ... 　嵌入式系统试题开卷 及答案_从业资格考试_资格考试/认证_教育专区。《嵌入式系统》试题开卷答题 时间:90 分钟 装 姓名: 1、试写抢占式和非抢占式的区别。6 分... 　嵌入式系统期末考试试卷 习题_工学_高等教育_教育专区。1.下面哪一种工作模式不属于 ARM 特权模式( A.用户模式 B.系统模式 D A )。 C.软中断模式 D.FIQ 模... 　ARM嵌入式系统试题及答案_电脑基础知识_IT/计算机_专业资料。ARM嵌入式系统试题及答案,考前必备ARM 嵌入式系统基础教程 --- 期中开卷专业:软件 1002 班 姓名:王世... 　效…… 答案及评分细则课程名称:_嵌入式系统开发_ 考试形式:闭卷 考试日期: 2012 年月日 考试时长:120 分钟 一、 判断题(共 15 分,共 15 题,每题 1 分... 　《嵌入式系统》考试试卷试题总分: 100 分 考试时限:120 分钟 题号 得分 一 二 三 四 五 总分 阅卷人 核分人 一、填空题(每空2分,共18分) 1、PC机开机... 　ARM嵌入式系统期末考试试卷_理学_高等教育_教育专区 暂无评价|0人阅读|0次下载|举报文档 ARM嵌入式系统期末考试试卷_理学_高等教育_教育专区。选择题(共 5 小题... 　一 填空 (每空 1 分,共 20 分) 1.嵌入式微处理器一般可分为嵌入式微控制器、嵌入式数字信号处理器、嵌入式微处理器和 嵌入式片上系统四种类型。 2.嵌入... 　2010 ─2011 学年 第 2 学期 序号 《 嵌入式系统 》课程考试试卷( B 卷) 学分:3 考试时间:120 分钟 专业: 计算机科学 年级:08 级 考试方式:闭卷 阅卷人...嵌入式考试题试题,考试,嵌入式,考试题,考试题目,考试题库,嵌入式试题,考试试题,嵌..
扫扫二维码，随身浏览文档
手机或平板扫扫即可继续访问
嵌入式考试题
举报该文档为侵权文档。
举报该文档含有违规或不良信息。
反馈该文档无法正常浏览。
举报该文档为重复文档。
推荐理由：
将文档分享至：
分享完整地址
文档地址：
粘贴到BBS或博客
flash地址：
支持嵌入FLASH地址的网站使用
html代码：
&embed src='/DocinViewer-4.swf' width='100%' height='600' type=application/x-shockwave-flash ALLOWFULLSCREEN='true' ALLOWSCRIPTACCESS='always'&&/embed&
450px*300px480px*400px650px*490px
支持嵌入HTML代码的网站使用
您的内容已经提交成功
您所提交的内容需要审核后才能发布，请您等待！
3秒自动关闭窗口您所在位置： &
&nbsp&&nbsp&nbsp&&nbsp
基于单片机的热能表设计毕业设计.doc77页
本文档一共被下载：
次 ,您可免费全文在线阅读后下载本文档
文档加载中...广告还剩秒
需要金币：200 &&
你可能关注的文档：
··········
··········
基于单片机的热能表设计
The Heat Meter Based on MCU
毕业设计 论文 开题报告
题目 基于单片机的热能表设计
专业 电气工程及其自动化
目前，北方大部分集中供暖的省市都发布了新建住宅集中采暖系统必须采用分户热计量的技术标准或行政法规，给热量表行业带来了巨大商机。然而，我国试点项目使用的热计量产品多为欧洲进口产品，国内自主研发的产品还未实现成熟的批量生产，质量参差不齐。从国内供热计量的试点经验来看，即使是进口产品，在施工和使用过程中也存在问题，某种程度上也影响了供热计量工作的顺利进行。
国内外研究现状
在国外，集中供暖计量收费是20世纪70年代中期由欧洲开始的。相应的“热量表”，也经历了从机械式、电子模拟积分式、电子数字积分式直到微处理器为基础的智能式的发展过程。直到90年代，户用热量表基本上定型，设计趋于一致1997年4月，欧洲共同体正式通过了统一的热量表标准，代号EN1434。现在向中国市场上推销的欧洲各国的热量表，大部分都标明了“符合OIML-R75”和“符合EN1434标准”。欧洲表热量积分计算仪一律采用K系数补偿的方式。K系数的取值在进水和回水上是不同的，只能规定其中一个固定的位置，不得变换。欧洲热量表采用测温元件是Pt100和Pt500。Pt100即在0℃时电阻值为100Ω。
在国内，中国热量表的自行研制开始于上世纪的九十年代。根据专利文献，中国最早研制“采暖用热量表”的是山西的一位教师。中国热量表的研发、生产中，认真学习借鉴了国外成熟的技术，也针对中国国情做了大量自主开发的努力。中国热量表有以下特点：测温传感器选用了Pt1000（相比欧洲过去采用的Pt100和P
正在加载中，请稍后...From Texas Instruments Wiki
This page addresses the logical communication protocol between the CC3000 wireless module and SPI host. For physical communication details, please see .
The content of this page applies to CC3000
(CC3000 firmware version 1.26).
All communication between the CC3000 and SPI host (e.g., a microcontroller) is carried out using SPI packets, and thus the SPI packet forms the outermost logical protocol layer. A single SPI packet is transferred always within a single active chip select period (between one falling and rising nCS edge). The CC3000 protocol offers no means to fragment packets, thus all data belonging to a single packet must be sent inside one nCS active period.
Every packet transfered over the SPI-Bus consists of 5-byte long SPI header followed by data bytes (SPI Payload). The CC3000 expects 16-bit aligned SPI communications, thus a SPI packet must always have even number of bytes. In case the data to be transported has odd bytes of data, an additional padding byte must be added. Although the documentation recommends to use 0x00 for padding byte, experimentation shows that the value is not being evaluated and thus could be arbitrary.
Every SPI packet exchanged between the CC3000 and the SPI host have to adhere to the following schema:
SPI Header, 5 bytes
SPI Payload (data+optional padding), Min. 5, max. 65535 bytes
Byte x; 5 ≤ x &#
Optional padding byte to achieve even byte long SPI packet
The shortest by CC3000 implemented packet has 5 byte SPI payload, thus the shortest SPI paket length is 10 bytes.
The fields in the 5-byte SPI header have different meaning, according to the direction of communication.
As SPI-Bus is under full control of SPI master, the master has to select either to push (write) or pull (read) data from CC3000 module. The first byte of every SPI packet the SPI master sends out defines the Operation Code. The Operation Code field has only two possibilites:
0x01 for WRITE
0x03 for READ
Although the SPI-Bus is capable of full duplex communications, the CC3000 SPI communication protocol is implemented in a half-duplex manner: if the SPI master is sending data towards CC3000 on the MOSI line, the bytes originating from CC3000 and vice versa when the CC3000 sends data to the SPI master on the MISO line, the CC3000 will not interpret the incoming bytes on the MOSI line.
Every SPI packet starts with SPI master sending the Operation Code byte towards CC3000. After the Operation Code, the selection of WRITE or READ is valid and cannot be changed until the end of current SPI packet (until nCS goes back high). In case when the Operation Code was 0x01=WRITE, the SPI master continues transmitting further bytes on the MOSI line and the CC3000 continues sampling the incoming bytes. If the Operation Code was 0x02=READ, the CC3000 ignores further bytes from the SPI master on the MOSI line, and starts answering with data bytes on the MISO line.
SPI MOSI WRITE packet is made of a SPI header and SPI payload. The SPI header consists always of 5 bytes, whereas the SPI payload length can vary to fit the transported data length. In case the SPI header plus payload length have odd amount of bytes, an additional padding byte is added to make SPI paket 16-bit aligned as required by CC3000.
The schema of a MOSI SPI WRITE packet:
SPI Header, 5 bytes
Operation Code WRITE
Payload length (16-bit Big-endian)=n
SPI Payload (data+optional padding), Length=n, min. 5, max. 65535 bytes
Optional padding byte to achieve even byte long SPI packet
Note that the payload length in bytes 2 and 3 includes also the optional padding byte. The SPI header 4th and 5th byte are so called Busy Bytes, to allow some time for CC3000 to prepare the payload. CC3000 datasheet recommends to use value 0x00 for both bytes.
During WRITE, the CC3000 publishes on MISO line:
SPI Header, 5 bytes
0x02 (always)
0x00 (always)
SPI Payload, Min. 5, max. 65535 bytes
The first two packet bytes the CC3000 outputs on MISO line are independent of MOSI Operation Code always 0x02 and 0x00. The MISO packet length is the same as MOSI SPI WRITE packet, all bytes in the MISO payload are 0x00. The SPI master can ignore all bytes sent out by the CC3000 during a WRITE command.
In case the CC3000 has an event or data to transmit to SPI master, it pulls the IRQ line low. It is up to SPI master to react to this (e.g., using a falling edge interrupt configured pin) and to read out the data using a READ packet.
When SPI master wants to read in data from CC3000, it should first clock out on MOSI line the Operation command 0x03 READ and 4 further bytes. Although the CC3000 datasheet recommends the bytes following the Operation code to have a value of 0x00, they do not get evaluated by CC3000 and thus can be arbitrary. (The host driver in
also does not adhere to the datasheet recomendation and uses 0x03 for all MOSI bytes during a READ packet.) The CC3000 answers in bytes 4 and 5 with the payload length it wishes to transmit, lets call this 16-bit value n. After the initial 5 bytes, the SPI master should continue to clock in/out n bytes before raising the nCS line back high. Note that n is always an odd value to adhere to even SPI packet length rule.
The schema of a MOSI SPI READ packet (n is the payload length sent in at MISO bytes 4 and 5):
SPI Header, 5 bytes
Operation Code READ
4 arbitrary bytes, e.g.:
SPI Payload, Min. 5, max. 65535 bytes
n arbitrary bytes
The CC3000 replies to SPI READ on MISO line as follows:
SPI Header, 5 bytes
Operation Code REPLY
Payload length (16-bit Big-endian)=n
SPI Payload, Length=n, min. 5, max. 65535 bytes
Note that the payload length in bytes 4 and 5 includes also the optional padding byte.
In the SPI payload, Host Controller Interface (HCI) messages are exchanged between the SPI master and the CC3000. Using HCI messages the SPI master can interact with CC3000.
There are 4 types of HCI messages (you'll find the same color coding in the packets below for easier recognition):
Description
TI abbrevation
SPI master -& CC3000
HCI_TYPE_CMND
HCI_TYPE_DATA
SPI master -& CC3000
HCI_TYPE_PATCH
CC3000 -& SPI master
HCI_TYPE_EVNT
Each HCI message is preluded with a header, with first byte of the header being the type. The length of the HCI header and the following field bytes are type-specific and thus will be handled separately next.
HCI command message is sent by SPI master towards CC3000 to trigger an action or data request, thus only MOSI direction HCI command message is defined.
SPI Header, 5 bytes
Payload length (16-bit Big-endian)=n
SPI Payload, Length=n, min. 5, max. 259 bytes
HCI message
HCI header (4-bytes)
HCI_TYPE_CMND
Command operation code (16-bit Little-endian)
Arguments length (8-bit)=p
HCI payload, p 0 ≤ p &#
Optional padding
The options for the Command operation code (possibly not a full list with all options. Note that the code in this table is the value, and not the Little-endian formation as in the original SPI packet):
Operation code
Arguments length
Minimum 29 (28 + min SSID length 1), maximum 92 (28 + max SSID length 32 + max key length 32)
Minimum 25 (24 + min SSID length 1), maximum 120 (36 + max SSID length 32 + 4* max WEP key length 13 bytes)
HCI_CMND_WLAN_CONFIGURE_PATCH
HCI_CMND_NVMEM_WRITE_PATCH
HCI_CMND_NVMEM_SWAP_ENTRY
HCI_CMND_SETSOCKOPT
HCI_CMND_GETSOCKOPT
HCI_CMND_RECVFROM
HCI_CMND_GETHOSTNAME
Minimum 8 + shortest host name length (1 ?), maximum =?
HCI_CMND_MDNS_ADVERTISE
Minimum 12 + shortest own host name length (1 ?), maximum =?
HCI_CMND_GETMSSVALUE
HCI_CMND_NETAPP_DHCP
HCI_CMND_NETAPP_SET_TIMERS
HCI Data messages can be transported in both directions - from SPI master to CC3000 (for example to send data over a wireless link) or other way around (for example to receive data over the wireless link). HCI Data message can carry two types of payload information: arguments and data.
The HCI part of the message is defined similarly in both directions, but the SPI header is different. For the sake of clarity full SPI packets are shown for both directions below separately.
SPI Header, 5 bytes
Payload length (16-bit Big-endian)=n
SPI Payload, Length=n, min. 5, max. 65535 bytes
HCI message
HCI header (5-bytes)
HCI_TYPE_DATA
Data operation code (8-bit)
Arguments length (8-bit)=p
Payload length (16-bit Little-endian)=m
HCI payload, m 0 ≤ m &#
Arguments, p 0 ≤ p &#
Data, m-p 0 ≤ m-p &#
Optional padding
Note that the HCI Data message does not explicitly include the amount of data bytes in the packet, instead this needs to be calculated by subtracting the arguments length from the HCI payload length.
The options for MOSI Data operation code (possibly not a full list with all options):
Operation code
SPI Header, 5 bytes
Payload length (16-bit Big-endian)=n
SPI Payload, Length=n, min. 5, max. 65535 bytes
HCI message
HCI header (5-bytes)
HCI_TYPE_DATA
Data operation code (8-bit)
Arguments length (8-bit)=p
Payload length (16-bit Little-endian)=m
HCI payload, m 0 ≤ m &#
Arguments, p 0 ≤ p &#
Data, m-p 0 ≤ m-p &#
Optional padding
Note that the data message from CC3000 needs to be clocked in by SPI master using a .
The options for MISO Data operation code (possibly not a full list with all options):
Operation code
HCI_DATA_RECVFROM
HCI_DATA_RECV
The TI CC3000 module includes the CC3000 chipset and also an 32KB EEPROM, which among other information, contains three end-user servicable code fragments, so called patches:
bootloader
WLAN driver ROM
WLAN firmware
From time to time, TI provides an updated
for CC3000 that updates these code segments with bugfixed code or new features. Altough the TI Patch Programmer (at least in version 1.12) uses HCI_CMND_NVMEM_WRITE command (see ) to (re-)write the EEPROM segments, the CC3000 supports also a dedicated HCI message type (HCI_TYPE_PATCH=0x03) for this purpose.
It is important that the WLAN driver ROM and WLAN firmware segments in the EEPROM have the same version patches. If this is not the case, the CC3000 sends
message, which must be answered with an HCI Patch message to continue operation (even if the code might opt to update the EEPROM using HCI_CMND_NVMEM_WRITE message instead). Thus, the host driver should implement HCI Patch message type, at least to be able to answer the
event message.
Inside a single HCI Patch message, the patch data can be optionally separated into multiple portions, whereas at least 1 patch portion needs to be included in the packet. The original
limits the portion data chunk size to 1000 bytes.
HCI Patch message schema:
SPI Header, 5 bytes
Payload length (16-bit Big-endian)=n
SPI Payload, Length=n, min. 7, max. 65535 bytes
HCI message
HCI header (4-bytes)
HCI_TYPE_PATCH
Patch operation code (8-bit)
Patch length (16-bit Little-endian)=p
HCI payload, p 2 ≤ p &#
Patch portion 1 (mandatory)
Patch portion length (16-bit Little-endian)=m
Patch Data, m 0 ≤ m &#
Patch portion r, r & 1 (optional)
Patch portion length (16-bit Little-endian)=s
Patch Data, s 0 ≤ s &#
Optional padding
The three possible options for Patch operation code field are:
Operation code
HCI_EVENT_PATCHES_DRV_REQ
HCI_EVENT_PATCHES_FW_REQ
HCI_EVENT_PATCHES_BOOTLOAD_REQ
See an example of HCI Patch message to deny the CC3000 firmware patch request .
HCI Event message is sent by CC3000 towards SPI master. It is either to acknowledge a command or to notify SPI master of asynchronous unsolicited event. Note that the event message needs to be clocked in by SPI master using .
Note that the transmission of selected event messages can be disabled using
command. Following events can be disabled:
, unsolicited connect event
, unsolicited disconnect event
HCI_EVNT_WLAN_UNSOL_INIT, initialization done event
HCI_EVNT_WLAN_UNSOL_TX_COMPLETE, tranmission complete event
report event
report event
, smart config done event
, keepalive event
SPI Header, 5 bytes
Payload length (16-bit Big-endian)=n
SPI Payload, Length=n, min. 5, max. 259 bytes
HCI message
HCI header (4-bytes)
HCI_TYPE_EVNT
Event operation code (16-bit Little-endian)
Arguments length (8-bit)=p
HCI payload, p 0 ≤ p &#
Optional padding
CC3000 acknowledges most commands using an event with the same hex value as the command.
The options for Event operation code (possibly not a full list with all options. Note that the code in this table is the value, not the Little-endian formation as in the original SPI packet):
Event operation code
Applicable command or data message
HCI_EVNT_WLAN_IOCTL_SMART_CONFIG_START
HCI_EVNT_WLAN_IOCTL_SMART_CONFIG_STOP
HCI_EVNT_WLAN_CONFIGURE_PATCH
HCI_CMND_WLAN_CONFIGURE_PATCH
HCI_EVNT_NVMEM_WRITE
HCI_EVNT_NVMEM_CREATE_ENTRY
HCI_EVNT_NVMEM_WRITE_PATCH
HCI_CMND_NVMEM_WRITE_PATCH
HCI_EVNT_NVMEM_SWAP_ENTRY
HCI_CMND_NVMEM_SWAP_ENTRY
Likely gets sent if EEPROM firmware version != driver version
HCI_EVNT_DATA_SEND
HCI_EVNT_RECV
HCI_EVNT_ACCEPT
HCI_EVNT_LISTEN
HCI_EVNT_SELECT
HCI_EVNT_SETSOCKOPT
HCI_CMND_SETSOCKOPT
HCI_EVNT_GETSOCKOPT
HCI_CMND_GETSOCKOPT
HCI_EVNT_CLOSE_SOCKET
HCI_EVNT_RECVFROM
HCI_CMND_RECVFROM
HCI_EVNT_WRITE
HCI_EVNT_GETHOSTBYNAME
HCI_CMND_GETHOSTNAME
HCI_EVNT_MDNS_ADVERTISE
HCI_CMND_MDNS_ADVERTISE
HCI_EVNT_GETMSSVALUE
HCI_CMND_GETMSSVALUE
HCI_EVNT_NETAPP_DHCP
HCI_CMND_NETAPP_DHCP
HCI_EVNT_NETAPP_ARP_FLUSH
HCI_EVNT_NETAPP_SET_DEBUG_LEVEL
HCI_EVNT_NETAPP_SET_TIMERS
HCI_CMND_NETAPP_SET_TIMERS
HCI_EVNT_WLAN_UNSOL_INIT
HCI_EVNT_WLAN_UNSOL_TX_COMPLETE
The following pages, can be useful as a reference: