CI20 Hardware



This page details the technical specifications and components of the MIPS Creator CI20 development board.

Files
The following links provide information (predominantly PDF files) about the SoC, board and components for the MIPS Creator CI20.

SoC Information
Overview on the Imagination web site

English page on the Ingenic web site

FTP download from the Ingenic ftp site

JZ4780 pdf datasheet from the CI20 file archive

Programmers Manual
JZ4780 pdf datasheet from the CI20 file archive

Schematic
Schematic pdf from the CI20 file archive

Board components and identification
Board/component (BOM) identication pdf from the CI20 file archive

DDR chip manual CI20 file archive

Ethernet chip manual CI20 file archive

NAND chip manual CI20 file archive

Power Management Unit (PMU) chip manual CI20 file archive

Real Time Clock (RTC) chip manual CI20 file archive

Expander pinouts
Main expander pinout and function diagram pdf from the CI20 file archive

Secondary expander pinout and function diagram pdf from the CI20 file archive

Dedicated UART header pinout and function diagram pdf from the CI20 file archive

Source code
The source code is hosted on github, and in the process of being upstreamed.

Please see the Dev Zone page for details.

SDcard images
Please see the Downloads page for links to the SDcard images.

Overview
Starting with the power connector, going anti-clockwise (ish) as you face the front of the board:

Power
The power connector is a 5V 4mm (shield) x 1.7mm (pin) center positive connector. It takes 5V only.

When somebody measures the current draw - maybe add it here?

Audio
Standard 4-pin headset connector, with auto OMTP/CTIA detection (so should work with any standard 4-pin headset).

EJTAG
14-pin MIPS EJTAG headers. See projects for proposed OpenOCD/wiggler support project.

Secondary 0.1" expansion header
Pinout diagram for the secondary CI20 0.1" pitch 16 pin header

HDMI
Full sized HDMI connection with audio out support as well. Can somebody confirm the HDMI version support (1.2a?), and also the number of audio out channels? (2, 5.1 ???).

Button
The button between HDMI and Ethernet is not a reset button.

It is boot_select0. Combined with JP3, it can be used to boot the CI20 from the USB.

It can also be used as a gpio once the CI20 is powered up. The boot_sel0 pin is connected to PD17.

Pinmux options can be checked to see which gpio is PD17 in kernel you booted.

In the 3.15 kernel, the gpio is number 113.

You can export the gpio via

echo 113 > /sys/class/gpio/export

And then use it.

Ethernet
10/100 RJ45, connects to the DM9000 chipset.

Boot mode selector
See the silkscreen on the board and the section at the end of the JZ4780 programmers manual (and can somebody transcribe the silkscreen into this section please...) - fundamentally you can boot from the on-board NAND or direct off the SDcard. There is also a USB boot function available, but it is not a standard DFU type boot, and requires JZ4780 specific host support.

Primary expansion header
Pinout diagram for the main CI20 0.1" pitch 26 pin header

Camera
The camera connector is 24 pin (26 pins on the schematic - two of which are the side ground solder tabs on the connector itself - the actual cable interface is 24 pin), and CMOS DVP 8-bit camera compatible. The Omnivision OV5640 5Mpixel unit can be used with the CI20 (often labelled FD5640 on the actual part)

IR
Receive only. Anybody got details on the protocols supported by hardware, and if pure software can be used to support other protocols?

LED
The CI20 board features a dual colour red & blue LED. It is controlled by GPIO PF15, which also controls the USB VBUS supply. When PF15 is high the LED lights red, when PF15 is low it lights blue. Software cannot power off the LED. A simple way to toggle the LED colour is to write to the PFPAT0S & PFPAT0C registers from the U-boot shell, in order to toggle the PF15 GPIO. The following example will toggle the colours rapidly, leading to the LED appearing purple:

while true; do mw.l 0xb0010548 0x8000; mw.l 0xb0010544 0x8000; done

SDcard
Standard pinout full sized SD/MMC slot. Can be used for direct booting, or for bulk storage (standard MTD support under Linux). Is wired to the MSC0 block in the SoC.

USB mini-OTG connector
Is paralleled with the left hand USB A connector - do not plug into both of these at once. Has the OTG VBUS controlled by the jumper next to it.

OTG VBUS jumper
Controls the VBUS for the OTG ports - would somebody like to describe the difference between having the connector fitted or not please.

USB A connector (left)
Paralleled with the mini-OTG connector.

USB A connector (right)
Connected to the EHCI USB controller in the SoC.

Dedicated UART header
Pinout and other functions of the dedicated UART header. This is uart4 of the SoC. Note that uart0 is on the 26pin main expansion header.



Test Points
Description of the (rather small little silver dot) test points on the board, derived from the schematic.

SoC
Ia an Ingenic JZ4780 - see the data sheet and programmers manuals referenced on this page.

DDR/RAM
Comprises of four H5TQ2G83DFR-H9C 2Gbit DDR3 chips, providing 8 bits of data each, providing a 32bit DDR3 memory bus to the SoC. Anybody have details of the standard clock rate?

ROM/NAND
Is provided by a single Samsung K9GBG08UOA NAND flash, using an 8bit data interface to the SoC.

Ethernet
Is provided by a Davicom DM9000C connected vi an 8-bit interface to the SoC, providing 10/100 ethernet.

WiFi/BT
Is provided by an Ingenic IW8103, based on a Broadcom BCM43362/4330, connected via SDIO to the SoC MSC1 port.

PMU
Is an active-semo ACT8600 specifically designed for the Ingenic JZ family of SoCs.

RTC
Is provided by a Pericom PT7C4337UE connected to the SoC via the I2C_4 bus.

Microphone switcher
The automatic 4-pin microphone switching/detection is provided by a Fairchild FSA8049 audio jack detection device.

OTP and MAC address formats
The following data is stored in the JZ4780 OTP ROM/efuse. This data can be accessed from Linux via the sysfs path of /sys/devices/platform/jz4780-efuse/

The C definition of the actual efuse area data format is: struct __packed__ otp { uint32 serial_number; /* As a decimal, huge range */ uint32 date; /* ISO8601 yyyymmdd format-ish as an int – for instance ‘20140527’d for May 27th 2014 */ char manufacturer[2]; /* ascii 2-character encoding of manufacturer – ‘NP’ == Nopa */ unsigned char mac[6]; /* six byte/48bit MAC address strored as 8-bit integers */ };