[U-Boot] DM9000x driver entering infinite loop

Hello,
first some information: -ELDk + U-Boot 200908 -PPC405 custom board(IBM39 STB02500 LFA) -DM9000AEP on board
i have successfully booted the board with u-boot200908, but upon issuing a network command(like ping), the DM9000x driver enters infinite loop. Here is the output:
U-Boot 2009.08 (Nov 29 2009 - 00:36:38)
CPU: IBM PowerPC STBx25xx(51510950) Board: CT550 I2C: ready DRAM: 64 MB Reserving 0x01000000 bytes for usb download buffer at 0x03000000. Top of RAM usable for U-Boot at: 03000000 Reserving 224k for U-Boot at: 02fc7000 Reserving 192k for malloc() at: 02f97000 Reserving 76 Bytes for Board Info at: 02f96fb4 Reserving 60 Bytes for Global Data at: 02f96f78 Stack Pointer at: 02f96f58 **gd->ram_size returned: 67108864 **gd->cpu_clk returned: 252000000 **gd->bus_clk returned: 63000000 **get_tbclk() returned: 252000000 **gd->bus_clk returned: 63000000 New Stack Pointer is: 02f96f58 Relocation Offset is: 03007000 Now running in RAM - U-Boot at: 02fc7000 monitor_flash_len is: 211456
Relocating the command table: Finished relocating the command table.
FLASH: Manufacturer (device:227e) Manufacturer (device:227e) 16 MB wel_header.length missing. clear screen. U-Boot relocated to 02fc7000 Net: dm9000 Data (writethrough) Cache is ON Instruction Cache is ON default for stv6412 ### JFFS2 loading 'init.denc.uboot.cmp' to 0x10 Scanning JFFS2 FS: | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - done.
find_inode failed for name=init.denc.uboot.cmp
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for init.denc.uboot.cmp! ### JFFS2 loading 'init.denc.uboot.rgb' to 0x10 Scanning JFFS2 FS: | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - \ | / - done.
find_inode failed for name=init.denc.uboot.rgb
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for init.denc.uboot.rgb! Un-Protect Flash Bank # 1 Un-Protect Flash Bank # 2 Press Ctrl-z to debug bootloader.
[u-boot@CT550 boot]$ ping 192.168.1.22
Trying dm9000 reseting dm9000... resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset
And here is what i have in the board config file:
#define CONFIG_NET_MULTI #define CONFIG_DRIVER_DM9000 #define CONFIG_DM9000_BASE 0xf2000000 #define DM9000_IO CONFIG_DM9000_BASE #define DM9000_DATA (CONFIG_DM9000_BASE+4) #define CONFIG_ETHADDR 00:0B:16:21:2C:05 #define CONFIG_NETMASK 255.255.255.0 #define CONFIG_IPADDR 192.168.1.11 #define CONFIG_SERVERIP 192.168.1.21 #define CONFIG_DM9000_USE_16BIT 1 #define CONFIG_NET_RETRY_COUNT 20 #define CONFIG_SYS_DIRECT_FLASH_TFTP
Any help will be appreciated.
Alan _________________________________________________________________ http://redirect.gimas.net/?n=M0911xIE2 Sicher ist besser. Internet Explorer 8.

Dear "alan A. A",
In message SNT132-w518308DF4AA45864B03E899E980@phx.gbl you wrote:
first some information: -ELDk + U-Boot 200908 -PPC405 custom board(IBM39 STB02500 LFA) -DM9000AEP on board
So this is a custom port, and we don't know your modifications to the code.
i have successfully booted the board with u-boot200908, but upon issuing a network command(like ping), the DM9000x driver enters infinite loop. Here is the output:
...
Data (writethrough) Cache is ON Instruction Cache is ON
...
[u-boot@CT550 boot]$ ping 192.168.1.22
Trying dm9000 reseting dm9000... resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset resetting the DM9000, 1st reset
Did you try disabling the data cache? And addressing the other issues reported before the network driver gets used?
Best regards,
Wolfgang Denk
participants (2)
-
alan A. A
-
Wolfgang Denk