MDK-ARM Keil, MDK-ARM Datasheet - Page 131

• Manufacturer Part Number: MDK-ARM
• Description: KIT REALVIEW MCU DEVELOPMENT
• Manufacturer: Keil
• Type: Compiler and IDEr

Specifications of MDK-ARM

• For Use With/related Products: ARM MCUs
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

Getting Started: Building Applications with RL-ARM
Once the input and output items have been defined, we can complete the Report
descriptor by closing the collection.
};
By default, the HID OUT packet is sent to
Endpoint 0 as a set_report control packet.
Endpoint 0 is normally reserved for control
information, but it is the way that the driver
works. The IN packet is sent from Endpoint 1.
The Endpoint events must be enabled for both of these Endpoints.
The IN packet is configured as an interrupt pipe. Its update rate and maximum
packet size are defined in the Endpoint descriptor.
USB_ENDPOINT_DESCRIPTOR_TYPE,
Once the descriptor configuration is complete, the application code can start the
RL-USB driver running.
__task void USB_Start (void)
}
When the driver has been started, any task can exchange data with the USB host.
The USB host will request data packets on Endpoint 1 at the rate you have
defined in the Endpoint descriptor. In
responsible for updating the Endpoint 1buffer with the current status of the
button data.
void USB_EndPoint1 (DWORD event)
}
HID_EndCollection
USB_ENDPOINT_IN(1),
USB_ENDPOINT_TYPE_INTERRUPT,
WBVAL(0x0004),
0x20,
USB_Init ();
USB_Connect (__TRUE);
os_tsk_delete_self ();
switch (event)
}
case USB_EVT_IN:
break;
GetInReport ();
USB_WriteEP (0x81, &InReport, sizeof (InReport));
{
{
{
usbuser.c
// bDescriptorType
// bEndpointAddress
// bmAttributes
// wMaxPacketSize
// 32ms
// USB Initialization
// USB Connect
// Terminate Task
the Endpoint 1 handler is
// bInterval
131