Difference between revisions of "Mini6410 Hardware Specification"
(Created page with "== Address Space == The following data is from the S3C6410 data sheet 11 == Power == The Mini6410 is powered by an external 5V power supply. It has two power inlets: CN1 is f...") |
|||
| Line 46: | Line 46: | ||
88 | 88 | ||
| + | |||
| + | == TV Output == | ||
| + | The S3C6410 has two TV outputs. The Mini6410 magnifies the output of DACOUT0, | ||
| + | users can connect the board to a TV via an AV cable. The other TV output is extended from | ||
| + | CPU to the 30th pin of CON6.<br> | ||
| + | |||
| + | Note: when connecting DACOUT0 to a TV users need to switch the TV to the CVBS mode. | ||
| + | |||
| + | 99 | ||
| + | |||
| + | |||
| + | == JTAG Interface == | ||
| + | When a board just comes off from production lines it is just a bare board without any data | ||
| + | and we usually have to burn the first program to it through the JTAG interface. However since | ||
| + | the S3C6410 supports booting from SD card the JTAG is not significant to users any more. | ||
| + | Now the JTAG is more often used for debugging. In fact, most of the widely used utilities in | ||
| + | markets like JLINK, ULINK and other simulators actually work via the JTAG interface. A | ||
| + | standard JTAG has 4 signals :TMS, TCK, TDI and TDO which are test mode select input, test | ||
| + | clock, test data input and test data output. These 4 signal lines plus a power line and a ground | ||
| + | line form 6 lines in total. In order for testing, most simulators even have a reset signal. | ||
| + | Therefore, a standard JTAG is meant to have those signal lines, and it does not mean whether it | ||
| + | is 20Pin or 10Pin. As long as a JTAG interface has those signal lines, it will be a standard | ||
| + | JTAG interface. The Mini6410 has a 10Pin JTAG interface which has complete standard | ||
| + | JTAG signals.<br> | ||
| + | |||
| + | Notes: for beginners who just want to focus on Linux or WinCE development, the JTAG | ||
| + | interface has no significance because most development boards already have a complete BSP | ||
| + | which includes commonly needed serial ports, network port and USB port. When a board runs | ||
| + | with Linux or WinCE installed, users can fully utilize more convenient functions and utilities | ||
| + | provided by the operating system to debug. They do not need a JTAG. Even if you can trace | ||
| + | your programs it will be extremely tough to step debug because it will go into the operating | ||
| + | system. This is not an easy job. | ||
| + | |||
| + | 10 10 | ||
| + | 11 | ||
Revision as of 06:10, 27 June 2012
Contents
Address Space
The following data is from the S3C6410 data sheet
11
Power
The Mini6410 is powered by an external 5V power supply. It has two power inlets: CN1 is for 5V power adapter and the white CON8 is a 4 pin socket used to connect an external power supply when the board is embedded in a closed box. The voltage is 5V and current is 800mA. 22
Serial Port
S3C6410 has 4 serial ports: UART0, 1, 2 and 3. UART0 and 1 are 5 wire serial ports and the other two are 3 wire serial ports. On this board, UART0 is converted via RS232 to COM0 and can communicate with a PC via a serial port cable. The rest 4 ports are connected to CPU via CON1-4. They are presented as below: 33 44 55
USB Interface
The Mini6410 board has two USB interfaces. One is a USB host 1.1 which is the same as a USB interface on a PC and can connect to a USB camera, keyboard, mouse, flash drive and other USB devices. The other is an OTG mini USB 2.0 which is usually used to download programs to a target board. When the board runs WinCE it can synchronize with a Windows via ActiveSync. For Linux there are no programs for synchronization for now.
Mini USB interface: 66
USB Host: 77
Network Interface
The Mini6410 incorporates a DM9000 chip and can communicate with 10/100M networks. The RJ45 connector includes coupling filters and does not need transformers. With a common network cable, you can connect a router or switch to the Mini6410.
Audio Interface
The S3C6410 supports I2S/PCM/AC97. The Mini6410 has an AC97 interface which uses
WM9714 as the CODEC chip.
The audio output is a 3.5 mm spaced green plug and the input is an on-board microphone. To get better audio quality please move the microphone as close as possible to the audio source when recording.
88
TV Output
The S3C6410 has two TV outputs. The Mini6410 magnifies the output of DACOUT0,
users can connect the board to a TV via an AV cable. The other TV output is extended from
CPU to the 30th pin of CON6.
Note: when connecting DACOUT0 to a TV users need to switch the TV to the CVBS mode.
99
JTAG Interface
When a board just comes off from production lines it is just a bare board without any data
and we usually have to burn the first program to it through the JTAG interface. However since
the S3C6410 supports booting from SD card the JTAG is not significant to users any more.
Now the JTAG is more often used for debugging. In fact, most of the widely used utilities in
markets like JLINK, ULINK and other simulators actually work via the JTAG interface. A
standard JTAG has 4 signals :TMS, TCK, TDI and TDO which are test mode select input, test
clock, test data input and test data output. These 4 signal lines plus a power line and a ground
line form 6 lines in total. In order for testing, most simulators even have a reset signal.
Therefore, a standard JTAG is meant to have those signal lines, and it does not mean whether it
is 20Pin or 10Pin. As long as a JTAG interface has those signal lines, it will be a standard
JTAG interface. The Mini6410 has a 10Pin JTAG interface which has complete standard
JTAG signals.
Notes: for beginners who just want to focus on Linux or WinCE development, the JTAG interface has no significance because most development boards already have a complete BSP which includes commonly needed serial ports, network port and USB port. When a board runs with Linux or WinCE installed, users can fully utilize more convenient functions and utilities provided by the operating system to debug. They do not need a JTAG. Even if you can trace your programs it will be extremely tough to step debug because it will go into the operating system. This is not an easy job.
10 10 11
