About watch dog timer limit of CPU (Xscale ->IXP425) How can I set more long time ?

2006-12-03 Thread Bob Zhang
Hello all , 

My embeded board hardware configuration is like this :
# cat /proc/cpuinfo
Processor   : XScale-IXP425/IXC1100 rev 1 (v5b)
BogoMIPS: 266.24
Features: swp half thumb fastmult edsp 

Hardware: Intel IXDP425 Development Platform
Revision: 
Serial  : 

Through reading datasheet of ixp4xx ,I know it has own watchdog functions ,
please see attchment :15 Timer 

I find a driver by goole , 
see attachment .


Watchdog timer counter is 32 bit register , its max value is 2<<32 -1 

#define TIMER_FREQ 6600 /* 66 MHZ timer */
#define TIMER_KEY 0x482e
#define TIMER_MARGIN 60  /* (secs) Default is 1 minute */ 
//I want to modify it ,I find its max value is 65

static int ixp425_margin = TIMER_MARGIN; /* in seconds */
static int ixp425wdt_users;
//static int pre_margin;  //IXP425 CPU 's watch dog timer is 32 bit , 
//so I define it to be unsigned int --bob
static unsigned int pre_margin;   
pre_margin = TIMER_FREQ *  TIMER_MARGIN 
*IXP425_OSWT = pre_margin; 

if I need one minutes , 
*IXP425_OSWT = 6600 * 60 =  39600  ,not overflow  

if I need two minutes , 
*IXP425_OSWT = 6600 * 120 = 79200  ( which has been >  2<<32-1  , 
overflow 

So I compute the max time I can set :
 T_max = 2<<32-1 / 6600=  65 seconds 。  



My question:

if need more seconds ( for example , 5 minutes ) ,what should I do ? 

I have a method based on datasheet (ixp4xx) ,but I don't know if it will 
successed when system crash 

How can I do to break the limit of hardware ? 
Thanks ahead ! 

--
Best Regards
bob

ixp425_wdt.c
Description: Binary data


About watch dog timer limit of CPU (Xscale ->IXP425) How can I set more long time ?

2006-12-04 Thread Bob Zhang
Hello all , 

My embeded board hardware configuration is like this :
# cat /proc/cpuinfo
Processor   : XScale-IXP425/IXC1100 rev 1 (v5b)
BogoMIPS: 266.24
Features: swp half thumb fastmult edsp 

Hardware: Intel IXDP425 Development Platform
Revision: 
Serial  : 

Through reading datasheet of ixp4xx ,I know it has own watchdog functions ,
please see attchment :15 Timer 

I find a driver by goole , 
see attachment .


Watchdog timer counter is 32 bit register , its max value is 2<<32 -1 

#define TIMER_FREQ 6600 /* 66 MHZ timer */
#define TIMER_KEY 0x482e
#define TIMER_MARGIN 60  /* (secs) Default is 1 minute */ 
//I want to modify it ,I find its max value is 65

static int ixp425_margin = TIMER_MARGIN; /* in seconds */
static int ixp425wdt_users;
//static int pre_margin;  //IXP425 CPU 's watch dog timer is 32 bit , 
//so I define it to be unsigned int --bob
static unsigned int pre_margin;   
pre_margin = TIMER_FREQ *  TIMER_MARGIN 
*IXP425_OSWT = pre_margin; 

if I need one minutes , 
*IXP425_OSWT = 6600 * 60 =  39600  ,not overflow  

if I need two minutes , 
*IXP425_OSWT = 6600 * 120 = 79200  ( which has been >  2<<32-1  , 
overflow 

So I compute the max time I can set :
 T_max = 2<<32-1 / 6600=  65 seconds ¡£  



My question:

if need more seconds ( for example , 5 minutes ) ,what should I do ? 

I have a method based on datasheet (ixp4xx) ,but I don't know if it will 
successed when system crash 

How can I do to break the limit of hardware ? 
Thanks ahead ! 

--
Best Regards
bob
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Fwd: stopped at "Freeing init memory: 100K "

2007-06-29 Thread Bob Zhang

I have used busybox 1.6.0 and 1.5.1
I used the kernel 2.6.18 from Montavista ,used arm_v5t_le-gcc to
compile kernel and busybox , but my busybox can't enter shell

I have no  "etc/inittab " file .

Following is my debug info :

---JK2410: Starting kernel , mach_type is 193 ...

Uncompressing 
Linux.
done, booting the kernel.
Linux version 2.6.18_pro500-versatile926ejs
([EMAIL PROTECTED]) (gcc version 4.2.0 20070126 (prerelease)
(MontaVista 4.2.0-3.0.0.0702771 2007-03-10)) #17 PREEMPT Wed Jun 20
11:37:00 EDT 2007
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=7177
Machine: SMDK2410
Ignoring unrecognised tag 0x54410008
Memory policy: ECC disabled, Data cache writeback
CPU S3C2410A (id 0x32410002)
S3C2410: core 200.000 MHz, memory 100.000 MHz, peripheral 50.000 MHz
S3C24XX Clocks, (c) 2004 Simtec Electronics
CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Real-Time Preemption Support (C) 2004-2006 Ingo Molnar
Built 1 zonelists. Total pages: 16384
Kernel command line: root=/dev/ram0 rw console=ttySAC0,115200 mem=64M
ramdisk=32768 initrd=0x3080,20M init=/linuxrc
WARNING: experimental RCU implementation.
irq: clearing subpending status 0002
PID hash table entries: 512 (order: 9, 2048 bytes)
timer tcon=0050, tcnt a2c1, tcfg 0200,, usec 1eb8
Console: colour dummy device 80x30
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 41976KB available (1952K code, 423K data, 100K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
checking if image is initramfs...it isn't (bad gzip magic numbers);
looks like an initrd
Freeing initrd memory: 20480K
NET: Registered protocol family 16
S3C2410: Initialising architecture
NET: Registered protocol family 2
IP route cache hash table entries: 512 (order: -1, 2048 bytes)
TCP established hash table entries: 2048 (order: 4, 65536 bytes)
TCP bind hash table entries: 1024 (order: 2, 28672 bytes)
TCP: Hash tables configured (established 2048 bind 1024)
TCP reno registered
NetWinder Floating Point Emulator V0.97 (extended precision)
NTFS driver 2.1.27 [Flags: R/O].
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Console: switching to colour frame buffer device 80x25
fb0: Virtual frame buffer device, using 1024K of video memory
S3C2410 RTC, (c) 2004 Simtec Electronics
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
s3c2410-uart.0: s3c2410_serial0 at MMIO map 0x5000 mem 0xf080
(irq = 70) is a S3C2410
s3c2410-uart.1: s3c2410_serial1 at MMIO map 0x50004000 mem 0xf0804000
(irq = 73) is a S3C2410
s3c2410-uart.2: s3c2410_serial2 at MMIO map 0x50008000 mem 0xf0808000
(irq = 76) is a S3C2410
RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize
dm9000 Ethernet Driver
mice: PS/2 mouse device common for all mice
IPv4 over IPv4 tunneling driver
TCP bic registered
NET: Registered protocol family 1
IP-Config: No network devices available.
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 20480KiB [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem).
*
* *
* REMINDER, the following debugging option is turned on in your .config: *
* *
* CONFIG_DEBUG_PREEMPT *
* *
* it may increase runtime overhead and latencies. *
* *
*
Freeing init memory: 100K

---
<<>>>


From: Ben Dooks <[EMAIL PROTECTED]>
To: Bob Zhang <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Date: 2007年6月22日 下午10:05

On Fri, Jun 22, 2007 at 09:54:29PM +0800, Bob Zhang wrote:

I have used busybox 1.6.0 and 1.5.1
I used the kernel 2.6.18 from Montavista ,used arm_v5t_le-gcc to
compile kernel and busybox , but my busybox can't enter shell


Why are you using an arm v5 compiler for an arm v4 system? Also
why do you feel the need to use a montavista kernel and one as
old as 2.6.18!
[引用文字已隐藏]did you ensure /dev/ttySAC where correctly created in the root fs?

--
Ben

Q:  What's a light-year?
A:  One-third less calories than a regular year.



From: Mike Frysinger <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: Bob Zhang <[EMAIL PROTECTED]>
Date: 2007年6月23日 上午2:32
Attachments: signature.asc

On Friday 22 June 2007, Bob Zhang wrote:

I have used busybox 1.6.0 and 1.5.1
I used the kernel 2.6.18 from Montavista ,used arm_v5t_le-gcc to
compile kernel and busybox , but my busybox can't enter shell


this is rarely a busybox prob