1 Boardcon EM3566 SBC

Contents

1.1 Board Overview

Boardcon EM3566 single board computer (SBC) features 2 GiB memory (up to 8 GiB), comes with MIPI/LVDS, HDMI and eDP video out, and offers Gigabit Ethernet port, as well as M.2 socket which enables expansion with a large hard drive and plus a miniPCIe, a Nano SIM card socket for 4G cellular connectivity. Display and camera capabilities with graphics and video hardware acceleration make it suitable for machine vision applications. And built-in independent NPU, computing power of 0.8 TOPS for AI accelerator extend the reach of AI solutions. EM3566 supports microphone array input, with high dynamic noise reduction algorithm, it can accurately recognize human voices even in noisy environments, and achieve precise voice control of the devices.

1.1.1 Photos

Fig. 1.38 Boardcon EM3566 front with an angle view

Fig. 1.39 Boardcon EM3566 top view

Fig. 1.40 Boardcon EM3566 back view

1.1.2 Specification

Table 1.20 Boardcon EM3566 Specification

Model	Boardcon EM3566
Processor	SoC Rockchip RK3566 Quad Cortex-A55 ARM 64 bits processor frequency up to 1.8 GHz
GPU	ARM Mali-G52 2EE GPU with support for OpenGL ES 1.1/2.0/3.2, OpenCL 2.0, Vulkan 1.1, 4Kp60 H.265/H.264/VP9 video decoder
NPU	0.8 TOPS
Memory	2 GiB, 4 GiB or 8 GiB LPDDR4
Storage	microSD(TF) 8 GiB eMMC flash (up to 128 GiB) M.2 PCIe 2.0 socket NVMe SSD SATA 3.0 (optional SATA 3.0 and USB 3.0 share the signal, switch with SW1)
Wireless	802.11 b/g/n WiFi Bluetooth 4.2 External antenna
Connectivity	PCIe socket with Nano SIM card port to support 4G/GPS module
USB	1 × USB OTG 2.0 4 × USB Host 2.0 (USB-AF or 4-pin connector) 1 × USB 3.0
Ethernet	1 × Gigabit Ethernet RJ45 ports (Realtek RTL8211F-CG controller)
Serial	1 × Serial port for debug (3-pin connector) 2 × UART (4-pin connectors) 1 × RS485 (2-pin header or 3-pin connector)
Video	HDMI 2.0, 4Kp60 MIPI DSI/LVDS, 1080p60 (40-pin header) eDP 1.3, 2560x1600@60Hz (30-pin header)
Audio	3.5 mm audio I/O jack, ES8388 audio codec 8-channel audio via HDMI
Camera (optional)	2 × Cameras via MIPI CSI (24-pin FPC connector)
Keys	1 × Recovery 1 × Switch for switch between SATA 3.0 and USB 3.0
Other Features	RTC with battery connector GPIO IR Receiver ADC
Power	12V/3A DC input jack
Dimensions	Base board: 135 mm × 95 mm CPU module: 40 mm × 47 mm

1.2 Build Targets

1.2.1 Machines

Table 1.21 Supported Machines

Board[1]	Target YAML[2]	Machine[3]	Target Recipe(s)[4]	Running Media[5]	Installation Media[6]
Boardcon EM3566	boardcon-em3566-sd.yml	boardcon-em3566-sd	tanowrt-image-full-swu	microSD card	–
	boardcon-em3566-emmc.yml	boardcon-em3566-emmc	tanowrt-image-full-swu-factory	internal eMMC	microSD card

[1]

Target board.

[2]

Target YAML-file located in the kas/targets directory.

[3]

Target machine name stored in the MACHINE BitBake variable for selected Target YAML.

[4]

Recipes that will be built by default for the target. In Section 1.2.2, you can find list of supported recipes for the target images, which you can build in addition to the default recipes using optional --target option in build command (see Section 1.3).

[5]

External or internal data storage where the TanoWrt operating system is running.

[6]

External storage device for which an installation image is generated. When booting from the Installation Media, the TanoWrt system is installed on the Running Media storage.

1.2.2 Images

Table 1.22 Supported Images

Read-Only Root Filesystem Image	Recipe[7]	Supported by Target(s)	Description
tanowrt-image-full	tanowrt-image-full	All	Standard TanoWrt image.
	tanowrt-image-full-swu	All	Standard TanoWrt image and firmware upgrade image. When building this image, tanowrt-image-full will also be built as dependency.
	tanowrt-image-full-swu-factory	boardcon-em3566-emmc.yml	Factory installation image for standard TanoWrt image. When building this image, tanowrt-image-full and tanowrt-image-full-swu will also be built as dependencies.

[7]

Image recipe name. This name can be used as argument for --target build command option (see Section 1.3 section).

1.3 Build

Please read the common information on how to perform a TanoWrt images build and preparing the build environment in section “Building TanoWrt”.

See also

• See section Section 1.2.1 to select the required target YAML file (<target-yml>).

• See section Section 1.2.2 to select the required root filesystem image recipe (<target-recipe>).

• See section Section 1.5 for detailed information about the produced build artifacts.

1.3.1 Examples

1.3.1.1 Build Default Images for Boardcon EM3566 Board

For microSD Card

$ kas build targets/kas/boardcon-em3566-sd.yml

Default images will be produced to boot and run from the microSD card on the Boardcon EM3566 target board.

For Internal eMMC Flash

$ kas build targets/kas/boardcon-em3566-emmc.yml

An initial factory installation image will be generated, intended to run from the microSD card. The installer image will install the default image to the internal eMMC flash memory and further the Boardcon EM3566 board will boot and run from the eMMC flash memory.

1.4 Partitioning Layouts

Images for Boardcon EM3566 board using default partitions layouts described here.

1.5 Produced Build Artifacts

All produced build artifacts are stored in the ~/tanowrt/build/tanowrt-glibc/deploy/images/<MACHINE> directory. Refer to table Produced Build Artifacts for a description of some common (not all) build artifacts.

Table 1.23 Produced Build Artifacts

Artifact	Target(s)	Description
Bootloader
idblock.img-<MACHINE>-sdcard	All	Rockchip IDBLOCK image for booting from SD card.
idblock.img-<MACHINE>-emmc	boardcon-em3566-emmc.yml	Rockchip IDBLOCK image for booting from internal eMMC.
Bootloader (U-Boot)
startup-<MACHINE>.img	All	U-Boot startup script.
startup-factory-<MACHINE>.img	boardcon-em3566-emmc.yml	U-Boot startup script for factory installation image.
u-boot-initial-env-<MACHINE>-sdcard	All	U-Boot initial environment image for SD card image.
u-boot-initial-env-<MACHINE>-emmc	boardcon-em3566-emmc.yml	U-Boot initial environment image for internal eMMC flash.
u-boot-<MACHINE>.bin-sdcard	All	U-Boot binary image for booting from SD card.
u-boot-<MACHINE>.bin-emmc	boardcon-em3566-emmc.yml	U-Boot binary image for booting from internal eMMC flash.
Linux Kernel and DTB
fitImage-<MACHINE>.bin	All	Flattened Image Tree (FIT) image with Linux kernel and Device Tree Blobs (DTB).
fitImage-<MACHINE>.ext4	All	FIT image packed into an ext4 file system image.
boardcon-em3566-<MACHINE>.dtb	All	Target Device Tree Blob (DTB).
Images
<rootfs-image>-<MACHINE>.sdcard.img	boardcon-em3566-sd.yml	SD card image including all required partitions for booting and running the system. This image is ready to be written to the SD card using the dd utility or similar (see Writing Images).
<rootfs-image>-swu-factory-<MACHINE>.sdcard.img	boardcon-em3566-emmc.yml	SD card factory installation image. This image is ready to be written to the SD card using the dd utility or similar (see Writing Images).
<rootfs-image>-<MACHINE>.squashfs-lzo	All	Root filesystem image (squashfs with LZO compression).
<rootfs-image>-swu-<MACHINE>.swu	All	Firmware upgrade image.

Note

<MACHINE> in the artifacts path and artifact file names are replaced by the actual value of the MACHINE BitBake variable for the chosen target. <rootfs-image> is replaced by the actual read-only root filesystem image name.

For example, below is the complete list of artifacts produced by the boardcon-em3566-sd.yml target build.

[~/tanowrt/build/tanowrt-glibc/deploy/images/boardcon-em3566-sd]$ ls -gGh
total 311M
-rw-r--r-- 2 105K Jul 20 06:00 boardcon-em3566--4.19.219+git0+40b753b965-tano2.2.20.20.1.8-boardcon-em3566-sd-20220720025543.dtb
lrwxrwxrwx 2   97 Jul 20 06:00 boardcon-em3566-boardcon-em3566-sd.dtb -> boardcon-em3566--4.19.219+git0+40b753b965-tano2.2.20.20.1.8-boardcon-em3566-sd-20220720025543.dtb
lrwxrwxrwx 2   97 Jul 20 06:00 boardcon-em3566.dtb -> boardcon-em3566--4.19.219+git0+40b753b965-tano2.2.20.20.1.8-boardcon-em3566-sd-20220720025543.dtb
lrwxrwxrwx 2   90 Jul 20 06:00 fitImage -> fitImage--4.19.219+git0+40b753b965-tano2.2.20.20.1.8-boardcon-em3566-sd-20220720025543.bin
-rw-r--r-- 2 9.0M Jul 20 06:00 fitImage--4.19.219+git0+40b753b965-tano2.2.20.20.1.8-boardcon-em3566-sd-20220720025543.bin
-rw-r--r-- 2  12M Jul 20 06:00 fitImage-4.19.219+gitAUTOINC+40b753b965-tano2.2.20.20.1.8-boardcon-em3566-sd.ext4
lrwxrwxrwx 2   90 Jul 20 06:00 fitImage-boardcon-em3566-sd.bin -> fitImage--4.19.219+git0+40b753b965-tano2.2.20.20.1.8-boardcon-em3566-sd-20220720025543.bin
-rw-r--r-- 2  12M Jul 20 06:00 fitImage-boardcon-em3566-sd.ext4
-rw-r--r-- 2 1.6K Jul 20 06:00 fitImage-its--4.19.219+git0+40b753b965-tano2.2.20.20.1.8-boardcon-em3566-sd-20220720025543.its
lrwxrwxrwx 2   94 Jul 20 06:00 fitImage-its-boardcon-em3566-sd -> fitImage-its--4.19.219+git0+40b753b965-tano2.2.20.20.1.8-boardcon-em3566-sd-20220720025543.its
-rw-r--r-- 2 8.9M Jul 20 06:00 fitImage-linux.bin--4.19.219+git0+40b753b965-tano2.2.20.20.1.8-boardcon-em3566-sd-20220720025543.bin
lrwxrwxrwx 2  100 Jul 20 06:00 fitImage-linux.bin-boardcon-em3566-sd -> fitImage-linux.bin--4.19.219+git0+40b753b965-tano2.2.20.20.1.8-boardcon-em3566-sd-20220720025543.bin
lrwxrwxrwx 2   78 Jul 20 05:56 idblock.img-boardcon-em3566-sd-sdcard -> idblock.img-boardcon-em3566-sd-sdcard-2017.09+gitAUTOINC+e3ca3c3805_fe66a9be19
-rwxr-xr-x 2 294K Jul 20 05:56 idblock.img-boardcon-em3566-sd-sdcard-2017.09+gitAUTOINC+e3ca3c3805_fe66a9be19
lrwxrwxrwx 2   77 Jul 20 05:56 loader.bin-boardcon-em3566-sd-sdcard -> loader.bin-boardcon-em3566-sd-sdcard-2017.09+gitAUTOINC+e3ca3c3805_fe66a9be19
-rwxr-xr-x 2 453K Jul 20 05:56 loader.bin-boardcon-em3566-sd-sdcard-2017.09+gitAUTOINC+e3ca3c3805_fe66a9be19
-rw-r--r-- 2  50M Jul 20 06:00 modules--4.19.219+git0+40b753b965-tano2.2.20.20.1.8-boardcon-em3566-sd-20220720025543.tgz
lrwxrwxrwx 2   89 Jul 20 06:00 modules-boardcon-em3566-sd.tgz -> modules--4.19.219+git0+40b753b965-tano2.2.20.20.1.8-boardcon-em3566-sd-20220720025543.tgz
lrwxrwxrwx 2   11 Jun  8 03:04 startup-boardcon-em3566-sd.img -> startup.img
lrwxrwxrwx 2   19 Jun  8 03:04 startup-boardcon-em3566-sd.img.version -> startup.img.version
-rw-r--r-- 2 2.2K Jun  8 03:04 startup.img
-rw-r--r-- 2   16 Jun  8 03:04 startup.img.version
-rw-r--r-- 2  55K Jul 20 10:44 tanowrt-image-full-boardcon-em3566-sd-20220720074256.rootfs.manifest
-rw-r--r-- 2 945M Jul 20 10:45 tanowrt-image-full-boardcon-em3566-sd-20220720074256.rootfs.sdcard.img
-rw-r--r-- 2  47M Jul 20 10:44 tanowrt-image-full-boardcon-em3566-sd-20220720074256.rootfs.squashfs-lzo
-rw-r--r-- 2   24 Jul 20 10:45 tanowrt-image-full-boardcon-em3566-sd-20220720074256.rootfs.version
-rw-r--r-- 2 393K Jul 20 10:44 tanowrt-image-full-boardcon-em3566-sd-20220720074256.testdata.json
lrwxrwxrwx 2   68 Jul 20 10:44 tanowrt-image-full-boardcon-em3566-sd.manifest -> tanowrt-image-full-boardcon-em3566-sd-20220720074256.rootfs.manifest
lrwxrwxrwx 2   70 Jul 20 10:45 tanowrt-image-full-boardcon-em3566-sd.sdcard.img -> tanowrt-image-full-boardcon-em3566-sd-20220720074256.rootfs.sdcard.img
lrwxrwxrwx 2   72 Jul 20 10:44 tanowrt-image-full-boardcon-em3566-sd.squashfs-lzo -> tanowrt-image-full-boardcon-em3566-sd-20220720074256.rootfs.squashfs-lzo
lrwxrwxrwx 2   66 Jul 20 10:44 tanowrt-image-full-boardcon-em3566-sd.testdata.json -> tanowrt-image-full-boardcon-em3566-sd-20220720074256.testdata.json
lrwxrwxrwx 2   67 Jul 20 10:45 tanowrt-image-full-boardcon-em3566-sd.version -> tanowrt-image-full-boardcon-em3566-sd-20220720074256.rootfs.version
-rw-r--r-- 2 5.3K Jul 20 10:44 tanowrt-image-full.env
-rw-r--r-- 2 2.3K Jul 20 10:44 tanowrt-image-full-sdimage-rockchip-swu-a-b.wks
-rw-r--r-- 2  61M Jul 20 10:45 tanowrt-image-full-swu-boardcon-em3566-sd-20220720074256.swu
lrwxrwxrwx 2   60 Jul 20 10:45 tanowrt-image-full-swu-boardcon-em3566-sd.swu -> tanowrt-image-full-swu-boardcon-em3566-sd-20220720074256.swu
lrwxrwxrwx 2   64 Jul 20 05:56 u-boot-boardcon-em3566-sd.bin -> u-boot-sdcard-2017.09+gitAUTOINC+e3ca3c3805_fe66a9be19-tano8.bin
lrwxrwxrwx 2   64 Jul 20 05:56 u-boot-boardcon-em3566-sd.bin-sdcard -> u-boot-sdcard-2017.09+gitAUTOINC+e3ca3c3805_fe66a9be19-tano8.bin
lrwxrwxrwx 2   91 Jul 20 05:56 u-boot-initial-env-boardcon-em3566-sd-sdcard -> u-boot-initial-env-boardcon-em3566-sd-sdcard-2017.09+gitAUTOINC+e3ca3c3805_fe66a9be19-tano8
-rw-r--r-- 2  468 Jul 20 05:56 u-boot-initial-env-boardcon-em3566-sd-sdcard-2017.09+gitAUTOINC+e3ca3c3805_fe66a9be19-tano8
-rw-r--r-- 2  32K Jul 20 05:56 u-boot-initial-env-boardcon-em3566-sd-sdcard-2017.09+gitAUTOINC+e3ca3c3805_fe66a9be19-tano8.bin
lrwxrwxrwx 2   95 Jul 20 05:56 u-boot-initial-env-boardcon-em3566-sd-sdcard.bin -> u-boot-initial-env-boardcon-em3566-sd-sdcard-2017.09+gitAUTOINC+e3ca3c3805_fe66a9be19-tano8.bin
lrwxrwxrwx 2   91 Jul 20 05:56 u-boot-initial-env-sdcard -> u-boot-initial-env-boardcon-em3566-sd-sdcard-2017.09+gitAUTOINC+e3ca3c3805_fe66a9be19-tano8
lrwxrwxrwx 2   95 Jul 20 05:56 u-boot-initial-env-sdcard.bin -> u-boot-initial-env-boardcon-em3566-sd-sdcard-2017.09+gitAUTOINC+e3ca3c3805_fe66a9be19-tano8.bin
-rw-r--r-- 2 2.0M Jul 20 05:56 u-boot-sdcard-2017.09+gitAUTOINC+e3ca3c3805_fe66a9be19-tano8.bin

1.6 Writing Images

1.6.1 Writing Image to microSD Card

No special information about writing images to microSD card for Boardcon EM3566 board. See common instructions in Writing Images to SD Card or USB Flash Drive section.

Examples

Writing factory installation image for the boardcon-em3566-emmc.yml target to the microSD card /dev/mmcblk1:

$ dd if=tanowrt-image-full-swu-factory-boardcon-em3566-emmc.sdcard.img of=/dev/mmcblk1

Writing bootable image for the boardcon-em3566-sd.yml target to the microSD card /dev/mmcblk1:

$ dd if=tanowrt-image-full-boardcon-em3566-sd.sdcard.img of=/dev/mmcblk1

1.6.2 Writing Image to eMMC Flash

For the initial flashing of the internal eMMC memory it is recommended to use the special image of the initial factory installation. If you choose a build target (see Build Targets for details) that assumes using the factory installation image for the initial flashing of the device, a factory installation image (<rootfs-image>-swu-factory-<MACHINE>.sdcard.img) will be automatically generated during the build process (see Build). To write the factory installation image to a SD card, follow the instructions from Writing Images to SD Card or USB Flash Drive section.

When you boot device from the prepaired SD card with factory installation image the installation of TanoWrt to the internal eMMC flash memory will be done automatically. The detailed installation log is available on the debug UART. After the installation is complete, the board will reboots automatically. When the device is rebooted, the installed system will be booted from the internal eMMC flash memory.

Caution

Be aware that during the installation all existing data on the internal eMMC flash memory will be permanently lost.

1.7 Booting and Running

1.7.1 Booting from SD Card

1. Insert the micro SD card to the board.

2. Connect the power cable to the DC input connector.

3. Boardcon EM3566 will boot.

4. (Optional) Use a USB to TTL serial cable to make a connection between your PC and Boardcon EM3566. See Serial Console section for details.

5. Log in to system using default credentials.

Attention

The internal eMMC flash memory must be empty in order to perform a boot from the SD card. See Erasing Internal eMMC Flash section for details about erasing internal eMMC flash.

1.7.2 Booting from Internal eMMC Flash

1. Connect the power cable to the DC input connector.

2. Boardcon EM3566 will boot.

3. (Optional) Use a USB to TTL serial cable to make a connection between your PC and Boardcon EM3566. See Serial Console section for details.

4. Log in to system using default credentials.

1.7.3 Erasing Internal eMMC Flash

You can erase the internal eMMC flash memory in the following ways:

• Linux command line;

• U-Boot command line;

• special utilities and USB connection with PC.

Linux CLIU-Boot CLIUSB Connection with PC

Erasing eMMC Using Linux Command Line

If the device has a bootable Linux system, you can erase the eMMC by the following command entered in the Linux terminal:

[root@tanowrt ~]# dd if=/dev/zero of=/dev/mmcblk0 bs=1k count=32768

Note that if the Linux distribution flashed on the eMMC flash memory is not TanoWrt, the device name of the eMMC flash memory may be different. You can usually find out the real device name by analysing the system boot log by running the command dmesg. For example:

[root@tanowrt ~]# dmesg | grep mmcblk
[    2.861965] mmcblk1: mmc1:aaaa SL16G 14.8 GiB
[    2.871858]  mmcblk1: p1 p2 p3 p4 p5 p6
[    2.890560] mmcblk0: mmc0:0001 8GTF4R 7.28 GiB
[    2.891462] mmcblk0boot0: mmc0:0001 8GTF4R partition 1 4.00 MiB
[    2.892322] mmcblk0boot1: mmc0:0001 8GTF4R partition 2 4.00 MiB
[    2.892741] mmcblk0rpmb: mmc0:0001 8GTF4R partition 3 512 KiB, chardev (238:0)
[    7.724257] overlay-resize: Root device mmcblk1
[    7.820211] overlay-resize: Overlay partition /dev/mmcblk1p6 (disk /dev/mmcblk1)
[    8.747050] overlay-resize: Partition /dev/mmcblk1p6 already resized
[    8.747189] overlay-resize: Resizing filesystem on partition /dev/mmcblk1p6...
[    8.786542] SWUPDATE: Failed to extract the idblock version from '/dev/mmcblk1'
[    8.788867] SWUPDATE: Failed to extract the U-Boot version from '/dev/mmcblk1p1'
[    8.791161] SWUPDATE: Failed to extract the U-Boot startup version from '/dev/mmcblk1'
[    8.855794] mount_root: /dev/mmcblk1p1: p1, rw, start 8388608, size 8388608
[    8.860902] mount_root: /dev/mmcblk1p2: p2, rw, start 16777216, size 67108864
[    8.861109] mount_root: /dev/mmcblk1p3: p3, rw, start 83886080, size 402653184 [rootfs]
[    8.865791] mount_root: /dev/mmcblk1p4: p4, rw, start 486539264, size 67108864
[    8.867224] mount_root: /dev/mmcblk1p5: p5, rw, start 553648128, size 402653184
[    8.871402] mount_root: /dev/mmcblk1p6: p6, rw, start 956301312, size 14975221248 [overlay]
[    8.871508] mount_root: root filesystem on the /dev/mmcblk1p3 partition of /dev/mmcblk1 (rw) device
[    8.887955] mount_root: founded suitable overlay partition /dev/mmcblk1p6
[    9.057146] EXT4-fs (mmcblk1p6): mounted filesystem with ordered data mode. Opts: (null)
[    9.170150] EXT4-fs (mmcblk1p6): mounted filesystem with ordered data mode. Opts: (null)

This output shows that device /dev/mmcblk0 is eMMC flash memory and device /dev/mmcblk1 is SD card.

1.8 Serial Console

Note

The default baudrate of Boardcon EM3566 with original firmware is 1500000 (1.5 Mbps), please check if your USB to TTL cable support 1.5 Mbps baudrate. Some model of CP210X and PL2303x have baudrate limitation, please check the specified model.

Connection

Connect the USB to TTL serial cable as described below. Don’t connect the VCC wire, connect only TX, RX and GND wires.

Attention

The original firmware for the debug output uses UART2 (3-pin connector J10) at 1500000 baudrate. In contrast, TanoWrt firmware by default uses UART4 (4-pin connector) for debug output.

Signal	Boardcon EM3566 Board
	J10 3-pin connector (UART2)	J11 4-pin connector (UART4)
RX	Pin 1 (UART2DBG_RX)	Pin 3 (UART4_RX_M0)
TX	Pin 2 (UART2DBG_TX)	Pin 2 (UART4_TX_M0)
GND	Pin 3 (GND)	Pin 1 (GND)
	Used by original firmware	Used by TanoWrt

See USB to TTL Converter Connection to Boardcon EM3566 figure for example connection USB to TTL converter with Boardcon EM3566.

Fig. 1.41 USB to TTL Converter Connection to Boardcon EM3566

Serial Setting on Host PC

The default serial console settings for Boardcon EM3566 for U-Boot and kernel are described in table below.

Parameter	Value
Baudrate	1500000
Data bits	8
Stop bits	1
Parity	none
Flow control	none

1.9 Default Network Configuration

By default Ethernet port (eth0 interface) are joined into a bridge (br-lan interface). Bridge (br-lan) configured to obtain IP configuration via DHCP client. To see obtained IP configuration use the following command:

[root@tanowrt ~]# ifstatus lan | jsonfilter -e '@["ipv4-address"][0].address'
192.168.0.39

In this example, the device got the IP address 192.168.0.39 via DHCP.

Also you can connect to the board using USB network connection (usb0 interface). USB network interface configured with static IP address 192.168.128.1 with enabled DHCP server with pool with single IP address for client (your PC) 192.168.128.100.

WiFi module and 3G/GPRS modules currently are not supported in TanoWrt.

1.10 Web User Interface

The WebUI can be accessed via Ethernet port or USB network connection through HTTP(s) protocol. You must see something like this in browser after you logged in:

Fig. 1.42 LuCI WebUI Login Page

Fig. 1.43 LuCI WebUI Overview Page

1.11 Firmware Upgrade

No special information about firmware upgrade. Use produced .swu artifact for upgrading running system.

See also

See common instructions in Firmware Upgrade section.

1.12 Additional Information

Here are sections with various additional information about the Boardcon EM3566 board and the operation of TanoWrt on it.

• 1.12.1 Boardcon EM3566 U-Boot Boot Log
• 1.12.2 Boardcon EM3566 Linux Boot Log (dmesg)
• 1.12.3 Boardcon EM3566 Factory Installation to eMMC Log

1.13 References

1. http://www.armdesigner.com/EM3566_SBC/