DM320 Platform developer board spec
From The Neuros Technology Wiki
This document gives a summary of the features for version 0.9.0 of the DM320 Platform developer board.
THIS INFORMATION IS NOT FOR THE DEV BOARDS BEING SHIPPED ON JUNE 15, 2006!!!
See OSD Developer Board page for more information on the OSD Developer Board.
This document serves simply as a guide to the board and its components; it does not address low-level hardware issues. For considerably more detail, consult the full documentation on the development board, available at this location.
Contents |
[edit] Development Board Features
- DM320 Multimedia SOC with 200 MHz ARM926, 120 MHz C54x DSP
- Up to 128 MB of SDRAM
- Up to 8 MB of FLASH
- USB 2.0, 12 Mbps Host interface via DM320
- USB 2.0, 480 Mbps Gadget interface using NET2272
- SD/MMC socket
- CF socket supporting I/O mode
- RS-232 serial console port
- IDE interface for HDD
- 10/100 Mbps Ethernet
- Infrared detector for remote control
- NTSC/PAL composite or S-Video input
- NTSC/PAL video output
- High quality 24-bit audio line level input and output
- S/PDIF digital audio output
- Headphones output
- User interface buttons (10)
[edit] Processor
The development platform uses a DM320 system on chip, comprised of an ARM926EJ core and a TI C54x DSP core. This design will support the DM320’s High Performance mode of operation. The maximum ARM clock is then specified as 203 MHz. The DSP is rated in excess of 120 MHz. In addition, the SoC also contain dedicated hardware acceleration for video encoding and decoding, making it capable of achieving DVD-like quality playback as well as high quality, D1 resolution video encoding using MPEG-4.
[edit] Interfaces
[edit] IDE HDD
Support for an IDE hard disk is implemented using the external memory interface of the DM320. The DM320 does not have an external DMA interface, so only PIO transfers will be supported.
[edit] Ethernet
Ethernet connectivity is implemented by using the SMSC LAN91C111 chip. The interface between the DM320 and the LAN91C111 use a 16-bit data path, and the Ethernet chip can be operate with or without DMA assistance. DMA transfers can be accomplished by using the DM320’s internal EMIF DMA engine.
[edit] SD/MMC
Support for SD and MMC cards is provided by a hardware interface block internal to the DM320. MMC cards with a single data bit and SD cards with 4 data bits are supported, with clock speeds up to 25 MHz.
[edit] CompactFlash
Support for Compact Flash is provided by a hardware interface block internal to the DM320. Data accesses can be made with or without DMA. The interface supports I/O Mode and Memory Mode transfers. This interface should support True-IDE micro drives that do not support the full CF specification.
[edit] NTSC/PAL video decoder and ADC
A Texas Instruments TVP5150A chip will be used to receive an NTSC or PAL composite or S-Video signal. The TVP5150 will decode and digitize the incoming video signal, then format it for delivery to the DM320 video input.
[edit] NTSC/PAL output and DAC
This analog output is produced directly by the DM320. It is controlled by the VENC module.
[edit] Audio ADC/DAC
Analog audio conversion is handled by independent Burr-Brown ADC and DAC for the highest possible audio quality. The ADC chip will digitize incoming line level audio signals. The DAC will convert digital samples provided by the DM320 DSP into line-level analog audio for consumption. A headphone jack will also be provided. The audio ADC and DAC circuits are powered by a separate power supply for maximum noise immunity.
A stub program will be created in the DSP to allow ARM code to have access to the ADC/DAC, allowing completely ARM-based and open-source applications to be created.
[edit] Audio ADC
The audio ADC chosen is a PCM1803 from Burr-Brown. This ADC is capable of digitizing 24 bits of stereo audio at 96 KHz sampling rate.
[edit] Audio DAC
The audio DAC chosen is a Burr-Brown PCM1742E. This DAC is capable of delivering 24 bits of stereo audio at up to 192 KHz sampling rate.
[edit] S/PDIF Output
The S/PDIF output is implemented using a Cirrus Logic CS8406 part. The same digital data signals provided to the audio DAC are fed into the CS8406. Simultaneous operation of the S/PDIF and analog audio interfaces is possible, but care must be taken to ensure that the CS8406 and the PCM1742 DAC are configured in a mutually compatible way.
[edit] USB Interfaces
[edit] USB Host interface
The DM320 internal USB interface logic will be used to provide a 12 Mbps Host interface port, capable of interfacing to any USB-compliant device, such as external USB mass storage devices, wired and wireless NIC cards, or keyboards.
The USB specification calls for Host devices being able to provide up to 2.5 watts of power to a USB Device. This will be accomplished by routing power directly from the Development Board’s 5V supply. There is no power switch to control the supply to an attached device nor means to sense the amount of power consumed by an attached device. Power to attached devices is always on.
The external power supply used with the Development Board must be able to provide enough power to any USB devices attached to the host port as well as the Development Board itself.
[edit] USB Device interface
A High Speed (480 Mbps) USB Gadget interface will be implemented using the NET2272 USB controller chip. The DM320 will mediate and arbitrate all data transfers to and from the USB bus, and will be able to implement any standard Device Class interface, such as mass storage, communications and serial device classes.
[edit] USB notes
The DM320 chip can stream files in real time via USB. The 12 Mbps USB interface is fast enough to pipe at least 4 Mbps of real data, and this is good enough for MPEG-4 video and audio.
Here's the usage scenario: you plug in a USB hard drive (preferably the vDrive) and instead of recording to CF SD or an internal hard drive, you record directly to an external hard drive through USB.
In order to accomplish this, the developer board (and later, the Recorder 3) will have to be capable to behave as a host, and the vDrive as the device. It will require some help with the USB drivers for the DM320, but the hardware will be capable of implementing it.
This requires the presence of a "host" connector - that flat one that you normally see on PC's. There is no such connector on the 442 - this is a "Recorder" feature. This is in addition to the "device" connector - the one like the 442's. There will then be 2 different USB connectors on the development board, but only 1 can be used at any given time, since the DM320 has only 1 USB interface.
Bob Faskos adds:
I will not add hardware support for OTG to the dev. board, since it is broken on DM320 and I am not sure if there is a fix. This means that software must be run to configure the board as host or device, there is no protocol-based negociation. I think I can come up with a detection mechanism that gives an interrupt whenever something gets plugged and unplugged, plus an indication of whether it is a device or a host that just plugged in. The driver will have to take it from there.
