Page History

The dmcli command for emulator platform use simu instead of eRT and a this is the reason for failing in emulator.

A sample command is :

dmcli simu getv Device.

The devices can connect over wifi to Raspberrypi by knowing the SSID and the corresponding password of the RaspberryPi Wifi network, which will be WPA2-PSK protected.

As of now, RDKM is not providing a ready-to-use pre-built image for emulator. But you can easily create an emulator build in an Ubuntu linux machine by following the instructions given at RDK-B Emulator Build Instructions . 

mkdir tmp/;
cd tmp/
wget https://repo.turris.cz/hbl/omnia/packages/turrispackages/u-boot-omnia_2019-07-7_arm_cortex-a9_vfpv3.ipk
tar xf u-boot-omnia_2019-07-7_arm_cortex-a9_vfpv3.ipk
tar xf data.tar.gz
cd usr/share/omnia/
flash_eraseall /dev/mtd0
nandwrite /dev/mtd0 uboot-devel
cd ../../../..
rm -rf tmp

mkdir tmp; cd tmp/
wget https://repo.turris.cz/hbl/omnia/packages/turrispackages/rescue-image_3.2-1_arm_cortex-a9_vfpv3.ipk
tar xf rescue-image_3.2-1_arm_cortex-a9_vfpv3.ipk
tar xf data.tar.gz
cd usr/share/rescue-image/
flash_eraseall /dev/mtd1
nandwrite /dev/mtd1 image.fit.lzma
cd ../../../..
rm -rf tmp

When we pass Legacy zImage(kernel) image with newer model of turris Omnia we get this error. We need to provide FIT rescue image for newer model of Turris Omnia

Go into u-boot prompt and get back to OpenWRT (failsafe) OS
=>env set yocto_mmcload false
=>saveenv
=>reset

Format /dev/mmcblk0p3 and /dev/mmcblk0p5 and new RDKB firmware into p3 and p5 partitions
To get back to RDKB image
=>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
=>saveenv
=>reset

Follow "Flashing with Medkit & Sysupgrade images" section in https://wiki.rdkcentral.com/pages/viewpage.action?pageId=114986683

Legacy and FIT image

TurrisFwUpgrade.sh is written with two models in mind(older and newer)Older model has this partitions in internal flash
mmcblk0p1 - openwrt bootfs
mmcblk0p2 - openwrt rootfs
mmcblk0p3 - rdk bootfs
mmcblk0p4 - Extended partition
mmcblk0p5- rdk rootfs(1)
mmcblk0p6 - nvram
mmcblk0p7 - rdk rootfs(2) for firmware upgradeNewer model has this partitions in internal flash
mmcblk0p1 - rdk bootfs
mmcblk0p2 - rdk rootfs(1)
mmcblk0p3 - rdk rootfs(2) for firmware upgrade
mmcblk0p4 - Extended partition
mmcblk0p5 - nvramThis TurrisFwUpgrade.sh script will fill new rootfs in alternate partition swap the rootfs partition and copy zImage (in bootfs) in internal flash memory.

We can change the resolution in rms.conf file that is there in /ust/local/rms/bin/ directory.

Yes, we have used AWS server to store 24*7 data for CVR.

We have used Use gstreamer plugin mainly, v4l2src plugin to capture data from camera like mainly used v4l2src plugin.

AS of now we used confidential page to check this feature,we are trying to support google based signalling server to resolve this conflict.

We have supported h264 encoded format is supported for RMS live streaming and Continuous video recording(CVR).