This is a legal agreement between you (either an individual or an entity) and Philips Semiconductors.
By accepting this product, you indicate your agreement to the disclaimer specified as follows:
DISCLAIMER
PRODUCT IS DEEMED ACCEPTED BY RECIPIENT. THE PRODUCT IS PROVIDED
“AS IS” WITHOUT WARRANTY OF ANY KIND. TO THE MAXIMUM EXTENT
PERMITTED BY APPLICABLE LAW, PHILIPS SEMICONDUCTORS FURTHER
DISCLAIMS ALL WARRANTIES, INCLUDING WITHOUT LIMITATION ANY
IMPLIED WARRANTIES OF MERCHANT ABILITY, FITNESS FOR A PARTICULAR
PURPOSE, AND NONINFRINGEMENT. THE ENTIRE RISK ARISING OUT OF THE
USE OR PERFORMANCE OF THE PRODUCT AND DOCUMENTATION REMAINS
WITH THE RECIPIENT. TO THE MAXIMUM EXTENT PERMITTED BY
APPLICABLE LAW, IN NO EVENT SHALL PHILIPS SEMICONDUCTORS OR ITS
SUPPLIERS BE LIABLE FOR ANY CONSEQUENTIAL, INCIDENTAL, DIRECT,
INDIRECT, SPECIAL, PUNITIVE, OR OTHER DAMAGES WHATSOEVER
(INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS
PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR
OTHER PECUNIARY LOSS) ARISING OUT OF THIS AGREEMENT OR THE USE OF
OR INABILITY TO USE THE PRODUCT, EVEN IF PHILIPS SEMICONDUCTORS HAS
BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
System Requirements .....................................................................................................................................4
Jumper’s setting on PDIUSBD12 ISA bridging board................................................................................... 5
Location of key components on the PDIUSBD12 evaluation board. ..............................................................6
Installation of firmware, INF and driver........................................................................................................ 7
Using the Host Applet ....................................................................................................................................7
PAL Equations.............................................................................................................................................11
Address and command decoder...................................................................................................................11
Schematics for PDIUSBD12 evaluation board ............................................................................................12
Schematic for PDIUSBD12 ISA bridging board..........................................................................................13
Bill of Materials............................................................................................................................................14
Bill of materials of the PDIUSBD12 evaluation board.................................................................................14
Bill of materials of the PDIUSBD12 ISA bridging board.............................................................................14
The PDIUSBD12 evaluation kit uses 2 PC as a complete USB development environment, a host PC
with USB host capability and a device PC running PDIUSBD12’s firmware. The PDIUSBD12 ISA
bridging board is plugged inside the device PC and connects to the evaluation board using a 25-wire
cable. So the device PC behaves as a big USB device.
Features evaluation of PDIUSBD12, firmware and product prototype development can be easily done
with this setup, without the resource limitation of a micro-controller. Customers can also connect the
evaluation board to their own CPU and bus through the 25-wire cable for final product development.
The firmware is carefully developed for high rate data transmission and is written in C, that supports
Borland Turbo C for x86 and Keil C51 for 8031 currently. Supporting to other CPU platforms will be
available soon.
System Requirements
1. PDIUSBD12 evaluation board and ISA bridging board;
2. 25-wire shielding data switch cable;
3. Host PC with USB motherboard or add-on card;
4. Microsoft Windows 98 or Windows NT 5.0 Beta 2;
5. Device PC running Microsoft DOS 6.x;
6. PDIUSBD12 evaluation diskette.
For firmware development:
1. X86 CPU platform: Borland Turbo C++ 3.0 or above;
The PDIUSBD12 ISA bridging board is plugged inside the device PC. It will occupy I/O, IRQ and DMA
resources of the device PC. To avoid possible conflicts in settings, we suggest removal of all the
unnecessary cards from the device PC. Sound card and network card may cause conflict in IRQ and
DMA setting.
J2
JP5 JP6
S1
18
JP1 JP2JP3 JP4
Switch S1 sets the base I/O address for the D12 evaluation board. Default base address is 0x368.
The D12 evaluation board occupies 8 I/O locations. A0 to A2 are decoded on the D12 evaluation
board. Switch S1 sets the address decoding of A3 to A9. Please notice that a switch ‘ON’ is logic ‘0’.
Jumpers JP3 to JP6 set the DMA number for the D12 evaluation board. Default setting is DMA3 or
JP4 and JP6 are shorted. Please note that a respective pair of jumpers is needed to set a particular
DMA channel.
DMA NumberDMA1DMA3
Jumper’s SettingJP3, JP5JP4, JP6
DefaultOFF, OFFON, ON
The firmware, D12FW.EXE, runs on the device PC under DOS mode. When D12FW starts, it lights up
test LEDs on the evaluation board for 1 second. This means that the I/O address setting is correct.
And the evaluation board is disconnected and re-connected to USB by SoftConnectTM. If this is the
first time that the evaluation board is connected to host PC, host OS Device Manager will prompt
installation of INF and driver. Select the location of D12TEST.INF and D12TEST.SYS and complete
installation procedure.
Some useful key command is supported when the firmware is running.
KeyOperation
ESCDisconnect USB and quit PDIUSBD12 firmware.
ENTER
iDisplay firmware status information.
vSwitch on/off verbose mode, normally turned off for faster operation.
Using the Host Applet
Reconnect USB using SoftConnectTM.
The test applet, D12TEST.EXE, exercises all PDIUSBD12 endpoints. Testing of control endpoints can
be further done by standard USB Chapter 9 test programs.
The operation of each endpoint is designed according to its nature that is supported in PDIUSBD12.
Generic in and generic out endpoints has max packet size of 16 bytes and supports I/O access only.
So they are suitable for small size and low rate data transfer like keyboard and logic controls. The
main endpoints have max packet size of 64 bytes or 128 bytes with double buffering and DMA
support. So they are suitable for high data rate, large size data transfer.
See the table below for the description of endpoints operations on PDIUSBD12 evaluation board.
Endpoint
Number
1GenericInThis pipe is defined as Interrupt In pipe. The PDIUSBD12 evaluation
1Generic
2Main In
Main endpoints support 3 different test modes:
1. Scan mode: The PDIUSBD12 evaluation board acts like a scanner. It sends data packets to the
host PC as fast as possible. This mode is used to evaluate the maximal Bulk In transfer rate.
2. Print mode: The PDIUSBD12 evaluation board acts like a printer. It receives data packets from
the host PC as fast as possible. This mode is used to evaluate the maximal Bulk Out transfer rate.
3. Loop back mode: In this mode, the PDIUSBD12 evaluation board receives data packets on Main
Out endpoint and sends them back to the host PC on Main In endpoint. This mode is used to test
the data integrity of transfers.
The “Buffer Size” setting on the test applet is determined by the firmware and hardware ability of the
evaluation board. For PC kit, the maximal size is limited to 64000; On USB-EPP kit, this is limited to
16384.
Endpoint
Type
Out
Main Out
Operations
board sends key press/release data packet to the host when test keys
are pressed or released. The firmware uses I/O accesses on this
endpoint.
This pipe is defined as Interrupt Out pipe. Data packet received from
host is interpreted as LED control and the D12 evaluation board
firmware will light up the corresponding LED. The firmware uses I/O
accesses on this endpoint.
These pipes are defined as Bulk In/Out endpoints. Test applet and the
PDIUSBD12 evaluation board supports 3 test modes: loop-back mode,
print mode and scan mode. The firmware uses DMA for data transfer
on these endpoints.
The “Repeat Times” for loop-back test controls the numbers of iterations of loop-back, which is useful
for debugging. “-1” means it is infinite.
running on device PC. The
firmware is written in C for easily
portable to other CPU platforms.
Command
and Address
Decoder
Bi-direction
Bus
Transceiver
Pin
Customer's System
25
Pin
I/F
CPU,
Memory,
and DMA
Controller
USB Device PC
25
I/F
D12 ISA Bridging Board
25
Pin
I/F
DIP
Switches
and
Jumpers
ISA
Slot
Block Diagram
Above block diagram shows 5 main components on the PDIUSBD12 evaluation board. Beside bus
transceiver, address/command decoder and PDIUSBD12, a general input port and a general output
port are included in the design. These input and output ports are designed for test purposes, such as
test switches and test LEDs. They also act as glue logic to adapt the PDIUSBD12 to the ISA bus. For
example, ISA interrupt is edge triggered, but PDIUSBD12 interrupt is level triggered. The MSB of the
general output port is used as interrupt enable to convert level triggered interrupt to edge triggered.
I/O Mapping
PDIUSBD12 evaluation board uses 8 I/O addresses:
OffsetUsage
0D12 data register, R/W
1D12 command register, W only
2General input port, R only
3General output port, W only
4 to 7Reserved for expansion board
BitUsage
0Key S1, ‘0’ for pressed
1Key S2, ‘0’ for pressed
2Key S3, ‘0’ for pressed
3Key S4, ‘0’ for pressed
4
5USB bus power state, ‘1’ for USB VBUS present
6D12 SUSPEND pin state
7D12 INT_N pin state
Bit description for general output port:
BitUsage
0LED D2, ‘1’ lights up LED
1LED D3, ‘1’ lights up LED
2LED D4, ‘1’ lights up LED
3LED D5, ‘1’ lights up LED
4Reserved
5Reserved
6Suspend control, ‘1’ forces D12 SUSPEND pin low
7Interrupt enable, ‘1’ enables interrupt
D12 GoodLinkTM pin state
Connectors
25 wire connector for PDIUSBD12 evaluation board:
PinTypeDescription
1POWERVCC
2POWERGND
3I/ODATA7
4I/OZero Wait State
5I/ODATA6
6I/OReserved
7I/ODATA5
8OCLKOUT: This line is connected to PDIUSBD12 CLKOUT pin.
9I/ODATA4
10I-AD_EN: This line is the decoder output for address decoding A3 to
A9. This signal is active low when PDIUSBD12 evaluation board I/O
address is selected.
11I/ODATA3
12IRESET: This line is used to reset or initialize system logic upon
power-up and is active high.
13I/ODATA2
14I-IOW: This command line instructs an I/O device to read the data on
the data bus. It may be driven by the processor or the DMA controller.
This signal is active low.
15I/ODATA1
16I-IOR: This command line instructs an I/O device to drive its data onto
the data bus. It may be driven by the processor or the DMA controller.