Drivers NXP USB Devices

USB Products
smxUSBD™

Thanks for the info, however, I had already tried everything. The apple device driver was never on my computer, however, I was able to install it after installing a program called 'Driver Update' for some reason when I downloaded the 'Apple mobile device driver' it did not install, but after downloading the driver update program, there was no problem and the file installed without a hitch. The package provides the installation files for NXP ProximityBased SmartCard Reader Driver version 1.0.4.42. If the driver is already installed on your system, updating (overwrite-installing) may fix various issues, add new functions, or just upgrade to the available version. Driver Description Download drivers for NXP ISSC Bluetooth USB Adapter Bluetooth devices (Windows 10 x86), or install DriverPack Solution software for automatic driver download and update Are you tired of looking for the drivers for your devices?


USB Device Stack
smxUSBD is a robust USB device stack especially designed and developed for embedded systems. It is written in C, and can run on any hardware platform. While optimized for SMX®, smxUSBD can be ported to another RTOS or operate in a stand-alone environment. NXP
smxUSBD is a full-featured USB device stack. It offers a clean, modular design that enables embedded developers to easily add USB device capabilities to their products. Normally this is done to permit connection to a PC or laptop in order to upload or download data, tables, code, or audio, or to control or configure devices. The smxUSBD device stack is offered separately from the smxUSBH host stack to reduce system cost and memory usage for projects not needing a host stack. It is compliant with the USB v2.0 specification (see www.usb.org).
For easy connectivity to a PC or laptop, smxUSBD includes mouse and keyboard function drivers, and the following are available separately: Audio, Device Firmware Upgrade (DFU), Ethernet over USB (ECM, NCM, RNDIS), Mass Storage, Media Transfer Protocol (MTP), Serial, and Video. Each is compatible with the corresponding Windows, Mac OS, and Linux USB driver. Thus, a device using smxUSBD does not require a custom W/M/L driver in order to connect to a PC or laptop. All that is needed is to decide on the connection type most appropriate for your device and to use the corresponding API for that device - see below.
Also available is a USB composite function driver framework, which allows a device to simultaneously look like two or more USB devices. The USB multi-port serial function driver allows a single USB connection to function as multiple serial ports (up to 1/2 the number of controller endpoints). This function driver comes with a custom Windows driver that supports it.
Layers

Drivers Nxp Usb Devices Wireless Adapter


  • Function Driver Layer provides USB functions to an application such as audio, mass storage, serial, and video.
  • Device Core Layer provides the common USB device framework.
  • Device Controller Driver Layer provides the interface to the selected USB device controller.
  • Porting Layer provides service functions related to the hardware, OS, and compiler.


Function Drivers
The following sections describe each function driver and its API. The USB host is a Windows, Mac OS, or Linux system. See the smxUSBD User’s Guide for any limitations and implementation you must do for these.
Audio
The Audio function driver makes your device look like a sound card to the USB host. You can include a speaker and/or microphone in this audio device so you can playback and/or record sound. You can also integrate a MIDI port into your device so it can accept MIDI data. There is no need to install any driver or .inf file in Windows, Mac OS, or Linux to support this device but you may need to implement the sound device driver yourself, according to your system hardware and software environment.
sud_AudioIsConnected(port)
sud_AudioSendAudioData(port, pData, iLen)
sud_AudioGetAudioData(port, pData, iLen)
sud_AudioGetCurSpkSettings(port, pSettings)
sud_AudioGetCurMicSettings(port, *pSettings)
sud_AudioSendMIDIData(port, pData, iLen)
sud_AudioGetMIDIData(port, pData, iLen)
sud_AudioRegisterNotify(port, handler)
sud_AudioPackMIDIEvent(port, pData, pEvent)
sud_AudioUnpackMIDIEvent(port, pData, pEvent)
DFU
The DFU function driver allows updating the firmware in your device. The Windows operating system does not have a built-in driver for it, so you need to use a driver, such as the one provided by MDI or others that are commonly available. The DFU runtime function may be used as part of a composite device with other functions such as serial or mass storage. This is not a full firmware update solution. See the smxUSBD User’s Guide for details.
sud_DFUIsConnected()
sud_DFURegisterInterface (*pIF)
sud_DFUWriteDone (result, condition)
sud_DFUIsRuntimeMode()
Ethernet over USB
The Ethernet over USB function driver makes your device look like a network adapter to a Windows, MacOS, or Linux USB host. The host can communicate with this device via Ethernet data packets. Normally you need a TCP/IP stack on your device and use the APIs provide by this function driver to emulate an Ethernet device and add it to your network stack. This device has been integrated with smxNS, our TCP/IP stack. Then the host and your device can communicate with each other by TCP/IP with a USB cable instead of an Ethernet cable. One use of this is to allow configuring a device from the web browser on a host communicating with a web server on your device. This is especially useful if your processor has only a USB device controller and no Ethernet controller.
This driver supports CDC-ECM, CDC-NCM, and RNDIS for different host OSes. Windows supports RNDIS, and MacOS and Linux support ECM and NCM. RNDIS and either ECM or NCM can be enabled to support all three OSes, and the proper one is used at runtime when the device is plugged in. NCM supports packet aggregation.
int sud_NetIsPortConnected(port)
int sud_NetIsAggregationSupported(port)
int sud_NetWriteData(port, pBuf[], len[], packets)
void sud_NetRegisterPortNotify(port, handler)
void sud_NetSetEthernetAddr(port, pMACAddr)
HID Communication
The HID Communication function driver is useful for transferring small amounts of data. It is an alternative to the Serial function driver that does not require installing a driver or .inf file on Windows. It requires writing a special Windows application to communicate with it; a sample is provided.
sud_HIDIsConnected()
sud_HIDSendInput(*pDataBuf, size)
sud_HIDRegisterOutputNotify(handler)
Keyboard (Included)
The Keyboard function driver makes your device look like an HID keyboard to the USB host. It inputs key events to your PC.
sud_KBDInput(modifier, *key, count)
Mass Storage
The Mass Storage function driver makes your device look like a removable disk to the USB host. You can copy files to and from it.
sud_MSRegisterDisk(pDiskOper, lun)
Media Transfer Protocol (MTP)
The Media Transfer Protocol (MTP) function driver includes PTP support. It makes your device look like a digital still image device to the USB host. There is no need to install any driver or .inf file in Windows to support this device, but you may need to implement the file system interface (if not using smxFS) and the interface to get the properties of the files your device will support, such as the image width, height, etc.
MTP can also be used for general file transfer as an alternative to Mass Storage. Advantages are the ability to limit which files are accessed and that it is unnecessary to have two modes of operation to switch between local and USB access to the disk, to protect the file structure.
sud_MTPIsConnected(port)
sud_MTPRegisterInterface(pObjOper)
sud_MTPSendEvent(EventCode, iNumPar, *Par)
Mouse (Included)
The Mouse function driver makes your device look like an HID mouse to the USB host. It moves the mouse pointer on your PC.
sud_MouseInput(button, x, y, wheel)
Serial
The Serial function driver makes your device look like one or more COM ports to a Windows, Mac OS, or Linux USB host. You can use standard Win32 functions to communicate with the device, just like if it were connected to a real RS232 port. For the multi-port option, we provide a custom Windows USB serial driver, since the built-in Windows driver supports only one port. Our driver also allows using only 1/2 the number of endpoints, saving them for other uses.
sud_SerialIsPortConnected(port)
sud_SerialWriteData(port, pBuf, len)
sud_SerialDataLen(port)
sud_SerialReadData(port, pBuf, len)
sud_SerialSetLineState(port, iState)
sud_SerialGetLineState(port, piState)
sud_SerialGetLineCoding(port, pdwDTERate, pbParityType, pbDataBits, pbStopBits)
sud_SerialRegisterPortNotify(port, handler)
Video
The Video function driver makes your device look like a web camera to a Windows, Mac OS, or Linux USB host. There is no need to install any driver or .inf file in Windows to support this device but you may need to implement the camera sensor driver, and you may also need to customize the configuration of the driver for your real hardware features, such as the set of features your camera sensor will support.
sud_VideoIsConnected(port)
sud_VideoSendVideoData(port, pData, len)
sud_VideoGetVideoDataLen(port, len)
sud_VideoRegisterNotify(port, handler)
Composite Devices
smxUSBD allows creating a composite device. Such a device has multiple interfaces that are active at the same time using a single controller chip. For example, a composite device might combine serial and mass storage. See the smxUSBD User's Guide for more discussion of this.
Writing New Drivers
Contact us first to make sure we are not already working on the driver you need.
smxUSBD provides a function driver template and a section in the manual to help you write a new function driver, if needed.
smxUSBD provides a USB device controller driver template and a section in the manual, to help you write a new driver in case it does not support yours.
Porting
Little or no porting is necessary when smxUSBD is used with SMX®. It is designed to also work with other RTOSs and to run standalone, but it works best in a multitasking environment. The RTOS porting layer is handled by smxBase.
The hardware porting layer consists of two files, udport.h and udport.c. These files contain definitions, macros, and functions to port to a new processor. In addition, if the USB device controller is not among those already supported, a new driver will need to be written.
16-Bit Addressing Support
smxUSBD supports processors that can only do 16-bit memory addressing (not byte addressing) such as the TI TMS320C55xx DSPs. These processors are difficult to support for typical communication protocols because of byte data and byte fields in standard protocol data structures. This support is enabled by a configuration option in smxUSBD.
Testing
We test smxUSBD with USBCheck Version 5.1 on a Windows PC to verify that it passes the Chapter 9 USB compliance tests for full speed and high speed. We also test with USBCV v1.3 and it passes the Chapter 9, HID, and MSC tests.
Code Size
Code size can vary greatly depending upon the processor, compiler, and optimization level.

ARM Thm
IAR
(KB)
ARM
IAR
(KB)
CF
CW
(KB)

Core

4
12

Audio driver

3
6
6.5

DFU driver

Ethernet over USB driver

2.5
3.5
4.7

HID Comm driver

0.5
1

Keyboard driver

0.5
1
1

Mass Storage driver

3
5.5

Mouse driver

0.5
1
1

MTP driver

Serial driver

1.5
2.5
2.7

Video driver

11

Composite driver

0.5
1
1

Analog Devices BF5xx

3.3

Atmel AT91

2
3

Atmel AT91 high speed

Freescale CF5225x/1x/2x, Kxx

5

Freescale CF532x/7x, 525x, 5445x, i.MX31

Maxim MAX342x

3.5

NXP ISP176x

NXP LPC31xx

3.5

NXP LPCxxxx

2

PLX Net2272

STMicro STR7/9, STM32F103

Synopsys, STMicro STM32F107, STM32F20x

TI AM1x, AM35x, LM3S

2

Drivers Nxp Usb Devices Pc Camera


IAR = IAR EWARM; CW = CodeWarrior; VDSP = VisualDSP
Data Size

All RAM used by smxUSBD for data is pre-allocated from the heap during initialization. Following is a table of RAM usage:

Size
(KB)

Core

Audio driver

2

DFU driver

Ethernet over USB driver

2

HID Communication driver

Keyboard driver

0.5

Mass Storage driver

Mouse driver

0.5

MTP driver

Serial driver

1

Video driver (full speed)

Video driver (high speed)

7

Composite driver

Analog Devices BF5xx

0.5

Atmel AT91

Atmel AT91 high speed

0.5

Freescale CF5225x/1x/2x, Kxx

Freescale CF532x/7x, 525x, 5445x, i.MX31

1

Maxim MAX3421

NXP ISP176x

1

NXP LPC31xx

NXP LPCxxxx

0.5

PLX Net2272

STMicro STR7/9, STM32F101/2/3

0.5

Synopsys, STMicro STM32F105/7

TI AM1x, AM35x, LM3S

0.5

MTP data size is 6KB + ObjectsNum*64
Stack Size

smxUSBD has one internal task in the device controller driver that uses about 1KB stack (or 2KB for MTP). Application tasks typically use 0.5 to 1.5KB depending on the function driver


Performance

Mass Storage
The following table shows mass storage performance using a RAM disk in the device.

File Read
(KB/sec)
BF5xx (HS)
5000
1071
ISP158x (HS)
3890

Ethernet over USB
The following table shows Ethernet over USB performance for the indicated packet size and controller.

Drivers Nxp Usb Devices Dongle

Packet Size
(Bytes)
CF532x/7x (HS)
256

Drivers Nxp Usb Devices Adapter

Serial
The following table shows the transfer rate for sending and receiving serial data for different application packet sizes and controllers.

Packet Size
(Bytes)
BF5xx (HS)
800
1024
ISP1362 (FS)
140
256
ISP1362 (FS)
804
1024
ISP1761 (HS)
1830
1024
MCF54455 (HS)
8000

Drivers NXP USB Devices


smxUSB Product Illustration (PDF)


For More Information


Comments are closed.