DOS=HIGH,UMB
lastdrive=Z
device=HIMEM.SYS
rem The following line loads Panasonic's universal USB- controller driver
devicehigh=USBASPI.SYS /v /w /e
rem the following is an aspi mass storage driver for usb- connected HDs and compactflash memory cards
devicehigh=DI1000DD.SYS
rem The following one loads CD-ROM driver
devicehigh=USBCD.SYS /d:USBCD001
[autoexec.bat]
@echo off
REM the following line adds a drive letter to the usb cd(rom/r/rw) mounted
LH MSCDEX /d:USBCD001
A very detailed explanation on how to use this driver and various options available with driver are nicely explained at http://www.theinquirer.net/inquirer/news/069/1046069/yes-there-are-usb-drivers-for-dos.
usbaspi.sys and usbcd.sys available at:http://panasonic.co.jp/pcc/products/drive/cdrrw/kxlrw40an/driver/kxlrw40an.exe
di1000dd.sys available at: http://www.stefan2000.com/darkehorse/PC/DOS/Drivers/USB/mhairu.zip
The XEM3050 FPGA Module promises to help in cutting design times and verification times of heavy electronic engineering projects.
Now USB flash drives are cheap and available everywhere. So, securing the drive's contents has become a major issue. To avoid this problem. There is a free software called Rohos Mini Drive helps in solving this problem. 
USB 3.0 uses different cable. But the connectors remains same. USB 3.0 cable carries 6 signals. The SuperSpeed USB carries 4 different signals, and can provide upto 50 percent more power for unconfigured or suspended devices, and 80 percent more power for configured devices.
Acer, and DisplayLink, announced the availability of a new USB computer LCD monitor which still supports Windows Vista’s Aero Glass interface as well as other 3D functions.
The B223 USB LCD Monitor comes with the following features:
22″ LCD display, 1,680 x 1,050 resolution, DisplayLink DL-160 network display chip, USB 2.0 connectivity, 5ms response time, 32-bit, true-color graphics.
The B223’s height, rotation and swivel angles can be adjusted for your optimal viewing comfort. It’s already available in Europe. Priced around $430.
DisplayLink plug-and-play technology helps you to quickly connect the screen without having to install any drivers in Windows; DisplayLink offers separate Mac drivers for USB monitors but hasn’t said whether the B223 is supported.
This Tiny USB Drive has 8GB capacity. This family of USB drives are available in the range of 1 GB to 8GB.
| Analyzer | Description | Image(If Available) |
| MQP Electronics Packet-Master USB480+ | Description:
|   |
| MQP Electronics Packet-Master USB480 | Description:
| |
| MQP Electronics Packet-Master USB12 | Description:
|  |
Ellisys USB Explorer 200 | Description:
|  |
| Ellisys USB Tracker 110 Recommended | Description:
|  |
| Wireless USB Explorer 300 Wireless USB Protocol Analyzer | Description:
|  |
| USB Ver.2.0 Bus Protocol Analyzer SB-2020 | Description:
|  |
| CATC USBTracer/Trainer™ Protocol Verification System | Description:
|  |
| CATC Advisor™ Protocol Analyzer | Description:
|  |
| CATC USBMobile™ Protocol Analyzer | Description:
|  |
| Beagle™ USB 12 Protocol Analyzer | Description:
|  |
| Beagle USB 480 Protocol Analyzer | Description:
|  |
| CATALYST Conquest™ Series USB Protocol Analyzers | Description:
|  |
| CATALYST SBAE Series, Universal Serial Bus (USB) | Description:
|  |
| USB2 SnooperTM (USB 2.0 Bus Analyzer) | Description:
|  |
.
| 1. DWORD _MPUSBGetDLLVersion(void) This function will retrieve the version number of the DLL. |
| 2. DWORD _MPUSBGetDeviceCount(PCHAR pVID_PID) This function takes the pVID_PID (Vendor ID and Product ID) string as an argument and returns the number of devices with that specific Vendor ID and Product ID. If the VID is 0x04d8 and PID is 0x000c, the pVID_PID string will need to have a the value as "vid_04d8&pid_000c" |
| 3. HANDLE _MPUSBOpen(DWORD instance, // Input PCHAR pVID_PID, // Input PCHAR pEP, // Input DWORD dwDir, // Input DWORD dwReserved); // Input This function returns a handle to the end-point. The argument instance is used for passing a zero based index. This index value is based on the number of devices returned by MPUSBGetDeviceCount(). pVID_PID is the VID and PID string as explained above. pEP is the name of end-point something like "\\MCHP_EP1". dwDir based on the end-point IN or OUT direction, MP_READ or MP_WRITE need to be passed as argument. dwReserved For future use. This function returns a HANDLE to the end point opened which will be used by other functions. If no device is found, returns NULL. Check for NULL. |
| 4. DWORD _MPUSBRead(HANDLE handle, // Input PVOID pData, // Output DWORD dwLen, // Input PDWORD pLength, // Output DWORD dwMilliseconds); // Input This function is used to read from an IN end-point. It uses the handle returned by _MPUSBOpen function. The _MPUSBOpen function need to open this end point, with MP_READ as Direction (dwDir) argument. pData is pointer to buffer. dwLen size of data to be read. pLength size of data actually read. dwMilliseconds Total wait time. Returns 1 on SUCCESS. |
| 5. DWORD _MPUSBWrite(HANDLE handle, // Input PVOID pData, // Input DWORD dwLen, // Input PDWORD pLength, // Output DWORD dwMilliseconds); // Input This function is used to write to OUT end-point. It uses the handle returned by _MPUSBOpen function. The _MPUSBOpen function need to open this end point, with MP_WRITE as Direction (dwDir) argument. pData is pointer to buffer. dwLen size of data to be written. pLength size of data actually written. dwMilliseconds Total wait time. Returns 1 on SUCCESS. |
| 6. DWORD _MPUSBReadInt(HANDLE handle, // Input PVOID pData, // Output DWORD dwLen, // Input PDWORD pLength, // Output DWORD dwMilliseconds); // Input Used in Isochronous transfer/ Interrupt transfer. Refer to _mpusbapi.cpp for more details. |
| 7. BOOL _MPUSBClose(HANDLE handle); Used to close the handle opened by the _MPUSBOpen function. Need to be called before application exits. Otherwise the device may not respond properly, if the application is re-opened. |
7. VC++ Example
Download the VC++ Example by clicking here.
In this example there are two files that need to be looked at.
7.1. PICConnector.h and PICConnector.cpp: In these 2 files I implemented a simple wrapper class which invokes the functions from MPUSBAPI.DLL. The LoadDLL() member function of PICConnector class need to be called and it uses the Win32 API LoadLibrary(), GetProcAddress(), and FreeLibrary() to load the MPUSBAPI.DLL. Take a look at the source code while reading this portion. When the GetProcAddress call is made, note that the function names are passed with an underscore and the return value is assigned to corresponding function pointer. The function pointers are declared in mpusbapi.h file which is in the project folder.
Once this DLL is loaded, the Open() and Close() functions can be called to open the pipes on end-point 1 of device with index 0. These functions use the MPUSBOpen() and MPUSBClose() functions internally. Also, take a look at the error checking that is done in these files. This code is designed to work only with the first connected device, which will have an index of 0. But by modifying the code, more than one device can be handled.
In the Open() function, before calling MPUSBOpen(), the function MPUSBGetDeviceCount() is called with the vid_pid argument. This function returns the count, and if the count is 0, then it means no devices are connected to the PC. This is another error checking mechanism that can be used.
The SendReceivePacket() function is responsible for actual data transmission. This function makes calls to both MPUSBWrite() as well as MPUSBRead(). The MPUSBRead() is called as soon as MPUSBWrite() is invoked. What it means is, as soon as the PC application sends a command, it is also expecting a response. You can see in the firmware that, after receiving the command and data, there is a response packet sent by the firmware which includes the command bytes in it. It is a kind of acknowledgement implemented in the Demo application. And all applications does not require to implement this feature. So, there can be independent calls to MPUSBRead and MPUSBWrite functions.
7.2. VCPICUSBDemoDlg.cpp and VCPICUSBDemoDlg.h: The cpp file, implements 3 event handler functions. They are, OnGetVersion(), OnLed3() and OnLed4(). Take a look at the code of these functions.
Here I will explain the OnGetVersion() function.
The m_PICConnector is a object of PICConenctor class which loads the MPUSBAPI.DLL, created in the CVCPICUSBDemoDlg class.
Step A: In this step the pipes on end-point 1(MCHP_EP1) are opened by calling the Open() function. This function inturn calls MPUSBOpen on MCHP_EP1 for both OUT and IN pipes and stores the handler values in two variables, myOutPipe and myInPipe. Take a look at how the calls are made in Open function.
Step B: In this step two buffers are declared. The length of an bulk endpoint can not exceed 64 bytes in Full-Speed USB. So, the buffer length for both OUT and IN pipes is 64 bytes. But actually we will be transmitting less number of bytes compared to the buffer size.
Step C: In this step, the Demo Application command(READ_VERSION) is defined. Take a look at the user.h file in the Demo firmware. The value of the command READ_VERSION is mentioned as 0. Then the send_buf is being filled with the command and the data length. When firmware receives this command, based on the command it interprets remaining fields.
Step D: SendReceivePacket is called in this step. The send_buf which is populated in the previous step with the command and data fields is transmitted in this step, at the same time, as this command is retrieving version information, the pointer to receive_buf and expected length which is 4 are passed as arguments.
The ServiceRequests() function in the firmware processes this command and fills the response data. When the firmware sets the counter to a non-zero value, the USB stack will transmit the buffer back to Host.
Step E: In this step, the received data is verified if it is generated by the firmware correctly.
Step F: As the operation is complete, both IN and OUT pipes are closed in this function.
Here I am stopping this article. And this article showed how to interact with Demo firmware on Microchip PICDEM FS USB Board using VC++.
Source Code for this article can be found here.
Posts
All Comments
