Radxa Wiki - User contributions [en]

Rock/flash the image

2023-08-16T02:37:41Z

Maycides:

{{rock_header}}
{{Languages|rock/flash_the_image}}
__TOC__

This page describes how to install an image to the nand flash of Radxa Rock, ie, how to flash the board. You can choose to either flash the whole nand image (ie, [[rock/update.img |update.img]]) to the board or just flash the selected [[rock/partitions |partitions]]. You can download the [[rock/prebuilt images| prebuilt images]] from our [http://dl.radxa.com/rock/images/ server] or build your own images.

== Before you start ==

Keep in mind that:
'''You can always flash the rock, it never bricks (as the name :)) unless some hardware damage occurs.'''

What you will need to flash the board is:

* Firmware image, check [[Rock/hardware_revision | hardware revision]]. there are Pro and Full/Lite, firmware is different
* Radxa Rock or Rock Pro or Rock2 Square board
* a PC running Windows (XP 32/64bit, Windows 7 32/64 bit) or Linux (32/64bit)
* a micro USB cable with one side plugged in to the OTG port of the board and the other side plugged into the USB port on PC.

== Windows ==

The Windows tool for flashing the image is provided by Rockchip. To flash the [[rock/update.img| update.img]](you'd better click this link and read this page,it's very Important for the radxa beginner), you need to use the RKBatchTool and to flash the [[rock/partitions| partitions]], you will need to use RKDevelopTool. Both RKBatchTool and RKDevelopTool rely on the RK USB driver so you will need to install it first as below:

=== Install driver ===
# install using RKDriverAssistant tools - the easy way(Just for winXp, Vista, Win7,not support Win8)
# install manually (WinXp,Vista,Win7,Win8)

<p></p>
'''If you have already installed the USB driver please skip this step.'''

====a. Install using RK Driver Assistant tools ====
Note:The method just support WinXp,Vista,Win7, NOT SUPPORT Win8

There’s no need to connect your Rockchip device during this procedure just download and extract [https://github.com/rockchip-linux/tools/raw/master/windows/DriverAssitant_v4.91.zip RKDriverAssistant.zip]
Then double click on DriverInstall.exe in the RKDriverAssistant directory to start the utility.
If you've previously tried to install the Rockchip USB drivers for any Rockchip devices make sure you click “Uninstall Driver” first.

[[File:RK_Driver_Assistant_Install_Uninstall.jpg]]

Then click “Install Driver” and when the driver has finish installing then shut down radxa board and connect the Radxa Rock board to your computer and let the board go to [[Rock/Loader mode|loader mode]], then your computer will detect the board and you will see it within device manager.

[[File:RK_Driver_Assistant_Install_Usb_driver.png]]

Now the driver should have been installed successfully!

====b. Install Manually====

Download driver file first. For WinXp,Vista,Win7,Download the file (usb_driver_v3.5.zip) from [http://dl.radxa.com/rock/tools/windows/usb_driver_v3.5.zip here] . For Win8 Download the file(usb_driver_v3.7.zip) from [http://dl.radxa.com/rock/tools/windows/Rockusb%20Driver%20v3.7.zip here]. shut down the Radxa Rock board then connect the Radxa Rock board to the computer and let the board go to [[Rock/Loader mode|loader mode]]. After your computer should detect the board and you will see an unknown device within device manager.

[[File:flash_image_1.jpg]]

Select the Unknown device then right click and select "Update Driver Software".

[[File:flash_image_2.jpg]]

Select "Browse the computer for driver software".

[[File:flash_image_2.5.jpg]]

Find the file unzipped file you downloaded earlier (usb_driver_v3.5.zip) and select either the 32/64bit folder then click "OK" to install.

[[File:flash_image_3.jpg]]

When the driver is installed successful you will then see a Rockusb Device in the device manager window.

[[File:flash_image_6.jpg]]

Now the driver is installed successfully.

===Flash Image===

Download the tool first [https://github.com/rockchip-linux/tools/raw/master/windows/AndroidTool_Release_v2.71.zip AndroidTool_Release_v2.71.zip]

There are two methods to flash an image.

# Flash the whole firmware only, it will erase everything.
# Flash firmware by partitions, it's very convenient when debugging part function such as kernel

====Flash the whole firmware ====

Power down the Radxa Rock board and connect the Radxa Rock board to the computer then let the board go to [[Rock/Loader mode|loader mode]] after the program should detect the device.<br/>

you can see “Found One MASKROM device “ at the bottom of the tool when you first flash the board or just unbrick the board

Or “Found One Loader Device” at the bottom of the tool when you flashed image not first time

Then Select an image (rockdev/update.img). For information on how to make nand image see [[Rock/update.img | update.img]]<br/>

After that, Click "Upgrade " to begin flashing

[[File:Flash_whole_firmware_1.png]]

[[File:Flash_whole_firmware_2.png]]

====Flash firmware by partitions====

Power down the Radxa Rock board and connect the Radxa Rock board to the computer then let the board go to [[Rock/Loader mode|loader mode]] after the program should detect the device.<br/>

you can see “Found One MASKROM device “ at the bottom of the tool when you first flash the board or just unbrick the board

Or “Found One Loader Device” at the bottom of the tool when you flashed image not first time.

Then select the partitions you need update, and select the right image which you can find under rockdev or kernel directory. finally click "Run " to flash

Note: if your address of the partitions doesn't the same as the pic below, you can modify the address by click the address item.

[[File:Flash_whole_firmware_3.png]]

Here is the video you can refer

http://v.youku.com/v_show/id_XNjkzNDk3MjEy.html

=== Troubleshooting ===
==== FlashTool can not recognize the board ====

This often happened by the follow reasons:

1) Not enter the loader mode (refer to [[Rock/Loader_mode | [rock loader mode]]] [[Rock2/square_bb/loader_mode | [rock2 square loader mode]]])

Note:

In general, When you connect to PC with radxa( in loader mode), the PC can recongize radxa as Rockusb Device(windows)

2) the used usb port of pc is usb3.0 (please change usb2.0 port)

3) the OS of PC is windows 8 (if windows 8,please use [http://dl.radxa.com/rock/tools/windows/Rockusb%20Driver%20v3.7.zip http://dl.radxa.com/rock/tools/windows/Rockusb%20Driver%20v3.7.zip])

4) bad quality usb cable, you can change a short and good quality one to try again

If the problem still exists, you can refer to the topics in [http://talk.radxa.com talk.radxa.com], create a new topic on it or send email to support@radxa.com

==== Flashing failed ====
For rock pro

After flashing, the uart print

DDR Version 1.04 20130517 In DDR3 300MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=2 Die Bus-Width=16 Size=2048MB Memory OK OUT BUILD=====6 SdmmcInit=0 20 F:32 1061 0 0 40 FlashReadRetry error!!,row = fff000 FlashReadRetry error!!,row = fff000

and not boot.

If flashing failed, try to format the nand flash before flashing it.
* AndroidTool V2.3 -> Upgrade firmware - click "Erease Flash" button to format the nand flash
* AndroidTool V2.3 -> Download Image - click "LowerFormat" to format the nand flash

For rock2 square

you can press reset key and reflash , if still failed ,you can refer to http://talk.radxa.com/topic/957/bricked-rock2/19 or send mail to support@radxa.com

==== Preparing IDB failed ====
This happens at upgrading bootloader, if you need to upgrade the bootloader or the update.img contains a new bootloader, you probably will meet this. The rock is "bricked". Follow this [[rock/unbrick | unbrick instructions]] to unbrick it.

==== Win8.1 and USB 3.0 ====
If you have problem with Win8.1 and USB 3.0, please check:
http://talk.radxa.com/topic/1026/solution-rk-batchtool-problem-with-64bit-windows-8-1-usb3

== Linux ==
Rockchip has provided tools for upgrading within Linux (closed source) since Android 4.4. It's called '''upgrade_tool'''.
It supports update.img, parameter, bootloader and other partitions, and it's command line based.

rkflashkit is an open source GUI version flashing tool for rockchip devices. It can not flash bootloader or parameter, only supports kernel and other partitions, but it supports backup the partitions.

For developers:
''The initial RE work of the Rockchip bootloader updating protocol is by naobsd and has been improved by some in '''rkflashtool'''. linuxerwang has made a GUI version of the rkflashtool called '''rkflashkit'''. Please note: both '''rkflashtool''' and '''rkflashkit''' can '''not''' flash the [[rock/update.img]] and can only flash within [[rock/bootloader]] mode and not [[rock/mask rom]] mode because the [[rock/mask rom]] updating protocol is not RE yet. If you are interested in the RE protocol ping naobsd at #radxa on IRC. Since the [[rock/bootloader]] has remained unchanged for a long time it's enough for normal usage. If you don't know what this means, just ignore it.''

=== Upgrade_tool from Rockchip ===

Download the Rockchip linux upgrade tool [http://dl.radxa.com/rock/tools/linux/Linux_Upgrade_Tool_V2.1.zip here]. Unzip it and you will get a file called '''upgrade_tool''' which is a binary executable file under Linux.

Note: there are two ways to flash the android image.

1> Just flash one image file. refer to the "Flash update.img" ,The image you can download here [[rock/prebuilt_images | '''prebuilt_image''' ]] . or you can build the image by yourself refer to [[rock/Android_Build | '''Android_Build''']]

2>Flash image by partitions,this methods you need flash serveral images depends on the partitions and your requirement. refer to "Flash parameter ", "Flash bootloader ","Flash the kernel(boot.img)"

====Flash all-in-one nand/emmc image file(Recommended)====

Let the board go to '''loader mode''' [[Rock/Loader mode| [Rock Loader mode]]], [[Rock2/square_bb/loader_mode | [Rock2 Square Loader mode]]] and run the following command to flash the [[rock/update.img | '''update.img''']]:
sudo ./upgrade_tool '''uf''' /path/to/update.img #(UF Upgrade Flash)

If you have an error with upgrading you can low level format the nand flash first with the following command:
sudo ./upgrade_tool '''lf''' #(LF Lowlevel Format) This will erase everything on nand

====Flash by partitions====

The whole files you should flash are"parameter","bootloader","boot.img","recovery.img""system.img" , all the file you can find under the rockdev/ after you build the android successful.

How to flash the file and images.

===== Flash bootloader =====
sudo ./upgrade_tool '''ul''' /path/to/bootloader #(UL Upgrade Loader)

Other partitions can be flashed by '''di''' command. You can use '''upgrade_tool di partition_name image_name''' to flash the image to the partition. There are some shortcuts for certain image name.

{| class="wikitable" border="1"
|-
! partition name
! short name
|-
| parameter
| -p
|-
| boot
| -b
|-
| system
| -s
|-
| recovery
| -r
|-
| misc
| -m
|}

===== Flash parameter =====
sudo ./upgrade_tool '''di''' '''parameter''' /path/to/parameter
or for short
sudo ./upgrade_tool '''di''' -p /path/to/parameter #(DI Download Image)

===== Flash the kernel(boot.img) =====
sudo ./upgrade_tool '''di''' boot /path/to/boot.img
or for short
sudo ./upgrade_tool '''di''' -b /path/to/boot.img

===== Flash the rootfs =====
sudo ./upgrade_tool '''di''' linuxroot /path/to/rootfs.img

===== Others =====
There are other commands in the upgrade_tool, such as:
EF: erease the nand flash

FAQ

1) why I must flash this file?

The android image is constructed by this files.

2)what's the paration info?

The partations info you can get from the paramteter file under the rockdev/ which in the android source code.

CMDLINE:console=ttyFIQ0 androidboot.console=ttyFIQ0
init=/init initrd=0x62000000,0x00800000
mtdparts=rk29xxnand:0x00002000@0x00002000(misc),
0x00006000@0x00004000(kernel),
0x00006000@0x0000a000(boot),
0x00010000@0x00010000(recovery),
0x00020000@0x00020000(backup),
0x00040000@0x00040000(cache),
0x003FC000@0x00080000(userdata),
0x00002000@0x0047C000(metadata),
0x00002000@0x0047E000(kpanic),
0x00180000@0x00480000(system),
-@0x00600000(user)

3) why other parations do have image to flash?

Other parations are used to store data.

4) why not flash the kernel.img ?

The kernel.img is packed into boot.img . more info you can refer to [[Rock/Android_Build | '''Android_Build''']]

5) Other questions

Post on the talk.radxa.com or send email to support@radxa.com

=== Flash with rkflashtool(Advanced) ===

rkflashtool is an open source tool to write nand flash via the loader mode for rockchip platform.

To install rkflashtool:

sudo apt-get install build-essential libusb-1.0-0-dev
git clone https://github.com/linux-rockchip/rkflashtool
cd rkflashtool
make
sudo cp rkflashtool rkcrc rkunpack rkunsign /usr/local/bin

To read/write parameter:

rkflashtool p > param
rkflashtool P < param

To read/write partitions:

rkflashtool r boot > boot.img
rkflashtool w boot < boot.img

rkflashtool r linuxroot > linuxroot.ext4
rkflashtool w linuxroot < linuxroot.ext4

=== Rkflashkit with GUI ===
You can download the pre-built rkflashkit [http://dl.radxa.com/rock/tools/linux/rkflashkit_0.1.1_all.deb here] or build it yourself with the following command:

git clone https://github.com/linuxerwang/rkflashkit
cd rkflashkit
./waf debian

And install it with the following command

sudo apt-get install python-gtk2
sudo dpkg -i rkflashkit_0.1.1_all.deb

Run it with the following command

sudo rkflashkit

You can see the interface looks like this:

[[File:rkflashkit1.png| 600px]]

Connect the Radxa Rock board to the computer and let the board go into [[Rock/Loader mode|loader mode]] you will then see the the program detect the board in loader mode.

# Click the Nand partition and you will see the partitions of the board listed then choose the one you want to flash.
# Choose the location of the image you want to flash to that partition.
# Click the "Flash image" button and it will start flashing
# After it's finished click "Reboot Device" button to reboot the board.

[[File:rkflashkit2.png| 500px]] [[File:rkflashkit3.png| 500px]]

=== Troubleshooting ===
==== Creating Comm Object failed! ====
that's udev issues… You can solve this by creating a new file in /etc/udev/rules.d/ with the rule for the rock.

To do that, copy and paste these commands:

echo 'SUBSYSTEM=="usb", ATTR{idVendor}=="2207", MODE="0666", GROUP="plugdev"' | sudo tee /etc/udev/rules.d/51-android.rules

Finally, just remove and reinsert the USB cable.

==== What's verision of My board and Which Image should I flash! ====

refer to [[Rock/update.img|update.img]]

== Install the image on RR without PC ==
If you want to write the image on RR without any other host PC, you can download the image and write with dd:
sudo dd if=XXX.img of=/dev/block/mtd/by-name/XXX bs=16384 conv=sync,fsync

== Videos tutorial ==
*Flashing the image to nand flash https://www.youtube.com/watch?v=r20lOKu2E1s&feature=youtu.be

== External Reference ==
* http://www.hagensieker.com/styled-26/index.html

Rock/flash the image/zh cn

2023-08-16T02:37:32Z

Maycides:

{{Languages|rock/flash_the_image}}
__TOC__

这个页面描述怎么往Radxa Rock的NAND flash上装系统，即大家喜闻乐见的'''刷机'''. 你可以选择完全刷机(就是刷 [[rock/update.img |update.img]]格式的固件)或者只刷特定的某个 [[rock/partitions |分区]]. 你可以从[http://radxa.com/download radxa网站download]下载radxa(android, lubuntu, 双启动固件)或者第三方[[rock/prebuilt images| 编译好的固件 ]]或者制作你自己的固件.

== 开始之前 ==

记住:
'''Radxa Rock是刷不死的，正如它的名字一样。除非你把硬件损坏了。'''
烧写固件所需要的硬件环境：
* 一块Radxa Rock的开发板（全功能版本或者精简版本）
* 一台运行windows XP/Windows 7(32位/64位)或者Linux（32位/64位）的计算机
* 一根用于连接Radxa Rock开发板的OTG口和计算机USB口的microUSB线

== Windows ==

Windows下烧写镜像的工具是由Rockchip提供的。你可以使用RKBatch Tool来烧写镜像文件 [[rock/update.img| update.img]]，并使用RKDevelop Tool来烧写partitions配置文件[[rock/partitions| partitions]]。不过这两种工具都依赖于RK USB驱动，所以你首先需要根据以下步骤安装RK USB驱动：

=== Install driver ===
在Windows下有两种方式安装该驱动：

# 使用RKDriverAssistant tools安装 - 比较容易的方式
# 手动安装
<p></p>
'''如果你已经安装好了USB驱动，请跳过此步骤。'''

==== 使用RK Driver Assistant tools安装 ====
在此安装过程中不需要连接Rockchip设备，只需要下载并解压[http://dl.radxa.com/rock/tools/windows/RK_DriverAssitant.zip RKDriverAssistant.zip]，然后在RKDriverAssistant目录下的DriveInstall.exe上双击运行即可。
如果你之前为其他Rockchip设备安装过Rockchip USB驱动，确保首先点击"Uninstall Driver"。

[[File:RK_Driver_Assistant_Install_Uninstall.jpg]]

然后点击 “Install Driver” 。当安装完成时，关闭Radxa Rock开发板，并将开发板与你的计算机连接起来（使用MicroUSB线）（注意不要使用USB3.0接口），然后使开发板进入[[Rock/Loader mode/zh_cn|Loader模式]]，此时你的计算机将检测到开发板，并且你将在设备管理器中看到它。

[[File:RK_Driver_Assistant_Install_Usb_driver.png]]

现在驱动应该已经安装成功了。

==== 手动安装====

从 [http://dl.radxa.com/rock/tools/windows/usb_driver_v3.5.zip 这里] 下载(usb_driver_v3.5.zip) 文件，并解压该文件，关闭Radxa Rock开发板，然后使用MicroUSB线连接开发板和计算机，并让开发板进入 [[Rock/Loader mode/zh_cn|Loader模式]]，然后你的计算机应该检测到开发板，同时你在设备管理器中会看到一个未知设备。

[[File:flash_image_1.jpg]]

选择该未知设备，并右键点击它，然后选择“更新驱动程序软件”。

[[File:flash_image_2.jpg]]

选择“浏览计算机以查找驱动程序”

[[File:flash_image_2.5.jpg]]

选择浏览，并在弹出的窗口中找到之前下载并解压的 (usb_driver_v3.5.zip)文件夹，选择32/64位文件夹其中之一，然后点击OK来安装

[[File:flash_image_3.jpg]]

当驱动安装成功，你将在设备管理器中看到一个Rockusb设备

[[File:flash_image_6.jpg]]

现在驱动程序已经安装成功了。

===烧写镜像===
要烧写一个镜像文件，我们有两种方式.

# 使用 RKBatchTool （工厂用来升级固件的工具，只能烧写update.img，注意会擦除原有的任何东西）
# 使用 RKAndroidTool （开发工具，可以按区块烧写）
<br/>
====使用 RKBatchTool 烧写 update.img====

从[http://dl.radxa.com/rock/tools/windows/RK_BatchTool_V1.7.zip 这里]下载RKBatchTool，然后解压，双击RKBatchTool.exe，你将看到如下界面：

[[File:flash_image_7.jpg]]

选择一个镜像(rockdev/update.img)。如果需要如何制作一个update.img文件的话，查看[[Rock/update.img | update.img]]。<br/>
[[File:flash_image_8.jpg]]

拔掉Radxa Rock开发板的电源，并使用MicroUSB线连接开发板与你的计算机，然后让开发板进入[[Rock/Loader mode/zh_cn|Loader模式]]，此时程序应该能检测到设备。
<br/>
[[File:flash_image_9.jpg]]

单击“升级”按钮进行烧写，在烧写成功时，你将看到如下界面。<br/>
[[File:flash_image_10.jpg]]

如果烧写操作失败，那么可能是update.img存在错误，你可以尝试重做以上操作或者重新制作update.img！

=== 使用RKAndroidTool 烧写选定的镜像 ====
从[http://dl.radxa.com/rock/tools/windows/RKDevelopTool_v1.37.zip 这里]下载RKAndroidTools，并解压，然后双击RKAndroidTool.exe，你将看到以下界面：

[[File:rkandroidtool_flash_image_1.png]]

拔掉Radxa Rock开发板的电源，连接开发板和计算机，并让开发板进入[[Rock/Loader mode/zh_cn|Loader模式]]，然后程序会自动检测到设备。

[[File:rkandroidtool_flash_image_2.png]]

界面上有8个可选项，选择正确的行并且选中左边的选择框，然后你必须单击该行右侧的按钮，选择你想烧写的文件路径。你可以一次选择一个或者多个文件并烧写它们。最后单击“Run”烧写镜像（程序右侧的框里面会显示过程日志）。

[[File:rkandroidtool_flash_image_3.png]]

[[File:rkandroidtool_flash_image_4.png]]

如果成功的话，板子会自动断开，并且引导到系统。

请注意：

# 当你通过“./mkimage.sh.ota”打包镜像文件时，内核是包含在boot.img中的。详情请查看 [[Rock/Android_Build]]。
# 你可以根据需要一次烧写一个或者多个镜像文件

=== 故障排除 ===
==== RKBatchTool 检测不到开发板 ====
1.Loader模式 : USB 设备硬件: VID_2207&PID_310B <br/>
2.引导进Android: USB 设备硬件: VID_2207&PID_0006

Loader模式<br/>
我已经手动安装了驱动，并且Loader模式的USB为PID_310B，“Rockusb device”驱动在Vista上安装成功了，但是RKBatchTool连接不到RK3188的板子，导致无法烧写镜像。

对于Loader模式无法连接的问题[已解决]<br/>
根本原因：RK3188板通过USB3.0 PMMCIA卡连接到笔记本电脑。这是一个USB2.0到USB3.0的兼容性问题，所以USB3.0端口换成USB 2.0端口，然后RKBatchTool应该可以连接到RK3188板子来烧写镜像了。

==== 烧写失败 ====

烧写后，串口打印：

DDR Version 1.04 20130517 In DDR3 300MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=2 Die Bus-Width=16 Size=2048MB Memory OK OUT BUILD=====6 SdmmcInit=0 20 F:32 1061 0 0 40 FlashReadRetry error!!,row = fff000 FlashReadRetry error!!,row = fff000

同时无法引导。

如果烧写失败，尝试在烧写前格式化NandFlash。
* RKAndroidTool - 单击 “Erease IDB”按钮，格式化NandFlash。
* RKBatchTool - 单击 “Restore”按钮格式化，然后烧写镜像。

==== Preparing IDB failed ====
这发生在升级bootloader的时候，如果你需要升级bootloader或update.img中包含了一个新的引导程序，那么你可能会遇到这个问题。板子这是“变砖”了。。。按照这个 [[rock/unbrick | unbrick 说明]]解决它。

== Linux ==
从Android 4.4起，Rockchip提供了一个在Linux系统下的升级工具（闭源）。叫做“upgrade_tool”。
它支持烧写update.img、parameter、bootloader和其他分区，注意它是基于命令行的工具。

rkflashkit 是一个用于烧写瑞芯微设备的开源图形界面版本软件。它不能烧写bootloader或者parameter，只支持烧写内核和其他分区，但是它支持备份这些分区。

针对开发者：
“早期的Rockchip bootloader刷机协议的逆向工程工作是由 naobsd 完成的，并且由一些在使用 “rkflashtool”的人进行了改进，linuxerwang 制作了一个rkflashtool的GUI版本，叫做 “rkflashkit”，请注意："rkflashtool" 和 “rkflashkit” 都不能烧写 [[rock/update.img | update.img格式的刷机包]] ，只能在 [[rock/bootloader | bootloader]] 模式下并且不在 [[rock/mask rom | mask rom]] 模式下烧写，因为这个 [[rock/mask rom | mask rom]] 升级协议还没有被逆向工程，如果你对逆向工程刷机协议有兴趣，可以在 #radxa 的聊天室上找naobsd，[[rock/bootloader | bootloader]] 通常不会变动太大，已经可以保证日常使用了。如果你不明白这段话的意思，只要忽略它就可以了。”

=== Rockchip的升级工具 ===

从 [http://dl.radxa.com/rock/tools/linux/Linux_Upgrade_Tool_V2.1.zip 这里]下载Rockchip的Linux升级工具并解压，然后你会得到一个在Linux下二进制可执行文件，叫做“upgrade_tool”。

==== 烧写 update.img ====
让板子进入[[Rock/Loader mode/zh_cn|Loader模式]]并运行以下命令烧写[[rock/update.img | update.img格式的刷机包]]：
sudo ./upgrade_tool '''uf''' /path/to/update.img #(UF Upgrade Flash)

如果你在升级过程中有一个错误，你可以首先使用以下命令来低格nandflash：
sudo ./upgrade_tool '''lf''' #(LF Lowlevel Format) This will erase everything on nand

==== 烧写 parameter ====
sudo ./upgrade_tool '''di''' -p /path/to/parameter #(DI Download Image)

==== 烧写 bootloader ====
sudo ./upgrade_tool '''ul''' /path/to/bootloader #(UL Upgrade Loader)

==== 烧写内核(boot.img) ====
sudo ./upgrade_tool '''di''' -b /path/to/boot.img #(DI Download Image)

==== 其他====
有一些在upgrade_tool中使用的其他命令，比如：
UL: 升级Loader
EF: 擦除nand flash

=== 图形化版本工具 - Rkflashkit ===
你可以从 [http://dl.radxa.com/rock/tools/linux/rkflashkit_0.1.1_all.deb 这里]下载已经编译好的rkflashkit，或者使用以下命令自己编译它：

git clone https://github.com/linuxerwang/rkflashkit
cd rkflashkit
./waf debian

并使用以下命令安装：

sudo apt-get install python-gtk2
sudo dpkg -i rkflashkit_0.1.1_all.deb

使用以下命令运行：

sudo rkflashkit

你会看到如下的界面:

[[File:rkflashkit1.png| 600px]]

连接Radxa Rock开发板和计算机，并且让板子进入[[Rock/Loader mode/zh_cn|Loader模式]] ，你将看到程序在Loader模式下检测到板子。

# 单击 Nand partition，然后你会看到板子的分区列表，然后从其中选择一个你要烧写的分区。
# 选择你想烧写到这个分区的镜像文件目录
# 单击 “Flash image” 按钮，就会开始烧写。
# 烧写结束后，单击“Reboot Device”按钮重启板子

[[File:rkflashkit2.png| 500px]]
[[File:rkflashkit3.png| 500px]]

== 不用计算机在RR上烧写镜像 ==
如果你想不用其他任何计算机，在Rockchip Rock板上写镜像，你可以下载镜像，并使用dd写：
sudo dd if=XXX.img of=/dev/block/mtd/by-name/XXX bs=16384 conv=sync,fsync

Rock3/3c

2023-06-30T07:17:53Z

Maycides: /* ROCK 3 Model C */

{{rock3_header}}

{{Languages|rock3/3c}}

__NOTOC__

<div class="col-md-12 ">
<div class="col-md-8 ">

= ROCK 3 Model C=
This is the documentation for ROCK 3 Model C, written by Radxa Team with community contributions.

ROCK 3C features a quad core Cortex-A55 ARM processor, 32bit 3200Mb/s LPDDR4, up to 1920x1080@60 HDMI, MIPI DSI, MIPI CSI, 3.5mm jack with mic, USB Port, GbE LAN, PCIe 2.0, 40-pin color expansion header.

=== Close look of ROCK 3C ===

[[File:Rock3C_top_800px.png | 400px]][[File:Rock3C_bottom_800px.png|400px]]

=== <span id="get_start_specs"></span> Features ===

{| class="wikitable"
! Model
! colspan="1" width=80% | ROCK 3 Model C
|-
!SoC<br><br>CPU<br>GPU
| colspan="2" | '''RK3566''' <br><br>Quad-core Cortex-A55, frequency 1.6Ghz<br>
Mali G52<br>
|-
! Memory
| colspan="2" | 1/2/4GB LPDDR4 2112MT/s
|-
! Storage
| colspan="2" | eMMC<br>μSD card (μSD slot supports up to 128 GB μSD card)<br />M.2 2230 SSD (M.2 connector supports up to 1TB M2 NVME SSD)
|-
! Display
| colspan="2" | HDMI 2.0 up to 1920x1080 60p<br />MIPI DSI 2 lanes via FPC connector<br />HDMI and MIPI DSI can not work at the same time
|-
! Audio
| colspan="2" | 3.5mm jack with mic<br />HD codec that supports up to 24-bit/96KHz audio.
|-
! Camera
| colspan="2" | MIPI CSI 2 lanes via FPC connector, support up to 800 MP camera.
|-
! Wireless
| colspan="2" | 802.11 ac WiFi 5/ BT 5
|-
! USB
| colspan="2" | USB 2.0 OTG X1(middle upper one), hardware switch for host/device switch<br />USB 3.0 HOST X1<br />USB 2.0 HOST X2
|-
! Ethernet
| colspan="2" | GbE LAN with Power over Ethernet (PoE) support<br />additional HAT is required for powering from PoE
|-
! IO
| colspan="2" | 40-pin expansion header<br />5 x UART<br />1 x SPI bus<br />2 x I2C bus<br />6 x PWM<br />1 x ADC<br /> 6 x GPIO<br />2 x 5V DC power in<br />1 x 3.3V DC power in
|-
! Others
| colspan="2" | RTC<br />RTC battery connector for time backup(optional)
|-
! Power
| colspan="2" | USB type C 5V, 5V/3A is suggested when using without SSD, 5V/5A is suggested when using with SSD.
|-
! Size
| colspan="2" | 85mm x 56mm
|}

=== Getting start guide ===

Follow the [[Rock3/getting_started/rock-3c | Guide]] to start using your ROCK 3C.

=== Use Radxa Debian ===

Follow the [[Rock3/Debian | Radxa Debian Guide]]

=== Download and install third party OS ===

Find [[Rock3/downloads | more OS]] by the Radxa friends and the community.

=== Find supported accessories ===

Discover the [[Rock3/hardware#accessories | accessories]] that just work on ROCK 3A

=== Learn more about the hardware details ===

Learn more about the ROCK 3A [[Rock3/hardware/3a | connectors and pinout]]

Check the [[Rock3/hardware#datasheet | data sheets]] of the components used on ROCK 3C.

</div> 

<div class="col-md-4 ">

<div class="thumbnail ">[[File:Start_3c.png | 440px]]</div>

<div class="panel panel-hearts-white">
<div class="panel-heading"> <h3 class="panel-title"><i class="fa fa-hand-o-up"></i>[[rock3/getting_started | Setup/Quick start ]]</h3> </div>
<div class="panel-body">
* [[rock3/getting_started/rock-3c | Getting started with ROCK 3C]], including what you need and how to get it booted.
* [[rock3/hardware/3c/gpio | ROCK 3C GPIO pinout]]
</div>
</div> 

<div class="panel panel-mango-white">
<div class="panel-heading"> <h3 class="panel-title"><i class="fa fa-star"></i> [[community_updates | What's new]]</h3> </div>
<div class="panel-body">
{{Community_updates}}
</div>
</div> 

<div class="panel panel-cocktail-white">
<div class="panel-heading"><h3 class="panel-title"><i class="fa fa-users"></i> Community</h3></div>
<div class="panel-body">
* Forum: http://forum.radxa.com
* Discord: https://rock.sh/go
* QQ Group: 591048098
* [[Rockpi4/contribute | How to contribute to this wiki, refer ROCK Pi 4 contribution page]]
</div>
</div> 

</div> 

</div>

Rock3/CM3/IO/pinout

2023-06-13T03:24:23Z

Maycides: /* U31 */

{{rock3_header}}
{{Languages|rock3/cm3/IO/pinout}}

[[rock3 | ROCK 3]] > [[rock3/CM3 | Compute Module 3]] > [[Rock3/CM3/IO | Radxa CM3 IO Board]] > [[Rock3/CM3/IO/pinout | Pinout]]

__TOC__

[[File:Cm3_io_label.jpg | 1200px]]

== LCD1 & LCD2 ==

* LCD1: MIPI DSI0 or LVDS
* LCD2: MIPI DSI1

{| class="wikitable"
|-
! Pin
! Name
|-
| 1
| VCC_LEDA2
|-
| 2
| VCC_LEDA2
|-
| 3
| VCC_LEDA2
|-
| 4
| NC
|-
| 5
| VCC_LEDK2
|-
| 6
| VCC_LEDK2
|-
| 7
| VCC_LEDK2
|-
| 8
| VCC_LEDK2
|-
| 9
| GND
|-
| 10
| GND
|-
| 11
| MIPI_DSI_TX_D2P
|-
| 12
| MIPI_DSI_TX_D2N
|-
| 13
| GND
|-
| 14
| MIPI_DSI_TX_D1P
|-
| 15
| MIPI_DSI_TX_D1N
|-
| 16
| GND
|-
| 17
| MIPI_DSI_TX_CLKP
|-
| 18
| MIPI_DSI_TX_CLKN
|-
| 19
| GND
|-
| 20
| MIPI_DSI_TX_D0P
|-
| 21
| MIPI_DSI_TX_D0N
|-
| 22
| GND
|-
| 23
| MIPI_DSI_TX_D3P
|-
| 24
| MIPI_DSI_TX_D3N
|-
| 25
| GND
|-
| 26
| NC
|-
| 27
| RESET
|-
| 28
| GND
|-
| 29
| VCC_1V8
|-
| 30
| VCC_LCD_MIPI
|-
| 31
| VCC_LCD_MIPI
|}

== J11 ==

* eDP 40P

{| class="wikitable"
|-
! Pin
! Name
|-
| 1
| NC
|-
| 2
| GND
|-
| 3
| EDP_TX_D3N
|-
| 4
| EDP_TX_D3P
|-
| 5
| GND
|-
| 6
| EDP_TX_D2N
|-
| 7
| EDP_TX_D2P
|-
| 8
| GND
|-
| 9
| EDP_TX_D1N
|-
| 10
| EDP_TX_D1P
|-
| 11
| GND
|-
| 12
| EDP_TX_D0N
|-
| 13
| EDP_TX_D0P
|-
| 14
| GND
|-
| 15
| EDPTX_AUXP
|-
| 16
| EDPTX_AUXN
|-
| 17
| GND
|-
| 18
| VCC3V3_LCD
|-
| 19
| VCC3V3_LCD
|-
| 20
| VCC3V3_LCD
|-
| 21
| VCC3V3_LCD
|-
| 22
| NC
|-
| 23
| GND
|-
| 24
| GND
|-
| 25
| GND
|-
| 26
| GND
|-
| 27
| NC
|-
| 28
| GND
|-
| 29
| GND
|-
| 30
| GND
|-
| 31
| GND
|-
| 32
| LCD0_BL_EN
|-
| 33
| LCD0_BL_PWM5
|-
| 34
| NC
|-
| 35
| NC
|-
| 36
| VCC12V_LCD
|-
| 37
| VCC12V_LCD
|-
| 38
| VCC12V_LCD
|-
| 39
| VCC12V_LCD
|-
| 40
| NC
|-
| 41
| NC
|-
| 42
| NC
|}

== J12 & J13==

* Touch Panel
{| class="wikitable"
|-
! Pin
! Name
|-
| 1
| GND
|-
| 2
| SCL_3V3
|-
| 3
| SDA_3V3
|-
| 4
| INT_3V3
|-
| 5
| RST_3V3
|-
| 6
| VCC_TP
|}

== J14 & J15==

* 2x MIPI CSI

{| class="wikitable"
|-
! Pin
! Name
|-
| 1
| RESET
|-
| 2
| PWDN
|-
| 3
| CAM_CLKOUT
|-
| 4
| GND
|-
| 5
| I2C_SCL
|-
| 6
| I2C_SDA
|-
| 7
| NC
|-
| 8
| 1V2
|-
| 9
| NC
|-
| 10
| 2V8
|-
| 11
| 1V8
|-
| 12
| GND
|-
| 13
| MIPI_CSI_RX_D0P
|-
| 14
| MIPI_CSI_RX_D0N
|-
| 15
| NC
|-
| 16
| MIPI_CSI_RX_D1P
|-
| 17
| MIPI_CSI_RX_D1N
|-
| 18
| GND
|-
| 19
| MIPI_CSI_RX_CLK0P
|-
| 20
| MIPI_CSI_RX_CLK0N
|-
| 21
| GND
|-
| 22
| NC
|-
| 23
| NC
|-
| 24
| GND
|-
| 25
| NC
|-
| 26
| NC
|}

== U26 ==

{| class="wikitable" style="vertical-align:middle; background-color:#F9F9F9;"
|- style="font-weight:bold; text-align:center; background-color:#F2F2F2;"
! Pin
! Name
|-
| 1
| GND
|-
| 2
| 12V
|-
| 3
| 3.3V
|-
| 4
| PWM
|}

== U31 ==
{| class="wikitable"
|-
! Name
! Number
|-
| WL_nDis
| 1
|-
| GND
| 2
|-
| BT_nDis
| 3
|}

== U32==
{| class="wikitable"
|-
! Name
! Number
|-
| PWRON_KEY
| 1
|-
| GND
| 2
|-
| RUN_PG(NC)
| 3
|}

== J9==

== J10 ==

== U36 ==
{| class="wikitable"
|-
! Name
! Number
|-
| 5V0_USB30
| 1
|-
| USB2_HOST3_DM
| 2
|-
| USB2_HOST3_DP
| 3
|-
| GND
| 4
|}
== U30 ==
{| class="wikitable"
|- style="font-weight:bold; background-color:#F2F2F2;"
! Name
! Number
|- style="background-color:#F9F9F9;"
| GND
| 1
|- style="background-color:#F9F9F9;"
| NRPIBOOT(NC)
| 2
|- style="background-color:#F9F9F9;"
| GND
| 3
|- style="background-color:#F9F9F9;"
| EEPROM_NWP
| 4
|-
| AIN0(NC)
| 5
|-
| AIN1(NC)
| 6
|-
| GND
| 7
|-
| SYNC_IN(NC)
| 8
|-
| SYNC_OUT(NC)
| 9
|-
| GND
| 10
|-
| TV_OUT(NC)
| 11
|-
| GND
| 12
|-
| RUN_PG(NC)
| 13
|-
| PWRON_KEY
| 14
|}
== J18 ==
{| class="wikitable"
|-
! Name
! Number
|-
| VCC5V0_USB2
| 1
|-
| VCC5V0_USB2
| 2
|-
| USB3_DM
| 3
|-
| USB4_DM
| 4
|-
| USB3_DP
| 5
|-
| USB4_DP
| 6
|-
| GND
| 7
|-
| GND
| 8
|-
| NC
| 9
|-
| NC
| 10
|}
== U28 ==

== CON1 ==

* [[Rock3/CM3/IO/GPIO | Radxa CM3 IO 40-pin Header GPIO]]

Rock3/CM3/IO/pinout

2023-06-13T03:24:19Z

Maycides: /* U32 */

{{rock3_header}}
{{Languages|rock3/cm3/IO/pinout}}

[[rock3 | ROCK 3]] > [[rock3/CM3 | Compute Module 3]] > [[Rock3/CM3/IO | Radxa CM3 IO Board]] > [[Rock3/CM3/IO/pinout | Pinout]]

__TOC__

[[File:Cm3_io_label.jpg | 1200px]]

== LCD1 & LCD2 ==

* LCD1: MIPI DSI0 or LVDS
* LCD2: MIPI DSI1

{| class="wikitable"
|-
! Pin
! Name
|-
| 1
| VCC_LEDA2
|-
| 2
| VCC_LEDA2
|-
| 3
| VCC_LEDA2
|-
| 4
| NC
|-
| 5
| VCC_LEDK2
|-
| 6
| VCC_LEDK2
|-
| 7
| VCC_LEDK2
|-
| 8
| VCC_LEDK2
|-
| 9
| GND
|-
| 10
| GND
|-
| 11
| MIPI_DSI_TX_D2P
|-
| 12
| MIPI_DSI_TX_D2N
|-
| 13
| GND
|-
| 14
| MIPI_DSI_TX_D1P
|-
| 15
| MIPI_DSI_TX_D1N
|-
| 16
| GND
|-
| 17
| MIPI_DSI_TX_CLKP
|-
| 18
| MIPI_DSI_TX_CLKN
|-
| 19
| GND
|-
| 20
| MIPI_DSI_TX_D0P
|-
| 21
| MIPI_DSI_TX_D0N
|-
| 22
| GND
|-
| 23
| MIPI_DSI_TX_D3P
|-
| 24
| MIPI_DSI_TX_D3N
|-
| 25
| GND
|-
| 26
| NC
|-
| 27
| RESET
|-
| 28
| GND
|-
| 29
| VCC_1V8
|-
| 30
| VCC_LCD_MIPI
|-
| 31
| VCC_LCD_MIPI
|}

== J11 ==

* eDP 40P

{| class="wikitable"
|-
! Pin
! Name
|-
| 1
| NC
|-
| 2
| GND
|-
| 3
| EDP_TX_D3N
|-
| 4
| EDP_TX_D3P
|-
| 5
| GND
|-
| 6
| EDP_TX_D2N
|-
| 7
| EDP_TX_D2P
|-
| 8
| GND
|-
| 9
| EDP_TX_D1N
|-
| 10
| EDP_TX_D1P
|-
| 11
| GND
|-
| 12
| EDP_TX_D0N
|-
| 13
| EDP_TX_D0P
|-
| 14
| GND
|-
| 15
| EDPTX_AUXP
|-
| 16
| EDPTX_AUXN
|-
| 17
| GND
|-
| 18
| VCC3V3_LCD
|-
| 19
| VCC3V3_LCD
|-
| 20
| VCC3V3_LCD
|-
| 21
| VCC3V3_LCD
|-
| 22
| NC
|-
| 23
| GND
|-
| 24
| GND
|-
| 25
| GND
|-
| 26
| GND
|-
| 27
| NC
|-
| 28
| GND
|-
| 29
| GND
|-
| 30
| GND
|-
| 31
| GND
|-
| 32
| LCD0_BL_EN
|-
| 33
| LCD0_BL_PWM5
|-
| 34
| NC
|-
| 35
| NC
|-
| 36
| VCC12V_LCD
|-
| 37
| VCC12V_LCD
|-
| 38
| VCC12V_LCD
|-
| 39
| VCC12V_LCD
|-
| 40
| NC
|-
| 41
| NC
|-
| 42
| NC
|}

== J12 & J13==

* Touch Panel
{| class="wikitable"
|-
! Pin
! Name
|-
| 1
| GND
|-
| 2
| SCL_3V3
|-
| 3
| SDA_3V3
|-
| 4
| INT_3V3
|-
| 5
| RST_3V3
|-
| 6
| VCC_TP
|}

== J14 & J15==

* 2x MIPI CSI

{| class="wikitable"
|-
! Pin
! Name
|-
| 1
| RESET
|-
| 2
| PWDN
|-
| 3
| CAM_CLKOUT
|-
| 4
| GND
|-
| 5
| I2C_SCL
|-
| 6
| I2C_SDA
|-
| 7
| NC
|-
| 8
| 1V2
|-
| 9
| NC
|-
| 10
| 2V8
|-
| 11
| 1V8
|-
| 12
| GND
|-
| 13
| MIPI_CSI_RX_D0P
|-
| 14
| MIPI_CSI_RX_D0N
|-
| 15
| NC
|-
| 16
| MIPI_CSI_RX_D1P
|-
| 17
| MIPI_CSI_RX_D1N
|-
| 18
| GND
|-
| 19
| MIPI_CSI_RX_CLK0P
|-
| 20
| MIPI_CSI_RX_CLK0N
|-
| 21
| GND
|-
| 22
| NC
|-
| 23
| NC
|-
| 24
| GND
|-
| 25
| NC
|-
| 26
| NC
|}

== U26 ==

{| class="wikitable" style="vertical-align:middle; background-color:#F9F9F9;"
|- style="font-weight:bold; text-align:center; background-color:#F2F2F2;"
! Pin
! Name
|-
| 1
| GND
|-
| 2
| 12V
|-
| 3
| 3.3V
|-
| 4
| PWM
|}

== U31 ==
{| class="wikitable"
|-
! Name
! Number
|-
| PWRON_KEY
| 1
|-
| GND
| 2
|-
| RUN_PG(NC)
| 3
|}

== U32==
{| class="wikitable"
|-
! Name
! Number
|-
| PWRON_KEY
| 1
|-
| GND
| 2
|-
| RUN_PG(NC)
| 3
|}

== J9==

== J10 ==

== U36 ==
{| class="wikitable"
|-
! Name
! Number
|-
| 5V0_USB30
| 1
|-
| USB2_HOST3_DM
| 2
|-
| USB2_HOST3_DP
| 3
|-
| GND
| 4
|}
== U30 ==
{| class="wikitable"
|- style="font-weight:bold; background-color:#F2F2F2;"
! Name
! Number
|- style="background-color:#F9F9F9;"
| GND
| 1
|- style="background-color:#F9F9F9;"
| NRPIBOOT(NC)
| 2
|- style="background-color:#F9F9F9;"
| GND
| 3
|- style="background-color:#F9F9F9;"
| EEPROM_NWP
| 4
|-
| AIN0(NC)
| 5
|-
| AIN1(NC)
| 6
|-
| GND
| 7
|-
| SYNC_IN(NC)
| 8
|-
| SYNC_OUT(NC)
| 9
|-
| GND
| 10
|-
| TV_OUT(NC)
| 11
|-
| GND
| 12
|-
| RUN_PG(NC)
| 13
|-
| PWRON_KEY
| 14
|}
== J18 ==
{| class="wikitable"
|-
! Name
! Number
|-
| VCC5V0_USB2
| 1
|-
| VCC5V0_USB2
| 2
|-
| USB3_DM
| 3
|-
| USB4_DM
| 4
|-
| USB3_DP
| 5
|-
| USB4_DP
| 6
|-
| GND
| 7
|-
| GND
| 8
|-
| NC
| 9
|-
| NC
| 10
|}
== U28 ==

== CON1 ==

* [[Rock3/CM3/IO/GPIO | Radxa CM3 IO 40-pin Header GPIO]]

File:Cm3 io label.jpg

2023-06-13T03:20:45Z

Maycides: Maycides uploaded a new version of "File:Cm3 io label.jpg"

Rock3/CM3/IO/pinout

2023-06-13T03:16:21Z

Maycides: /* U31 */

{{rock3_header}}
{{Languages|rock3/cm3/IO/pinout}}

[[rock3 | ROCK 3]] > [[rock3/CM3 | Compute Module 3]] > [[Rock3/CM3/IO | Radxa CM3 IO Board]] > [[Rock3/CM3/IO/pinout | Pinout]]

__TOC__

[[File:Cm3_io_label.jpg | 1200px]]

== LCD1 & LCD2 ==

* LCD1: MIPI DSI0 or LVDS
* LCD2: MIPI DSI1

{| class="wikitable"
|-
! Pin
! Name
|-
| 1
| VCC_LEDA2
|-
| 2
| VCC_LEDA2
|-
| 3
| VCC_LEDA2
|-
| 4
| NC
|-
| 5
| VCC_LEDK2
|-
| 6
| VCC_LEDK2
|-
| 7
| VCC_LEDK2
|-
| 8
| VCC_LEDK2
|-
| 9
| GND
|-
| 10
| GND
|-
| 11
| MIPI_DSI_TX_D2P
|-
| 12
| MIPI_DSI_TX_D2N
|-
| 13
| GND
|-
| 14
| MIPI_DSI_TX_D1P
|-
| 15
| MIPI_DSI_TX_D1N
|-
| 16
| GND
|-
| 17
| MIPI_DSI_TX_CLKP
|-
| 18
| MIPI_DSI_TX_CLKN
|-
| 19
| GND
|-
| 20
| MIPI_DSI_TX_D0P
|-
| 21
| MIPI_DSI_TX_D0N
|-
| 22
| GND
|-
| 23
| MIPI_DSI_TX_D3P
|-
| 24
| MIPI_DSI_TX_D3N
|-
| 25
| GND
|-
| 26
| NC
|-
| 27
| RESET
|-
| 28
| GND
|-
| 29
| VCC_1V8
|-
| 30
| VCC_LCD_MIPI
|-
| 31
| VCC_LCD_MIPI
|}

== J11 ==

* eDP 40P

{| class="wikitable"
|-
! Pin
! Name
|-
| 1
| NC
|-
| 2
| GND
|-
| 3
| EDP_TX_D3N
|-
| 4
| EDP_TX_D3P
|-
| 5
| GND
|-
| 6
| EDP_TX_D2N
|-
| 7
| EDP_TX_D2P
|-
| 8
| GND
|-
| 9
| EDP_TX_D1N
|-
| 10
| EDP_TX_D1P
|-
| 11
| GND
|-
| 12
| EDP_TX_D0N
|-
| 13
| EDP_TX_D0P
|-
| 14
| GND
|-
| 15
| EDPTX_AUXP
|-
| 16
| EDPTX_AUXN
|-
| 17
| GND
|-
| 18
| VCC3V3_LCD
|-
| 19
| VCC3V3_LCD
|-
| 20
| VCC3V3_LCD
|-
| 21
| VCC3V3_LCD
|-
| 22
| NC
|-
| 23
| GND
|-
| 24
| GND
|-
| 25
| GND
|-
| 26
| GND
|-
| 27
| NC
|-
| 28
| GND
|-
| 29
| GND
|-
| 30
| GND
|-
| 31
| GND
|-
| 32
| LCD0_BL_EN
|-
| 33
| LCD0_BL_PWM5
|-
| 34
| NC
|-
| 35
| NC
|-
| 36
| VCC12V_LCD
|-
| 37
| VCC12V_LCD
|-
| 38
| VCC12V_LCD
|-
| 39
| VCC12V_LCD
|-
| 40
| NC
|-
| 41
| NC
|-
| 42
| NC
|}

== J12 & J13==

* Touch Panel
{| class="wikitable"
|-
! Pin
! Name
|-
| 1
| GND
|-
| 2
| SCL_3V3
|-
| 3
| SDA_3V3
|-
| 4
| INT_3V3
|-
| 5
| RST_3V3
|-
| 6
| VCC_TP
|}

== J14 & J15==

* 2x MIPI CSI

{| class="wikitable"
|-
! Pin
! Name
|-
| 1
| RESET
|-
| 2
| PWDN
|-
| 3
| CAM_CLKOUT
|-
| 4
| GND
|-
| 5
| I2C_SCL
|-
| 6
| I2C_SDA
|-
| 7
| NC
|-
| 8
| 1V2
|-
| 9
| NC
|-
| 10
| 2V8
|-
| 11
| 1V8
|-
| 12
| GND
|-
| 13
| MIPI_CSI_RX_D0P
|-
| 14
| MIPI_CSI_RX_D0N
|-
| 15
| NC
|-
| 16
| MIPI_CSI_RX_D1P
|-
| 17
| MIPI_CSI_RX_D1N
|-
| 18
| GND
|-
| 19
| MIPI_CSI_RX_CLK0P
|-
| 20
| MIPI_CSI_RX_CLK0N
|-
| 21
| GND
|-
| 22
| NC
|-
| 23
| NC
|-
| 24
| GND
|-
| 25
| NC
|-
| 26
| NC
|}

== U26 ==

{| class="wikitable" style="vertical-align:middle; background-color:#F9F9F9;"
|- style="font-weight:bold; text-align:center; background-color:#F2F2F2;"
! Pin
! Name
|-
| 1
| GND
|-
| 2
| 12V
|-
| 3
| 3.3V
|-
| 4
| PWM
|}

== U31 ==
{| class="wikitable"
|-
! Name
! Number
|-
| PWRON_KEY
| 1
|-
| GND
| 2
|-
| RUN_PG(NC)
| 3
|}

== U32==
{| class="wikitable"
|-
! Name
! Number
|-
| WL_nDis
| 1
|-
| GND
| 2
|-
| BT_nDis
| 3
|}

== J9==

== J10 ==

== U36 ==
{| class="wikitable"
|-
! Name
! Number
|-
| 5V0_USB30
| 1
|-
| USB2_HOST3_DM
| 2
|-
| USB2_HOST3_DP
| 3
|-
| GND
| 4
|}
== U30 ==
{| class="wikitable"
|- style="font-weight:bold; background-color:#F2F2F2;"
! Name
! Number
|- style="background-color:#F9F9F9;"
| GND
| 1
|- style="background-color:#F9F9F9;"
| NRPIBOOT(NC)
| 2
|- style="background-color:#F9F9F9;"
| GND
| 3
|- style="background-color:#F9F9F9;"
| EEPROM_NWP
| 4
|-
| AIN0(NC)
| 5
|-
| AIN1(NC)
| 6
|-
| GND
| 7
|-
| SYNC_IN(NC)
| 8
|-
| SYNC_OUT(NC)
| 9
|-
| GND
| 10
|-
| TV_OUT(NC)
| 11
|-
| GND
| 12
|-
| RUN_PG(NC)
| 13
|-
| PWRON_KEY
| 14
|}
== J18 ==
{| class="wikitable"
|-
! Name
! Number
|-
| VCC5V0_USB2
| 1
|-
| VCC5V0_USB2
| 2
|-
| USB3_DM
| 3
|-
| USB4_DM
| 4
|-
| USB3_DP
| 5
|-
| USB4_DP
| 6
|-
| GND
| 7
|-
| GND
| 8
|-
| NC
| 9
|-
| NC
| 10
|}
== U28 ==

== CON1 ==

* [[Rock3/CM3/IO/GPIO | Radxa CM3 IO 40-pin Header GPIO]]

Rock3/CM3/IO/pinout

2023-06-13T03:16:17Z

Maycides: /* U32 */

{{rock3_header}}
{{Languages|rock3/cm3/IO/pinout}}

[[rock3 | ROCK 3]] > [[rock3/CM3 | Compute Module 3]] > [[Rock3/CM3/IO | Radxa CM3 IO Board]] > [[Rock3/CM3/IO/pinout | Pinout]]

__TOC__

[[File:Cm3_io_label.jpg | 1200px]]

== LCD1 & LCD2 ==

* LCD1: MIPI DSI0 or LVDS
* LCD2: MIPI DSI1

{| class="wikitable"
|-
! Pin
! Name
|-
| 1
| VCC_LEDA2
|-
| 2
| VCC_LEDA2
|-
| 3
| VCC_LEDA2
|-
| 4
| NC
|-
| 5
| VCC_LEDK2
|-
| 6
| VCC_LEDK2
|-
| 7
| VCC_LEDK2
|-
| 8
| VCC_LEDK2
|-
| 9
| GND
|-
| 10
| GND
|-
| 11
| MIPI_DSI_TX_D2P
|-
| 12
| MIPI_DSI_TX_D2N
|-
| 13
| GND
|-
| 14
| MIPI_DSI_TX_D1P
|-
| 15
| MIPI_DSI_TX_D1N
|-
| 16
| GND
|-
| 17
| MIPI_DSI_TX_CLKP
|-
| 18
| MIPI_DSI_TX_CLKN
|-
| 19
| GND
|-
| 20
| MIPI_DSI_TX_D0P
|-
| 21
| MIPI_DSI_TX_D0N
|-
| 22
| GND
|-
| 23
| MIPI_DSI_TX_D3P
|-
| 24
| MIPI_DSI_TX_D3N
|-
| 25
| GND
|-
| 26
| NC
|-
| 27
| RESET
|-
| 28
| GND
|-
| 29
| VCC_1V8
|-
| 30
| VCC_LCD_MIPI
|-
| 31
| VCC_LCD_MIPI
|}

== J11 ==

* eDP 40P

{| class="wikitable"
|-
! Pin
! Name
|-
| 1
| NC
|-
| 2
| GND
|-
| 3
| EDP_TX_D3N
|-
| 4
| EDP_TX_D3P
|-
| 5
| GND
|-
| 6
| EDP_TX_D2N
|-
| 7
| EDP_TX_D2P
|-
| 8
| GND
|-
| 9
| EDP_TX_D1N
|-
| 10
| EDP_TX_D1P
|-
| 11
| GND
|-
| 12
| EDP_TX_D0N
|-
| 13
| EDP_TX_D0P
|-
| 14
| GND
|-
| 15
| EDPTX_AUXP
|-
| 16
| EDPTX_AUXN
|-
| 17
| GND
|-
| 18
| VCC3V3_LCD
|-
| 19
| VCC3V3_LCD
|-
| 20
| VCC3V3_LCD
|-
| 21
| VCC3V3_LCD
|-
| 22
| NC
|-
| 23
| GND
|-
| 24
| GND
|-
| 25
| GND
|-
| 26
| GND
|-
| 27
| NC
|-
| 28
| GND
|-
| 29
| GND
|-
| 30
| GND
|-
| 31
| GND
|-
| 32
| LCD0_BL_EN
|-
| 33
| LCD0_BL_PWM5
|-
| 34
| NC
|-
| 35
| NC
|-
| 36
| VCC12V_LCD
|-
| 37
| VCC12V_LCD
|-
| 38
| VCC12V_LCD
|-
| 39
| VCC12V_LCD
|-
| 40
| NC
|-
| 41
| NC
|-
| 42
| NC
|}

== J12 & J13==

* Touch Panel
{| class="wikitable"
|-
! Pin
! Name
|-
| 1
| GND
|-
| 2
| SCL_3V3
|-
| 3
| SDA_3V3
|-
| 4
| INT_3V3
|-
| 5
| RST_3V3
|-
| 6
| VCC_TP
|}

== J14 & J15==

* 2x MIPI CSI

{| class="wikitable"
|-
! Pin
! Name
|-
| 1
| RESET
|-
| 2
| PWDN
|-
| 3
| CAM_CLKOUT
|-
| 4
| GND
|-
| 5
| I2C_SCL
|-
| 6
| I2C_SDA
|-
| 7
| NC
|-
| 8
| 1V2
|-
| 9
| NC
|-
| 10
| 2V8
|-
| 11
| 1V8
|-
| 12
| GND
|-
| 13
| MIPI_CSI_RX_D0P
|-
| 14
| MIPI_CSI_RX_D0N
|-
| 15
| NC
|-
| 16
| MIPI_CSI_RX_D1P
|-
| 17
| MIPI_CSI_RX_D1N
|-
| 18
| GND
|-
| 19
| MIPI_CSI_RX_CLK0P
|-
| 20
| MIPI_CSI_RX_CLK0N
|-
| 21
| GND
|-
| 22
| NC
|-
| 23
| NC
|-
| 24
| GND
|-
| 25
| NC
|-
| 26
| NC
|}

== U26 ==

{| class="wikitable" style="vertical-align:middle; background-color:#F9F9F9;"
|- style="font-weight:bold; text-align:center; background-color:#F2F2F2;"
! Pin
! Name
|-
| 1
| GND
|-
| 2
| 12V
|-
| 3
| 3.3V
|-
| 4
| PWM
|}

== U31 ==
{| class="wikitable"
|-
! Name
! Number
|-
| WL_nDis
| 1
|-
| GND
| 2
|-
| BT_nDis
| 3
|}
== U32==
{| class="wikitable"
|-
! Name
! Number
|-
| WL_nDis
| 1
|-
| GND
| 2
|-
| BT_nDis
| 3
|}

== J9==

== J10 ==

== U36 ==
{| class="wikitable"
|-
! Name
! Number
|-
| 5V0_USB30
| 1
|-
| USB2_HOST3_DM
| 2
|-
| USB2_HOST3_DP
| 3
|-
| GND
| 4
|}
== U30 ==
{| class="wikitable"
|- style="font-weight:bold; background-color:#F2F2F2;"
! Name
! Number
|- style="background-color:#F9F9F9;"
| GND
| 1
|- style="background-color:#F9F9F9;"
| NRPIBOOT(NC)
| 2
|- style="background-color:#F9F9F9;"
| GND
| 3
|- style="background-color:#F9F9F9;"
| EEPROM_NWP
| 4
|-
| AIN0(NC)
| 5
|-
| AIN1(NC)
| 6
|-
| GND
| 7
|-
| SYNC_IN(NC)
| 8
|-
| SYNC_OUT(NC)
| 9
|-
| GND
| 10
|-
| TV_OUT(NC)
| 11
|-
| GND
| 12
|-
| RUN_PG(NC)
| 13
|-
| PWRON_KEY
| 14
|}
== J18 ==
{| class="wikitable"
|-
! Name
! Number
|-
| VCC5V0_USB2
| 1
|-
| VCC5V0_USB2
| 2
|-
| USB3_DM
| 3
|-
| USB4_DM
| 4
|-
| USB3_DP
| 5
|-
| USB4_DP
| 6
|-
| GND
| 7
|-
| GND
| 8
|-
| NC
| 9
|-
| NC
| 10
|}
== U28 ==

== CON1 ==

* [[Rock3/CM3/IO/GPIO | Radxa CM3 IO 40-pin Header GPIO]]

File:Cm3 io label.jpg

2023-06-13T03:13:54Z

Maycides: Maycides uploaded a new version of "File:Cm3 io label.jpg"

File:Cm3 io label.jpg

2023-06-12T10:11:59Z

Maycides: Maycides uploaded a new version of "File:Cm3 io label.jpg"

Rock3/3c

2023-06-08T06:10:04Z

Maycides:

{{rock3_header}}

{{Languages|rock3/3c}}

__NOTOC__

<div class="col-md-12 ">
<div class="col-md-8 ">

= ROCK 3 Model C=
This is the documentation for ROCK 3 Model C, written by Radxa Team with community contributions.

ROCK 3C features a quad core Cortex-A55 ARM processor, 32bit 3200Mb/s LPDDR4, up to 4K@60 HDMI, MIPI DSI, MIPI CSI, 3.5mm jack with mic, USB Port, GbE LAN, PCIe 2.0, 40-pin color expansion header.

=== Close look of ROCK 3C ===

[[File:Rock3C_top_800px.png | 400px]][[File:Rock3C_bottom_800px.png|400px]]

=== <span id="get_start_specs"></span> Features ===

{| class="wikitable"
! Model
! colspan="1" width=80% | ROCK 3 Model C
|-
!SoC<br><br>CPU<br>GPU
| colspan="2" | '''RK3566''' <br><br>Quad-core Cortex-A55, frequency 1.6Ghz<br>
Mali G52<br>
|-
! Memory
| colspan="2" | 1/2/4GB LPDDR4 2112MT/s
|-
! Storage
| colspan="2" | eMMC<br>μSD card (μSD slot supports up to 128 GB μSD card)<br />M.2 2230 SSD (M.2 connector supports up to 1TB M2 NVME SSD)
|-
! Display
| colspan="2" | HDMI 2.0 up to 1920x1080 60p<br />MIPI DSI 2 lanes via FPC connector<br />HDMI and MIPI DSI can not work at the same time
|-
! Audio
| colspan="2" | 3.5mm jack with mic<br />HD codec that supports up to 24-bit/96KHz audio.
|-
! Camera
| colspan="2" | MIPI CSI 2 lanes via FPC connector, support up to 800 MP camera.
|-
! Wireless
| colspan="2" | 802.11 ac WiFi 5/ BT 5
|-
! USB
| colspan="2" | USB 2.0 OTG X1(middle upper one), hardware switch for host/device switch<br />USB 3.0 HOST X1<br />USB 2.0 HOST X2
|-
! Ethernet
| colspan="2" | GbE LAN with Power over Ethernet (PoE) support<br />additional HAT is required for powering from PoE
|-
! IO
| colspan="2" | 40-pin expansion header<br />5 x UART<br />1 x SPI bus<br />2 x I2C bus<br />6 x PWM<br />1 x ADC<br /> 6 x GPIO<br />2 x 5V DC power in<br />1 x 3.3V DC power in
|-
! Others
| colspan="2" | RTC<br />RTC battery connector for time backup(optional)
|-
! Power
| colspan="2" | USB type C 5V, 5V/3A is suggested when using without SSD, 5V/5A is suggested when using with SSD.
|-
! Size
| colspan="2" | 85mm x 56mm
|}

=== Getting start guide ===

Follow the [[Rock3/getting_started/rock-3c | Guide]] to start using your ROCK 3C.

=== Use Radxa Debian ===

Follow the [[Rock3/Debian | Radxa Debian Guide]]

=== Download and install third party OS ===

Find [[Rock3/downloads | more OS]] by the Radxa friends and the community.

=== Find supported accessories ===

Discover the [[Rock3/hardware#accessories | accessories]] that just work on ROCK 3A

=== Learn more about the hardware details ===

Learn more about the ROCK 3A [[Rock3/hardware/3a | connectors and pinout]]

Check the [[Rock3/hardware#datasheet | data sheets]] of the components used on ROCK 3C.

</div> 

<div class="col-md-4 ">

<div class="thumbnail ">[[File:Start_3c.png | 440px]]</div>

<div class="panel panel-hearts-white">
<div class="panel-heading"> <h3 class="panel-title"><i class="fa fa-hand-o-up"></i>[[rock3/getting_started | Setup/Quick start ]]</h3> </div>
<div class="panel-body">
* [[rock3/getting_started/rock-3c | Getting started with ROCK 3C]], including what you need and how to get it booted.
* [[rock3/hardware/3c/gpio | ROCK 3C GPIO pinout]]
</div>
</div> 

<div class="panel panel-mango-white">
<div class="panel-heading"> <h3 class="panel-title"><i class="fa fa-star"></i> [[community_updates | What's new]]</h3> </div>
<div class="panel-body">
{{Community_updates}}
</div>
</div> 

<div class="panel panel-cocktail-white">
<div class="panel-heading"><h3 class="panel-title"><i class="fa fa-users"></i> Community</h3></div>
<div class="panel-body">
* Forum: http://forum.radxa.com
* Discord: https://rock.sh/go
* QQ Group: 591048098
* [[Rockpi4/contribute | How to contribute to this wiki, refer ROCK Pi 4 contribution page]]
</div>
</div> 

</div> 

</div>