https://www.vividunit.com:443/api.php?action=feedcontributions&feedformat=atom&user=AdminVivid Unit - User contributions [en]2026-04-29T07:01:12ZUser contributionsMediaWiki 1.41.0https://www.vividunit.com:443/index.php?title=download-system-image&diff=768download-system-image2026-04-28T08:45:22Z<p>Admin: /* Vivid Unit OS */</p>
<hr />
<div>= Download OS Images =<br />
Vivid Unit comes with Debian operating system pre-installed, usually you don't need to install system by yourself.<br />
<br />
However if you want to re-install the system, or want to install a different system (if available), you can download the system disk image here.<br />
= Vivid Unit OS =<br />
[[File:vuos-desktop.png|alt=Debian 12 @ Vivid Unit|thumb|Vivid Unit OS Desktop Preview]]<br />
'''Vivid Unit OS (Debian 12 - Bookworm): version 20260428'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vuos-debian12-20260428-vivid-unit.img.xz vuos-debian12-20260428-vivid-unit.img.xz (398MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: 26ebee1ebb7b2c045083d357e3c1d975''<br />
<br />
''SHA1: b0b7cc9924f37204727235a5fafe2de7b8580a27''<br />
<br />
Build system on GitHub: <br />
<br />
https://github.com/uugear/vivid-unit-os/releases/tag/20260428<br />
<br />
</blockquote><br />
<br />
= Older Versions of System =<br />
[[File:debian11 preview.jpg|alt=Debian 11 @ Vivid Unit|thumb|Desktop Preview|right]]<br />
'''Debian GNU/Linux 11 (bullseye)'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-20240129.img.xz vivid-unit-v13-debian11-20240129.img.xz (933 MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: b66ab31e21bec94ff5a1d0f98b54716b''<br />
<br />
''SHA1: 0f2be8a9670585808909da65c67e02869ad7c859''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
[[File:Debian11 Retropie preview.jpg|thumb|RetroPie Preview|alt=RetroPie on Vivid Unit]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://retropie.org.uk/ RetroPie] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-retropie-20240129.img.xz vivid-unit-v13-debian11-retropie-20240129.img.xz (1.06 GB)]<br />
<br />
<blockquote><br />
<br />
''MD5: 86dd3cd81e1474880b455dfc41b23792''<br />
<br />
''SHA1: cc1df6a419a53c6fb3b4b1d6b9e5417e759e20c8''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
<br />
[[File:Home Assistant Preview.jpg|thumb|alt=Home Assistant on Vivid Unit|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/ Home Assistant (Docker)] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-20240320.img.xz vivid-unit-v13-debian11-home-assistant-20240320.img.xz (1.39 GB)]<br />
<br />
''MD5: bb19226675b7bab9ff3900fdce0a7ce5''<br />
<br />
''SHA1: 070b4a8030a8924f277e992c76f9830db3fce47c''<br />
<br />
<br />
<br />
<br />
[[File:Home-Assistant-Supervised-Preview.jpg|alt=Home Assistant on Vivid Unit|thumb|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/installation/#advanced-installation-methods Home Assistant Supervised] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz (1.52 GB)]<br />
<br />
''MD5: 776435bdc297958f1a591787a0e48e02''<br />
<br />
''SHA1: 90019ab7b989b6bd2ba1911699d6c2c9a3413d70''<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
You can find more details about how to install system [[install-os|here]].</div>Adminhttps://www.vividunit.com:443/index.php?title=gpio-and-adc&diff=767gpio-and-adc2026-04-26T11:48:42Z<p>Admin: /* GPIO */</p>
<hr />
<div>= '''GPIO and ADC''' =<br />
<br />
== '''What is GPIO?''' ==<br />
GPIO stands for Gerneral Purpose Input/Ouput. It usually refers to a set of pins on your computer’s mainboard or add-on boards. These pins are not designed for any specific purpose, and they can send or receive electrical signals.<br />
<br />
== '''What is ADC?''' ==<br />
ADC stands for analog-to-digital converter. It is a system that converts an analog signal into a digital signal. It can be used to measure voltage and give the numberic result.<br />
<br />
== '''GPIO and ADC on Vivid Unit''' ==<br />
<br />
=== '''GPIO''' ===<br />
Vivid Unit comes with a 40-pin GPIO header, whose pinout is compatible with Raspberry Pi. There are two 5V power pins, two 3.3V power pins and 8 ground pins. The rest are I/O pins and they are all at 3.3V level.<br />
<br />
The GPIOs are provided by RK3399, which has 5 banks (GPIO0 to GPIO4). Each bank has 4 groups (A, B, C and D) and each group has 8 pins (number 0~7). That makes 160 GPIOs in total, but only partial of them are routed to the 40-pin GPIO header.<br />
<br />
<pic src="images/1/16/The_40-pin_header_on_Vivid_Unit.png" width="100%" align="text" caption=""></pic><br />
<br />
'''Remarks:''' in Vivid Unit OS, the SDMMC host is disabled in device tree by default, and hence GPIO4_B0~B5 are initialized as normal GPIO pins.<br />
<br />
The GPIOs are named like these:<br />
<br />
<pic src="images/b/be/vivid_unit_gpio_naming.png" width="100%" align="text" caption=""></pic><br />
<br />
For the simplicity we use a short GPIO name for each GPIO pin. We put the bank number, the group name and the pin number in group together, to make the GPIO name.<br />
<br />
[[File:Gpio short name.png]]<br />
<br />
For example, 2B5 is for GPIO2_B5, and 3C6 is for GPIO3_C6.<br />
<br />
=== '''ADC''' ===<br />
Vivid Unit also provides three 10-bit ADC channels (A0, A3 and A4). RK3399 provides ADC with 1.8V full-scale voltage, and Vivid Unit adds voltage divider and protection circuit (as shown below), to increase the full-scale voltage to 5V. The final resolution is 4.88mV.<br />
<br />
[[File:Adc.png]]<br />
<br />
It is safe to connect A0, A3 or A4 channel to any pin in the 40-pin GPIO header, because they can measure voltage up to 5V. If you want to measure voltage higher than 5V, you will need to implement an additional voltage divider.<br />
<br />
[https://www.instructables.com/Measure-Low-Higher-and-Negative-Voltages-With-Vivi This tutorial] covers how to measure higher or negative voltage with Vivid Unit.<br />
<br />
<br />
== '''VGP Utility''' ==<br />
VGP is an open-sourced application to control or monitor GPIOs and ADC channels on Vivid Unit. It contains two executables, one for command line interface (vgp) and the other for GUI enviroment (vgpw).<br />
<br />
VGP is by default installed into the system. If it is not, you can always install it with:<blockquote><br />
sudo apt update<br />
<br />
sudo apt install vgp<br />
</blockquote><br />
<br />
=== '''VGP in CLI (Command Line Interface)''' ===<br />
<br />
==== '''Overview of 40-Pin''' ====<br />
If you want to get an overview of the GPIOs in the 40-pin header, you can run:<blockquote><br />
vgp list<br />
</blockquote>It will list the GPIO information in a format that similar to the wiringPi:<br />
<br />
[[File:Gpio list-600x523.png]]<br />
<br />
The value and voltage of all ADC channels are also printed at the bottom.<br />
<br />
==== '''List All GPIOs''' ====<br />
If you want to list all GPIOs, even including those pins that are not brought out to the 40-pin header. You can run:<blockquote><br />
vgp all<br />
</blockquote>It will list the name, alternate function, value and mode for all GPIO pins:<br />
<br />
[[File:Gpio all-259x300.jpg]]<br />
<br />
==== '''Get Pin Mode''' ====<br />
If you want to get the current mode of a specifi pin, you can use:<blockquote><br />
vgp mode [pin]<br />
</blockquote>Here [pin] should be replaced with the GPIO name or physical pin number.<br />
<br />
The result could be “IN” or “OUT”.<br />
<br />
==== '''Set Pin Mode''' ====<br />
If you want to set the mode of a specific pin, you can use:<blockquote><br />
vgp mode [pin] [mode]<br />
</blockquote>Here [pin] should be replaced with the GPIO name or physical pin number, and [mode] should be one of these value:<br />
<br />
* IN<br />
* in<br />
* INPUT<br />
* input<br />
* OUT<br />
* out<br />
* OUTPUT<br />
* output<br />
<br />
The “IN”, “in”, “INPUT” and “input” are the same, while the “OUT”, “out”, “OUTPUT” and “output” are the same.<br />
<br />
==== '''Get Pin Alternative Function''' ====<br />
The same physical pin can be configured to different alternative function. A pin can have up to 4 alternative functions (ALT0 ~ ALT3), and ALT0 is the default one. You can get the current alternative function for specific pin with:<blockquote><br />
vgp alt [pin]<br />
</blockquote>Here [pin] should be replaced with the GPIO name or physical pin number.<br />
<br />
The result can be 0, 1, 2 or 3, which means ALT0, ALT1, ALT2, ALT3 accordingly.<br />
<br />
==== '''Set Pin Alternative Function''' ====<br />
You can also set alternative function for specific pin with:<blockquote><br />
vgp alt [pin] [alt]<br />
</blockquote>Here [pin] should be replaced with the GPIO name or physical pin number, and [alt] should be replaced with the alternative function (0, 1, 2 or 3).<br />
<br />
==== '''Get Pin Value''' ====<br />
To get value for given pin, you can use:<blockquote><br />
vgp get [pin]<br />
</blockquote>Here [pin] should be replaced with the GPIO name or physical pin number.<br />
<br />
The result could be 1 (high) or 0 (low).<br />
<br />
==== '''Set Pin Value''' ====<br />
To set value for given pin, you may use:<blockquote><br />
vgp set [pin] [value]<br />
</blockquote>Here [pin] should be replaced with the GPIO name or physical pin number, and [value] should be 1 or 0.<br />
<br />
==== '''Wait for Interrupt''' ====<br />
If you wish to monitor the state of given pin, you may use:<blockquote><br />
vpg wfi [pin] [edge]<br />
</blockquote>Here [pin] should be replaced with the GPIO name or physical pin number, and [edge] should be rising, falling or both.<br />
<br />
This command will block until the state of the pin changes.<br />
<br />
==== '''ADC''' ====<br />
You can read the ADC result at specific chanel with:<blockquote><br />
vpg adc [channel]<br />
</blockquote>Here [channel] should be 0 (for A0), 3 (for A3) or 4 (for A4). The result is a number (0~1023).<br />
<br />
If you want to get voltage value, you may use:<blockquote><br />
vpg adc [channel] v<br />
</blockquote>By adding a lower case letter v as the last argument, this command prints out the voltage value (for example 4.21).<br />
<br />
If you want to print out the voltage value with the unit (V) together, you may use:<blockquote><br />
vgp adc [channel] V<br />
</blockquote>By adding an upper case letter V as the last argument, this command prints out the voltage value with unit (for example 4.21V).<br />
<br />
==== '''Get Help Information''' ====<br />
If you need help during usage, you can run this command to get help information:<blockquote><br />
vgp --help<br />
</blockquote><br />
<br />
=== '''VGP in GUI (Graphical User Interface)''' ===<br />
You may run the GUI version of VGP via the "System" category in Applications Menu.<br />
<br />
[[File:run-vgpw.jpg]]<br />
<br />
You may also run “vgpw” in command line terminal to launch the same GUI application.<br />
<br />
You will see the interface that represents the 40-pin header:<br />
<br />
<pic src="images/a/ad/vgpw-202-1.png" width="100%" align="text" caption=""></pic><br />
<br />
The value of three ADC channels are also listed at the bottom, including the raw values (0~1023) and the voltage values. These values refresh for every second.<br />
<br />
There is a “Flip” button at the bottom right corner, and you can click it to flip the view.<br />
<br />
You can click the mode button for each pin to change its mode or alternative function. The possilbe mode/funtion could be IN, OUT, ALT1, ALT2 or ALT3.<br />
<br />
When the mode is set to OUT, you may click the value button to toggle the pin’s value.<br />
<br />
When the mode is set to IN, its value will get updated automatically when the pin is pulled up or down.</div>Adminhttps://www.vividunit.com:443/index.php?title=install-vuos&diff=766install-vuos2026-04-26T11:32:49Z<p>Admin: </p>
<hr />
<div>__TOC__<br />
<br />
'''Remarks:''' this tutorial is for (re)installing Vivid Unit OS (Debian 12) into Vivid Unit device. If you want to install the old system (Debian 11), please read [[install-os|this page]] instead.<br />
<br />
= (Re)install Vivid Unit OS =<br />
Starting from 27th April in 2026, the Vivid Unit in UUGear's inventory have Vivid Unit OS (Debian 12 with XFCE desktop enviroment) pre-installed in the eMMC.<br />
<br />
Usually you do not need to (re)install operating system by yourself. However if:<br />
<br />
* Your Vivid Unit has old system (Debian 11) and you want new system, or<br />
* The system on your Vivid Unit corrupts, or<br />
* You want to install a different operating system (if available)<br />
<br />
Then you may follow this instructions.<br />
<br />
You may download the OS image from [[download-system-image|this page]]. The downloaded image is an img.xz file, and you need to extract it to get the .img file, which can be flashed into Vivid Unit.<br />
<br />
=== Instructions in Windows ===<br />
In order to flash the OS image into VIvid Unit, you need to put Vivid Unit into MASKROM mode, and your Windows may need extra drivers from Rockchip to recognize your Vivid Unit as a MASKROM device, so it can write data into it via USB.<br />
<br />
You can download and run [[download/tools/DriverAssitant v5.11.zip|this RK Driver Assistant]] to help installing the required Rockchip drivers.<br />
<br />
<pic src="images/1/18/installed_RK_driver.jpg" width="50%" align="text" caption=""></pic><br />
<br />
You can download and run [http://vividunit.com/download/tools/RKDevTool_v3.32.zip the RKDevTool] to flash the OS image into your Vivid Unit.<br />
<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. After releasing both buttons you should see the MASKROM device is detected by RKDevTool. If it doesn't show up, please repeat this step.<br />
<br />
<pic src="images/f/f8/maskrom_and_power_buttons.jpg" width="70%" align="text" caption=""></pic><br />
<br />
Then you can specify the Loader file, which can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here], or found in the RKDevTool package we provided on this page. The Loader's address should be set to 0x00000000.<br />
<br />
You also need to specify the Image file to flash. The Image file is the .img file extracted from the .img.xz file you previously downloaded. The "Storage" of the Image should be set to "EMMC", with address 0x00000000.<br />
<br />
Make sure to tick the checkboxes in the Loader and Image lines, as well as the "Write by Address" checkbox, as shown in the figure below. Click the "Run" button to start flashing.<br />
<br />
[[File:RKDevTool flashing image.png]]<br />
<br />
Logging information will be displayed in the right region of the RKDevTool window, and it shows the progress of flashing as well. Once the flashing is done, you may disconnect your Vivid Unit from your computer.<br />
<br />
[[File:RKDevTool flashing progress.png]]<br />
<br />
After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.<br />
<br />
<br />
=== Instructions for Mac OS X / Linux ===<br />
The RKDevTool only works in Windows, in Mac OS X or Linux, you may use its alternative [https://github.com/rockchip-linux/rkdeveloptool rkdeveloptool] instead.<br />
<br />
In Mac OS X, you may build rkdeveloptool with Homebrew, or download [https://www.vividunit.com/download/tools/rkdeveloptool_MacOSX.zip here]:<br />
brew install automake autoconf libusb pkg-config git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
cp rkdeveloptool /opt/homebrew/bin/<br />
In Linux (Debian or Ubuntu), you may build rkdeveloptool as below:<br />
sudo apt-get update<br />
sudo apt-get install -y libudev-dev libusb-1.0-0-dev dh-autoreconf pkg-config libusb-1.0 build-essential git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
sudo cp rkdeveloptool /usr/local/sbin/<br />
You may confirm rkdeveloptool's version by:<br />
rkdeveloptool --version<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. <br />
<br />
<pic src="images/f/f8/maskrom_and_power_buttons.jpg" width="70%" align="text" caption=""></pic><br />
<br />
After releasing both buttons you should see the MASKROM device get listed with "rkdeveloptool ld" command. If it doesn't show up, please repeat this step.<br />
Work:~ user$ rkdeveloptool ld<br />
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1402 Maskrom<br />
Work:~ user$ <br />
Once you confirm Vivid Unit is detected as MASKROM device, you can load the loader and then flash the image into the device:<br />
Work:~ user$ rkdeveloptool db rk3399_loader_v1.30.130.bin <br />
Downloading bootloader succeeded.<br />
Work:~ user$ rkdeveloptool wl 0x00 vuos-20260327-1.img <br />
Write LBA from file (100%)<br />
Work:~ user$ <br />
The Loader file can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here]. <br />
<br />
The Image file is the .img file extracted from the .img.xz file you previously downloaded. It should be flashed at address 0x00.<br />
<br />
Once the flashing is done, you may disconnect your Vivid Unit from your computer. After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.</div>Adminhttps://www.vividunit.com:443/index.php?title=download-system-image&diff=765download-system-image2026-04-26T09:22:26Z<p>Admin: /* Vivid Unit OS */</p>
<hr />
<div>= Download OS Images =<br />
Vivid Unit comes with Debian operating system pre-installed, usually you don't need to install system by yourself.<br />
<br />
However if you want to re-install the system, or want to install a different system (if available), you can download the system disk image here.<br />
= Vivid Unit OS =<br />
[[File:vuos-desktop.png|alt=Debian 12 @ Vivid Unit|thumb|Vivid Unit OS Desktop Preview]]<br />
'''Vivid Unit OS (Debian 12 - Bookworm): version 20260426'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vuos-debian12-20260426-vivid-unit.img.xz vuos-debian12-20260426-vivid-unit.img.xz (398MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: 67099f2605e3d1b84dc8c32c4f99eb1c''<br />
<br />
''SHA1: 5dcdd85d5e87ea27a665e4f0dcd384a32162dbb3''<br />
<br />
Build system on GitHub: <br />
<br />
https://github.com/uugear/vivid-unit-os/releases/tag/20260426<br />
<br />
</blockquote><br />
<br />
= Older Versions of System =<br />
[[File:debian11 preview.jpg|alt=Debian 11 @ Vivid Unit|thumb|Desktop Preview|right]]<br />
'''Debian GNU/Linux 11 (bullseye)'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-20240129.img.xz vivid-unit-v13-debian11-20240129.img.xz (933 MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: b66ab31e21bec94ff5a1d0f98b54716b''<br />
<br />
''SHA1: 0f2be8a9670585808909da65c67e02869ad7c859''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
[[File:Debian11 Retropie preview.jpg|thumb|RetroPie Preview|alt=RetroPie on Vivid Unit]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://retropie.org.uk/ RetroPie] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-retropie-20240129.img.xz vivid-unit-v13-debian11-retropie-20240129.img.xz (1.06 GB)]<br />
<br />
<blockquote><br />
<br />
''MD5: 86dd3cd81e1474880b455dfc41b23792''<br />
<br />
''SHA1: cc1df6a419a53c6fb3b4b1d6b9e5417e759e20c8''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
<br />
[[File:Home Assistant Preview.jpg|thumb|alt=Home Assistant on Vivid Unit|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/ Home Assistant (Docker)] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-20240320.img.xz vivid-unit-v13-debian11-home-assistant-20240320.img.xz (1.39 GB)]<br />
<br />
''MD5: bb19226675b7bab9ff3900fdce0a7ce5''<br />
<br />
''SHA1: 070b4a8030a8924f277e992c76f9830db3fce47c''<br />
<br />
<br />
<br />
<br />
[[File:Home-Assistant-Supervised-Preview.jpg|alt=Home Assistant on Vivid Unit|thumb|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/installation/#advanced-installation-methods Home Assistant Supervised] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz (1.52 GB)]<br />
<br />
''MD5: 776435bdc297958f1a591787a0e48e02''<br />
<br />
''SHA1: 90019ab7b989b6bd2ba1911699d6c2c9a3413d70''<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
You can find more details about how to install system [[install-os|here]].</div>Adminhttps://www.vividunit.com:443/index.php?title=download-system-image&diff=759download-system-image2026-04-21T07:07:00Z<p>Admin: /* Vivid Unit OS */</p>
<hr />
<div>= Download OS Images =<br />
Vivid Unit comes with Debian operating system pre-installed, usually you don't need to install system by yourself.<br />
<br />
However if you want to re-install the system, or want to install a different system (if available), you can download the system disk image here.<br />
= Vivid Unit OS =<br />
[[File:vuos-desktop.png|alt=Debian 12 @ Vivid Unit|thumb|Vivid Unit OS Desktop Preview]]<br />
'''Vivid Unit OS (Debian 12 - Bookworm): version 20260420'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vuos-debian12-20260420-vivid-unit.img.xz vuos-debian12-20260420-vivid-unit.img.xz (400 MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: 8ea34f0a8752d90e4e3116851563f75a''<br />
<br />
''SHA1: d8987d555a98467141f185dd8a64ded76371c847''<br />
<br />
Build system on GitHub: <br />
<br />
https://github.com/uugear/vivid-unit-os/releases/tag/20260420<br />
<br />
</blockquote><br />
<br />
= Older Versions of System =<br />
[[File:debian11 preview.jpg|alt=Debian 11 @ Vivid Unit|thumb|Desktop Preview|right]]<br />
'''Debian GNU/Linux 11 (bullseye)'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-20240129.img.xz vivid-unit-v13-debian11-20240129.img.xz (933 MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: b66ab31e21bec94ff5a1d0f98b54716b''<br />
<br />
''SHA1: 0f2be8a9670585808909da65c67e02869ad7c859''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
[[File:Debian11 Retropie preview.jpg|thumb|RetroPie Preview|alt=RetroPie on Vivid Unit]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://retropie.org.uk/ RetroPie] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-retropie-20240129.img.xz vivid-unit-v13-debian11-retropie-20240129.img.xz (1.06 GB)]<br />
<br />
<blockquote><br />
<br />
''MD5: 86dd3cd81e1474880b455dfc41b23792''<br />
<br />
''SHA1: cc1df6a419a53c6fb3b4b1d6b9e5417e759e20c8''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
<br />
[[File:Home Assistant Preview.jpg|thumb|alt=Home Assistant on Vivid Unit|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/ Home Assistant (Docker)] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-20240320.img.xz vivid-unit-v13-debian11-home-assistant-20240320.img.xz (1.39 GB)]<br />
<br />
''MD5: bb19226675b7bab9ff3900fdce0a7ce5''<br />
<br />
''SHA1: 070b4a8030a8924f277e992c76f9830db3fce47c''<br />
<br />
<br />
<br />
<br />
[[File:Home-Assistant-Supervised-Preview.jpg|alt=Home Assistant on Vivid Unit|thumb|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/installation/#advanced-installation-methods Home Assistant Supervised] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz (1.52 GB)]<br />
<br />
''MD5: 776435bdc297958f1a591787a0e48e02''<br />
<br />
''SHA1: 90019ab7b989b6bd2ba1911699d6c2c9a3413d70''<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
You can find more details about how to install system [[install-os|here]].</div>Adminhttps://www.vividunit.com:443/index.php?title=download-system-image&diff=758download-system-image2026-04-21T07:06:27Z<p>Admin: /* Vivid Unit OS */ VUOS version 20260420</p>
<hr />
<div>= Download OS Images =<br />
Vivid Unit comes with Debian operating system pre-installed, usually you don't need to install system by yourself.<br />
<br />
However if you want to re-install the system, or want to install a different system (if available), you can download the system disk image here.<br />
= Vivid Unit OS =<br />
[[File:vuos-desktop.png|alt=Debian 12 @ Vivid Unit|thumb|Vivid Unit OS Desktop Preview]]<br />
'''Vivid Unit OS (Debian 12 - Bookworm): version 20260327'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vuos-debian12-20260420-vivid-unit.img.xz vuos-debian12-20260420-vivid-unit.img.xz (400 MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: 8ea34f0a8752d90e4e3116851563f75a''<br />
<br />
''SHA1: d8987d555a98467141f185dd8a64ded76371c847''<br />
<br />
Build system on GitHub: <br />
<br />
https://github.com/uugear/vivid-unit-os/releases/tag/20260420<br />
<br />
</blockquote><br />
<br />
= Older Versions of System =<br />
[[File:debian11 preview.jpg|alt=Debian 11 @ Vivid Unit|thumb|Desktop Preview|right]]<br />
'''Debian GNU/Linux 11 (bullseye)'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-20240129.img.xz vivid-unit-v13-debian11-20240129.img.xz (933 MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: b66ab31e21bec94ff5a1d0f98b54716b''<br />
<br />
''SHA1: 0f2be8a9670585808909da65c67e02869ad7c859''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
[[File:Debian11 Retropie preview.jpg|thumb|RetroPie Preview|alt=RetroPie on Vivid Unit]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://retropie.org.uk/ RetroPie] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-retropie-20240129.img.xz vivid-unit-v13-debian11-retropie-20240129.img.xz (1.06 GB)]<br />
<br />
<blockquote><br />
<br />
''MD5: 86dd3cd81e1474880b455dfc41b23792''<br />
<br />
''SHA1: cc1df6a419a53c6fb3b4b1d6b9e5417e759e20c8''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
<br />
[[File:Home Assistant Preview.jpg|thumb|alt=Home Assistant on Vivid Unit|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/ Home Assistant (Docker)] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-20240320.img.xz vivid-unit-v13-debian11-home-assistant-20240320.img.xz (1.39 GB)]<br />
<br />
''MD5: bb19226675b7bab9ff3900fdce0a7ce5''<br />
<br />
''SHA1: 070b4a8030a8924f277e992c76f9830db3fce47c''<br />
<br />
<br />
<br />
<br />
[[File:Home-Assistant-Supervised-Preview.jpg|alt=Home Assistant on Vivid Unit|thumb|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/installation/#advanced-installation-methods Home Assistant Supervised] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz (1.52 GB)]<br />
<br />
''MD5: 776435bdc297958f1a591787a0e48e02''<br />
<br />
''SHA1: 90019ab7b989b6bd2ba1911699d6c2c9a3413d70''<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
You can find more details about how to install system [[install-os|here]].</div>Adminhttps://www.vividunit.com:443/index.php?title=install-vuos&diff=757install-vuos2026-04-04T09:08:13Z<p>Admin: </p>
<hr />
<div>__TOC__<br />
<br />
'''Remarks:''' this tutorial is for (re)installing Vivid Unit OS (Debian 12) into Vivid Unit device. If you want to install the old system (Debian 11), please read [[install-os|this page]] instead.<br />
<br />
= (Re)install Vivid Unit OS =<br />
Starting from [an undecided date] in 2026, the Vivid Unit in UUGear's inventory have Vivid Unit OS (Debian 12 with XFCE desktop enviroment) pre-installed in the eMMC.<br />
<br />
Usually you do not need to (re)install operating system by yourself. However if:<br />
<br />
* Your Vivid Unit has old system (Debian 11) and you want new system, or<br />
* The system on your Vivid Unit corrupts, or<br />
* You want to install a different operating system (if available)<br />
<br />
Then you may follow this instructions.<br />
<br />
You may download the OS image from [[download-system-image|this page]]. The downloaded image is an img.xz file, and you need to extract it to get the .img file, which can be flashed into Vivid Unit.<br />
<br />
=== Instructions in Windows ===<br />
In order to flash the OS image into VIvid Unit, you need to put Vivid Unit into MASKROM mode, and your Windows may need extra drivers from Rockchip to recognize your Vivid Unit as a MASKROM device, so it can write data into it via USB.<br />
<br />
You can download and run [[download/tools/DriverAssitant v5.11.zip|this RK Driver Assistant]] to help installing the required Rockchip drivers.<br />
<br />
<pic src="images/1/18/installed_RK_driver.jpg" width="50%" align="text" caption=""></pic><br />
<br />
You can download and run [http://vividunit.com/download/tools/RKDevTool_v3.32.zip the RKDevTool] to flash the OS image into your Vivid Unit.<br />
<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. After releasing both buttons you should see the MASKROM device is detected by RKDevTool. If it doesn't show up, please repeat this step.<br />
<br />
<pic src="images/f/f8/maskrom_and_power_buttons.jpg" width="70%" align="text" caption=""></pic><br />
<br />
Then you can specify the Loader file, which can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here], or found in the RKDevTool package we provided on this page. The Loader's address should be set to 0x00000000.<br />
<br />
You also need to specify the Image file to flash. The Image file is the .img file extracted from the .img.xz file you previously downloaded. The "Storage" of the Image should be set to "EMMC", with address 0x00000000.<br />
<br />
Make sure to tick the checkboxes in the Loader and Image lines, as well as the "Write by Address" checkbox, as shown in the figure below. Click the "Run" button to start flashing.<br />
<br />
[[File:RKDevTool flashing image.png]]<br />
<br />
Logging information will be displayed in the right region of the RKDevTool window, and it shows the progress of flashing as well. Once the flashing is done, you may disconnect your Vivid Unit from your computer.<br />
<br />
[[File:RKDevTool flashing progress.png]]<br />
<br />
After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.<br />
<br />
<br />
=== Instructions for Mac OS X / Linux ===<br />
The RKDevTool only works in Windows, in Mac OS X or Linux, you may use its alternative [https://github.com/rockchip-linux/rkdeveloptool rkdeveloptool] instead.<br />
<br />
In Mac OS X, you may build rkdeveloptool with Homebrew, or download [https://www.vividunit.com/download/tools/rkdeveloptool_MacOSX.zip here]:<br />
brew install automake autoconf libusb pkg-config git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
cp rkdeveloptool /opt/homebrew/bin/<br />
In Linux (Debian or Ubuntu), you may build rkdeveloptool as below:<br />
sudo apt-get update<br />
sudo apt-get install -y libudev-dev libusb-1.0-0-dev dh-autoreconf pkg-config libusb-1.0 build-essential git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
sudo cp rkdeveloptool /usr/local/sbin/<br />
You may confirm rkdeveloptool's version by:<br />
rkdeveloptool --version<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. <br />
<br />
<pic src="images/f/f8/maskrom_and_power_buttons.jpg" width="70%" align="text" caption=""></pic><br />
<br />
After releasing both buttons you should see the MASKROM device get listed with "rkdeveloptool ld" command. If it doesn't show up, please repeat this step.<br />
Work:~ user$ rkdeveloptool ld<br />
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1402 Maskrom<br />
Work:~ user$ <br />
Once you confirm Vivid Unit is detected as MASKROM device, you can load the loader and then flash the image into the device:<br />
Work:~ user$ rkdeveloptool db rk3399_loader_v1.30.130.bin <br />
Downloading bootloader succeeded.<br />
Work:~ user$ rkdeveloptool wl 0x00 vuos-20260327-1.img <br />
Write LBA from file (100%)<br />
Work:~ user$ <br />
The Loader file can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here]. <br />
<br />
The Image file is the .img file extracted from the .img.xz file you previously downloaded. It should be flashed at address 0x00.<br />
<br />
Once the flashing is done, you may disconnect your Vivid Unit from your computer. After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.</div>Adminhttps://www.vividunit.com:443/index.php?title=install-vuos&diff=756install-vuos2026-04-03T14:30:18Z<p>Admin: /* (Re)install Vivid Unit OS */</p>
<hr />
<div>__TOC__<br />
<br />
'''Remarks:''' this tutorial is for (re)installing Vivid Unit OS (Debian 12) into Vivid Unit device. If you want to install the old system (Debian 11), please read [[install-os|this page]] instead.<br />
<br />
= (Re)install Vivid Unit OS =<br />
Starting from April 7th, 2026, the Vivid Unit in UUGear's inventory have Vivid Unit OS (Debian 12 with XFCE desktop enviroment) pre-installed in the eMMC.<br />
<br />
Usually you do not need to (re)install operating system by yourself. However if:<br />
<br />
* Your Vivid Unit has old system (Debian 11) and you want new system, or<br />
* The system on your Vivid Unit corrupts, or<br />
* You want to install a different operating system (if available)<br />
<br />
Then you may follow this instructions.<br />
<br />
You may download the OS image from [[download-system-image|this page]]. The downloaded image is an img.xz file, and you need to extract it to get the .img file, which can be flashed into Vivid Unit.<br />
<br />
=== Instructions in Windows ===<br />
In order to flash the OS image into VIvid Unit, you need to put Vivid Unit into MASKROM mode, and your Windows may need extra drivers from Rockchip to recognize your Vivid Unit as a MASKROM device, so it can write data into it via USB.<br />
<br />
You can download and run [[download/tools/DriverAssitant v5.11.zip|this RK Driver Assistant]] to help installing the required Rockchip drivers.<br />
<br />
<pic src="images/1/18/installed_RK_driver.jpg" width="50%" align="text" caption=""></pic><br />
<br />
You can download and run [http://vividunit.com/download/tools/RKDevTool_v3.32.zip the RKDevTool] to flash the OS image into your Vivid Unit.<br />
<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. After releasing both buttons you should see the MASKROM device is detected by RKDevTool. If it doesn't show up, please repeat this step.<br />
<br />
<pic src="images/f/f8/maskrom_and_power_buttons.jpg" width="70%" align="text" caption=""></pic><br />
<br />
Then you can specify the Loader file, which can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here], or found in the RKDevTool package we provided on this page. The Loader's address should be set to 0x00000000.<br />
<br />
You also need to specify the Image file to flash. The Image file is the .img file extracted from the .img.xz file you previously downloaded. The "Storage" of the Image should be set to "EMMC", with address 0x00000000.<br />
<br />
Make sure to tick the checkboxes in the Loader and Image lines, as well as the "Write by Address" checkbox, as shown in the figure below. Click the "Run" button to start flashing.<br />
<br />
[[File:RKDevTool flashing image.png]]<br />
<br />
Logging information will be displayed in the right region of the RKDevTool window, and it shows the progress of flashing as well. Once the flashing is done, you may disconnect your Vivid Unit from your computer.<br />
<br />
[[File:RKDevTool flashing progress.png]]<br />
<br />
After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.<br />
<br />
<br />
=== Instructions for Mac OS X / Linux ===<br />
The RKDevTool only works in Windows, in Mac OS X or Linux, you may use its alternative [https://github.com/rockchip-linux/rkdeveloptool rkdeveloptool] instead.<br />
<br />
In Mac OS X, you may build rkdeveloptool with Homebrew, or download [https://www.vividunit.com/download/tools/rkdeveloptool_MacOSX.zip here]:<br />
brew install automake autoconf libusb pkg-config git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
cp rkdeveloptool /opt/homebrew/bin/<br />
In Linux (Debian or Ubuntu), you may build rkdeveloptool as below:<br />
sudo apt-get update<br />
sudo apt-get install -y libudev-dev libusb-1.0-0-dev dh-autoreconf pkg-config libusb-1.0 build-essential git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
sudo cp rkdeveloptool /usr/local/sbin/<br />
You may confirm rkdeveloptool's version by:<br />
rkdeveloptool --version<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. <br />
<br />
<pic src="images/f/f8/maskrom_and_power_buttons.jpg" width="70%" align="text" caption=""></pic><br />
<br />
After releasing both buttons you should see the MASKROM device get listed with "rkdeveloptool ld" command. If it doesn't show up, please repeat this step.<br />
Work:~ user$ rkdeveloptool ld<br />
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1402 Maskrom<br />
Work:~ user$ <br />
Once you confirm Vivid Unit is detected as MASKROM device, you can load the loader and then flash the image into the device:<br />
Work:~ user$ rkdeveloptool db rk3399_loader_v1.30.130.bin <br />
Downloading bootloader succeeded.<br />
Work:~ user$ rkdeveloptool wl 0x00 vuos-20260327-1.img <br />
Write LBA from file (100%)<br />
Work:~ user$ <br />
The Loader file can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here]. <br />
<br />
The Image file is the .img file extracted from the .img.xz file you previously downloaded. It should be flashed at address 0x00.<br />
<br />
Once the flashing is done, you may disconnect your Vivid Unit from your computer. After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.</div>Adminhttps://www.vividunit.com:443/index.php?title=MediaWiki:Sidebar&diff=755MediaWiki:Sidebar2026-04-03T14:13:08Z<p>Admin: </p>
<hr />
<div>* Buy<br />
** https://www.uugear.com/product/vivid-unit/|from UUGear e-Shop<br />
* Download<br />
** download-system-image|OS Images<br />
** schematic|Schematic<br />
** drawings-models|Drawings and Models<br />
* About ...<br />
** technical-specifications|Technical Specifications<br />
** interfaces|Interfaces<br />
** compliance|Compliance<br />
** gpio-and-adc|GPIO and ADC<br />
** screen-and-touch-buttons|Screen and Touch Buttons<br />
** expansion-addon-board-development|Expansion / Add-on Board Development<br />
* Accessories<br />
** back-panel-kit|Back Panel Kit<br />
** extender|Vivid Unit Extender<br />
** vu-breakout|VU Breakout<br />
** vu-gpsdr|VU GPSDR<br />
* How to ...<br />
** turn-on-off|Turn on/off Vivid Unit<br />
** connect-to-internet|Connect to Internet<br />
** use-virtual-keyboard|Use Virtual Keyboard<br />
** gesture|Use Gesture<br />
** connect-via-ssh|Connect to Vivid Unit via SSH<br />
** connect-via-VNC|Connect to Vivid Unit via VNC<br />
** record-audio|Record Audio<br />
** replay-audio-video|Replay Audio and Video<br />
** install-vuos|(Re)install Vivid Unit OS<br />
** boot-from-nvme|Boot from NVME SSD<br />
** play-retro-games|Play retro games on Vivid Unit<br />
* FAQs<br />
** default-username-password|What is the default username/password?<br />
** gpio-voltage-level|What is the voltage level of GPIO?<br />
** rtc|Is there an RTC on Vivid Unit?<br />
* Support & Help<br />
** https://www.uugear.com/forums/technial-support-discussion/|UUGear Forum: Technial Support / Discussion</div>Adminhttps://www.vividunit.com:443/index.php?title=extender&diff=754extender2026-04-03T14:11:43Z<p>Admin: /* Vivid Unit Extender 2 (2nd generation) */</p>
<hr />
<div>__TOC__<br />
The [https://www.uugear.com/product/vivid-unit-extender-2/ Vivid Unit Extender] is an advanced expansion motherboard for the Vivid Unit, designed to enhance both functionality and versatility. With the same dimensions as the Vivid Unit, the Extender adds essential features like active and passive cooling (VCOOL), additional power management and RTC backup battery etc.<br />
[[File:VCOOL in Extender.png|center|700x700px]]<br />
<br />
Vivid Unit Extender also comes with a Mini PCIe slot for developing custom expansion boards. It is one of the two expansion methods suggested by the [[download/files/VividUnit Expansions Specification.pdf|Vivid Unit Expansions Specification]].<br />
<br />
<pic src="/images/f/f6/VUE_A1.jpg" width="40%" align="text" caption=""></pic><br />
<pic src="/images/d/d0/VU_Extender_2.jpg" width="40%" align="text" caption=""></pic><br />
<br />
Vivid Unit Extender is open-sourced. The firmware and software source code can be found in its GitHub repository. The schematic will be released on Vivid Unit’s website.<br />
<br />
=== '''Key Features''' ===<br />
<br />
* '''Mini PCIe Expansion Slot''': As a true expansion motherboard, the Extender routes all signal lines from the Vivid Unit to a Mini PCIe slot, providing a versatile platform for users to develop custom expansion boards. This slot supports a wide range of applications, from prototyping to final product deployment.<br />
* '''Active and Passive Cooling''': Utilizing the same cooling system (VCOOL) as the Cooler Panel Kit, the Extender is equipped with an integrated fan and configurable cooling strategy. It ensures optimal thermal management, automatically controlling the fan based on real-time temperatures to maintain performance while minimizing noise.<br />
* '''Efficient Power Management''': The Extender provides an additional USB-C power input and a dedicated power button. When the Vivid Unit is shut down, the Extender cuts power to it, reducing idle current from approximately 11-12mA to under 1mA—ideal for conserving power in long-term deployments.<br />
* '''Overvoltage and Undervoltage Protection''': The Extender’s input voltage can withstand up to 30V DC, but its expected normal input voltage is 5V DC (±5%). The Extender continuously monitors input voltage. Based on the readings, it can automatically power down or disconnect to protect the Vivid Unit and attached components. This protection mechanism ensures stability without requiring specialized hardware circuits.<br />
* '''Watchdog Functionality''': Prevent system freezes and ensure reliability with the Extender’s watchdog timer. If the Vivid Unit becomes unresponsive, the watchdog function can trigger a restart, keeping your device running smoothly.<br />
* '''RTC Backup Battery''': An onboard battery maintains the Vivid Unit’s real-time clock (RTC) for 1-2 days, even when the device is completely powered off, depending on the battery’s charge level. This feature helps keep the system clock accurate across power cycles.<br />
<br />
=== '''Technical Specifications''' ===<br />
<br />
* '''Expansion Interface''': Mini PCIe slot for custom board development<br />
* '''Power Input''': 5V DC (±5% expected), withstands up to 30V DC, via USB-C connector or the reserved pads on the PCB<br />
* '''Idle Current''': <1mA in standby mode<br />
* '''Cooling''': Active and passive with automated fan control<br />
* '''Over/Undervoltage Protection''': Configurable tolerance levels<br />
* '''RTC Backup''': Battery backup for RTC, lasting 1-2 days<br />
<br />
=== '''Package Content''' ===<br />
<br />
* Assembled Vivid Unit Extender PCB x 1<br />
* M3 screw x 4<br />
* Plastic 3.2x7x2.5 standoff x 4<br />
* Copper heatsink (with adhesive thermal tape) x 1<br />
* Thermal pad x 1<br />
* M2 screw x 4<br />
* MX1.25 dual head cable x 4<br />
<br />
=== '''Applications''' ===<br />
The Vivid Unit Extender is ideal for developers looking to expand their Vivid Unit’s capabilities, whether through custom hardware solutions or by integrating additional features directly. With comprehensive power management, efficient cooling, and easy expansion options, it’s suitable for applications in embedded development, IoT, industrial control, and more.<br />
<br />
With its robust design and thoughtful feature set, the Vivid Unit Extender offers everything needed to elevate your Vivid Unit setup. Whether you aim to boost performance, manage power more effectively, or protect against system downtime, the Vivid Unit Extender is a reliable and essential upgrade for your projects.<br />
<br />
=== '''Vivid Unit Extender 2 (2nd generation)''' ===<br />
Compared to the first generation, the [https://www.uugear.com/product/vivid-unit-extender-2/ Vivid Unit Extender 2] deploys the CH224K fast charging protocol controller, thus offering better compatibility with various PD/QC chargers (note that it still only negotiates 5V output, as it does not have a built-in DC/DC converter).<br />
<br />
The Vivid Unit Extender 2 uses a 4-wire DC blower to replace the 2-wire DC blower, which allows real-time adjustment and measurement of fan speed. Furthermore, fan noise is significantly reduced.<br />
<br />
[[File:4 wire blower.jpg]]<br />
<br />
The Vivid Unit Extender 2 also adds two screw terminals, making it easier to integrate with external power modules.<br />
<br />
[[File:screw terminals.jpg]]</div>Adminhttps://www.vividunit.com:443/index.php?title=extender&diff=753extender2026-04-03T14:11:10Z<p>Admin: /* Vivid Unit Extender 2 (2nd generation) */</p>
<hr />
<div>__TOC__<br />
The [https://www.uugear.com/product/vivid-unit-extender-2/ Vivid Unit Extender] is an advanced expansion motherboard for the Vivid Unit, designed to enhance both functionality and versatility. With the same dimensions as the Vivid Unit, the Extender adds essential features like active and passive cooling (VCOOL), additional power management and RTC backup battery etc.<br />
[[File:VCOOL in Extender.png|center|700x700px]]<br />
<br />
Vivid Unit Extender also comes with a Mini PCIe slot for developing custom expansion boards. It is one of the two expansion methods suggested by the [[download/files/VividUnit Expansions Specification.pdf|Vivid Unit Expansions Specification]].<br />
<br />
<pic src="/images/f/f6/VUE_A1.jpg" width="40%" align="text" caption=""></pic><br />
<pic src="/images/d/d0/VU_Extender_2.jpg" width="40%" align="text" caption=""></pic><br />
<br />
Vivid Unit Extender is open-sourced. The firmware and software source code can be found in its GitHub repository. The schematic will be released on Vivid Unit’s website.<br />
<br />
=== '''Key Features''' ===<br />
<br />
* '''Mini PCIe Expansion Slot''': As a true expansion motherboard, the Extender routes all signal lines from the Vivid Unit to a Mini PCIe slot, providing a versatile platform for users to develop custom expansion boards. This slot supports a wide range of applications, from prototyping to final product deployment.<br />
* '''Active and Passive Cooling''': Utilizing the same cooling system (VCOOL) as the Cooler Panel Kit, the Extender is equipped with an integrated fan and configurable cooling strategy. It ensures optimal thermal management, automatically controlling the fan based on real-time temperatures to maintain performance while minimizing noise.<br />
* '''Efficient Power Management''': The Extender provides an additional USB-C power input and a dedicated power button. When the Vivid Unit is shut down, the Extender cuts power to it, reducing idle current from approximately 11-12mA to under 1mA—ideal for conserving power in long-term deployments.<br />
* '''Overvoltage and Undervoltage Protection''': The Extender’s input voltage can withstand up to 30V DC, but its expected normal input voltage is 5V DC (±5%). The Extender continuously monitors input voltage. Based on the readings, it can automatically power down or disconnect to protect the Vivid Unit and attached components. This protection mechanism ensures stability without requiring specialized hardware circuits.<br />
* '''Watchdog Functionality''': Prevent system freezes and ensure reliability with the Extender’s watchdog timer. If the Vivid Unit becomes unresponsive, the watchdog function can trigger a restart, keeping your device running smoothly.<br />
* '''RTC Backup Battery''': An onboard battery maintains the Vivid Unit’s real-time clock (RTC) for 1-2 days, even when the device is completely powered off, depending on the battery’s charge level. This feature helps keep the system clock accurate across power cycles.<br />
<br />
=== '''Technical Specifications''' ===<br />
<br />
* '''Expansion Interface''': Mini PCIe slot for custom board development<br />
* '''Power Input''': 5V DC (±5% expected), withstands up to 30V DC, via USB-C connector or the reserved pads on the PCB<br />
* '''Idle Current''': <1mA in standby mode<br />
* '''Cooling''': Active and passive with automated fan control<br />
* '''Over/Undervoltage Protection''': Configurable tolerance levels<br />
* '''RTC Backup''': Battery backup for RTC, lasting 1-2 days<br />
<br />
=== '''Package Content''' ===<br />
<br />
* Assembled Vivid Unit Extender PCB x 1<br />
* M3 screw x 4<br />
* Plastic 3.2x7x2.5 standoff x 4<br />
* Copper heatsink (with adhesive thermal tape) x 1<br />
* Thermal pad x 1<br />
* M2 screw x 4<br />
* MX1.25 dual head cable x 4<br />
<br />
=== '''Applications''' ===<br />
The Vivid Unit Extender is ideal for developers looking to expand their Vivid Unit’s capabilities, whether through custom hardware solutions or by integrating additional features directly. With comprehensive power management, efficient cooling, and easy expansion options, it’s suitable for applications in embedded development, IoT, industrial control, and more.<br />
<br />
With its robust design and thoughtful feature set, the Vivid Unit Extender offers everything needed to elevate your Vivid Unit setup. Whether you aim to boost performance, manage power more effectively, or protect against system downtime, the Vivid Unit Extender is a reliable and essential upgrade for your projects.<br />
<br />
=== '''Vivid Unit Extender 2 (2nd generation)''' ===<br />
Compared to the first generation, the Vivid Unit Extender 2 deploys the CH224K fast charging protocol controller, thus offering better compatibility with various PD/QC chargers (note that it still only negotiates 5V output, as it does not have a built-in DC/DC converter).<br />
<br />
The Vivid Unit Extender 2 uses a 4-wire DC blower to replace the 2-wire DC blower, which allows real-time adjustment and measurement of fan speed. Furthermore, fan noise is significantly reduced.<br />
<br />
[[File:4 wire blower.jpg]]<br />
<br />
The Vivid Unit Extender 2 also adds two screw terminals, making it easier to integrate with external power modules.<br />
<br />
[[File:screw terminals.jpg]]</div>Adminhttps://www.vividunit.com:443/index.php?title=extender&diff=752extender2026-04-03T14:10:35Z<p>Admin: </p>
<hr />
<div>__TOC__<br />
The [https://www.uugear.com/product/vivid-unit-extender-2/ Vivid Unit Extender] is an advanced expansion motherboard for the Vivid Unit, designed to enhance both functionality and versatility. With the same dimensions as the Vivid Unit, the Extender adds essential features like active and passive cooling (VCOOL), additional power management and RTC backup battery etc.<br />
[[File:VCOOL in Extender.png|center|700x700px]]<br />
<br />
Vivid Unit Extender also comes with a Mini PCIe slot for developing custom expansion boards. It is one of the two expansion methods suggested by the [[download/files/VividUnit Expansions Specification.pdf|Vivid Unit Expansions Specification]].<br />
<br />
<pic src="/images/f/f6/VUE_A1.jpg" width="40%" align="text" caption=""></pic><br />
<pic src="/images/d/d0/VU_Extender_2.jpg" width="40%" align="text" caption=""></pic><br />
<br />
Vivid Unit Extender is open-sourced. The firmware and software source code can be found in its GitHub repository. The schematic will be released on Vivid Unit’s website.<br />
<br />
=== '''Key Features''' ===<br />
<br />
* '''Mini PCIe Expansion Slot''': As a true expansion motherboard, the Extender routes all signal lines from the Vivid Unit to a Mini PCIe slot, providing a versatile platform for users to develop custom expansion boards. This slot supports a wide range of applications, from prototyping to final product deployment.<br />
* '''Active and Passive Cooling''': Utilizing the same cooling system (VCOOL) as the Cooler Panel Kit, the Extender is equipped with an integrated fan and configurable cooling strategy. It ensures optimal thermal management, automatically controlling the fan based on real-time temperatures to maintain performance while minimizing noise.<br />
* '''Efficient Power Management''': The Extender provides an additional USB-C power input and a dedicated power button. When the Vivid Unit is shut down, the Extender cuts power to it, reducing idle current from approximately 11-12mA to under 1mA—ideal for conserving power in long-term deployments.<br />
* '''Overvoltage and Undervoltage Protection''': The Extender’s input voltage can withstand up to 30V DC, but its expected normal input voltage is 5V DC (±5%). The Extender continuously monitors input voltage. Based on the readings, it can automatically power down or disconnect to protect the Vivid Unit and attached components. This protection mechanism ensures stability without requiring specialized hardware circuits.<br />
* '''Watchdog Functionality''': Prevent system freezes and ensure reliability with the Extender’s watchdog timer. If the Vivid Unit becomes unresponsive, the watchdog function can trigger a restart, keeping your device running smoothly.<br />
* '''RTC Backup Battery''': An onboard battery maintains the Vivid Unit’s real-time clock (RTC) for 1-2 days, even when the device is completely powered off, depending on the battery’s charge level. This feature helps keep the system clock accurate across power cycles.<br />
<br />
=== '''Technical Specifications''' ===<br />
<br />
* '''Expansion Interface''': Mini PCIe slot for custom board development<br />
* '''Power Input''': 5V DC (±5% expected), withstands up to 30V DC, via USB-C connector or the reserved pads on the PCB<br />
* '''Idle Current''': <1mA in standby mode<br />
* '''Cooling''': Active and passive with automated fan control<br />
* '''Over/Undervoltage Protection''': Configurable tolerance levels<br />
* '''RTC Backup''': Battery backup for RTC, lasting 1-2 days<br />
<br />
=== Package Content ===<br />
<br />
* Assembled Vivid Unit Extender PCB x 1<br />
* M3 screw x 4<br />
* Plastic 3.2x7x2.5 standoff x 4<br />
* Copper heatsink (with adhesive thermal tape) x 1<br />
* Thermal pad x 1<br />
* M2 screw x 4<br />
* MX1.25 dual head cable x 4<br />
<br />
=== '''Applications''' ===<br />
The Vivid Unit Extender is ideal for developers looking to expand their Vivid Unit’s capabilities, whether through custom hardware solutions or by integrating additional features directly. With comprehensive power management, efficient cooling, and easy expansion options, it’s suitable for applications in embedded development, IoT, industrial control, and more.<br />
<br />
With its robust design and thoughtful feature set, the Vivid Unit Extender offers everything needed to elevate your Vivid Unit setup. Whether you aim to boost performance, manage power more effectively, or protect against system downtime, the Vivid Unit Extender is a reliable and essential upgrade for your projects.<br />
<br />
=== Vivid Unit Extender 2 (2nd generation) ===<br />
Compared to the first generation, the Vivid Unit Extender 2 deploys the CH224K fast charging protocol controller, thus offering better compatibility with various PD/QC chargers (note that it still only negotiates 5V output, as it does not have a built-in DC/DC converter).<br />
<br />
The Vivid Unit Extender 2 uses a 4-wire DC blower to replace the 2-wire DC blower, which allows real-time adjustment and measurement of fan speed. Furthermore, fan noise is significantly reduced.<br />
<br />
[[File:4 wire blower.jpg]]<br />
<br />
The Vivid Unit Extender 2 also adds two screw terminals, making it easier to integrate with external power modules.<br />
<br />
[[File:screw terminals.jpg]]</div>Adminhttps://www.vividunit.com:443/index.php?title=File:screw_terminals.jpg&diff=751File:screw terminals.jpg2026-04-03T14:09:09Z<p>Admin: </p>
<hr />
<div>screw terminals</div>Adminhttps://www.vividunit.com:443/index.php?title=File:4_wire_blower.jpg&diff=750File:4 wire blower.jpg2026-04-03T14:08:42Z<p>Admin: </p>
<hr />
<div>4 wire blower</div>Adminhttps://www.vividunit.com:443/index.php?title=replay-audio-video&diff=749replay-audio-video2026-04-03T13:58:08Z<p>Admin: </p>
<hr />
<div>The old system (Debian 11) has SMPlayer pre-installed has its default media player. You can find it in the "Multimedia" category in the application menu.<br />
<br />
[[File:smplayer.jpg|500x500px]]<br />
<br />
The new system (Vivid Unit OS) doesn't have SMPlayer pre-installed, but you can still install it manually:<br />
sudo apt update<br />
sudo apt install smplayer<br />
SMPlayer has very intuitive user interface and it looks just like other media players you use everyday. After loading the audio/video file into the player, you can click the play button to start playing it.<br />
<br />
[[File:smplayer ui.jpg|500x500px]]</div>Adminhttps://www.vividunit.com:443/index.php?title=replay-audio-video&diff=748replay-audio-video2026-04-03T13:57:35Z<p>Admin: </p>
<hr />
<div>The old system (Debian 11) has SMPlayer pre-installed has its default media player. You can find it in the "Multimedia" category in the application menu.<br />
<br />
[[File:smplayer.jpg|500x500px]]<br />
<br />
The new system (Vivid Unit OS) doesn't have SMPlayer pre-installed, and you need to install it manually:<br />
sudo apt update<br />
sudo apt install smplayer<br />
SMPlayer has very intuitive user interface and it looks just like other media players you use everyday. After loading the audio/video file into the player, you can click the play button to start playing it.<br />
<br />
[[File:smplayer ui.jpg|500x500px]]</div>Adminhttps://www.vividunit.com:443/index.php?title=record-audio&diff=747record-audio2026-04-03T13:55:16Z<p>Admin: /* Record Audio */</p>
<hr />
<div>= Record Audio =<br />
Vivid Unit has two on board microphones and it can be used for audio streaming or recording.<br />
<br />
You may use the "Sound Recorder" app to record audio. This application is pre-installed in the old system (Debian 11). In the new system (Vivid Unit OS), it is not pre-installed, but you can still install it manually:<br />
sudo apt update<br />
sudo apt install gnome-sound-recorder<br />
In the application menu, under the “Multimedia” category, you can find “Sound Recorder”. <br />
<br />
[[File:sound recorder.png|500x500px]]<br />
<br />
Just click the blue “Record” button to start the recording:<br />
<br />
[[File:recording.png|500x500px]]<br />
<br />
To stop the recording, you just need to click the red button. You can then save this recording with specified name, and even export the audio file.<br />
<br />
[[File:save recorded audio.png|500x500px]]<br />
<br />
If you find the volume of the recorded .wav file is rather low, you may use the sox tool (already pre-installed in the system) to increase its valume:<br />
<br />
<span style=color:blue>sox -v 5 old.wav new.wav</span><br />
<br />
The example above increase the volume of old.wav file and save it as the new.wav file (the old.wav file itself remains unchanged).</div>Adminhttps://www.vividunit.com:443/index.php?title=use-virtual-keyboard&diff=746use-virtual-keyboard2026-04-03T13:40:06Z<p>Admin: /* Use Virtual Keyboard */</p>
<hr />
<div>= Use Virtual Keyboard =<br />
Vivid Unit doesn’t come with a physical keyboard, but it features a touchscreen display that allows you to input text through a virtual keyboard.<br />
<br />
Vivid Unit already have the virtual keyboard (onboard) pre-installed. To use the virtual keyboard, you can simply tap on the onboard icon located on the taskbar at the bottom of the screen. This will bring up the virtual keyboard, which you can use to type in text just like a physical keyboard. You can also swipe up on touchscreen with two fingers to show it. <br />
<br />
[[File:onboard icon.jpg]]<br />
<br />
When the virtual keyboard is shown, you can switch between letters, numbers, and symbols by tapping the relevant keys on the keyboard. <br />
<br />
[[File:onboard input.jpg|500x500px]]<br />
<br />
To hide the virtual keyboard, simply tap the onboard icon on the taskbar again. You can also swipe down on touchscreen with two fingers to hide it.</div>Adminhttps://www.vividunit.com:443/index.php?title=MediaWiki:Sidebar&diff=745MediaWiki:Sidebar2026-04-03T13:36:53Z<p>Admin: </p>
<hr />
<div>* Buy<br />
** https://www.uugear.com/product/vivid-unit/|from UUGear e-Shop<br />
* Download<br />
** download-system-image|OS Images<br />
** schematic|Schematic<br />
** drawings-models|Drawings and Models<br />
* About ...<br />
** technical-specifications|Technical Specifications<br />
** interfaces|Interfaces<br />
** compliance|Compliance<br />
** gpio-and-adc|GPIO and ADC<br />
** screen-and-touch-buttons|Screen and Touch Buttons<br />
** expansion-addon-board-development|Expansion / Add-on Board Development<br />
* Accessories<br />
** back-panel-kit|Back Panel Kit<br />
** cooler-panel-kit|Cooler Panel Kit<br />
** extender|Vivid Unit Extender<br />
** vu-breakout|VU Breakout<br />
** vu-gpsdr|VU GPSDR<br />
* How to ...<br />
** turn-on-off|Turn on/off Vivid Unit<br />
** connect-to-internet|Connect to Internet<br />
** use-virtual-keyboard|Use Virtual Keyboard<br />
** gesture|Use Gesture<br />
** connect-via-ssh|Connect to Vivid Unit via SSH<br />
** connect-via-VNC|Connect to Vivid Unit via VNC<br />
** record-audio|Record Audio<br />
** replay-audio-video|Replay Audio and Video<br />
** install-vuos|(Re)install Vivid Unit OS<br />
** boot-from-nvme|Boot from NVME SSD<br />
** play-retro-games|Play retro games on Vivid Unit<br />
* FAQs<br />
** default-username-password|What is the default username/password?<br />
** gpio-voltage-level|What is the voltage level of GPIO?<br />
** rtc|Is there an RTC on Vivid Unit?<br />
* Support & Help<br />
** https://www.uugear.com/forums/technial-support-discussion/|UUGear Forum: Technial Support / Discussion</div>Adminhttps://www.vividunit.com:443/index.php?title=gesture&diff=744gesture2026-04-03T13:35:16Z<p>Admin: </p>
<hr />
<div>Vivid Unit OS supports these gesture via the pre-installed application "VSA":<br />
<br />
* '''Single-finger long press:''' Mouse right-click <br />
* '''Single-finger clockwise circle:''' Open the magnifier <br />
* '''Single-finger counter-clockwise circle:''' Close the magnifier <br />
* '''Two-finger swipe up:''' Show the Onboard on-screen keyboard <br />
* '''Two-finger swipe down:''' Hide the Onboard on-screen keyboard <br />
* '''Three-finger tap:''' Toggle local IP address display <br />
* '''Three-finger drag:''' Move the active window</div>Adminhttps://www.vividunit.com:443/index.php?title=right-and-middle-click&diff=743right-and-middle-click2026-04-03T13:30:51Z<p>Admin: </p>
<hr />
<div>'''Remarks:''' this page is for the old system (Debian 11). For the new system (Vivid Unit OS / Debian 12), related information can be found on [[gesture|this page]].<br />
<br />
= Emulate Right/Middle Click on Touchscreen =<br />
<br />
=== Right Click ===<br />
In case you don't connect a mouse to your Vivid Unit, and you want to emulate right click, you may '''tap the touchscreen with two fingers''' at the same time.<br />
<br />
<pic src="images/6/68/vivid_unit_right_click.png" width="70%" align="text" caption=""></pic><br />
<br />
=== Middle Click ===<br />
If you want to emulate middle click, you may '''tap the touchscreen with three fingers''' at the same time.<br />
<br />
<pic src="images/f/f8/vivid_unit_middle_click.png" width="70%" align="text" caption=""></pic></div>Adminhttps://www.vividunit.com:443/index.php?title=gesture&diff=742gesture2026-04-03T13:30:04Z<p>Admin: Created page with "On Vivid Unit OS, gesture support is provided by the pre-installed application "VSA"."</p>
<hr />
<div>On Vivid Unit OS, gesture support is provided by the pre-installed application "VSA".</div>Adminhttps://www.vividunit.com:443/index.php?title=install-vuos&diff=741install-vuos2026-04-03T13:25:01Z<p>Admin: /* Install Vivid Unit OS */</p>
<hr />
<div>__TOC__<br />
<br />
'''Remarks:''' this tutorial is for (re)installing Vivid Unit OS (Debian 12) into Vivid Unit device. If you want to install the old system (Debian 11), please read [[install-os|this page]] instead.<br />
<br />
= (Re)install Vivid Unit OS =<br />
Vivid Unit has eMMC storage onboard and the operating system (Debian with XFCE desktop enviroment) has been pre-installed in the eMMC. Usually you do not need to install operating system by yourself. However if the operating system corrupts or you want to install a different operating system (if available), you may follow this instructions.<br />
<br />
You may download the OS image from [[download-system-image|this page]]. The downloaded image is an img.xz file, and you need to extract it to get the .img file, which can be flashed into Vivid Unit.<br />
<br />
=== Instructions in Windows ===<br />
In order to flash the OS image into VIvid Unit, you need to put Vivid Unit into MASKROM mode, and your Windows may need extra drivers from Rockchip to recognize your Vivid Unit as a MASKROM device, so it can write data into it via USB.<br />
<br />
You can download and run [[download/tools/DriverAssitant v5.11.zip|this RK Driver Assistant]] to help installing the required Rockchip drivers.<br />
<br />
<pic src="images/1/18/installed_RK_driver.jpg" width="50%" align="text" caption=""></pic><br />
<br />
You can download and run [http://vividunit.com/download/tools/RKDevTool_v3.32.zip the RKDevTool] to flash the OS image into your Vivid Unit.<br />
<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. After releasing both buttons you should see the MASKROM device is detected by RKDevTool. If it doesn't show up, please repeat this step.<br />
<br />
<pic src="images/f/f8/maskrom_and_power_buttons.jpg" width="70%" align="text" caption=""></pic><br />
<br />
Then you can specify the Loader file, which can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here], or found in the RKDevTool package we provided on this page. The Loader's address should be set to 0x00000000.<br />
<br />
You also need to specify the Image file to flash. The Image file is the .img file extracted from the .img.xz file you previously downloaded. The "Storage" of the Image should be set to "EMMC", with address 0x00000000.<br />
<br />
Make sure to tick the checkboxes in the Loader and Image lines, as well as the "Write by Address" checkbox, as shown in the figure below. Click the "Run" button to start flashing.<br />
<br />
[[File:RKDevTool flashing image.png]]<br />
<br />
Logging information will be displayed in the right region of the RKDevTool window, and it shows the progress of flashing as well. Once the flashing is done, you may disconnect your Vivid Unit from your computer.<br />
<br />
[[File:RKDevTool flashing progress.png]]<br />
<br />
After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.<br />
<br />
<br />
=== Instructions for Mac OS X / Linux ===<br />
The RKDevTool only works in Windows, in Mac OS X or Linux, you may use its alternative [https://github.com/rockchip-linux/rkdeveloptool rkdeveloptool] instead.<br />
<br />
In Mac OS X, you may build rkdeveloptool with Homebrew, or download [https://www.vividunit.com/download/tools/rkdeveloptool_MacOSX.zip here]:<br />
brew install automake autoconf libusb pkg-config git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
cp rkdeveloptool /opt/homebrew/bin/<br />
In Linux (Debian or Ubuntu), you may build rkdeveloptool as below:<br />
sudo apt-get update<br />
sudo apt-get install -y libudev-dev libusb-1.0-0-dev dh-autoreconf pkg-config libusb-1.0 build-essential git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
sudo cp rkdeveloptool /usr/local/sbin/<br />
You may confirm rkdeveloptool's version by:<br />
rkdeveloptool --version<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. <br />
<br />
<pic src="images/f/f8/maskrom_and_power_buttons.jpg" width="70%" align="text" caption=""></pic><br />
<br />
After releasing both buttons you should see the MASKROM device get listed with "rkdeveloptool ld" command. If it doesn't show up, please repeat this step.<br />
Work:~ user$ rkdeveloptool ld<br />
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1402 Maskrom<br />
Work:~ user$ <br />
Once you confirm Vivid Unit is detected as MASKROM device, you can load the loader and then flash the image into the device:<br />
Work:~ user$ rkdeveloptool db rk3399_loader_v1.30.130.bin <br />
Downloading bootloader succeeded.<br />
Work:~ user$ rkdeveloptool wl 0x00 vuos-20260327-1.img <br />
Write LBA from file (100%)<br />
Work:~ user$ <br />
The Loader file can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here]. <br />
<br />
The Image file is the .img file extracted from the .img.xz file you previously downloaded. It should be flashed at address 0x00.<br />
<br />
Once the flashing is done, you may disconnect your Vivid Unit from your computer. After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.</div>Adminhttps://www.vividunit.com:443/index.php?title=MediaWiki:Sidebar&diff=740MediaWiki:Sidebar2026-04-03T13:24:26Z<p>Admin: </p>
<hr />
<div>* Buy<br />
** https://www.uugear.com/product/vivid-unit/|from UUGear e-Shop<br />
* Download<br />
** download-system-image|OS Images<br />
** schematic|Schematic<br />
** drawings-models|Drawings and Models<br />
* About ...<br />
** technical-specifications|Technical Specifications<br />
** interfaces|Interfaces<br />
** compliance|Compliance<br />
** gpio-and-adc|GPIO and ADC<br />
** screen-and-touch-buttons|Screen and Touch Buttons<br />
** expansion-addon-board-development|Expansion / Add-on Board Development<br />
* Accessories<br />
** back-panel-kit|Back Panel Kit<br />
** cooler-panel-kit|Cooler Panel Kit<br />
** extender|Vivid Unit Extender<br />
** vu-breakout|VU Breakout<br />
** vu-gpsdr|VU GPSDR<br />
* How to ...<br />
** turn-on-off|Turn on/off Vivid Unit<br />
** connect-to-internet|Connect to Internet<br />
** use-virtual-keyboard|Use Virtual Keyboard<br />
** right-and-middle-click|Right/Middle Click on Touchscreen<br />
** connect-via-ssh|Connect to Vivid Unit via SSH<br />
** connect-via-VNC|Connect to Vivid Unit via VNC<br />
** record-audio|Record Audio<br />
** replay-audio-video|Replay Audio and Video<br />
** install-vuos|(Re)install Vivid Unit OS<br />
** boot-from-nvme|Boot from NVME SSD<br />
** play-retro-games|Play retro games on Vivid Unit<br />
* FAQs<br />
** default-username-password|What is the default username/password?<br />
** gpio-voltage-level|What is the voltage level of GPIO?<br />
** rtc|Is there an RTC on Vivid Unit?<br />
* Support & Help<br />
** https://www.uugear.com/forums/technial-support-discussion/|UUGear Forum: Technial Support / Discussion</div>Adminhttps://www.vividunit.com:443/index.php?title=install-vuos&diff=739install-vuos2026-04-03T13:22:03Z<p>Admin: </p>
<hr />
<div>__TOC__<br />
<br />
'''Remarks:''' this tutorial is for (re)installing Vivid Unit OS (Debian 12) into Vivid Unit device. If you want to install the old system (Debian 11), please read [[install-os|this page]] instead.<br />
<br />
= Install Vivid Unit OS =<br />
Vivid Unit has eMMC storage onboard and the operating system (Debian with XFCE desktop enviroment) has been pre-installed in the eMMC. Usually you do not need to install operating system by yourself. However if the operating system corrupts or you want to install a different operating system (if available), you may follow this instructions.<br />
<br />
You may download the OS image from [[download-system-image|this page]]. The downloaded image is an img.xz file, and you need to extract it to get the .img file, which can be flashed into Vivid Unit.<br />
<br />
=== Instructions in Windows ===<br />
In order to flash the OS image into VIvid Unit, you need to put Vivid Unit into MASKROM mode, and your Windows may need extra drivers from Rockchip to recognize your Vivid Unit as a MASKROM device, so it can write data into it via USB.<br />
<br />
You can download and run [[download/tools/DriverAssitant v5.11.zip|this RK Driver Assistant]] to help installing the required Rockchip drivers.<br />
<br />
<pic src="images/1/18/installed_RK_driver.jpg" width="50%" align="text" caption=""></pic><br />
<br />
You can download and run [http://vividunit.com/download/tools/RKDevTool_v3.32.zip the RKDevTool] to flash the OS image into your Vivid Unit.<br />
<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. After releasing both buttons you should see the MASKROM device is detected by RKDevTool. If it doesn't show up, please repeat this step.<br />
<br />
<pic src="images/f/f8/maskrom_and_power_buttons.jpg" width="70%" align="text" caption=""></pic><br />
<br />
Then you can specify the Loader file, which can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here], or found in the RKDevTool package we provided on this page. The Loader's address should be set to 0x00000000.<br />
<br />
You also need to specify the Image file to flash. The Image file is the .img file extracted from the .img.xz file you previously downloaded. The "Storage" of the Image should be set to "EMMC", with address 0x00000000.<br />
<br />
Make sure to tick the checkboxes in the Loader and Image lines, as well as the "Write by Address" checkbox, as shown in the figure below. Click the "Run" button to start flashing.<br />
<br />
[[File:RKDevTool flashing image.png]]<br />
<br />
Logging information will be displayed in the right region of the RKDevTool window, and it shows the progress of flashing as well. Once the flashing is done, you may disconnect your Vivid Unit from your computer.<br />
<br />
[[File:RKDevTool flashing progress.png]]<br />
<br />
After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.<br />
<br />
<br />
=== Instructions for Mac OS X / Linux ===<br />
The RKDevTool only works in Windows, in Mac OS X or Linux, you may use its alternative [https://github.com/rockchip-linux/rkdeveloptool rkdeveloptool] instead.<br />
<br />
In Mac OS X, you may build rkdeveloptool with Homebrew, or download [https://www.vividunit.com/download/tools/rkdeveloptool_MacOSX.zip here]:<br />
brew install automake autoconf libusb pkg-config git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
cp rkdeveloptool /opt/homebrew/bin/<br />
In Linux (Debian or Ubuntu), you may build rkdeveloptool as below:<br />
sudo apt-get update<br />
sudo apt-get install -y libudev-dev libusb-1.0-0-dev dh-autoreconf pkg-config libusb-1.0 build-essential git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
sudo cp rkdeveloptool /usr/local/sbin/<br />
You may confirm rkdeveloptool's version by:<br />
rkdeveloptool --version<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. <br />
<br />
<pic src="images/f/f8/maskrom_and_power_buttons.jpg" width="70%" align="text" caption=""></pic><br />
<br />
After releasing both buttons you should see the MASKROM device get listed with "rkdeveloptool ld" command. If it doesn't show up, please repeat this step.<br />
Work:~ user$ rkdeveloptool ld<br />
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1402 Maskrom<br />
Work:~ user$ <br />
Once you confirm Vivid Unit is detected as MASKROM device, you can load the loader and then flash the image into the device:<br />
Work:~ user$ rkdeveloptool db rk3399_loader_v1.30.130.bin <br />
Downloading bootloader succeeded.<br />
Work:~ user$ rkdeveloptool wl 0x00 vuos-20260327-1.img <br />
Write LBA from file (100%)<br />
Work:~ user$ <br />
The Loader file can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here]. <br />
<br />
The Image file is the .img file extracted from the .img.xz file you previously downloaded. It should be flashed at address 0x00.<br />
<br />
Once the flashing is done, you may disconnect your Vivid Unit from your computer. After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.</div>Adminhttps://www.vividunit.com:443/index.php?title=install-vuos&diff=738install-vuos2026-04-03T13:21:24Z<p>Admin: </p>
<hr />
<div>__TOC__<br />
= Install Vivid Unit OS =<br />
'''Remarks:''' this tutorial is for (re)installing Vivid Unit OS (Debian 12) into Vivid Unit device. If you want to install the old system (Debian 11), please read [[install-os|this page]] instead.<br />
<br />
Vivid Unit has eMMC storage onboard and the operating system (Debian with XFCE desktop enviroment) has been pre-installed in the eMMC. Usually you do not need to install operating system by yourself. However if the operating system corrupts or you want to install a different operating system (if available), you may follow this instructions.<br />
<br />
You may download the OS image from [[download-system-image|this page]]. The downloaded image is an img.xz file, and you need to extract it to get the .img file, which can be flashed into Vivid Unit.<br />
<br />
=== Instructions in Windows ===<br />
In order to flash the OS image into VIvid Unit, you need to put Vivid Unit into MASKROM mode, and your Windows may need extra drivers from Rockchip to recognize your Vivid Unit as a MASKROM device, so it can write data into it via USB.<br />
<br />
You can download and run [[download/tools/DriverAssitant v5.11.zip|this RK Driver Assistant]] to help installing the required Rockchip drivers.<br />
<br />
<pic src="images/1/18/installed_RK_driver.jpg" width="50%" align="text" caption=""></pic><br />
<br />
You can download and run [http://vividunit.com/download/tools/RKDevTool_v3.32.zip the RKDevTool] to flash the OS image into your Vivid Unit.<br />
<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. After releasing both buttons you should see the MASKROM device is detected by RKDevTool. If it doesn't show up, please repeat this step.<br />
<br />
<pic src="images/f/f8/maskrom_and_power_buttons.jpg" width="70%" align="text" caption=""></pic><br />
<br />
Then you can specify the Loader file, which can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here], or found in the RKDevTool package we provided on this page. The Loader's address should be set to 0x00000000.<br />
<br />
You also need to specify the Image file to flash. The Image file is the .img file extracted from the .img.xz file you previously downloaded. The "Storage" of the Image should be set to "EMMC", with address 0x00000000.<br />
<br />
Make sure to tick the checkboxes in the Loader and Image lines, as well as the "Write by Address" checkbox, as shown in the figure below. Click the "Run" button to start flashing.<br />
<br />
[[File:RKDevTool flashing image.png]]<br />
<br />
Logging information will be displayed in the right region of the RKDevTool window, and it shows the progress of flashing as well. Once the flashing is done, you may disconnect your Vivid Unit from your computer.<br />
<br />
[[File:RKDevTool flashing progress.png]]<br />
<br />
After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.<br />
<br />
<br />
=== Instructions for Mac OS X / Linux ===<br />
The RKDevTool only works in Windows, in Mac OS X or Linux, you may use its alternative [https://github.com/rockchip-linux/rkdeveloptool rkdeveloptool] instead.<br />
<br />
In Mac OS X, you may build rkdeveloptool with Homebrew, or download [https://www.vividunit.com/download/tools/rkdeveloptool_MacOSX.zip here]:<br />
brew install automake autoconf libusb pkg-config git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
cp rkdeveloptool /opt/homebrew/bin/<br />
In Linux (Debian or Ubuntu), you may build rkdeveloptool as below:<br />
sudo apt-get update<br />
sudo apt-get install -y libudev-dev libusb-1.0-0-dev dh-autoreconf pkg-config libusb-1.0 build-essential git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
sudo cp rkdeveloptool /usr/local/sbin/<br />
You may confirm rkdeveloptool's version by:<br />
rkdeveloptool --version<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. <br />
<br />
<pic src="images/f/f8/maskrom_and_power_buttons.jpg" width="70%" align="text" caption=""></pic><br />
<br />
After releasing both buttons you should see the MASKROM device get listed with "rkdeveloptool ld" command. If it doesn't show up, please repeat this step.<br />
Work:~ user$ rkdeveloptool ld<br />
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1402 Maskrom<br />
Work:~ user$ <br />
Once you confirm Vivid Unit is detected as MASKROM device, you can load the loader and then flash the image into the device:<br />
Work:~ user$ rkdeveloptool db rk3399_loader_v1.30.130.bin <br />
Downloading bootloader succeeded.<br />
Work:~ user$ rkdeveloptool wl 0x00 vuos-20260327-1.img <br />
Write LBA from file (100%)<br />
Work:~ user$ <br />
The Loader file can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here]. <br />
<br />
The Image file is the .img file extracted from the .img.xz file you previously downloaded. It should be flashed at address 0x00.<br />
<br />
Once the flashing is done, you may disconnect your Vivid Unit from your computer. After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.</div>Adminhttps://www.vividunit.com:443/index.php?title=install-vuos&diff=737install-vuos2026-04-03T13:19:20Z<p>Admin: /* Instructions in Windows */</p>
<hr />
<div>= Install Vivid Unit OS =<br />
'''Remarks:''' this tutorial is for (re)installing Vivid Unit OS (Debian 12) into Vivid Unit device. If you want to install the old system (Debian 11), please read [[install-os|this page]] instead.<br />
<br />
Vivid Unit has eMMC storage onboard and the operating system (Debian with XFCE desktop enviroment) has been pre-installed in the eMMC. Usually you do not need to install operating system by yourself. However if the operating system corrupts or you want to install a different operating system (if available), you may follow this instructions.<br />
<br />
You may download the OS image from [[download-system-image|this page]]. The downloaded image is an img.xz file, and you need to extract it to get the .img file, which can be flashed into Vivid Unit.<br />
<br />
=== Instructions in Windows ===<br />
In order to flash the OS image into VIvid Unit, you need to put Vivid Unit into MASKROM mode, and your Windows may need extra drivers from Rockchip to recognize your Vivid Unit as a MASKROM device, so it can write data into it via USB.<br />
<br />
You can download and run [[download/tools/DriverAssitant v5.11.zip|this RK Driver Assistant]] to help installing the required Rockchip drivers.<br />
<br />
<pic src="images/1/18/installed_RK_driver.jpg" width="50%" align="text" caption=""></pic><br />
<br />
You can download and run [http://vividunit.com/download/tools/RKDevTool_v3.32.zip the RKDevTool] to flash the OS image into your Vivid Unit.<br />
<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. After releasing both buttons you should see the MASKROM device is detected by RKDevTool. If it doesn't show up, please repeat this step.<br />
<br />
<pic src="images/f/f8/maskrom_and_power_buttons.jpg" width="70%" align="text" caption=""></pic><br />
<br />
Then you can specify the Loader file, which can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here], or found in the RKDevTool package we provided on this page. The Loader's address should be set to 0x00000000.<br />
<br />
You also need to specify the Image file to flash. The Image file is the .img file extracted from the .img.xz file you previously downloaded. The "Storage" of the Image should be set to "EMMC", with address 0x00000000.<br />
<br />
Make sure to tick the checkboxes in the Loader and Image lines, as well as the "Write by Address" checkbox, as shown in the figure below. Click the "Run" button to start flashing.<br />
<br />
[[File:RKDevTool flashing image.png]]<br />
<br />
Logging information will be displayed in the right region of the RKDevTool window, and it shows the progress of flashing as well. Once the flashing is done, you may disconnect your Vivid Unit from your computer.<br />
<br />
[[File:RKDevTool flashing progress.png]]<br />
<br />
After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.<br />
<br />
<br />
=== Instructions for Mac OS X / Linux ===<br />
The RKDevTool only works in Windows, in Mac OS X or Linux, you may use its alternative [https://github.com/rockchip-linux/rkdeveloptool rkdeveloptool] instead.<br />
<br />
In Mac OS X, you may build rkdeveloptool with Homebrew, or download [https://www.vividunit.com/download/tools/rkdeveloptool_MacOSX.zip here]:<br />
brew install automake autoconf libusb pkg-config git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
cp rkdeveloptool /opt/homebrew/bin/<br />
In Linux (Debian or Ubuntu), you may build rkdeveloptool as below:<br />
sudo apt-get update<br />
sudo apt-get install -y libudev-dev libusb-1.0-0-dev dh-autoreconf pkg-config libusb-1.0 build-essential git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
sudo cp rkdeveloptool /usr/local/sbin/<br />
You may confirm rkdeveloptool's version by:<br />
rkdeveloptool --version<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. <br />
<br />
<pic src="images/f/f8/maskrom_and_power_buttons.jpg" width="70%" align="text" caption=""></pic><br />
<br />
After releasing both buttons you should see the MASKROM device get listed with "rkdeveloptool ld" command. If it doesn't show up, please repeat this step.<br />
Work:~ user$ rkdeveloptool ld<br />
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1402 Maskrom<br />
Work:~ user$ <br />
Once you confirm Vivid Unit is detected as MASKROM device, you can load the loader and then flash the image into the device:<br />
Work:~ user$ rkdeveloptool db rk3399_loader_v1.30.130.bin <br />
Downloading bootloader succeeded.<br />
Work:~ user$ rkdeveloptool wl 0x00 vuos-20260327-1.img <br />
Write LBA from file (100%)<br />
Work:~ user$ <br />
The Loader file can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here]. <br />
<br />
The Image file is the .img file extracted from the .img.xz file you previously downloaded. It should be flashed at address 0x00.<br />
<br />
Once the flashing is done, you may disconnect your Vivid Unit from your computer. After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.</div>Adminhttps://www.vividunit.com:443/index.php?title=install-vuos&diff=736install-vuos2026-04-03T13:17:28Z<p>Admin: /* Re(install) Vivid Unit OS */</p>
<hr />
<div>= Install Vivid Unit OS =<br />
'''Remarks:''' this tutorial is for (re)installing Vivid Unit OS (Debian 12) into Vivid Unit device. If you want to install the old system (Debian 11), please read [[install-os|this page]] instead.<br />
<br />
Vivid Unit has eMMC storage onboard and the operating system (Debian with XFCE desktop enviroment) has been pre-installed in the eMMC. Usually you do not need to install operating system by yourself. However if the operating system corrupts or you want to install a different operating system (if available), you may follow this instructions.<br />
<br />
You may download the OS image from [[download-system-image|this page]]. The downloaded image is an img.xz file, and you need to extract it to get the .img file, which can be flashed into Vivid Unit.<br />
<br />
=== Instructions in Windows ===<br />
In order to flash the OS image into VIvid Unit, you need to put Vivid Unit into MASKROM mode, and your Windows may need extra drivers from Rockchip to recognize your Vivid Unit as a MASKROM device, so it can write data into it via USB.<br />
<br />
You can download and run [[download/tools/DriverAssitant v5.11.zip|this RK Driver Assistant]] to help installing the required Rockchip drivers.<br />
<br />
<pic src="images/1/18/installed_RK_driver.jpg" width="50%" align="text" caption=""></pic><br />
<br />
You can download and run [http://vividunit.com/download/tools/RKDevTool_v3.32.zip the RKDevTool] to flash the OS image into your Vivid Unit.<br />
<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. After releasing both buttons you should see the MASKROM device is detected by RKDevTool. If it doesn't show up, please repeat this step.<br />
<br />
Then you can specify the Loader file, which can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here], or found in the RKDevTool package we provided on this page. The Loader's address should be set to 0x00000000.<br />
<br />
You also need to specify the Image file to flash. The Image file is the .img file extracted from the .img.xz file you previously downloaded. The "Storage" of the Image should be set to "EMMC", with address 0x00000000.<br />
<br />
Make sure to tick the checkboxes in the Loader and Image lines, as well as the "Write by Address" checkbox, as shown in the figure below. Click the "Run" button to start flashing.<br />
<br />
[[File:RKDevTool flashing image.png]]<br />
<br />
Logging information will be displayed in the right region of the RKDevTool window, and it shows the progress of flashing as well. Once the flashing is done, you may disconnect your Vivid Unit from your computer.<br />
<br />
[[File:RKDevTool flashing progress.png]]<br />
<br />
After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.<br />
<br />
=== Instructions for Mac OS X / Linux ===<br />
The RKDevTool only works in Windows, in Mac OS X or Linux, you may use its alternative [https://github.com/rockchip-linux/rkdeveloptool rkdeveloptool] instead.<br />
<br />
In Mac OS X, you may build rkdeveloptool with Homebrew, or download [https://www.vividunit.com/download/tools/rkdeveloptool_MacOSX.zip here]:<br />
brew install automake autoconf libusb pkg-config git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
cp rkdeveloptool /opt/homebrew/bin/<br />
In Linux (Debian or Ubuntu), you may build rkdeveloptool as below:<br />
sudo apt-get update<br />
sudo apt-get install -y libudev-dev libusb-1.0-0-dev dh-autoreconf pkg-config libusb-1.0 build-essential git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
sudo cp rkdeveloptool /usr/local/sbin/<br />
You may confirm rkdeveloptool's version by:<br />
rkdeveloptool --version<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. After releasing both buttons you should see the MASKROM device get listed with "rkdeveloptool ld" command. If it doesn't show up, please repeat this step.<br />
Work:~ user$ rkdeveloptool ld<br />
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1402 Maskrom<br />
Work:~ user$ <br />
Once you confirm Vivid Unit is detected as MASKROM device, you can load the loader and then flash the image into the device:<br />
Work:~ user$ rkdeveloptool db rk3399_loader_v1.30.130.bin <br />
Downloading bootloader succeeded.<br />
Work:~ user$ rkdeveloptool wl 0x00 vuos-20260327-1.img <br />
Write LBA from file (100%)<br />
Work:~ user$ <br />
The Loader file can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here]. <br />
<br />
The Image file is the .img file extracted from the .img.xz file you previously downloaded. It should be flashed at address 0x00.<br />
<br />
Once the flashing is done, you may disconnect your Vivid Unit from your computer. After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.</div>Adminhttps://www.vividunit.com:443/index.php?title=install-vuos&diff=735install-vuos2026-04-03T13:14:24Z<p>Admin: /* Instructions for Mac OS X / Linux */</p>
<hr />
<div>= Re(install) Vivid Unit OS =<br />
Vivid Unit has eMMC storage onboard and the operating system (Debian with XFCE desktop enviroment) has been pre-installed in the eMMC. Usually you do not need to install operating system by yourself. However if the operating system corrupts or you want to install a different operating system (if available), you may follow this instructions.<br />
<br />
You may download the OS image from [[download-system-image|this page]]. The downloaded image is an img.xz file, and you need to extract it to get the .img file, which can be flashed into Vivid Unit.<br />
<br />
=== Instructions in Windows ===<br />
In order to flash the OS image into VIvid Unit, you need to put Vivid Unit into MASKROM mode, and your Windows may need extra drivers from Rockchip to recognize your Vivid Unit as a MASKROM device, so it can write data into it via USB.<br />
<br />
You can download and run [[download/tools/DriverAssitant v5.11.zip|this RK Driver Assistant]] to help installing the required Rockchip drivers.<br />
<br />
<pic src="images/1/18/installed_RK_driver.jpg" width="50%" align="text" caption=""></pic><br />
<br />
You can download and run [http://vividunit.com/download/tools/RKDevTool_v3.32.zip the RKDevTool] to flash the OS image into your Vivid Unit.<br />
<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. After releasing both buttons you should see the MASKROM device is detected by RKDevTool. If it doesn't show up, please repeat this step.<br />
<br />
Then you can specify the Loader file, which can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here], or found in the RKDevTool package we provided on this page. The Loader's address should be set to 0x00000000.<br />
<br />
You also need to specify the Image file to flash. The Image file is the .img file extracted from the .img.xz file you previously downloaded. The "Storage" of the Image should be set to "EMMC", with address 0x00000000.<br />
<br />
Make sure to tick the checkboxes in the Loader and Image lines, as well as the "Write by Address" checkbox, as shown in the figure below. Click the "Run" button to start flashing.<br />
<br />
[[File:RKDevTool flashing image.png]]<br />
<br />
Logging information will be displayed in the right region of the RKDevTool window, and it shows the progress of flashing as well. Once the flashing is done, you may disconnect your Vivid Unit from your computer.<br />
<br />
[[File:RKDevTool flashing progress.png]]<br />
<br />
After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.<br />
<br />
=== Instructions for Mac OS X / Linux ===<br />
The RKDevTool only works in Windows, in Mac OS X or Linux, you may use its alternative [https://github.com/rockchip-linux/rkdeveloptool rkdeveloptool] instead.<br />
<br />
In Mac OS X, you may build rkdeveloptool with Homebrew, or download [https://www.vividunit.com/download/tools/rkdeveloptool_MacOSX.zip here]:<br />
brew install automake autoconf libusb pkg-config git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
cp rkdeveloptool /opt/homebrew/bin/<br />
In Linux (Debian or Ubuntu), you may build rkdeveloptool as below:<br />
sudo apt-get update<br />
sudo apt-get install -y libudev-dev libusb-1.0-0-dev dh-autoreconf pkg-config libusb-1.0 build-essential git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
sudo cp rkdeveloptool /usr/local/sbin/<br />
You may confirm rkdeveloptool's version by:<br />
rkdeveloptool --version<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. After releasing both buttons you should see the MASKROM device get listed with "rkdeveloptool ld" command. If it doesn't show up, please repeat this step.<br />
Work:~ user$ rkdeveloptool ld<br />
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=1402 Maskrom<br />
Work:~ user$ <br />
Once you confirm Vivid Unit is detected as MASKROM device, you can load the loader and then flash the image into the device:<br />
Work:~ user$ rkdeveloptool db rk3399_loader_v1.30.130.bin <br />
Downloading bootloader succeeded.<br />
Work:~ user$ rkdeveloptool wl 0x00 vuos-20260327-1.img <br />
Write LBA from file (100%)<br />
Work:~ user$ <br />
The Loader file can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here]. <br />
<br />
The Image file is the .img file extracted from the .img.xz file you previously downloaded. It should be flashed at address 0x00.<br />
<br />
Once the flashing is done, you may disconnect your Vivid Unit from your computer. After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.</div>Adminhttps://www.vividunit.com:443/index.php?title=install-vuos&diff=734install-vuos2026-04-02T15:08:16Z<p>Admin: /* Re(install) Vivid Unit OS */</p>
<hr />
<div>= Re(install) Vivid Unit OS =<br />
Vivid Unit has eMMC storage onboard and the operating system (Debian with XFCE desktop enviroment) has been pre-installed in the eMMC. Usually you do not need to install operating system by yourself. However if the operating system corrupts or you want to install a different operating system (if available), you may follow this instructions.<br />
<br />
You may download the OS image from [[download-system-image|this page]]. The downloaded image is an img.xz file, and you need to extract it to get the .img file, which can be flashed into Vivid Unit.<br />
<br />
=== Instructions in Windows ===<br />
In order to flash the OS image into VIvid Unit, you need to put Vivid Unit into MASKROM mode, and your Windows may need extra drivers from Rockchip to recognize your Vivid Unit as a MASKROM device, so it can write data into it via USB.<br />
<br />
You can download and run [[download/tools/DriverAssitant v5.11.zip|this RK Driver Assistant]] to help installing the required Rockchip drivers.<br />
<br />
<pic src="images/1/18/installed_RK_driver.jpg" width="50%" align="text" caption=""></pic><br />
<br />
You can download and run [http://vividunit.com/download/tools/RKDevTool_v3.32.zip the RKDevTool] to flash the OS image into your Vivid Unit.<br />
<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. After releasing both buttons you should see the MASKROM device is detected by RKDevTool. If it doesn't show up, please repeat this step.<br />
<br />
Then you can specify the Loader file, which can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here], or found in the RKDevTool package we provided on this page. The Loader's address should be set to 0x00000000.<br />
<br />
You also need to specify the Image file to flash. The Image file is the .img file extracted from the .img.xz file you previously downloaded. The "Storage" of the Image should be set to "EMMC", with address 0x00000000.<br />
<br />
Make sure to tick the checkboxes in the Loader and Image lines, as well as the "Write by Address" checkbox, as shown in the figure below. Click the "Run" button to start flashing.<br />
<br />
[[File:RKDevTool flashing image.png]]<br />
<br />
Logging information will be displayed in the right region of the RKDevTool window, and it shows the progress of flashing as well. Once the flashing is done, you may disconnect your Vivid Unit from your computer.<br />
<br />
[[File:RKDevTool flashing progress.png]]<br />
<br />
After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.<br />
<br />
=== Instructions for Mac OS X / Linux ===<br />
The RKDevTool only works in Windows, in Mac OS X or Linux, you may use its alternative [https://github.com/rockchip-linux/rkdeveloptool rkdeveloptool] instead.<br />
<br />
In Mac OS X, you may build rkdevloptool with Homebrew, or download [https://www.vividunit.com/download/tools/rkdeveloptool_MacOSX.zip here]:<br />
brew install automake autoconf libusb pkg-config git wget<br />
git clone <nowiki>https://github.com/rockchip-linux/rkdeveloptool</nowiki><br />
cd rkdeveloptool<br />
autoreconf -i<br />
./configure<br />
make -j $(nproc)<br />
cp rkdeveloptool /opt/homebrew/bin/</div>Adminhttps://www.vividunit.com:443/index.php?title=install-vuos&diff=733install-vuos2026-04-02T14:49:43Z<p>Admin: /* Re(install) Vivid Unit OS */</p>
<hr />
<div>= Re(install) Vivid Unit OS =<br />
Vivid Unit has eMMC storage onboard and the operating system (Debian with XFCE desktop enviroment) has been pre-installed in the eMMC. Usually you do not need to install operating system by yourself. However if the operating system corrupts or you want to install a different operating system (if available), you may follow this instructions.<br />
<br />
You may download the OS image from [[download-system-image|this page]]. The downloaded image is an img.xz file, and you need to extract it to get the .img file, which can be flashed into Vivid Unit.<br />
<br />
=== Instructions in Windows ===<br />
In order to flash the OS image into VIvid Unit, you need to put Vivid Unit into MASKROM mode, and your Windows may need extra drivers from Rockchip to recognize your Vivid Unit as a MASKROM device, so it can write data into it via USB.<br />
<br />
You can download and run [[download/tools/DriverAssitant v5.11.zip|this RK Driver Assistant]] to help installing the required Rockchip drivers.<br />
<br />
<pic src="images/1/18/installed_RK_driver.jpg" width="50%" align="text" caption=""></pic><br />
<br />
You can download and run [http://vividunit.com/download/tools/RKDevTool_v3.32.zip the RKDevTool] to flash the OS image into your Vivid Unit.<br />
<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. After releasing both buttons you should see the MASKROM device is detected by RKDevTool. If it doesn't show up, please repeat this step.<br />
<br />
Then you can specify the Loader file, which can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here], or found in the RKDevTool package we provided on this page. The Loader's address should be set to 0x00000000.<br />
<br />
You also need to specify the Image file to flash. The Image file is the .img file extracted from the .img.xz file you previously downloaded. The "Storage" of the Image should be set to "EMMC", with address 0x00000000.<br />
<br />
Make sure to tick the checkboxes in the Loader and Image lines, as well as the "Write by Address" checkbox, as shown in the figure below. Click the "Run" button to start flashing.<br />
<br />
[[File:RKDevTool flashing image.png]]<br />
<br />
Logging information will be displayed in the right region of the RKDevTool window, and it shows the progress of flashing as well. Once the flashing is done, you may disconnect your Vivid Unit from your computer.<br />
<br />
[[File:RKDevTool flashing progress.png]]<br />
<br />
After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.</div>Adminhttps://www.vividunit.com:443/index.php?title=install-vuos&diff=732install-vuos2026-04-02T14:49:09Z<p>Admin: /* Re(install) Vivid Unit OS */</p>
<hr />
<div>= Re(install) Vivid Unit OS =<br />
Vivid Unit has eMMC storage onboard and the operating system (Debian with XFCE desktop enviroment) has been pre-installed in the eMMC. Usually you do not need to install operating system by yourself. However if the operating system corrupts or you want to install a different operating system (if available), you may follow this instructions.<br />
<br />
You may download the OS image from [[download-system-image|this page]]. The downloaded image is an img.xz file, and you need to extract it to get the .img file, which can be flashed into Vivid Unit.<br />
<br />
=== Instructions in Windows ===<br />
In order to flash the OS image into VIvid Unit, you need to put Vivid Unit into MASKROM mode, and your Windows may need extra drivers from Rockchip to recognize your Vivid Unit as a MASKROM device, so it can write data into it via USB.<br />
<br />
You can download and run [[download/tools/DriverAssitant v5.11.zip|this RK Driver Assistant]] to help installing the required Rockchip drivers.<br />
<br />
<pic src="images/1/18/installed_RK_driver.jpg" width="50%" align="text" caption=""></pic><br />
<br />
You can download and run [http://vividunit.com/download/tools/RKDevTool_v3.32.zip the RKDevTool] to flash the OS image into your Vivid Unit.<br />
<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. After releasing both buttons you should see the MASKROM device is detected by RKDevTool. If it doesn't show up, please repeat this step.<br />
<br />
Then you can specify the Loader file, which can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here], or found in the RKDevTool package we provided on this page. The Loader's address should be set to 0x00000000.<br />
<br />
You also need to specify the Image file to flash. The Image file is the .img file extracted from the .img.xz file you previously downloaded. The "Storage" of the Image should be set to "EMMC", with address 0x00000000.<br />
<br />
Make sure to tick the checkboxes in the Loader and Image lines, as well as the "Write by Address" checkbox, as shown in the figure below. Click the "Run" button to start flashing.<br />
<br />
[[File:RKDevTool flashing image.png]]<br />
<br />
Logging information will be displayed in the right region of the RKDevTool window, and it shows the progress of flashing as well. Once the flashing is done, you may disconnect your Vivid Unit from your computer.<br />
<br />
[[File:RKDevTool logging progress.png]]<br />
<br />
After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.</div>Adminhttps://www.vividunit.com:443/index.php?title=File:RKDevTool_flashing_progress.png&diff=731File:RKDevTool flashing progress.png2026-04-02T14:48:40Z<p>Admin: </p>
<hr />
<div></div>Adminhttps://www.vividunit.com:443/index.php?title=File:RKDevTool_flashing_image.png&diff=730File:RKDevTool flashing image.png2026-04-02T14:48:12Z<p>Admin: </p>
<hr />
<div></div>Adminhttps://www.vividunit.com:443/index.php?title=install-vuos&diff=726install-vuos2026-04-02T07:58:12Z<p>Admin: /* Re(install) Vivid Unit OS */</p>
<hr />
<div>= Re(install) Vivid Unit OS =<br />
Vivid Unit has eMMC storage onboard and the operating system (Debian with XFCE desktop enviroment) has been pre-installed in the eMMC. Usually you do not need to install operating system by yourself. However if the operating system corrupts or you want to install a different operating system (if available), you may follow this instructions.<br />
<br />
You may download the OS image from [[download-system-image|this page]]. The downloaded image is an img.xz file, and you need to extract it to get the .img file, which can be flashed into Vivid Unit.<br />
<br />
=== Instructions in Windows ===<br />
In order to flash the OS image into VIvid Unit, you need to put Vivid Unit into MASKROM mode, and your Windows may need extra drivers from Rockchip to recognize your Vivid Unit as a MASKROM device, so it can write data into it via USB.<br />
<br />
You can download and run [[download/tools/DriverAssitant v5.11.zip|this RK Driver Assistant]] to help installing the required Rockchip drivers.<br />
<br />
<pic src="images/1/18/installed_RK_driver.jpg" width="50%" align="text" caption=""></pic><br />
<br />
You can download and run [http://vividunit.com/download/tools/RKDevTool_v3.32.zip the RKDevTool] to flash the OS image into your Vivid Unit.<br />
<br />
Connect your Vivid Unit to your computer via an USB type-C cable. Press and hold the small MASKROM button in the middle of Vivid Unit's circuit board (do not release it) and then press the power button (also do not release it) for about 5 seconds. After releasing both buttons you should see the MASKROM device is detected by RKDevTool. If it doesn't show up, please repeat this step.<br />
<br />
Then you can specify the Loader file, which can be downloaded [https://github.com/uugear/vivid-unit-os/blob/main/boards/vivid-unit/rkbin/rk3399_loader_v1.30.130.bin here], or found in the RKDevTool package we provided on this page. The Loader's address should be set to 0x00000000.<br />
<br />
You also need to specify the Image file to flash. The Image file is the .img file extracted from the .img.xz file you previously downloaded. The "Storage" of the Image should be set to "EMMC", with address 0x00000000.<br />
<br />
Make sure to tick the checkboxes in the Loader and Image lines, as well as the "Write by Address" checkbox, as shown in the figure below. Click the "Run" button to start flashing.<br />
<br />
[[File:RKDevTool flashing image.png]]<br />
<br />
Logging information will be displayed in the right region of the RKDevTool window, and it shows the progress of flashing as well. Once the flashing is done, you may disconnect your Vivid Unit from your computer.<br />
<br />
After connecting the power supply to your Vivid Unit, you can tap the power button to boot up the system.</div>Adminhttps://www.vividunit.com:443/index.php?title=download-system-image&diff=724download-system-image2026-04-01T14:26:27Z<p>Admin: /* Download OS Images */</p>
<hr />
<div>= Download OS Images =<br />
Vivid Unit comes with Debian operating system pre-installed, usually you don't need to install system by yourself.<br />
<br />
However if you want to re-install the system, or want to install a different system (if available), you can download the system disk image here.<br />
= Vivid Unit OS =<br />
[[File:vuos-desktop.png|alt=Debian 12 @ Vivid Unit|thumb|Vivid Unit OS Desktop Preview]]<br />
'''Vivid Unit OS (Debian 12 - Bookworm): version 20260327'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vuos-debian12-20260327-vivid-unit.img.xz vuos-debian12-20260327-vivid-unit.img.xz (400 MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: bf9f85abc9512b543708261d1ea6485f''<br />
<br />
''SHA1: 6c764ed1a90f7cdaacf338a1b90227ec4a0603bf''<br />
<br />
Build system on GitHub: <br />
<br />
https://github.com/uugear/vivid-unit-os/releases/tag/20260327<br />
<br />
</blockquote><br />
<br />
= Older Versions of System =<br />
[[File:debian11 preview.jpg|alt=Debian 11 @ Vivid Unit|thumb|Desktop Preview|right]]<br />
'''Debian GNU/Linux 11 (bullseye)'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-20240129.img.xz vivid-unit-v13-debian11-20240129.img.xz (933 MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: b66ab31e21bec94ff5a1d0f98b54716b''<br />
<br />
''SHA1: 0f2be8a9670585808909da65c67e02869ad7c859''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
[[File:Debian11 Retropie preview.jpg|thumb|RetroPie Preview|alt=RetroPie on Vivid Unit]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://retropie.org.uk/ RetroPie] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-retropie-20240129.img.xz vivid-unit-v13-debian11-retropie-20240129.img.xz (1.06 GB)]<br />
<br />
<blockquote><br />
<br />
''MD5: 86dd3cd81e1474880b455dfc41b23792''<br />
<br />
''SHA1: cc1df6a419a53c6fb3b4b1d6b9e5417e759e20c8''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
<br />
[[File:Home Assistant Preview.jpg|thumb|alt=Home Assistant on Vivid Unit|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/ Home Assistant (Docker)] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-20240320.img.xz vivid-unit-v13-debian11-home-assistant-20240320.img.xz (1.39 GB)]<br />
<br />
''MD5: bb19226675b7bab9ff3900fdce0a7ce5''<br />
<br />
''SHA1: 070b4a8030a8924f277e992c76f9830db3fce47c''<br />
<br />
<br />
<br />
<br />
[[File:Home-Assistant-Supervised-Preview.jpg|alt=Home Assistant on Vivid Unit|thumb|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/installation/#advanced-installation-methods Home Assistant Supervised] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz (1.52 GB)]<br />
<br />
''MD5: 776435bdc297958f1a591787a0e48e02''<br />
<br />
''SHA1: 90019ab7b989b6bd2ba1911699d6c2c9a3413d70''<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
You can find more details about how to install system [[install-os|here]].</div>Adminhttps://www.vividunit.com:443/index.php?title=download-system-image&diff=723download-system-image2026-04-01T14:25:46Z<p>Admin: </p>
<hr />
<div>= Download OS Images =<br />
Vivid Unit comes with Debian operating system pre-installed, usually you don't need to install system by yourself.<br />
<br />
However if you want to re-install the system, or want to install a different system (if available), you can download the system disk image here.<br />
= Debian =<br />
[[File:vuos-desktop.png|alt=Debian 12 @ Vivid Unit|thumb|Vivid Unit OS Desktop Preview]]<br />
'''Vivid Unit OS (Debian 12 - Bookworm): version 20260327'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vuos-debian12-20260327-vivid-unit.img.xz vuos-debian12-20260327-vivid-unit.img.xz (400 MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: bf9f85abc9512b543708261d1ea6485f''<br />
<br />
''SHA1: 6c764ed1a90f7cdaacf338a1b90227ec4a0603bf''<br />
<br />
Build system on GitHub: <br />
<br />
https://github.com/uugear/vivid-unit-os/releases/tag/20260327<br />
<br />
</blockquote><br />
<br />
= Older Versions of System =<br />
----[[File:debian11 preview.jpg|alt=Debian 11 @ Vivid Unit|thumb|Desktop Preview|right]]<br />
'''Debian GNU/Linux 11 (bullseye)'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-20240129.img.xz vivid-unit-v13-debian11-20240129.img.xz (933 MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: b66ab31e21bec94ff5a1d0f98b54716b''<br />
<br />
''SHA1: 0f2be8a9670585808909da65c67e02869ad7c859''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
[[File:Debian11 Retropie preview.jpg|thumb|RetroPie Preview|alt=RetroPie on Vivid Unit]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://retropie.org.uk/ RetroPie] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-retropie-20240129.img.xz vivid-unit-v13-debian11-retropie-20240129.img.xz (1.06 GB)]<br />
<br />
<blockquote><br />
<br />
''MD5: 86dd3cd81e1474880b455dfc41b23792''<br />
<br />
''SHA1: cc1df6a419a53c6fb3b4b1d6b9e5417e759e20c8''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
<br />
[[File:Home Assistant Preview.jpg|thumb|alt=Home Assistant on Vivid Unit|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/ Home Assistant (Docker)] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-20240320.img.xz vivid-unit-v13-debian11-home-assistant-20240320.img.xz (1.39 GB)]<br />
<br />
''MD5: bb19226675b7bab9ff3900fdce0a7ce5''<br />
<br />
''SHA1: 070b4a8030a8924f277e992c76f9830db3fce47c''<br />
<br />
<br />
<br />
<br />
[[File:Home-Assistant-Supervised-Preview.jpg|alt=Home Assistant on Vivid Unit|thumb|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/installation/#advanced-installation-methods Home Assistant Supervised] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz (1.52 GB)]<br />
<br />
''MD5: 776435bdc297958f1a591787a0e48e02''<br />
<br />
''SHA1: 90019ab7b989b6bd2ba1911699d6c2c9a3413d70''<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
You can find more details about how to install system [[install-os|here]].</div>Adminhttps://www.vividunit.com:443/index.php?title=download-system-image&diff=722download-system-image2026-04-01T14:23:22Z<p>Admin: /* Debian */</p>
<hr />
<div>= Download OS Images =<br />
Vivid Unit comes with Debian operating system pre-installed, usually you don't need to install system by yourself.<br />
<br />
However if you want to re-install the system, or want to install a different system (if available), you can download the system disk image here.<br />
= Debian =<br />
[[File:vuos-desktop.png|alt=Debian 12 @ Vivid Unit|thumb|Vivid Unit OS Desktop Preview]]<br />
'''Vivid Unit OS (Debian 12 - Bookworm): version 20260327'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vuos-debian12-20260327-vivid-unit.img.xz vuos-debian12-20260327-vivid-unit.img.xz (400 MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: bf9f85abc9512b543708261d1ea6485f''<br />
<br />
''SHA1: 6c764ed1a90f7cdaacf338a1b90227ec4a0603bf''<br />
<br />
Build system on GitHub: <br />
<br />
https://github.com/uugear/vivid-unit-os/releases/tag/20260327<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
[[File:debian11 preview.jpg|alt=Debian 11 @ Vivid Unit|thumb|Desktop Preview|right]]<br />
'''Debian GNU/Linux 11 (bullseye)'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-20240129.img.xz vivid-unit-v13-debian11-20240129.img.xz (933 MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: b66ab31e21bec94ff5a1d0f98b54716b''<br />
<br />
''SHA1: 0f2be8a9670585808909da65c67e02869ad7c859''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
[[File:Debian11 Retropie preview.jpg|thumb|RetroPie Preview|alt=RetroPie on Vivid Unit]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://retropie.org.uk/ RetroPie] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-retropie-20240129.img.xz vivid-unit-v13-debian11-retropie-20240129.img.xz (1.06 GB)]<br />
<br />
<blockquote><br />
<br />
''MD5: 86dd3cd81e1474880b455dfc41b23792''<br />
<br />
''SHA1: cc1df6a419a53c6fb3b4b1d6b9e5417e759e20c8''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
<br />
[[File:Home Assistant Preview.jpg|thumb|alt=Home Assistant on Vivid Unit|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/ Home Assistant (Docker)] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-20240320.img.xz vivid-unit-v13-debian11-home-assistant-20240320.img.xz (1.39 GB)]<br />
<br />
''MD5: bb19226675b7bab9ff3900fdce0a7ce5''<br />
<br />
''SHA1: 070b4a8030a8924f277e992c76f9830db3fce47c''<br />
<br />
<br />
<br />
<br />
[[File:Home-Assistant-Supervised-Preview.jpg|alt=Home Assistant on Vivid Unit|thumb|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/installation/#advanced-installation-methods Home Assistant Supervised] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz (1.52 GB)]<br />
<br />
''MD5: 776435bdc297958f1a591787a0e48e02''<br />
<br />
''SHA1: 90019ab7b989b6bd2ba1911699d6c2c9a3413d70''<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
You can find more details about how to install system [[install-os|here]].</div>Adminhttps://www.vividunit.com:443/index.php?title=install-vuos&diff=721install-vuos2026-04-01T14:20:04Z<p>Admin: /* Re(install) Vivid Unit OS */</p>
<hr />
<div>= Re(install) Vivid Unit OS =<br />
Vivid Unit has eMMC storage onboard and the operating system (Debian with XFCE desktop enviroment) has been pre-installed in the eMMC. Usually you do not need to install operating system by yourself. However if the operating system corrupts or you want to install a different operating system (if available), you may follow this instructions.<br />
<br />
You may download the OS image from [[download-system-image|this page]]. The downloaded image is an img.xz file, and you need to extract it to get the .img file, which can be flashed into Vivid Unit.</div>Adminhttps://www.vividunit.com:443/index.php?title=install-vuos&diff=720install-vuos2026-04-01T14:18:02Z<p>Admin: Created page with "= Re(install) Vivid Unit OS = Vivid Unit has eMMC storage onboard and the operating system (Debian with XFCE desktop enviroment) has been pre-installed in the eMMC. Usually you do not need to install operating system by yourself. However if the operating system corrupts or you want to install a different operating system (if available), you may follow this instructions. You may download the OS image from this page."</p>
<hr />
<div>= Re(install) Vivid Unit OS =<br />
Vivid Unit has eMMC storage onboard and the operating system (Debian with XFCE desktop enviroment) has been pre-installed in the eMMC. Usually you do not need to install operating system by yourself. However if the operating system corrupts or you want to install a different operating system (if available), you may follow this instructions.<br />
<br />
You may download the OS image from [[download-system-image|this page]].</div>Adminhttps://www.vividunit.com:443/index.php?title=download-system-image&diff=719download-system-image2026-04-01T14:12:43Z<p>Admin: /* Debian */</p>
<hr />
<div>= Download OS Images =<br />
Vivid Unit comes with Debian operating system pre-installed, usually you don't need to install system by yourself.<br />
<br />
However if you want to re-install the system, or want to install a different system (if available), you can download the system disk image here.<br />
= Debian =<br />
[[File:vuos-desktop.png|alt=Debian 12 @ Vivid Unit|thumb|Vivid Unit OS Desktop Preview]]<br />
'''Vivid Unit OS (Debian 12 - Bookworm): version 20260327'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vuos-debian12-20260327-vivid-unit.img.xz vuos-debian12-20260327-vivid-unit.img.xz (400 MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: bf9f85abc9512b543708261d1ea6485f''<br />
<br />
''SHA1: 6c764ed1a90f7cdaacf338a1b90227ec4a0603bf''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
[[File:debian11 preview.jpg|alt=Debian 11 @ Vivid Unit|thumb|Desktop Preview|right]]<br />
'''Debian GNU/Linux 11 (bullseye)'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-20240129.img.xz vivid-unit-v13-debian11-20240129.img.xz (933 MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: b66ab31e21bec94ff5a1d0f98b54716b''<br />
<br />
''SHA1: 0f2be8a9670585808909da65c67e02869ad7c859''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
[[File:Debian11 Retropie preview.jpg|thumb|RetroPie Preview|alt=RetroPie on Vivid Unit]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://retropie.org.uk/ RetroPie] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-retropie-20240129.img.xz vivid-unit-v13-debian11-retropie-20240129.img.xz (1.06 GB)]<br />
<br />
<blockquote><br />
<br />
''MD5: 86dd3cd81e1474880b455dfc41b23792''<br />
<br />
''SHA1: cc1df6a419a53c6fb3b4b1d6b9e5417e759e20c8''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
<br />
[[File:Home Assistant Preview.jpg|thumb|alt=Home Assistant on Vivid Unit|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/ Home Assistant (Docker)] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-20240320.img.xz vivid-unit-v13-debian11-home-assistant-20240320.img.xz (1.39 GB)]<br />
<br />
''MD5: bb19226675b7bab9ff3900fdce0a7ce5''<br />
<br />
''SHA1: 070b4a8030a8924f277e992c76f9830db3fce47c''<br />
<br />
<br />
<br />
<br />
[[File:Home-Assistant-Supervised-Preview.jpg|alt=Home Assistant on Vivid Unit|thumb|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/installation/#advanced-installation-methods Home Assistant Supervised] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz (1.52 GB)]<br />
<br />
''MD5: 776435bdc297958f1a591787a0e48e02''<br />
<br />
''SHA1: 90019ab7b989b6bd2ba1911699d6c2c9a3413d70''<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
You can find more details about how to install system [[install-os|here]].</div>Adminhttps://www.vividunit.com:443/index.php?title=File:vuos-desktop.png&diff=718File:vuos-desktop.png2026-04-01T14:11:30Z<p>Admin: </p>
<hr />
<div></div>Adminhttps://www.vividunit.com:443/index.php?title=download-system-image&diff=717download-system-image2026-04-01T14:10:37Z<p>Admin: /* Debian */</p>
<hr />
<div>= Download OS Images =<br />
Vivid Unit comes with Debian operating system pre-installed, usually you don't need to install system by yourself.<br />
<br />
However if you want to re-install the system, or want to install a different system (if available), you can download the system disk image here.<br />
= Debian =<br />
[[File:debian11 preview.jpg|alt=Debian 11 @ Vivid Unit|thumb|Desktop Preview|right]]<br />
'''Vivid Unit OS (Debian 12 - Bookworm) ver-20260327'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vuos-debian12-20260327-vivid-unit.img.xz vuos-debian12-20260327-vivid-unit.img.xz (400 MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: bf9f85abc9512b543708261d1ea6485f''<br />
<br />
''SHA1: 6c764ed1a90f7cdaacf338a1b90227ec4a0603bf''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
[[File:debian11 preview.jpg|alt=Debian 11 @ Vivid Unit|thumb|Desktop Preview|right]]<br />
'''Debian GNU/Linux 11 (bullseye)'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-20240129.img.xz vivid-unit-v13-debian11-20240129.img.xz (933 MB)]<br />
<br />
<blockquote><br />
<br />
''MD5: b66ab31e21bec94ff5a1d0f98b54716b''<br />
<br />
''SHA1: 0f2be8a9670585808909da65c67e02869ad7c859''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
[[File:Debian11 Retropie preview.jpg|thumb|RetroPie Preview|alt=RetroPie on Vivid Unit]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://retropie.org.uk/ RetroPie] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-retropie-20240129.img.xz vivid-unit-v13-debian11-retropie-20240129.img.xz (1.06 GB)]<br />
<br />
<blockquote><br />
<br />
''MD5: 86dd3cd81e1474880b455dfc41b23792''<br />
<br />
''SHA1: cc1df6a419a53c6fb3b4b1d6b9e5417e759e20c8''<br />
<br />
</blockquote><br />
<br />
<br />
<br />
<br />
<br />
[[File:Home Assistant Preview.jpg|thumb|alt=Home Assistant on Vivid Unit|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/ Home Assistant (Docker)] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-20240320.img.xz vivid-unit-v13-debian11-home-assistant-20240320.img.xz (1.39 GB)]<br />
<br />
''MD5: bb19226675b7bab9ff3900fdce0a7ce5''<br />
<br />
''SHA1: 070b4a8030a8924f277e992c76f9830db3fce47c''<br />
<br />
<br />
<br />
<br />
[[File:Home-Assistant-Supervised-Preview.jpg|alt=Home Assistant on Vivid Unit|thumb|Home Assistant Preview]]<br />
'''Debian GNU/Linux 11 (bullseye) with [https://www.home-assistant.io/installation/#advanced-installation-methods Home Assistant Supervised] installed'''<br />
<br />
[https://www.vividunit.com/download/system/Debian/vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz vivid-unit-v13-debian11-home-assistant-supervised-20240405.img.xz (1.52 GB)]<br />
<br />
''MD5: 776435bdc297958f1a591787a0e48e02''<br />
<br />
''SHA1: 90019ab7b989b6bd2ba1911699d6c2c9a3413d70''<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
You can find more details about how to install system [[install-os|here]].</div>Adminhttps://www.vividunit.com:443/index.php?title=screen-and-touch-buttons&diff=716screen-and-touch-buttons2026-03-28T08:44:50Z<p>Admin: /* VSA (Vivid Screen Assistant) Usage */</p>
<hr />
<div>= Screen and Touch Buttons =<br />
Vivid Unit comes with a 5.5 inches touchscreen. The display area is 120mm x 67.5mm, and the resolution is 1280x720.<br />
<br />
<pic src="images/f/f9/Screen_Size.jpg" width="70%" align="text" caption=""></pic><br />
<br />
Aside the display area there are three touch buttons. You may have seen similar buttons on smart phone. In Vivid Unit, the functionality of these three buttons can be configured with the tool named VSA (Vivid Screen Assistant).<br />
<br />
=== VSA (Vivid Screen Assistant) Usage ===<br />
VSA is a pre-installed GUI tool that can help you to configure your screen and the touch buttons aside.<br />
<br />
You can run VSA by typing "vsa" in the command line terminal (in any directory will do), alternatively you can find VSA application in the Apllication menu -> System category.<br />
<br />
<pic src="images/d/df/vsaw-204-1.png" width="50%" align="text" caption=""></pic><br />
<br />
By default the "Screen" tab is selected and there are 4 big buttons on top of the window. You may click any of these button to set the orientation of your screen.<br />
<br />
You can also adjust the brightness of the screen here.<br />
<br />
If you click the "Touch Buttons" tab, you switch to the tab for configuring those touch buttons.<br />
<br />
<pic src="images/7/74/vsaw-204-2.png" width="50%" align="text" caption=""></pic><br />
<br />
Here you can define the behavior of each touch button. It can send a hotkey (emulate pressing a key on keyboard), or run a command.<br />
<br />
In the older version (1.x.x) of VSA, the default behavior of these three touch buttons are:<br />
<br />
* '''Button ☰:''' Open command line terminal (Hotkey: CTRL+ALT+t)<br />
* '''Button ○:''' Open web browser (Hotkey Scan Code =180)<br />
* '''Button ❮:''' Bring up the desktop / minimize current application (Hotkey: CTRL+ALT+d)<br />
In the newer version (2.x.x) of VSA, the default behavior of touch buttons are changed to:<br />
* '''Button ☰:''' Paste content (Hotkey: CTRL+v)<br />
* '''Button ○:''' Bring up the desktop / minimize current application (Hotkey: CTRL+ALT+d)<br />
* '''Button ❮:''' Copy content or terminate current command(Hotkey: CTRL+c)<br />
Also the newer version has the gesture support built-in:<br />
<br />
* '''Single-finger long press:''' Right-click<br />
* '''Single-finger clockwise circle:''' Open the magnifier<br />
* '''Single-finger counter-clockwise circle:''' Close the magnifier<br />
* '''Two-finger swipe up:''' Show the Onboard on-screen keyboard<br />
* '''Two-finger swipe down:''' Hide the Onboard on-screen keyboard<br />
* '''Three-finger tap:''' Toggle local IP address display<br />
* '''Three-finger drag:''' Move the active window</div>Adminhttps://www.vividunit.com:443/index.php?title=screen-and-touch-buttons&diff=715screen-and-touch-buttons2026-03-28T08:43:07Z<p>Admin: /* VSA (Vivid Screen Assistant) Usage */</p>
<hr />
<div>= Screen and Touch Buttons =<br />
Vivid Unit comes with a 5.5 inches touchscreen. The display area is 120mm x 67.5mm, and the resolution is 1280x720.<br />
<br />
<pic src="images/f/f9/Screen_Size.jpg" width="70%" align="text" caption=""></pic><br />
<br />
Aside the display area there are three touch buttons. You may have seen similar buttons on smart phone. In Vivid Unit, the functionality of these three buttons can be configured with the tool named VSA (Vivid Screen Assistant).<br />
<br />
=== VSA (Vivid Screen Assistant) Usage ===<br />
VSA is a pre-installed GUI tool that can help you to configure your screen and the touch buttons aside.<br />
<br />
You can run VSA by typing "vsa" in the command line terminal (in any directory will do), alternatively you can find VSA application in the Apllication menu -> System category.<br />
<br />
<pic src="images/d/df/vsaw-204-1.png" width="50%" align="text" caption=""></pic><br />
<br />
By default the "Screen" tab is selected and there are 4 big buttons on top of the window. You may click any of these button to set the orientation of your screen.<br />
<br />
You can also adjust the brightness of the screen here.<br />
<br />
If you click the "Touch Buttons" tab, you switch to the tab for configuring those touch buttons.<br />
<br />
<pic src="images/7/74/vsaw-204-2.png" width="50%" align="text" caption=""></pic><br />
<br />
Here you can define the behavior of each touch button. It can send a hotkey (emulate pressing a key on keyboard), or run a command.<br />
<br />
In the older version (1.x.x) of VSA, the default behavior of these three touch buttons are:<br />
<br />
* Button ☰: Open command line terminal (Hotkey: CTRL+ALT+t)<br />
* Button '''○''': Open web browser (Hotkey Scan Code =180)<br />
* Button ❮: Bring up the desktop / minimize current application (Hotkey: CTRL+ALT+d)<br />
In the newer version (2.x.x) of VSA, the default behavior of touch buttons are changed to:<br />
* Button ☰: Paste content (Hotkey: CTRL+v)<br />
* Button '''○''': Bring up the desktop / minimize current application (Hotkey: CTRL+ALT+d)<br />
* Button ❮: Copy content or terminate current command(Hotkey: CTRL+c)<br />
Also the newer version brings the gesture support:<br />
<br />
* '''Single-finger long press:''' Right-click<br />
* '''Single-finger clockwise circle:''' Open the magnifier<br />
* '''Single-finger counter-clockwise circle:''' Close the magnifier<br />
* '''Two-finger swipe up:''' Show the Onboard on-screen keyboard<br />
* '''Two-finger swipe down:''' Hide the Onboard on-screen keyboard<br />
* '''Three-finger tap:''' Toggle local IP address display<br />
* '''Three-finger drag:''' Move the active window</div>Adminhttps://www.vividunit.com:443/index.php?title=screen-and-touch-buttons&diff=714screen-and-touch-buttons2026-03-28T08:42:52Z<p>Admin: /* Screen and Touch Buttons */</p>
<hr />
<div>= Screen and Touch Buttons =<br />
Vivid Unit comes with a 5.5 inches touchscreen. The display area is 120mm x 67.5mm, and the resolution is 1280x720.<br />
<br />
<pic src="images/f/f9/Screen_Size.jpg" width="70%" align="text" caption=""></pic><br />
<br />
Aside the display area there are three touch buttons. You may have seen similar buttons on smart phone. In Vivid Unit, the functionality of these three buttons can be configured with the tool named VSA (Vivid Screen Assistant).<br />
<br />
=== VSA (Vivid Screen Assistant) Usage ===<br />
VSA is a pre-installed GUI tool that can help you to configure your screen and the touch buttons aside.<br />
<br />
You can run VSA by typing "vsa" in the command line terminal (in any directory will do), alternatively you can find VSA application in the Apllication menu -> System category.<br />
<br />
<pic src="images/d/df/vsaw-204-1.png" width="50%" align="text" caption=""></pic><br />
<br />
By default the "Screen" tab is selected and there are 4 big buttons on top of the window. You may click any of these button to set the orientation of your screen.<br />
<br />
You can also adjust the brightness of the screen here.<br />
<br />
If you click the "Touch Buttons" tab, you switch to the tab for configuring those touch buttons.<br />
<br />
<pic src="images/7/74/vsaw-204-2.png" width="50%" align="text" caption=""></pic><br />
<br />
Here you can define the behavior of each touch button. It can send a hotkey (emulate pressing a key on keyboard), or run a command.<br />
<br />
In the older version (1.x.x) of VSA, the default behavior of these three touch buttons are:<br />
<br />
* Button ☰: Open command line terminal (Hotkey: CTRL+ALT+t)<br />
* Button '''○''': Open web browser (Hotkey Scan Code =180)<br />
* Button ❮: Bring up the desktop / minimize current application (Hotkey: CTRL+ALT+d)<br />
In the newer version (2.x.x) of VSA, the default behavior of touch buttons are changed to:<br />
* Button ☰: Paste content (Hotkey: CTRL+v)<br />
* Button '''○''': Bring up the desktop / minimize current application (Hotkey: CTRL+ALT+d)<br />
* Button ❮: Copy content or terminate current command(Hotkey: CTRL+c)<br />
Also the newer version brings the gesture support:<br />
<br />
* '''Single-finger long press:''' Right-click<br />
* '''Single-finger clockwise circle:''' Open the magnifier<br />
* '''Single-finger counter-clockwise circle:''' Close the magnifier<br />
* '''Two-finger swipe up:''' Show the Onboard on-screen keyboard<br />
* '''Two-finger swipe down:''' Hide the Onboard on-screen keyboard<br />
* '''Three-finger tap:''' Toggle local IP address display<br />
<br />
* '''Three-finger drag:''' Move the active window</div>Adminhttps://www.vividunit.com:443/index.php?title=gpio-and-adc&diff=713gpio-and-adc2026-03-28T08:34:56Z<p>Admin: </p>
<hr />
<div>= '''GPIO and ADC''' =<br />
<br />
== '''What is GPIO?''' ==<br />
GPIO stands for Gerneral Purpose Input/Ouput. It usually refers to a set of pins on your computer’s mainboard or add-on boards. These pins are not designed for any specific purpose, and they can send or receive electrical signals.<br />
<br />
== '''What is ADC?''' ==<br />
ADC stands for analog-to-digital converter. It is a system that converts an analog signal into a digital signal. It can be used to measure voltage and give the numberic result.<br />
<br />
== '''GPIO and ADC on Vivid Unit''' ==<br />
<br />
=== '''GPIO''' ===<br />
Vivid Unit comes with a 40-pin GPIO header, whose pinout is compatible with Raspberry Pi. There are two 5V power pins, two 3.3V power pins and 8 ground pins. The rest are I/O pins and they are all at 3.3V level.<br />
<br />
The GPIOs are provided by RK3399, which has 5 banks (GPIO0 to GPIO4). Each bank has 4 groups (A, B, C and D) and each group has 8 pins (number 0~7). That makes 160 GPIOs in total, but only partial of them are routed to the 40-pin GPIO header.<br />
<br />
<pic src="images/1/16/The_40-pin_header_on_Vivid_Unit.png" width="100%" align="text" caption=""></pic><br />
<br />
The GPIOs are named like these:<br />
<br />
<pic src="images/b/be/vivid_unit_gpio_naming.png" width="100%" align="text" caption=""></pic><br />
<br />
For the simplicity we use a short GPIO name for each GPIO pin. We put the bank number, the group name and the pin number in group together, to make the GPIO name.<br />
<br />
[[File:Gpio short name.png]]<br />
<br />
For example, 2B5 is for GPIO2_B5, and 3C6 is for GPIO3_C6.<br />
<br />
=== '''ADC''' ===<br />
Vivid Unit also provides three 10-bit ADC channels (A0, A3 and A4). RK3399 provides ADC with 1.8V full-scale voltage, and Vivid Unit adds voltage divider and protection circuit (as shown below), to increase the full-scale voltage to 5V. The final resolution is 4.88mV.<br />
<br />
[[File:Adc.png]]<br />
<br />
It is safe to connect A0, A3 or A4 channel to any pin in the 40-pin GPIO header, because they can measure voltage up to 5V. If you want to measure voltage higher than 5V, you will need to implement an additional voltage divider.<br />
<br />
[https://www.instructables.com/Measure-Low-Higher-and-Negative-Voltages-With-Vivi This tutorial] covers how to measure higher or negative voltage with Vivid Unit.<br />
<br />
<br />
== '''VGP Utility''' ==<br />
VGP is an open-sourced application to control or monitor GPIOs and ADC channels on Vivid Unit. It contains two executables, one for command line interface (vgp) and the other for GUI enviroment (vgpw).<br />
<br />
VGP is by default installed into the system. If it is not, you can always install it with:<blockquote><br />
sudo apt update<br />
<br />
sudo apt install vgp<br />
</blockquote><br />
<br />
=== '''VGP in CLI (Command Line Interface)''' ===<br />
<br />
==== '''Overview of 40-Pin''' ====<br />
If you want to get an overview of the GPIOs in the 40-pin header, you can run:<blockquote><br />
vgp list<br />
</blockquote>It will list the GPIO information in a format that similar to the wiringPi:<br />
<br />
[[File:Gpio list-600x523.png]]<br />
<br />
The value and voltage of all ADC channels are also printed at the bottom.<br />
<br />
==== '''List All GPIOs''' ====<br />
If you want to list all GPIOs, even including those pins that are not brought out to the 40-pin header. You can run:<blockquote><br />
vgp all<br />
</blockquote>It will list the name, alternate function, value and mode for all GPIO pins:<br />
<br />
[[File:Gpio all-259x300.jpg]]<br />
<br />
==== '''Get Pin Mode''' ====<br />
If you want to get the current mode of a specifi pin, you can use:<blockquote><br />
vgp mode [pin]<br />
</blockquote>Here [pin] should be replaced with the GPIO name or physical pin number.<br />
<br />
The result could be “IN” or “OUT”.<br />
<br />
==== '''Set Pin Mode''' ====<br />
If you want to set the mode of a specific pin, you can use:<blockquote><br />
vgp mode [pin] [mode]<br />
</blockquote>Here [pin] should be replaced with the GPIO name or physical pin number, and [mode] should be one of these value:<br />
<br />
* IN<br />
* in<br />
* INPUT<br />
* input<br />
* OUT<br />
* out<br />
* OUTPUT<br />
* output<br />
<br />
The “IN”, “in”, “INPUT” and “input” are the same, while the “OUT”, “out”, “OUTPUT” and “output” are the same.<br />
<br />
==== '''Get Pin Alternative Function''' ====<br />
The same physical pin can be configured to different alternative function. A pin can have up to 4 alternative functions (ALT0 ~ ALT3), and ALT0 is the default one. You can get the current alternative function for specific pin with:<blockquote><br />
vgp alt [pin]<br />
</blockquote>Here [pin] should be replaced with the GPIO name or physical pin number.<br />
<br />
The result can be 0, 1, 2 or 3, which means ALT0, ALT1, ALT2, ALT3 accordingly.<br />
<br />
==== '''Set Pin Alternative Function''' ====<br />
You can also set alternative function for specific pin with:<blockquote><br />
vgp alt [pin] [alt]<br />
</blockquote>Here [pin] should be replaced with the GPIO name or physical pin number, and [alt] should be replaced with the alternative function (0, 1, 2 or 3).<br />
<br />
==== '''Get Pin Value''' ====<br />
To get value for given pin, you can use:<blockquote><br />
vgp get [pin]<br />
</blockquote>Here [pin] should be replaced with the GPIO name or physical pin number.<br />
<br />
The result could be 1 (high) or 0 (low).<br />
<br />
==== '''Set Pin Value''' ====<br />
To set value for given pin, you may use:<blockquote><br />
vgp set [pin] [value]<br />
</blockquote>Here [pin] should be replaced with the GPIO name or physical pin number, and [value] should be 1 or 0.<br />
<br />
==== '''Wait for Interrupt''' ====<br />
If you wish to monitor the state of given pin, you may use:<blockquote><br />
vpg wfi [pin] [edge]<br />
</blockquote>Here [pin] should be replaced with the GPIO name or physical pin number, and [edge] should be rising, falling or both.<br />
<br />
This command will block until the state of the pin changes.<br />
<br />
==== '''ADC''' ====<br />
You can read the ADC result at specific chanel with:<blockquote><br />
vpg adc [channel]<br />
</blockquote>Here [channel] should be 0 (for A0), 3 (for A3) or 4 (for A4). The result is a number (0~1023).<br />
<br />
If you want to get voltage value, you may use:<blockquote><br />
vpg adc [channel] v<br />
</blockquote>By adding a lower case letter v as the last argument, this command prints out the voltage value (for example 4.21).<br />
<br />
If you want to print out the voltage value with the unit (V) together, you may use:<blockquote><br />
vgp adc [channel] V<br />
</blockquote>By adding an upper case letter V as the last argument, this command prints out the voltage value with unit (for example 4.21V).<br />
<br />
==== '''Get Help Information''' ====<br />
If you need help during usage, you can run this command to get help information:<blockquote><br />
vgp --help<br />
</blockquote><br />
<br />
=== '''VGP in GUI (Graphical User Interface)''' ===<br />
You may run the GUI version of VGP via the "System" category in Applications Menu.<br />
<br />
[[File:run-vgpw.jpg]]<br />
<br />
You may also run “vgpw” in command line terminal to launch the same GUI application.<br />
<br />
You will see the interface that represents the 40-pin header:<br />
<br />
<pic src="images/a/ad/vgpw-202-1.png" width="100%" align="text" caption=""></pic><br />
<br />
The value of three ADC channels are also listed at the bottom, including the raw values (0~1023) and the voltage values. These values refresh for every second.<br />
<br />
There is a “Flip” button at the bottom right corner, and you can click it to flip the view.<br />
<br />
You can click the mode button for each pin to change its mode or alternative function. The possilbe mode/funtion could be IN, OUT, ALT1, ALT2 or ALT3.<br />
<br />
When the mode is set to OUT, you may click the value button to toggle the pin’s value.<br />
<br />
When the mode is set to IN, its value will get updated automatically when the pin is pulled up or down.</div>Adminhttps://www.vividunit.com:443/index.php?title=File:run-vgpw.jpg&diff=712File:run-vgpw.jpg2026-03-28T08:30:18Z<p>Admin: </p>
<hr />
<div></div>Adminhttps://www.vividunit.com:443/index.php?title=File:vgpw-202-1.png&diff=711File:vgpw-202-1.png2026-03-27T14:58:32Z<p>Admin: </p>
<hr />
<div></div>Adminhttps://www.vividunit.com:443/index.php?title=File:vsaw-204-2.png&diff=710File:vsaw-204-2.png2026-03-27T14:57:04Z<p>Admin: </p>
<hr />
<div></div>Admin