Share via


AMD DBAu1500 Development Board Supported Features

The following table shows the supported features in the board support package (BSP) for the hardware components on the AMD DBAu1500 Development Board for Au1500 processors.

Hardware component Hardware support BSP support
RAM 64 MB Yes
Flash 32 MB Yes
Boot ROM Yes Yes
Timers Yes Yes
Real-time clock No Not applicable
VGA PCI slot

Supported video cards: ATI Rage XL, 3Dlabs Permedia 3

Yes
LCD No Not applicable
Ethernet Yes Yes
Serial 2 Yes
Note   One of the serial ports is for data only while the other has full support.
PCMCIA or CF Yes Yes
Mouse Universal serial bus (USB) only Yes
Keyboard USB only Yes
Hardware reset through a cold boot Yes Yes
Hardware reset through a warm boot Yes Yes
Software reset through a warm boot Yes Yes
Touch controller No Not applicable
USB host Yes Yes
USB function Yes No
Serial Infrared (SIR) No Not applicable
Fast Infrared (FIR) No Not applicable
Audio output Yes Yes
Audio input Yes Yes
Parallel for printing No Not applicable
Integrated Device Electronics (IDE) Yes No
Smart card No Not applicable
IEEE 1394 No Not applicable
Floppy disk No Not applicable
TV output No Not applicable
Floating point unit No Not applicable
Expansion connector Yes No
PCI slots 1
Note   This is for 3.3V PCI cards only.
Yes
Note   This slot is for VGA only.
Compact PCI or PCI extender Yes No
Logic analyzer probes Yes No
JTAG Yes Yes
Debug LEDs Yes Yes
Companion or add-on cards No Not applicable
Form factor Custom Not applicable

The following list shows BSP limitations related to hardware issues on the AMD DBAu1500 Development Board.

  • No support for USB function.
  • No support for the IDE ATA/133 controller.
  • The PCI bus does not fully support devices behind bridge. This issue is related to bus latency for transfers initialized by the Au1 PCI 2.2 Controller for PCI device behind bridge.
  • The boot loader and KITL only support Au1 on-chip Ethernet controllers.
  • Audio input uses the J17 connector or plug.
  • Audio output uses the J20 connector or plug.

The following list shows BSP limitations related to silicon issues on the AMD DBAu1500 Development Board. For more information, see the AMD Web site.

  • The OAL sets the OD bit in the Config0 coprocessor register to fix or work around some silicon-related problems.

  • By default, the BSP builds with the OAL using coprocessor 0 count and compare registers for the system timer. In this mode, the device does not support the power-saving IDLE0/IDLE1 instruction in the OEMIdle function.

    If you want to use the TOY counter as the system timer, you must set the DBAU1500_TOYTIMER environment variable. In this mode, the BSP or kernel using the TOY timer also uses the IDLE0 instruction to set the CPU to power save mode. However, the device does not support the high-resolution timer and profiling when in this mode.

    If the DBAU1500_YAMON flag is set, the boot loader and the BSP are compiled and built in a way that allows you to flash the boot loader to address 0xBFD00000. In this mode, the YAMON autorun should be used to jump to the boot loader.

  • The USB host driver reads enable the register to work around the silicon problem twice.

  • A USB host controller silicon problem might cause some USB devices not to work or to work incorrectly. As a result, the memory can be corrupted and the USB device will randomly crash. This problem is typical for USB mouse devices that have a 4-byte interrupt endpoint size. This problem does not affect the Microsoft® IntelliMouse®.

  • The static mapping uses two translation look-aside buffer (TLB) entries to work around silicon problems with the page frame when the size is greater than 4 KB.

  • Due to a known silicon problem, the PCMCIA slot does not support 8-bit I/O operations on odd addresses. As a result, some PCMCIA cards — such as modem cards or Bluetooth cards — may not work or may work incorrectly.

See Also

How to Use the BSP for the AMD DBAu1500 Development Board | Setting up the AMD DBAu1500 Development Board Hardware

Last updated on Wednesday, April 13, 2005

© 2005 Microsoft Corporation. All rights reserved.