# Hardware

# Does the URVE BOARD Pi have a built-in microphone?

Yes, the computer has a built-in microphone.

# Why does the clock (RTC) consume a battery?

A battery-powered clock ensures that the time is kept when there is no power and no network connection. Otherwise, it would behave like the Raspberry Pi - the time will deviate from the actual time when the device is off.

# Is there a reset button/pin/pad?

We don't have a reset button/pin/pad. Only removing the cable from microUSB.

# What is the energy consumption?

URVE Board Pi consumes approximately 2W when idle. At medium load, the consumption is at 4W.

# Does the clock (RTC) use any pins?

No, it doesn't.

# What is the reason for temperature range limitation (0-70°C). Are you planning any developments for industrial scopes?

The temperature range is the result of the use of components (RAM, eMMC, CPU). We are not planning an industrial version. The URVEBoard A55 we are working on will have an industrial variant based on the RK3568 processor (equivalent to the 3566, but industrial).

# Are there URVE Pi versions with more memory than 8GB?

Only for the right OQ (order quantity).

# URVEPi Hardware Benchmark

## URVEPi eMMC/USB2/USB3

URVEPi is a competitive single-board computer that boasts impressive performance, outpacing the popular Raspberry Pi in sequential read/write speed. With its fast read/write speeds, URVEPi is well-suited for a wide range of applications, from data-intensive tasks to multimedia streaming. Additionally, URVEPi offers a variety of connectivity options and expansion interfaces, making it a versatile and powerful option for hobbyists and professionals alike.

<table id="bkmrk-device-interface-cap"><thead><tr><th>Device</th><th>Interface</th><th>Capacity</th><th>Seq Read Speed</th><th>Command</th></tr></thead><tbody><tr><td>eMMC (built-in storage)</td><td></td><td>8GB</td><td>145.01 MB/sec</td><td>hdparm -t --direct /dev/mmcblk0</td></tr><tr><td>Kingston 16GB USB 2.0 flash drive</td><td>USB 2.0</td><td>16GB</td><td>24.40 MB/sec</td><td>hdparm -t --direct /dev/sda</td></tr><tr><td>SanDisk 64GB USB 3.0 flash drive</td><td>USB 2.0</td><td>64GB</td><td>30.13 MB/sec</td><td>hdparm -t --direct /dev/sda</td></tr><tr><td>SanDisk 64GB USB 3.0 flash drive</td><td>USB 3.0</td><td>64GB</td><td>150.95 MB/sec</td><td>hdparm -t --direct /dev/sda</td></tr><tr><td>SanDisk 256GB USB 3.0 flash drive</td><td>USB 3.0</td><td>256GB</td><td>262.00 MB/sec</td><td>hdparm -t --direct /dev/sda</td></tr><tr><td>Unbranded SD Card</td><td>SD</td><td>32GB</td><td>22.240 MB/sec</td><td>hdparm -t --direct /dev/mmcblk1</td></tr></tbody></table>

It's worth mentioning that the same "Unbranded SD Card" benchmarked with "hdparm -t --direct /dev/mmcblk0" on Raspberry Pi 3 achieved a transfer rate 2MB/sec lower than when inserted into URVEPi.