LZ85194
IrDA Control Peripheral Engine User
’
s Guide
13
Table 5 shows a list of PE messages identified by MID.
Table 5. List of PE Messages
TYPE OF MESSAGE
MID
DESCRIPTION
Recv_Data
0x1X
Data received from the Host device by IR communication. The Data part represents the
received data with the byte length of (Length -2) bytes. Shows targeted Endpoint where
the data was received by lower 4 bits of MID. Values are shown in the following table.
When PE receives Set_Mode packet, PE outputs the payload data of Set_Mode packet
(LED lighting direction information) as received data by EP0.
X
0
2
Endpoint
EP0
EP2 (Future extension)
Give_Peripheral_Info
0x2X
Need Peripheral devices
’
specific information. The μP must immediately set the required
information to PE with Set_Peripheral_Info command. Shows required specific informa-
tion for PE by lower 4 bits of MID. Values are the following:
X
0
1
2
3
4
5
6
7
Three bytes, which are Descriptor Index, LangID (lower), and LangID (upper) follows
after MID (23H) that indicates the String Descriptor. These are corresponding to the
Descriptor Index and LangID or request Get_Descriptor (STRING)) specified in Universal
Serial Bus Rev. 1.0. One Endpoint ID byte comes after Report Descriptor MID (24H). It
indicates the Endpoint that the Report Descriptor to be applied. Report Descriptor for
Endpoint1 must be applied in case of 01H, that of Endpoint3 must be applied in case of
03H. In the event that ReportID (00H) and ReportType (F0H) replied in this order after
Get_Status MID (27H), this is an inquiry asking for the Peripheral device battery status.
If the Peripheral device has voltage detection capability, the status of battery must be
replied. The
‘
Peripheral Device Specific Information
’
section should be referred for the
details of information.
Type of Specific Information
Peripheral Information
Device Descriptor
Configuration Descriptor
String Descriptor
Report Descriptor
IrDA-Control Descriptor
Copyright Descriptor
Get_Status
IrDA-Control
_Status_Change
0x3X
Report to μP with the change of PE
’
s IrDA Control communication status. Shows
IrDA Control communication status by lower 4 bit of MID. Values are shown in the
following table. Details of the communication status should be referred to the
‘
PE Status
’
section. In addition, this function is only available when the Mode bit of
IrDA-Control_Status_Indication is set enabled.
Data
0
1
2
PE Communication Status
Unenumerated
Unbound
Bound
Abort_Indication
0x4X
PE to report number of packets undelivered to the Host due to some reasons despite of
Send_Data_withAck via IrDA Control communication to the μP. The value upper 2 bits
out of MID lower 4 bits refers to the number of undelivered packets to EP1 and that of
lower 2 bits to EP3. No report when all data is properly sent. This function is effective so
long as Abort_Indication of Mode bit is enabled. PE has two data transmission buffers for
each Endpoint (EP1 and EP3). Thus, the number of packets not transmitted should be
less that two for each Endpoint (EP1 and EP3). Of the value
‘
4X
’
replied as MID, the up-
per 2 bits of
‘
X
’
represents the data failed to be transmitted by EP3, while the lower 2bits
represents the failed data for EP1. For example, if 48H is replied as MID, it indicates that
two data out of all data sent by Send_Data_withAck for EP3 were not sent though they
had ACK on SS-Wire at last process. If 41H is given as MID, it indicates that one data of
out all data sent by Send_Data_withAck for EP1 was not sent though they had ACK on
SS-Wire at last process.