[coldfire-gnu-discuss] P&E debugger support in Eclipse broke

[Tarmo Kuuse <tarmo.kuuse@xxxxxxxxxxxxx>]

Hi,

After working just fine for over a year, Eclipse suddenly stopped 
recognizing my BDM debugger (the blue USB Coldfire Multilink from P&E 
Micro). All cabling is OK, debugger's LED-s indicate that connection is 
established, target is powered on etc. Symptoms:

1. Attempting to configure the debugger in "Run", "Debug configurations" 
results in message "Discovering configuration: Available devices" being 
displayed for 30 seconds:
http://people.proekspert.ee/tarmok/sgpp/eclipse_discovering.png

2. After 30 seconds error message "Warning: could not obtain device 
list." appears:
http://people.proekspert.ee/tarmok/sgpp/eclipse_device_list.png

I ran command "m68k-elf-sprite -i". It takes nearly 90 seconds to 
execute. The return code is 0 and output is following:

 ~$ m68k-elf-sprite -i
CodeSourcery ColdFire Debug Sprite (Sourcery G++ 4.3-252)
pe: [speed=<n:0-31>&memory-timeout=<n:0-99>] P&E Adaptor
  pe://USBMultilink/PE6015220 - USB1 : USB-ML-CF Rev C (PE6015220)
  pe://CycloneProMaxSerial:1 - COM1 : Serial Port 1
  pe://ParallelPortCable:1 - LPT1 : Parallel Port 1 (Address $0378)
ccs: [timeout=<n>&speed=<n>] CCS Protocol
  ccs://$Host:$Port/$Chain_position - Command Converter Server
tblcf: TBLCF Interface
osbdm: Open Source BDM
osbdm: Cannot load OSBDM library 'OSBDM-JM60.DLL'

My P&E debug device is correctly identified. By the way - it appears to 
work OK. The Freescale "CF Flasher" utility can successfully communicate 
with the target, show Flash content etc.

I have no idea what I could have done to cause this. The last thing I 
remember changing in system was loading a new colour profile for the 
monitor and rebooting. That's not a likely suspect.

Have tried so far:
-Replaced P&E BDM devices
-Replaced USB ports
-Reinstalled SourceryG++ (3-4 times), including removal of P&E drivers
-Replaced Sourcery-shipped device drivers with fresh ones from P&E (v. 
10). Sprite refused to digest new DLL-s.

Our tool version is currently locked to 4.3-252, so upgrade is not an 
option. Any advice on how to debug the debugger?

--
Kind regards,
Tarmo Kuuse