Page History

Hardware Information

Requirements

Two files are required to bring up Newer model of Turris Omnia (Turris Omnia 2019 & Turris Omnia 2020)[Revision: CZ11NIC23]

...

View file

name	omnia-medkit-openwrt-mvebu-cortexa9-cznic_turris-omnia-initramfs_autoupgrade.tar.gz
height	250

Compressed WIC gzip image(Example: rdkb-generic-broadband-image_default_20200809095738.rootfs.wic.gz* ) coming out of build Turris Omnia RDKB Gateway: Yocto Build Instructions

Extract *.wic.gz or *.wic.bz2 image and rename to sysupgrade.wicimg. For example,

Code Block

languagetheme	bash	DJango

manigandan@manigandan-Latitude-3400:~$ gunzip rdkb-generic-broadband-image_default_20200809095738*.rootfs.wic.gz
manigandan@manigandan-Latitude-3400:~$ 
(or)
bzip2 -d rdkb-generic-broadband-image_default_*.rootfs.wic.bz2

mv rdkb-generic-broadband-image_default_20200809095738*.rootfs.wic sysupgrade.img

Flashing RDKB image (A Yocto Project based Distro)

Flashing with Medkit & Sysupgrade images

NOTE: This upgrade procedure wipes out eMMC flash storage(/dev/mmcblk0) completely. Earlier partitions are lost.

Perform following steps to flash New Turris Omnia with RDKB image.

Connect a USB flash drive to PC that is running Linux. Create a partition in flash drive and format the partition with mkfs.ext2
Copy both attached medkit image and sysupgrade.img image to USB flash drive.
Disconnect other USB devices from the Turris Omnia and connect the flash drive to either USB port.
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). _{Please check here to see more detail on rescue modes.}
Wait approximately 2 minutes for the Turris Omnia to flash itself with the temporary image, during which LEDs will change multiple times.

During 4-led upgrade procedure, following things are done:

...

.

...

Creating additional partitions

Create partitions for /additional rootfs and nvram and rootfs. Reboot Then, reboot the system.

bash

Code Block

language

theme	FadeToGreyDJango
collapse	true

root@TurrisOmnia-GW:/#~# fdisk /dev/mmcblk0  

Welcome to fdisk (util-linux 2.28.1).
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: 0xec7ceddc

Device         Boot Start    End Sectors   Size Id Type
/dev/mmcblk0p1 *     2048  34623   32576  15.9M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      34816 755359  720544 351.8M 83 Linux

Command (m for help): n
Partition type
   p   primary (2 primary, 0 extended, 2 free)
   e   extended (container for logical partitions)
Select (default p): 

Using default response p.
Partition number (3,4, default 3): 
First sector (34624-15269887, default 755712): 
Last sector, +sectors or +size{K,M,G,T,P} (755712-15269887, default 15269887): +128M512M

Created a new partition 3 of type 'Linux' and of size 128512 MiB.

Command (m for help): n
Partition type
   p   primary (3 primary, 0 extended, 1 free)
   e   extended (container for logical partitions)
Select (default e): 

Using default response e.
Selected partition 4
First sector (34624-15269887, default 10178561804288): 
Last sector, +sectors or +size{K,M,G,T,P} (10178561804288-15269887, default 15269887):      

Created a new partition 4 of type 'Extended' and of size 6.84 GiB.

Command (m for help): n
All primary partitions are in use.
Adding logical partition 5
First sector (10199041806336-15269887, default 10199041806336): 
Last sector, +sectors or +size{K,M,G,T,P} (10199041806336-15269887, default 15269887): +512M128M

Created a new partition 5 of type 'Linux' and of size 512128 MiB.

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: 0xec7ceddc

Device         Boot   Start      End  Sectors   Size Id Type
/dev/mmcblk0p1 *       2048    34623    32576  15.9M  c W95 FAT32 (LBA)
/dev/mmcblk0p2        34816   755359   720544 351.8M 83 Linux
/dev/mmcblk0p3       755712  10178551804287  1048576 262144  512M 128M 83 Linux
/dev/mmcblk0p4      10178561804288 15269887 1425203213465600   6.8G4G  5 Extended
/dev/mmcblk0p5      10199041806336  2068479  1048576 262144   512M128M 83 Linux

Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Re-reading the partition table failed.: Device or resource busy

The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).

root@TurrisOmnia-GW:/#~# reboot

Format all newly created two partitions with mkfs.as ext2 partitions.

language

Code Block

bash	theme	EmacsDJango
collapse	true

root@TurrisOmnia-GW:~# mkfs.ext2  /dev/mmcblk0p3
mke2fs 1.43 (17-May-2016)
Discarding device blocks: done                            
Creating filesystem with 131072 1k4k blocks and 32768 inodes
Filesystem UUID: 58f6eb63c2d8887f-b8926e6b-4c274d9b-a49eb57a-8c3d44ceba90f3bc28374841
Superblock backups stored on blocks: 
	819332768, 24577, 40961, 57345, 7372998304

Allocating group tables: done                            
Writing inode tables: done                            
Writing superblocks and filesystem accounting information: done 

root@TurrisOmnia-GW:~# mkfs.ext2  /dev/mmcblk0p5
mke2fs 1.43 (17-May-2016)
Discarding device blocks: done                            
Creating filesystem with 131072 4k1k blocks and 32768 inodes
Filesystem UUID: d2c61c602e4cee8d-c5dcf1d5-4922488a-bc7399f9-2e2f3547cff45e3a233dcf4f
Superblock backups stored on blocks: 
	327688193, 24577, 40961, 57345, 9830473729

Allocating group tables: done                            
Writing inode tables: done                            
Writing superblocks and filesystem accounting information: done

RDK Firmware(Image) upgrade: (Yet to validate)

Approach 1:

RDK firmware upgrade with XConf server: Firmware upgrade through XCONF server - Turris-Omnia - User Manual - 2020 - M6

Approach 2(Quick):

Copy zImage , dtb file and rootfs files(not *dbg* rootfs file) from PC or VM to /tmp/ directory of Turris Omnia which is running runs RDK Image.

For example

Code Block

theme	DJango

scp zImage--4.14.22-r0-turris-20200720105910.bin root@<TurrisOmnia-IP>:/tmp/
scp armada-385-turris-omnia.dtb root@<TurrisOmnia-IP>:/tmp/

...


scp rdkb-generic-broadband-image_default_20200720105910.rootfs.tar.gz root@<TurrisOmnia-IP>:/tmp/

In Turris Omnia, execute /lib/rdk/TurrisFwUpgrade.sh to flash new RDK image present in /tmp folder

Code Block

theme	DJango

sh /lib/rdk/TurrisFwUpgrade.sh

Turris Omnia will now run upgraded version of Yocto based RDK image.

RDK Resources

[RDK Preferred]

Code Management Facility

RDK Forums

[RDK Conferences]

RDK Support

Archives

In the News!

Versions Compared

Old Version 8

New Version Current

Key

Hardware Information

Requirements

Flashing RDKB image (A Yocto Project based Distro)

Flashing with Medkit & Sysupgrade images

Creating additional partitions

RDK Firmware(Image) upgrade: (Yet to validate)

Approach 1:

Approach 2(Quick):

RDK Resources

[*RDK Preferred*]

Code Management Facility

RDK Forums

[RDK Conferences]

RDK Support

Archives

In the News!

Page History

Versions Compared

Old Version 8

New Version Current

Key

Hardware Information

Requirements

Flashing RDKB image (A Yocto Project based Distro)

Flashing with Medkit & Sysupgrade images

Creating additional partitions

RDK Firmware(Image) upgrade: (Yet to validate)

Approach 1:

Approach 2(Quick):

[RDK Preferred]