public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: My-Hong Vuong <My-Hong.Vuong@au.thalesgroup.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Linux - problems with the RTC?
Date: Tue, 07 Jan 2003 14:55:44 +1100	[thread overview]
Message-ID: <se1aeaf0.058@au.thalesgroup.com> (raw)

Hi,

Hope you all had a great Xmas and New Years! :)

I managed to get linux to visibly start executing through smc1 - it
turns out that I had chosen the standard generic serial support option,
when it was in fact, non-standard... oops!

A new year, new problem... i'm afraid :(  Here's a short listing of
what I see at bootup :

-----------------------------------------------------
## Booting image at 01000000 ...
   Image Name:   Linux-2.4.19-pre7
   Created:      2003-01-07   1:50:16 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    595622 Bytes = 581.7 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
Linux version 2.4.19-pre7 (myhong at nemo) (gcc version 3.0.4) #46 Tue Jan
7 12:49:52 EST 2003
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/hda1
Decrementer Frequency = 78750000/60
			
-----

NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
 /dev/ide/host0/bus0/target0/lun0: p1
  /dev/ide/host0/bus0/target0/lun0: p1
  VFS: Mounted root (ext2 filesystem) readonly.
  Mounted devfs on /dev
  Freeing unused kernel memory: 52k init
  init started:  BusyBox v0.60.3 (2002.07.16-02:05+0000) multi-call
binaryStarted device management daemon for /dev
   /dev/ide/host0/bus0/target0/lun0: p1
   VFS: busy inodes on changed media..
    /dev/ide/host0/bus0/target0/lun0: p1
    SIOCSIFNETMASK: Cannot assign requested address
    eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
    eth0: status: link up, 10 Mbps Half Duplex, auto-negotiation
complete.
-----------------------------------------------------

At this point, linux hangs.  Now, I'm not too familiar with what is
supposed to happen next - but according to the output that i had on the
fads860 board (i'm currenlty working on a custom design, mpc860T board),
I am supposed to get something like:

-----------------------------------------------------
Tue Jan  7 11:23:43 2003
VFS: busy inodes on changed media.
mount: Mounting /dev/ide/host0/bus0/target0/lun0/part1 on /mnt/idedisk
failed: No such file or directory
Caught SIGHUP

Please press Enter to activate this console. 
/dev/ide/host0/bus0/target0/lun0: p1
VFS: busy inodes on changed media..
 /dev/ide/host0/bus0/target0/lun0: p1

 BusyBox v0.60.3 (2002.07.16-02:05+0000) Built-in shell (ash)
 Enter 'help' for a list of built-in commands.

 root:/#
-----------------------------------------------------

I can ping and telnet my target (sometimes) and i can get something
like the above - however, i have to login and exit telnet to type
anything at the prompt.  

Now, each time I do a "date" , I get the exact same response - i.e., my
RTC seems to have halted.  I don't get it... I can do "date" in PPCBoot
and my seconds change.  I put in some register dumps and I get:

TBSCR: 0x00000103
RTCSC: 0x00000013
RTC:   0x5fffc058
PISCR: 0x00000004
SCCR:  0x03800000

how do i get my clock to tick??

Thanks in advance,
My Hong Vuong

                 reply	other threads:[~2003-01-07  3:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=se1aeaf0.058@au.thalesgroup.com \
    --to=my-hong.vuong@au.thalesgroup.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox