[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Watchdog & ./flashitall



Hi again,

Ok. The problem does not occur during the flashloading itself. 
The problem occurs during the mounting of the filesystem. 
We will soon release a 2.4.14 based firmware. In this release
we have solved a couple of problems related to the watchdog.
It would be great if you could test this and tell me if it
makes any difference.

I could also send a patch to you for the affected files if you
tell which kernel version you are running (2.4.5?)

Which filesystem are you using on the disks?

/Mikael

-----Original Message-----
From: Jihoon Bang [mailto:room4u@xxxxxxx.kr]
Sent: Monday, December 10, 2001 8:39 AM
To: Mikael Starvik; dev-etrax
Subject: RE: Watchdog & ./flashitall


SDRAM in my board is K4S281632(2M * 16bit * 4bank).

I have two SDRAM in my board. so It can be configured as 32MSDRAM.

Thanks you.

with best reguards

Jihoon

p.s. The following text is printed on debug port when watchdog is enabled.



Serial interface initialized.


Device ID = 0xBFBFA03F
This bootloader hacked by randylee Thu Sep  6 14:36:33 KST 2001.
Checksum of bootloader is 0x000A15AE
Waiting for load info.
Checksum of file is 0x00003AA3
Got load info.
SET_REGISTER
0xB0000000
0xFFFFFFFF
SET_REGISTER
0xB0000004
0x00000100
SET_REGISTER
0xB000000C
0x09E05757
SET_REGISTER
0xB0000008
0x8000C801
PAUSE_LOOP
0x00020000
SET_REGISTER
0xB0000008
0x8000CE01
SET_REGISTER
0xB0000008
0x8000C801
SET_REGISTER
0xB0000008
0x8000CC01
SET_REGISTER
0xB0000008
0x8000C801
SET_REGISTER
0xB0000008
0x8000CC01
SET_REGISTER
0xB0000008
0x8000C801
SET_REGISTER
0xB0000008
0x8000CC01
SET_REGISTER
0xB0000008
0x8000C801
SET_REGISTER
0xB0000008
0x8000CC01
SET_REGISTER
0xB0000008
0x8000C801
SET_REGISTER
0xB0000008
0x8000CC01
SET_REGISTER
0xB0000008
0x8000C801
SET_REGISTER
0xB0000008
0x8000CC01
SET_REGISTER
0xB0000008
0x8000C801
SET_REGISTER
0xB0000008
0x8000CC01
SET_REGISTER
0xB0000008
0x8000C801
SET_REGISTER
0xB0000008
0x8000CC01
SET_REGISTER
0xB0000008
0x8000C801
SET_REGISTER
0xB0000008
0x8040CA01
SET_REGISTER
0xB0000008
0x8000C801
SET_REGISTER
0xB0000008
0x80004801
SET_REGISTER
0xB0000030
0x00000707
SET_REGISTER
0xB0000038
0x0000FFFF
PACKET_INFO
0xC0004000
0x00400018
Checksum of file is 0x2F0AC20C
FLASH
0xC0004000
0x00000000
0x00400000
Found 1 x 16Mb BB at 0x80000000
Found 1 x 16Mb BB at 0x84000000
Erasing 0x00200000 bytes at 0x80000000...done, verifying...OK
Erasing 0x00200000 bytes at 0x84000000...done, verifying...OK
Flashing 0x00400000 bytes...done and verified
JUMP
0x00000000
Uncompressing Linux...
Done. Now booting the kernel.
Linux version 2.4.5 (max1@xxxxxxx.96 20000427 (experimental)) #488 Thu Nov 8 22:14:40 KST 2001
Setting up paging and the MMU.
On node 0 totalpages: 4096
zone(0): 4096 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Linux/CRIS port on ETRAX 100LX (c) 2001 Axis Communications AB
Kernel command line: 
ds1302: RTC found.
ds1302: SDA, SCL, RST on PB0, PB1, PA2
rtc_time	: 00:00:80
rtc_date	: 2000-01-01
rtc: sec 0x80 min 0x0 hour 0x0 day 0x1 mon 0x1 year 0x0
Enabling watchdog...
Calibrating delay loop... 33.17 BogoMIPS
Memory: 31128k/32768k available (855k kernel code, 1640k reserved, 89k data, 24k init)
kmem_create: Forcing size word alignment - vm_area_struct
kmem_create: Forcing size word alignment - filp
Dentry-cache hash table entries: 4096 (order: 2, 32768 bytes)
Inode-cache hash table entries: 2048 (order: 1, 16384 bytes)
kmem_create: Forcing size word alignment - inode_cache
kmem_create: Forcing size word alignment - bdev_cache
kmem_create: Forcing size word alignment - cdev_cache
Buffer-cache hash table entries: 2048 (order: 0, 8192 bytes)
Page-cache hash table entries: 4096 (order: 1, 16384 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
kmem_create: Forcing size word alignment - sock
Starting kswapd v1.8
kmem_create: Forcing size word alignment - file lock cache
JFFS version 1.0, (C) 1999, 2000  Axis Communications AB
early initialization of device eth0 is deferred
ETRAX 100LX serial-driver $Revision: 1.13 $, (c) 2000 Axis Communications AB
ttyS0 at 0xb0000060 is a builtin UART with DMA
ttyS1 at 0xb0000068 is a builtin UART with DMA
ttyS2 at 0xb0000070 is a builtin UART with DMA
ttyS3 at 0xb0000078 is a builtin UART with DMA
Axis flash mapping: 8000000 at f0000000
Axis flash: Found 1 x16 CFI device at 0x0 in 16 bit mode
Axis flash: Found 1 x16 CFI device at 0x4000000 in 16 bit mode
 Amd/Fujitsu Extended Query Table v1.0 at 0x0040
number of CFI chips: 2
 Found valid partition table at 0xF001000A-0xF0010056.
  /dev/flash1 at 0x10000, size 0x1f0000
  /dev/flash2 at 0x200000, size 0x200000
I2C driver v2.2, (c) 1999-2001 Axis Communications AB
ETRAX 100LX GPIO driver v2.1, (c) 2001 Axis Communications AB
3R DVR driver v0.1, 3R Inc.
KEY_Open()
LED_Open()
ADV7176_Open(...)
[AD]NTSC
ORION_Open()
kmem_create: Forcing size word alignment - blkdev_requests
block: queued sectors max/low 20581kB/6860kB, 64 slots per queue
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
ide: ETRAX 100LX built-in ATA DMA controller
ide: waiting 7 seconds for drives to regain consciousness
hda: Maxtor 4D040H2, ATA DISK drive
ide0 at 0x10000000-0x10000007,0x2c000000 on irq 4
hda: 80043264 sectors (40982 MB) w/2048KiB Cache, CHS=79408/16/63
Partition check:
 hda: [PTBL] [4982/255/63] hda1
ETRAX 100LX 10/100MBit ethernet v2.0 (c) 2000-2001 Axis Communications AB
eth0 initialized
eth0: changed MAC to 00:40:8C:CD:00:00
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
kmem_create: Forcing size word alignment - ip_dst_cache
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP: Hash tables configured (established 4096 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (cramfs filesystem) readonly.
Freeing unused kernel memory: 24k freed


-----Original Message-----
From: owner-dev-etrax@xxxxxxx.com]On">mailto:owner-dev-etrax@xxxxxxx.com]On
Behalf Of Mikael Starvik
Sent: Monday, December 10, 2001 3:48 PM
To: 'Jihoon Bang'; dev-etrax
Subject: RE: Watchdog & ./flashitall


Hi!

CONFIG_ETRAX_WATCHDOG should not be used during the flash loading
process at all. Is anything printed on the debug port during flash
loading when CONFIG_ETRAX_WATCHDOG is enabled?

I can verify your kernelconfig if you send me the partnumbers for
the memory chips you are using. 

ETRAX 100LX exist in two versions:
ETRAX-100-LX-v1: First ETRAX 100LX. Some known bugs in e.g. MMU.
ETRAX-100-LX-v2: Second revision of ETRAX 100LX. 

ETRAX-100-LX-v1 is safe even if you have an ETRAX 100LX v2.
On v1 the numer 17511 is printed. On v2 the number 17854 is printed. 

ETRAX-100-LX-for-xsim-simulator is only used when we 
simulate the CPU at Axis. You should not use this
(because you don't have the simulator anyway).

Regards
/Mikael

-----Original Message-----
From: owner-dev-etrax@xxxxxxx.com]On">mailto:owner-dev-etrax@xxxxxxx.com]On Behalf Of Jihoon Bang
Sent: Monday, December 10, 2001 7:24 AM
To: dev-etrax
Subject: Watchdog & ./flashitall


Hi. all

A few weeks ago, I had no idea about boot failure through ./flashitall when I use only group0 in SDRAM_CONFIG.
That is solved disabling CONFIG_ETRAX_WATCHDOG.

To tell the old history,
When I was using 16M SDRAM, .Both of ./ktest and ./flashitall are working well.
but, When 32M SDRAM, ./flashitall didn't succeed.
After disabling CONFIG_ETRAX_WATCHDOG, it succeeded !!!
How come is this value related with SDRAM size.?
I'll attach a menuconfig file.


and.. I have another question. in menuconfig, There is a Processor type menu.(ETRAX-100-LX-v1, ETRAX-100-LX-v2, ETRAX-100-LX-for-xsim-simulator)
what is this? In my case, ETRAX-100-LX-v2 is selected.



~~~~~~~~~~~~~~~~~~~~~~~~
Jihoon Bang
3R, Inc
phone : +82-2-840-3562
fax      : +82-2-836-6270
email  : room4u@xxxxxxx.kr