eth0: WakeUp interrupt ! (PPC 405EP board)

2008-05-16 Thread Albert David
Dear Friends,
we have a custom board based on PPC405EP processor, this design is
based on bubinga reference board.
we have ported u-boot 1.4 and linux kernel 2.4.32 - this design is
already in production for several months
recently, on few boards we started seeing "eth0: WakeUp interrupt !"
message while linux bootup(to be specific when ethernet driver is
loaded). but this problem is sort of intermittant in nature, out of 5
reboots, once or twice "eth0: WakeUp interrupt !" keeps printing on
terminal without proceeding any further

can anyone give me a direction why this happens?
Thanks for your support,
Albert.


following is the boot message from my target board,


U-Boot 1.1.4.1.4 (Dec  5 2007 - 17:22:12)

CPU:   AMCC PowerPC 405EP Rev. B at 266.666 MHz (PLB=133, OPB=66, EBC=33 MHz)
   I2C boot EEPROM disabled
   16 kB I-Cache 16 kB D-Cache
Board: ### No HW ID - assuming PICO4
I2C:   ready
DRAM:  32 MB
FLASH: 16 MB
Hit any key to stop autoboot:  0
00fd: fd.

## Checking Image at ff00 ...
   Bad Magic Number
## Booting image at ff96 ...
   Image Name:   GH2(PICO4) ukernel V-2.4.32-2.6
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:789480 Bytes = 771 kB
   Load Address: 
   Entry Point:  
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at ffc0 ...
   Image Name:   GH2(PICO4) uramdisk V-2.4.32
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
   Data Size:1640575 Bytes =  1.6 MB
   Load Address: 
   Entry Point:  
   Verifying Checksum ... OK
   Loading Ramdisk to 01dae000, end 01f3e87f ... OK
id mach(): done
MMU:enter
MMU:hw init
MMU:mapin
MMU:mapin_ram done
MMU:setio
MMU:exit
setup_arch: enter
setup_arch: bootmem
setup_arch: ocp_early_init
arch: exit
Linux version 2.4.32-2.6 ([EMAIL PROTECTED]) (gcc version 3.4.2) #7
Mon Feb 12 17:31:12 IST 2007
Pico4 Barco
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/ram rw
ip=192.168.1.144:192.168.1.128:192.168.1.1:255.255.255.0::eth0:off
panic=1 console=ttyS0,115200
Calibrating delay loop... 266.24 BogoMIPS
Memory: 28968k available (1352k kernel code, 388k data, 64k init, 0k highmem)
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
POSIX conformance testing by UNIFIX

Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
Squashfs 2.2-r2 (released 2005/09/08) (C) 2002-2005 Phillip Lougher
i2c-core.o: i2c core module version 2.6.1 (20010830)
i2c-dev.o: i2c /dev entries driver module version 2.6.1 (20010830)
i2c-algo-bit.o: i2c bit algorithm module
i2c-proc.o version 2.6.1 (20010830)
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with no serial options enabled
ttyS00 at 0xef600300 (irq = 0) is a 16550A
ttyS01 at 0xef600400 (irq = 1) is a 16550A
IBM gpio driver version 07.25.02
GPIO #0 at 0xc307d700
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
emac: IBM OCP EMAC Ethernet driver, version 2.0
Maintained by Benjamin Herrenschmidt <[EMAIL PROTECTED]>
mal0: Initialized, 4 tx channels, 2 rx channels
eth0: IBM emac, MAC 00:04:a5:06:15:6b
eth0: Found Generic MII PHY (0x00)
emac1: Cannot reset EMAC
Looking for 3 devices
probing for memory type cfi_probe
physmap flash device: 100 at ff00
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit mode
 Amd/Fujitsu Extended Query Table at 0x0040
phys_mapped_flash: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
probing for memory type map_ram
physmap flash device: 800 at f000
probing for memory type map_ram
physmap flash device: 800 at e000
Pico40: Found 1 x16 devices at 0x0 in 8-bit mode
 Amd/Fujitsu Extended Query Table at 0x0040
Pico40: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Pico4 flash bank 0: Using static image partition definition
Creating 13 MTD partitions on "Pico40":
0x-0x0036 : "uscratchpad (3.4MB)"
0x0036-0x0066 : "ugh2disk (3MB)"
0x0066-0x0076 : "ujffs2_1 (1MB)"
0x0076-0x0096 : "ujffs2_2 (2MB)"
0x0096-0x00b0 : "uimage (1.6MB)"
0x00b0-0x00b8 : "ufpga (512Kb)"
0x00b8-0x00be : "uiiu (384Kb)"
0x00c0-0x00ee : "uramdisk (2944KB)"
0x00f6-0x0100 : "uboot (640KB)"
0x00360040-0x0066 : "Pico4 GH2Disk mount point"
mtd: partition "Pico4 GH2Disk mount poi

u-boot debugging

2006-01-22 Thread Albert David
>> On Friday 20 January 2006 08:00 pm, AtulAtulhSabharwalte:
>> > First learn to communicate in English. I can give you 25 Us
>> cents as I
>> > cannot afford 1 Mark. You are not work even a Mark.
>>
>> The complete lack of civility in this remark is inexcusable in
>> a public forum.
>> Herr DenkDenk provided an incredibly valuable service to the
>> community, and
>> deserves more respect than this.

>I agree whole heartily Glenn...

glenn and frank,
even me too! i agree with you.

Best regards,
Albert David.



BDI2000 with PPC405EP

2005-09-08 Thread Albert David
Dear Eugene,
Thanks for your suggestion! This was indeed a hardware bug! I found a
problem with my cpu strapping pins! UART0_TX was never driven
externally(it was left open),
Thanks again for your reply,
with best regards,
Albert.

On 9/8/05, Eugene Surovegin  wrote:
> On Thu, Sep 08, 2005 at 11:33:53AM +0530, Albert David wrote:
> > Friends,
> > I have been trying to find a solution to fix "PPC: timeout while
> > waiting for freeze" for my custom board.
> > BDI2000 keeps resetting the system with the following message...
> >
> > TARGET: processing user reset request
> > TARGET: resetting target passed
> > TARGET: processing target startup 
> > *** TARGET: core #0 startup failed # PPC: timeout while waiting for freeze
> > TARGET: target will be restarted in 10 sec
> >
> > I tried all the possible solutions provided at
> > http://www.ultsol.com/faq-P206.htm for this perticular behaviour but
> > the problem remains same!
> >
> > I have ensured that my Board's JTAG interface is properly working by
> > boundary scanning the pins of PPC405EP using UniversalScan software
> > with Altera-ByteBlaster MV.
> >
> > for your information: twice i could succeed connecting BDI2000 with my
> > target! somehow it happen to work while i was trying to execute low
> > level JTAG commands such as 'rir' rdr'  and then after exiting(JTAG
> > command shell of BDI) it worked, but there is no consistency!
> >
> > looks like my cpu core is not halting after asserting HALT line.
> > has anyone faced similar problem??
> 
> In _all_ cases I saw this problem it was a hw bug. Ask your hw
> engineers to help you. Start with the usual suspects: power, clocks,
> strapping, etc.
> 
> I don't think working boundary scan is an indication that hw design is
> OK.
> 
> --
> Eugene
> 
>



BDI2000 with PPC405EP

2005-09-08 Thread Albert David
Friends,
I have been trying to find a solution to fix "PPC: timeout while
waiting for freeze" for my custom board.
BDI2000 keeps resetting the system with the following message...

TARGET: processing user reset request
TARGET: resetting target passed
TARGET: processing target startup 
*** TARGET: core #0 startup failed # PPC: timeout while waiting for freeze
TARGET: target will be restarted in 10 sec

I tried all the possible solutions provided at
http://www.ultsol.com/faq-P206.htm for this perticular behaviour but
the problem remains same!

I have ensured that my Board's JTAG interface is properly working by
boundary scanning the pins of PPC405EP using UniversalScan software
with Altera-ByteBlaster MV.

for your information: twice i could succeed connecting BDI2000 with my
target! somehow it happen to work while i was trying to execute low
level JTAG commands such as 'rir' rdr'  and then after exiting(JTAG
command shell of BDI) it worked, but there is no consistency!

looks like my cpu core is not halting after asserting HALT line.
has anyone faced similar problem??

please help!
BR,
Albert David.