Fixed
Created: Jul 29, 2014
Updated: Dec 3, 2018
Resolved Date: Aug 19, 2014
Found In Version: 6.0
Fix Version: 6.0.0.11
Severity: Standard
Applicable for: Wind River Linux 6
Component/s: BSP - Async
root@localhost:~# dmesg | grep -i rtc
[ 7.570000] rtc-ds1374: probe of 1-0068 failed with error -145
[ 40.280000] /buildarea2/wr-taf/std/all/bitbake_build/tmp/work/bcm_xlp-wrs-linux/linux-windriver/3.10-r0/linux/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
root@localhost:~# grep -i rtc config | grep -v ^#.*
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_SYSTOHC=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
CONFIG_RTC_DRV_DS1374=y
root@localhost:~#
------------------
On xlp8xx board, CGL kernel.
...........
Wind River Linux 6.0.0.0 localhost console
localhost login: root
Password:
root@localhost:~# dmesg | grep -i rtc
[ 6.200000] rtc-ds1374: probe of 1-0068 failed with error -145
[ 36.760000] /buildarea2/wr-taf/cgl/all/bitbake_build/tmp/work/bcm_xlp-wrs-linux/linux-windriver/3.10-r0/linux/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
root@localhost:~#
root@localhost:~# zcat /proc/config.gz | grep -i rtc | grep -v ^#.*
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_SYSTOHC=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
CONFIG_RTC_DRV_DS1374=y
root@localhost:~#
root@localhost:~# zcat /proc/config.gz | grep -i i2c | grep -v ^#.*
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_OCORES=y
CONFIG_I2C_XLP9XX=y
root@localhost:~#
root@localhost:~#
1) configure --enable-board=bcm-xlp --enable-kernel=standard --enable-rootfs=glibc-std --enable-test=yes --with-layer=/runtime/wr-testing/ltp,/runtime/wr-testing/kts-test,/runtime/wr-testing/bts --with-template=feature/kts-basic,feature/kts-extended,feature/kts-cgl --enable-parallel-pkgbuilds=24 --enable-jobs=24
2) make all
3) deploy images on xlp2xx boards (22052)
4) boot target
Check the boot logs.