Re: [U-Boot-Users] Re: Interrupt management under PPC4xx platform

I agree, SDRAM should be OK!
If you enable the "irq" command (CFG_CMD_IRQ), do you see any irq's incrementing at all?
This is what I see on a PPC405GP(r):
=> tftp 100000 /tftpboot/pImage ENET Speed is 100 Mbps - FULL duplex connection ARP broadcast 1 TFTP from server 10.0.18.190; our IP address is 10.0.18.160 Filename '/tftpboot/pImage'. Load address: 0x100000 Loading: ################################################################# ################################################################# ########## done Bytes transferred = 712344 (ade98 hex) => irqs
Interrupt-Information: Nr Routine Arg Count 09 01fc3f84 00000000 0 10 01fc3f84 00000000 0 11 01fc3f84 00000000 0 12 01fc3f84 00000000 1394 13 01fc3f84 00000000 0 14 01fc3f84 00000000 0 15 01fc3f84 00000000 0
Sorry, but I haven't digged into the PPC405EP this deep. It could be, that there is a difference in the implementation. Please check the above irq test at first...
Best regards, Stefan.
No irq is incrementing:
U-Boot 0.2.0 (Apr 14 2003 - 16:41:00)
CPU: IBM PowerPC 405EP Rev. A at 266.666 MHz (PLB=133, OPB=66, EBC=66 MHz) PCI async ext clock used (sync mode not supported), internal PCI arbiter enabled 16 kB I-Cache 16 kB D-Cache Board: ### No HW ID - assuming WALNUT405 I2C: ready DRAM: 128 MB Top of RAM usable for U-Boot at: 08000000 Reserving 192k for U-Boot at: 07fd0000 Reserving 132k for malloc() at: 07faf000 Reserving 112 Bytes for Board Info at: 07faef90 Reserving 44 Bytes for Global Data at: 07faef64 Stack Pointer at: 07faef48 New Stack Pointer is: 07faef48 Now running in RAM - U-Boot at: 07fd0000 FLASH: 512 kB [board.c, 767] Calling env_relocate ... env_relocate[203] offset = 0x8050000 env_relocate[221] malloced ENV at 07faf008 In: serial Out: serial Err: serial KGDB: kgdb ready ready U-Boot relocated to 07fd0000 ### main_loop entered: bootdelay=3
### main_loop: bootcmd="tftpboot 0x400000 vmlinux.PPCBoot" Hit any key to stop autoboot: 0 ENET Speed is 10 Mbps - HALF duplex connection ARP broadcast 1
Abort => irqs
Interrupt-Information: Nr Routine Arg Count 09 07fd4988 00000000 0 10 07fd4988 00000000 0 11 07fd4988 00000000 0 12 07fd4988 00000000 0 13 07fd4988 00000000 0 14 07fd4988 00000000 0 15 07fd4988 00000000 0 =>
It is clear that if the Ethernet RX interrupt is not generated, no frame will be received. I think I'll look at te Ethernet driver in more detail.
llandre

Hi Llandre!
=> irqs
Interrupt-Information: Nr Routine Arg Count 09 07fd4988 00000000 0 10 07fd4988 00000000 0 11 07fd4988 00000000 0 12 07fd4988 00000000 0 13 07fd4988 00000000 0 14 07fd4988 00000000 0 15 07fd4988 00000000 0 =>
It is clear that if the Ethernet RX interrupt is not generated, no frame will be received. I think I'll look at te Ethernet driver in more detail.
You could ask the linuxppc-embedded mailing-list. I think that MontaVista has linux running on the PPC405EP eval board (bubinga == evb405ep). They could have a hint about differences in the 405 EMAC implementations...
Stefan.
participants (2)
-
llandre
-
Stefan Roese