do a: make kernel_menuconfig and configure the rtc (as explained on www.acmesystems.it) _____
Da: [email protected] [mailto:[EMAIL PROTECTED] Per conto di guellep Inviato: venerdì 11 aprile 2008 11.45 A: [email protected] Oggetto: Re: R: [foxboard] Cannot access hardware clock using CrisOS --- In [EMAIL PROTECTED] <mailto:foxboard%40yahoogroups.com> s.com, "Michele Costantino" <[EMAIL PROTECTED]> wrote: > > Does dmesg says that the rtc has been found? No, there is no message concerning the rtc, neither when running dmesg nor when looking at the startup messages at the console port. > > _____ > > Da: [EMAIL PROTECTED] <mailto:foxboard%40yahoogroups.com> s.com [mailto:[EMAIL PROTECTED] <mailto:foxboard%40yahoogroups.com> s.com] Per conto di > guellep > Inviato: giovedì 10 aprile 2008 12.55 > A: [EMAIL PROTECTED] <mailto:foxboard%40yahoogroups.com> s.com > Oggetto: [foxboard] Cannot access hardware clock using CrisOS > > > > Hi, > > just started to check the features of CrisOS. > > I appreciate the read/write file system and the easy way > to add new packages and features. Great work! > > Now I tried to build a custom image, which makes use of the > real time clock on my SX18 socket board (DS1302 rtc). > I tried both the "classic red" ETRAX 100LX MCM fox board > and the ETRAX 100LX 832 board. > > Using make menuconfig I choose: > > -------------------- > Target System (Foxboard (ETRAX 100LX) (2.6) > > Image configuration -> Utilities -> hwclock > > Kernel modules -> I2C Bus -> kmod-i2c-core > Kernel modules -> I2C Bus -> kmod-i2c-algos > > Kernel modules -> Other modules -> kmod-hwmon > > -------------------- > > After flashing the appropriate image > (crisos-alpah-832 or crisos-alpha-MCM, respectively) and rebooting: > > -------------------- > [EMAIL PROTECTED]:/# uname -a > Linux CrisOs 2.6.19.2 #10 Thu Apr 10 12:14:00 CEST 2008 cris unknown > [EMAIL PROTECTED]:/# hwclock --debug > hwclock from util-linux-ng 2.13.0.1 > hwclock: Open of /dev/rtc failed, errno=2: No such file or directory > No usable clock interface found. > Cannot access the Hardware Clock via any known method. > [EMAIL PROTECTED]:/# > -------------------- > > /dev/rtc cannot be found because it is not there. > > After creating it trying > > mknod /dev/rtc c 10 135 > > I get a slightly different error message: > > --------------------- > [EMAIL PROTECTED]:/dev# hwclock --debug > hwclock from util-linux-ng 2.13.0.1 > hwclock: Open of /dev/rtc failed, errno=19: No such device. > No usable clock interface found. > Cannot access the Hardware Clock via any known method. > [EMAIL PROTECTED]:/dev# > ---------------------- > > I guess there is a problem with the IO pins / reset pins mapping > which could be arranged using make kernelconfig in the > devboard-R2_01 SDK. > > I could not find any tool to rearrange the IO settings > for the CrisOS SDK. Looking through some of the headerfiles > e. g. /asm/io.h did not help either. > > So here is the final question: > > How can I define the proper IO port pins to access the DS1302 > real time clock on the SX18 socket board? > > Thank you for helpful suggestions. > > Regards > > Klaus >
