No - it sounds like you will have to reload the firmware.  Here is the procedure -  
    http://www.surveyor.com/cgi-bin/yabb2/YaBB.pl?num=1205225367

Mmm, when at step 1, I install the windows software, go in the command console and start the loader. Then it only gives a list of the commands and also the supported LDR targets. I guess I need to connect to the robot another way first, like with the little usb-board or so?
 
I'm unable to connect to the srv1 network at the moment, although it is still broadcasting. I guess the firmware is set to infrastructure or so (I'm not getting an IP from the robot).
 
Sorry for the trouble !!!

UPDATE: I see the network again but I'm think that the dhcp of the robot ain't working no more.
 
Why do I think that?
 
Well:  
 
Robot:  
IP: 169.254.0.10
SM: 0.0.0.0
DG: 0.0.0.0
 
PC:
IP:169.254.192.38 (varies)
SM:255.255.0.0
DG: empty
 
While I have access to the robot using 169.254.0.10 in my browser, is there anything usefull I can do to restore everything so it works again?

First thing I did was move from adhoc to infrastructure and use my wireless router as the base station. I made the robot a static IP address on my home IP address. This means that any computer connected to the home network can connect to the robot rather than faffing with adhoc (although adhoc is better if you're moving around with both the robot and computer).
 
It seems odd that your PC is has a class B address (255.255.0.0) and the robot is a class A (0.0.0.0).
 
Usually people use a a subnet mask of 255.255.255.0 (class C). This means that you network is identified by three bytes and the computer is identified by the 4th on the IP address.
 
Traffic is probably being routed all over the place - hence your issues.
 
Personally I would setup the PC network to be a class C and also the robot. You shouldn't have problems then, for example:
 
This assumes your internal LAN is 196.254.0.0 and the robot is being connected in infrastructure mode and that you have full control over the LAN it's connected too.
 
Robot
SSID: MyWirelessLAN (or whatever your wireless LAN SSID is.
IP: 196.254.0.10 (static)
subnet mask: 255.255.255.0
gateway: 196.254.0.1 (or whatever the LAN side address of your gateway router is)
 
PC
IP: 196.254.0.x (set up DHCP on the gateway for 100-200 address range for dynamic IP)
subnet mask: 255.255.255.0
gateway: 196.254.0.1 (again - to match the LAN side address of the gateway)
 
Gateway
Internal LAN IP: 196.254.0.1
Internal LAN subnet mask: 255.255.255.0
Internal LAN DHCP address range: 100-255 (this stops the DHCP from attempting to allocate '10' which is the IP address of the rover at any point in time)
<your external WAN addresses should not need changing)
 
There may be differences with what you require to use but you see that the subnet masks match (same subnet) and the gateways are the same.
 
If you have anything else connected to the LAN then it should pick up the changes from DHCP but may need a poke to reapply for an IP address.

No - all you need todo is to reconfigure the IP addresses initially.
 
The IP address (which the Matchport provides) will allow access to the blackfin board.
 
Let's get your IP addresses set up first and work from there.

Ok, looking good. So we now have:
 
[pc] --{IP LAN}--> [router] --{wireless IP LAN}--> [MatchPort] --{serial}--> [BlackFin]
 
So the ping means we have got from the PC to the MatchPort. It's the MatchPort that is responding to the ping (it implements the IP stack on the srv-1).
 
This means the next point to check and set up is the MatchPort - the serial link and ensuring that the Blackfin is also setup to communicate with the MatchPort. This means getting the right serial communication speed.
 
What settings have you got on the MatchPort? Specifically which MatchPort firmware (ie 912Kbit or 2500Kbit ?).
 
If you telnet to 196.168.0.110 port 9999 then you should log onto the MatchPort itself. And look like:
Code:

MrFlibble:~ Nick$ telnet 196.168.0.10 9999
Trying 196.168.0.10...
Connected to 196.168.0.10.
Escape character is '^]'.

MAC address 00204AAE4106
Software version V6.5.0.0GE (080331) 

Press Enter for Setup Mode 
 

Yup, the MatchPort is the wireless component - it looks after the wireless LAN to serial bits and bobs.
 
Ok, next it would be good if you could enter the setup mode and copy out the parameters for "Channel 1", "Expert" (we don't need the others and posting the wireless details would be a security risk).
Code:

*** Channel 1
Baudrate divisor 2, I/F Mode 4C, Flow 02
Port 10001
Connect Mode : C0
Send '+++' in Modem Mode enabled
Show IP addr after 'RING' enabled
Auto increment source port disabled
Remote IP Adr: --- none ---, Port 00000
Disconn Mode : 00
Flush   Mode : 80
Pack Cntrl   : C0
...
*** Expert
TCP Keepalive    : 45s
ARP cache timeout: 600s
CPU performance: Regular, clk 81
Monitor Mode @ bootup : enabled
HTTP Port Number : 80
SMTP Port Number : 25
MTU Size: 1024
Alternate MAC: disabled
Ethernet connection type: auto-negotiate
 

 
The settings I have above may differ - I'm running 2500Kbit. but lets see if we can get you working first.