Page History

Cloud Server Network Operation Center(NOC) access

Contact Plume for the creation of User accounts in Plume NOC for Academy cloud server(https://piranha-osacademy.dev.us-west-2.aws.plume.tech/noc/explorer/reports), here after it is referred as "Cloud NOC".

Account creation

For creating user account, we need to provide following details

* Full Name
* Email ID

Plume will create two account, one for logging into academy Cloud NOC and another is for managing your network from inside Cloud NOC.

* username@company.com (for logging purpose)
* username-test-1 CUSTOMER  for example, used for managing your network

Addition of devices in Global Inventory

Load Cloud NOC link https://piranha-osacademy.dev.us-west-2.aws.plume.tech/noc/explorer/reports in Web browser.

Log into Plume's Academy cloud server NOC with your login credentials.

Click on drop down at Top-right corner of Plume Cloud NOC and click on "Global Inventory".

Add your devices in Global inventory with following details for each device.

ID: MAC address of eth1 interface without colon chosen as NodeID for Turris Omnia by convention (Eg.: D858D700A5D5)
MODEL: RTROM01-2G/RTROM01-2G-EX (RTROM01-2G for gateway; RTROM01-2G-EX for extender)
RADIO MAC (5GHz): MAC address of 5GHz radio interface
RADIO MAC (2.4GHz): MAC address of 2.4GHz radio interface
RESIDENTIAL GATEWAY: YES/NO

Example details for provisioning gateway

NodeID: D858D700A5D5
MODEL: RTROM01-2G
RADIO MAC (5GHz): 04:F0:21:31:DA:A2
RADIO MAC (2.4GHz): 04:F0:21:31:96:9A
RESIDENTIAL GATEWAY: YES

Example details for provisioning extender device

NodeID: D858D700A6B3 (used for claiming)
Model: RTROM01-2G-EX
RADIO MAC (5GHz): 04:F0:21:31:EF:8C
RADIO MAC (2.4GHz): 04:F0:21:31:93:43
RESIDENTIAL GATEWAY: NO

Claim devices in your location

Type "username-test-1 CUSTOMER" on left-top of the Plume Cloud NOC for name search. Then, your default location will be loaded.

Go to Network tab, search for "Claim Node" parameter. Then copy-paste NodeID of your device in the field corresponding to "Claim Node" parameter and press "Submit".

Repeat above step for claiming all of your devices in your default location.

Network Management

When Opensync running in device gets connected to Plume Cloud server, corresponding Device Icon in Network Topology section will turn "Green" signifying its Online status.

Now, Device details, Statistics, Connected devices and others details can be explored in Cloud NOC.

Hardware Information

Wi-Fi Extender Reference Targets

Serial Port Access

https://doc.turris.cz/doc/en/troubleshooting/serial_link#turris_omnia

Image Removed

Caution:  Do not connect Vcc!

NOTE:  Wouter Cloetens shared links and information on taking serial connection and flashing OpenWRT image

PREREQUISITE: Following flashing instructions works well with U-Boot 2015.10-rc2 bootloader version. If bootloader version found to be U-Boot SPL 2019.07  in your Turris Omnia, then please follow steps in Bootloader Downgrade section below in this page.

Flashing

The Omnia ships with TurrisOS preinstalled. This is an OpenWrt fork with the older Linux 4.4 kernel. It uses btrfs to manage the eMMC flash.

We do not use it in this mode. The RDK-B port is closer to the mainline OpenWrt port, which uses Linux 4.14, and a traditional partition table.

Reflashing procedure from TurrisOS:

...

Download openwrt-18.06.2-mvebu-cortexa9-turris-omnia-sysupgrade.img.gz and omnia-medkit-openwrt-18.06.2-mvebu-cortexa9-turris-omnia-initramfs.tar.gz from http://downloads.openwrt.org/releases/18.06.2/targets/mvebu/cortexa9/ and copy both files to the root of the flash drive.

...

Disconnect other USB devices from the Omnia and connect the flash drive to either USB port. (I have only verified this with the USB port at the front).

...

Hold down the reset button (backside, bottom centre) and plug in the power cord. Wait until the fourth LED lights up (green), then release (before the 5th LED lights up).

...

Wait approximately 2 minutes for the Turris Omnia to flash itself with the temporary image, during which LEDs will change multiple times.

Either use the serial console, or connect a computer to a LAN port (LAN0 to LAN4) of the Turris Omnia with a DHCP client.
From a computer:

Then, from the ssh session or a serial console:

...

mount /dev/sda1 /mnt
sysupgrade /mnt/openwrt-18.06.2-mvebu-cortexa9-turris-omnia-sysupgrade.img.gz

...

Wait another minute for the final OpenWrt image to be flashed. The Turris Omnia will reboot itself and you can remove the flash drive.

At this point, the boot loader (U-boot) will fail to boot the image:

...

U-boot: CRC error in environment, using default environment.

...

...

•  Wouter Cloetens to provide an updated medkit image that fixes the U-boot environment, removing the need to open the casing and connect a serial port.

The eMMC disk is now regularly partitioned.

...

root@OpenWrt:~# fdisk /dev/mmcblk0
 
Welcome to fdisk (util-linux 2.32).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
 
Command (m for help): p
Disk /dev/mmcblk0: 7.3 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x15344058
 
Device         Boot Start    End Sectors   Size Id Type
/dev/mmcblk0p1 *     2048  35327   33280  16.3M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      36864 561663  524800 256.3M 83 Linux

Create a new partition for RDK-B.

The devicetree database and the Linux kernel are in the FAT32 partition:

...

root@OpenWrt:~# mount /dev/mmcblk0p1 /mnt
root@OpenWrt:~# ls -l /mnt
-rwxr-xr-x    1 root     root         17353 Aug 17  2018 armada-385-turris-omnia.dtb
-rwxr-xr-x    1 root     root       2445072 Aug 17  2018 zImage

Copy the kernel in the FAT32 partition.

Reconfigure U-boot to boot from your kernel and root partition.

It is strongly recommend to keep the OpenWrt partition and kernel. If boot fails, it is easy to change the U-boot environment and boot back into OpenWrt.

Flashing RDKB image(A Yocto Project based Distro)

...

root@OpenWrt:~# opkg update
root@OpenWrt:~# opkg install fdisk

Create one primary partition for zImage. Create another extended partition for holding logical partitions for rootfs and /nvram.

After reboot, format /dev/mmcblk0p3, /dev/mmcblk0p5 and /dev/mmcblk0p6 as ext2 partitions.

Copy zImage, dtb and a rootfs tar file from yocto workspace to turris omnia(whose IP is 192.168.1.1).
(in your PC)

...

$ scp <yocto_workspace>build-turris/tmp/deploy/images/turris/zImage root@192.168.1.1:/tmp
$ scp <yocto_workspace>build-turris/tmp/deploy/images/turris/zImage-armada-385-turris-omnia.dtb root@192.168.1.1:/tmp/armada-385-turris-omnia.dtb
$ scp <yocto_workspace>build-turris/tmp/deploy/images/turris/rdkb-generic-broadband-image_default_<image-timestamp>.rootfs.tar.gz root@192.168.1.1:/tmp/

(in turris omnia)

...

root@OpenWrt:~# mount /dev/mmcblk0p3 /mnt
root@OpenWrt:~# mv /tmp/zImage /mnt
root@OpenWrt:~# mv /tmp/armada-385-turris-omnia.dtb /mnt
root@OpenWrt:~# umount /mnt
root@OpenWrt:~# mount /dev/mmcblk0p5 /mnt
root@OpenWrt:~# tar -xzf /tmp/rdkb-generic-broadband-image_default_<image-timestamp>.rootfs.tar.gz -C /mnt
root@OpenWrt:~# umount /mnt
root@OpenWrt:~# reboot

...

=> env set yocto_bootargs earlyprintk console=ttyS0,115200 root=/dev/mmcblk0p5 rootfstype=ext2 rw rootwait
=> env set yocto_mmcload setenv bootargs \"\$yocto_bootargs cfg80211.freg=\$regdomain\"\; ext2load mmc 0:3 0x01000000 zImage\; ext2load mmc 0:3 0x02000000 armada-385-turris-omnia.dtb
=> env set mmcboot run yocto_mmcload \|\| run openwrt_mmcload \|\| run factory_mmcload\; bootz 0x01000000 - 0x02000000
=> saveenv
=> reset

...

To fallback to openwrt OS, enter following u-boot commands.

...

=> env set mmcboot run openwrt_mmcload \|\| run factory_mmcload\; bootz 0x01000000 - 0x02000000
=> saveenv
=> reset

Yocto image upgrade procedure from OpenWrt OS: (Better approach is welcome)

Go back to OpenWrt OS (please refer Fallback to OpenWrt OS section above ).

Have Ethernet connection from your PC to LAN port of Turris Omnia.

Run following commands from inside OpenWrt OS.

root@OpenWrt:/# scp manigandan@<Your-PC-IP>:BOX/*$1* /tmp/
root@OpenWrt:/# mount /dev/mmcblk0p3 /mnt
root@OpenWrt:/# mv /tmp/zImage-* /mnt/zImage
root@OpenWrt:/# umount /mnt
root@OpenWrt:/# mount /dev/mmcblk0p5 /mnt
root@OpenWrt:/# rm -rf /mnt/*
root@OpenWrt:/# tar -xzf /tmp/rdkb-* -C /mnt/
root@OpenWrt:/# umount /mnt
root@OpenWrt:/# reboot

...

=> env set yocto_bootargs earlyprintk console=ttyS0,115200 root=/dev/mmcblk0p5 rootfstype=ext2 rw rootwait
=> env set yocto_mmcload setenv bootargs \"\$yocto_bootargs cfg80211.freg=\$regdomain\"\; ext2load mmc 0:3 0x01000000 zImage\; ext2load mmc 0:3 0x02000000 armada-385-turris-omnia.dtb
=> env set mmcboot run yocto_mmcload \|\| run openwrt_mmcload \|\| run factory_mmcload\; bootz 0x01000000 - 0x02000000
=> saveenv
=> reset

Turris Omnia is now running upgraded version of Yocto based RDKB image.

Bootloader Downgrade:

(Following steps are derived from https://wiki.debian.org/InstallingDebianOn/TurrisOmnia#Bootloader_update)

Install a tftp server (eg. tftpd-hpa) on your computer and place the attached uboot-turris-omnia-spl.kwb file into your computer's tftp directory(eg. /srv/tftp/) and run the following commands at the u-boot prompt on Turris Omnia.

...