RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Page History
| Expand | ||
|---|---|---|
| ||
The dmcli command for emulator platform use simu instead of eRT and this is the reason for failing in emulator. A sample command is : dmcli simu getv Device. |
1.RDK-B
| Expand | ||
|---|---|---|
| ||
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. |
| Expand | ||
|---|---|---|
| ||
The dmcli command for emulator platform use simu instead of eRT and a sample command is : dmcli simu getv Device. |
| Expand | ||
|---|---|---|
| ||
We can change the resolution in rms.conf file that is there in /ust/local/rms/bin/ directory. |
| Expand | ||
|---|---|---|
| ||
Yes, we have used AWS server to store 24*7 data for CVR. |
| Expand | ||
|---|---|---|
| ||
We have used gstreamer plugin to capture data from camera like mainly used v4l2src plugin. |
| Expand | ||
|---|---|---|
| ||
AS of now we used confidential page to check this feature,we are trying to support google based signalling server to resolve this conflict. |
| Expand | ||
|---|---|---|
| ||
We have supported h264 encoded format for RMS live streaming and Continuous video recording(CVR). |
...
1.1.Emulator
| Expand | |
|---|---|
|
|
...
| |
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 . |
...
| title | How to customize kernel modules for RDK-B emulator? |
|---|
Follow the below steps to customize kernel –
...
1.2.Turris Omnia
| Expand | ||
|---|---|---|
| ||
mkdir |
...
tmp/; |
...
|
...
tmp/ |
...
...
xf |
...
u-boot-omnia_2019-07-7_arm_cortex-a9_vfpv3.ipk |
...
xf |
...
data.tar.gz |
...
usr/share/omnia/ |
...
/dev/mtd0 |
...
/dev/mtd0 |
...
uboot-devel |
...
../../../.. |
...
-rf |
...
tmp |
| Expand | ||
|---|---|---|
| ||
mkdir |
...
tmp; |
...
cd |
...
tmp/ |
...
...
xf |
...
rescue-image_3.2-1_arm_cortex-a9_vfpv3.ipk |
...
xf |
...
data.tar.gz |
...
usr/share/rescue-image/ |
...
/dev/mtd1 |
...
/dev/mtd1 |
...
image.fit.lzma |
...
../../../.. |
...
-rf |
...
tmp |
| Expand | ||
|---|---|---|
| ||
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 |
| Expand | ||
|---|---|---|
| ||
Go |
...
into |
...
u-boot |
...
prompt |
...
and |
...
get |
...
back |
...
to |
...
OpenWRT |
...
(failsafe) |
...
OS |
...
set |
...
yocto_mmcload |
...
false Format |
...
/dev/mmcblk0p3 |
...
and |
...
/dev/mmcblk0p5 |
...
and |
...
new |
...
RDKB |
...
firmware |
...
into |
...
p3 |
...
and |
...
p5 |
...
partitions |
...
get |
...
back |
...
to |
...
RDKB |
...
image |
...
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 |
| Expand | ||
|---|---|---|
| ||
Follow |
...
"Flashing |
...
with |
...
Medkit |
...
& |
...
Sysupgrade |
...
images" |
...
section |
...
in |
...
https://wiki.rdkcentral.com/pages/viewpage.action?pageId=114986683 |
| Expand | ||
|---|---|---|
| ||
Legacy |
...
and |
...
FIT |
...
image |
| Expand | ||
|---|---|---|
| ||
TurrisFwUpgrade.sh |
...
is |
...
written |
...
with |
...
two |
...
models |
...
in |
...
mind(older |
...
and |
...
newer)Older |
...
model |
...
has |
...
this |
...
partitions |
...
in |
...
internal |
...
flash |
...
- |
...
openwrt |
...
bootfs |
...
- |
...
openwrt |
...
rootfs |
...
- |
...
rdk |
...
bootfs |
...
- |
...
Extended |
...
partition |
...
rdk |
...
rootfs(1) |
...
- |
...
nvram |
...
- |
...
rdk |
...
rootfs(2) |
...
for |
...
firmware |
...
upgradeNewer |
...
model |
...
has |
...
this |
...
partitions |
...
in |
...
internal |
...
flash |
...
- |
...
rdk |
...
bootfs |
...
- |
...
rdk |
...
rootfs(1) |
...
- |
...
rdk |
...
rootfs(2) |
...
for |
...
firmware |
...
upgrade |
...
- |
...
Extended |
...
partition |
...
- |
...
nvramThis |
...
TurrisFwUpgrade.sh |
...
script |
...
will |
...
fill |
...
new |
...
rootfs |
...
in |
...
alternate |
...
partition |
...
swap |
...
the |
...
rootfs |
...
partition |
...
and |
...
copy |
...
zImage |
...
(in |
...
bootfs) |
...
in |
...
internal |
...
flash |
...
memory. |
2.RDK-Camera
| Expand | ||
|---|---|---|
| ||
We can change the resolution in rms.conf file that is there in /ust/local/rms/bin/ directory. |
| Expand | ||
|---|---|---|
| ||
Yes, we have used AWS server to store 24*7 data for CVR. |
| Expand | ||
|---|---|---|
| ||
Use gstreamer plugin mainly, v4l2src plugin to capture data from camera. |
| Expand | ||
|---|---|---|
| ||
AS of now we used confidential page to check this feature,we are trying to support google based signalling server to resolve this conflict. |
| Expand | ||
|---|---|---|
| ||
h264 encoded format is supported for RMS live streaming and Continuous video recording(CVR). |
Overview
Community Forums
Content Tools
Tasks