OSD Developer Board v1
From The Neuros Technology Wiki
NOTE: OSD1 DEVELOPER BOARDS ARE SOLD OUT GO TO OSD 2.0 HD FOR OSD 2.0 HARDWARE
If you are interested in beta testing the OSD, go to Thinkgeek
As mentioned elsewhere the developer boards have been split into the various products that they will become. In the case of the Neuros OSD [Previously called the R3]) this is simply a first spin of the board, because the OSD, as a finished product already has the interfaces for normal development (serial and ethernet). The OSD Developer Board will ship with a pre-production housing (clear instead of black as in the production housing) and with all the production peripherals (remote control and power supply).
The developer board will be finished and tested HW, so no soldering iron is required, but the SW development will still be well underway. The unit will boot to linux and run and record and playback video, etc, but there will be plenty of bugs and missing functionality. Further, while the HW is "finished" it is possible that specs on the HW will change and that the final production run will be slightly different.
Basically, the OSD Developer board is for folks that want to get in on the ground floor of developing a new product and want the product sooner and want to participate with our developers earlier. Or maybe you want to build something different than what we're doing and don't need our finished software.
Differences between the Developer Samples and the Production Product
- Incomplete, Alpha level software (see Neuros-BSP WebSVN for source code and the Linux development environment setup notes for how to set up a development environment)
- Universal remote instead of semi-programmable
- This means the remote can control any TV/VCR but it does not have dedicated buttons to control your TV and the OSD simultaneously as the production remote will do.
- 8MB Flash and 32MB RAM instead of 16MB/64MB as in Production
- Clear housing (instead of black)
- $100 cheaper than production ($150)
Development Board Features
- DM320 Multimedia SOC with 200 MHz ARM926, 120 MHz C54x DSP
- 64 MB of SDRAM
- 16 MB of FLASH
- USB 2.0, 12 Mbps Host interface via DM320
- SD/MMC/MemoryStick, Pro, Duo socket
- CF socket supporting I/O mode
- RS-232 serial console port (also used for controlling tuner boxes)
- 10/100 Mbps Ethernet
- Infrared detector for remote control
- Infrared blaster for controlling tuner boxes
- NTSC/PAL composite or S-Video input
- NTSC/PAL composite video output
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.
Ethernet connectivity is implemented by using the DM9000AEP chip. The interface between the DM320 and the 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.
Support for SD , MMC and MS cards is provided by a hardware interface block internal to the DM320. MMC cards with a single data bit and SD , MS cards with 4 data bits are supported, with SD and MMC clock speeds up to 25 MHz. Normal MS clock speeds up to 20MHz and MS Pro clock speeds up to 40MHz.
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.
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. And has pass-through function, composite Video in delivery to composite Video out directly while power_down.
NTSC/PAL output and DAC
This analog output is produced directly by the DM320. It is controlled by the VENC module.
Analog audio conversion is handled by TLV320AIC23PW. 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.
The audio ADC chosen is a TLV320AIC23PW
The audio DAC chosen is a TLV320AIC23PW
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.
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.
Connecting to a PC
The OSD will not have support for USB device, thus it cannot connect to a PC through USB
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.
Hacking the OSD
If you're new to Neuros, the Developer Welcome is a good place to start.
You can find links to documentation and source code Here
Here is information about the Neuros DM320 Platform
DEVELOPER SAMPLES ARE SOLD OUT-LOOK FOR BETA in September
The dev protos will be available only at https://www.americantechpushers.com/nboard.html and will likely sell out before shipping (there are only 50 peices available), interested purchasers are encourged to pre-order ASAP or wait until the Gamma launch.
Existing pre-order customers will have to re-enter the order for this board, see here http://open.neurostechnology.com/node/260
Check the MPEG4 RECORDER Blog on OdNT