I cannot boot and connect to my development board.

It was after I install a new video card (matrox dual head) and updated the ethernet driver (VIA RHINE II).

It has been working for an year and a half. Same scripts, same everything.

The problem. I use teraterm to bring the nic up. Then, I download the image, and then boot. But now, the image boots, but it does not finish the process witht he PB 5.0.

The image initializes the screen, but it stops there. Just before Windows screen. Inside PB, it shows as attached, but if I open Target/Ce Processes. the windows shows "waiting data" forever.

here are the commands, i use:

ifconfig sm0 dhcp
bootme &

I used this one for a long time and it worked fine.
exec rtc:rtc_a404_int:dbg_enet:91C111:dbg_enet_base:0x70000000:dbg_enet_irq:0x00000016:share_eth:1

Then I change to this one, I don't remember why, but it also worked.
exec rtc:rtc_a404_int:dbg_enet:91C111:dbg_enet_base:0x70000000:dbg_enet_irq:0x00000016:share_eth:1:kitl:true

Here is the teraterm output.

image launch addr: 0xc0201000

Verifying checksums: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Checksums good.
BOOTME: loaded
BOOTME: Got jump command
exec rtc:rtc_a404_int:dbg_enet:91C111:dbg_enet_base:0x70000000:dbg_enet_irq:0x00
000016:share_eth:1:kitl:true
kernel cmdline: 'rtc:rtc_a404_int:dbg_enet:91C111:dbg_enet_base:0x70000000:dbg_e
net_irq:0x00000016:share_eth:1:kitl:true:ip_addr:192.168.1.235' at c005a7f4


and here is the PB:

The Kernel Debugger is waiting to connect with target.
The Kernel Debugger has been disconnected successfully.
0 PID:0 TID:0 Sp=ffffc7cc
1837 PID:25fb1dc2 TID:25fbcf82 SmSC_91C111: Resource conflict! Base address (0x70000000) in use by KITL.
1837 PID:25fb1dc2 TID:25fbcf82 SmSC_91C111: Driver will not initialize.
1884 PID:25fb1dc2 TID:e5efa242
HCD RHSC IST: stat:0x40, prt_1:0x100, prt_2:0x100
2551 PID:45e8465a TID:45fb16c2 +LcdCtlr::SetPalette
2589 PID:45e8465a TID:45fb16c2 +LcdCtlr::SetPalette



The 91C111 has always been there, no problem.


If I take ony "dbg_enet:91C111" out. The board will boot and run the application.

I even got it to boot when I took "kitl:true" out. But it also did not connected to the debugger.

I tried 3 card engines already. They work fine auto booting.

Thanks

Raul