# While sending pilot BIOS Timeout while waiting for response from target **URL:** \ **Category:** Rabbit\ **Created:** [March 11, 2009, 3:07am UTC](https://forums.digi.com/t/while-sending-pilot-bios-timeout-while-waiting-for-response-from-target/9576 "2009-03-11T03:07:06Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![Franklin97355](https://avatars.discourse-cdn.com/v4/letter/f/46a35a/32.png) [@Franklin97355](https://forums.digi.com/u/Franklin97355)\ **Post date:** [March 11, 2009, 3:07am UTC](https://forums.digi.com/t/while-sending-pilot-bios-timeout-while-waiting-for-response-from-target/9576/1 "2009-03-11T03:07:06Z")
I just received my MiniCore RCM5600W Standard Development Kit and after installing the Dynamic C and drivers I plug in the board, load the scanwifi.c program into the compiler, set the com port (13) and hit F9 :)…after a bit I get the message in the title.😕 What should I have done to get this working? Thanks, Stephen ---
**Author:** ![kobuseng](https://avatars.discourse-cdn.com/v4/letter/k/f0a364/32.png) [@kobuseng](https://forums.digi.com/u/kobuseng)\ **Post date:** [March 11, 2009, 7:31am UTC](https://forums.digi.com/t/while-sending-pilot-bios-timeout-while-waiting-for-response-from-target/9576/2 "2009-03-11T07:31:09Z")
Well at least you got past the first possible massage nl. “While sending cold loader, no rabbit processor detected”, which means Dynamic C can initially see your rabbit. I would check for loose programming cable connections, also make sure the prgrammer connector makes fully contact with the rabbit programming port. Lastly your using comm port 13, which seems a bit high for a standard PC comm port. Are you using a usb -\> serial converter. They are notorious for not working with the Dynamic C programmer. Rabbit did introduce a checkbox in the Options-\>Project options-\>Communications tab to enable usb-\>serial converters, but I am still not convinced it works. ---
**Author:** ![Franklin97355](https://avatars.discourse-cdn.com/v4/letter/f/46a35a/32.png) [@Franklin97355](https://forums.digi.com/u/Franklin97355)\ **Post date:** [March 11, 2009, 4:15pm UTC](https://forums.digi.com/t/while-sending-pilot-bios-timeout-while-waiting-for-response-from-target/9576/3 "2009-03-11T16:15:27Z")
Thanks, I’ll check the connections and the settings. The module has a usb connection so I’m just using a straight usb cable. The converter is on the development board so I would hope it works. ---
**Author:** ![interxoft](https://avatars.discourse-cdn.com/v4/letter/i/e9a140/32.png) [@interxoft](https://forums.digi.com/u/interxoft)\ **Post date:** [March 4, 2013, 6:29pm UTC](https://forums.digi.com/t/while-sending-pilot-bios-timeout-while-waiting-for-response-from-target/9576/4 "2013-03-04T18:29:06Z")
Three years late we faced the same problem. Our situation got better by using a Trendnet USB to serial converter, the generic converters produced that error 99% of the time. Also we had to check conductivity on both ribbon cables, to discard problems there. Good luck! ---
**Author:** ![Franklin97355](https://avatars.discourse-cdn.com/v4/letter/f/46a35a/32.png) [@Franklin97355](https://forums.digi.com/u/Franklin97355)\ **Post date:** [March 12, 2009, 2:47am UTC](https://forums.digi.com/t/while-sending-pilot-bios-timeout-while-waiting-for-response-from-target/9576/5 "2009-03-12T02:47:12Z")
Well, no real luck so far. It still throws the error message 99 percent of the time. Twice I got a window with the filename I was trying to load but nothing happened after that. I guess nothing is as easy as they make it look in the literature. I’ll keep plugging away for now. ---
**Author:** ![Margaret](https://avatars.discourse-cdn.com/v4/letter/m/a88e57/32.png) [@Margaret](https://forums.digi.com/u/Margaret)\ **Post date:** [March 12, 2009, 11:54pm UTC](https://forums.digi.com/t/while-sending-pilot-bios-timeout-while-waiting-for-response-from-target/9576/6 "2009-03-12T23:54:00Z")
Hi, Can you try a simple sample like pong.c? Do you get the timeout error with that sample? ---
**Author:** ![Franklin97355](https://avatars.discourse-cdn.com/v4/letter/f/46a35a/32.png) [@Franklin97355](https://forums.digi.com/u/Franklin97355)\ **Post date:** [March 13, 2009, 3:07am UTC](https://forums.digi.com/t/while-sending-pilot-bios-timeout-while-waiting-for-response-from-target/9576/7 "2009-03-13T03:07:29Z")
No, I just tried that and I get the same message. It seems to be just after the negotiating baud rate message. Is there a way to reset everything back to “default” I’ve changed things now and don’t have a clue just what might be causing the problem. Two quick questions, what are the baud rates for download and communication and should there be one or two stop bits? Thanks, Stephen ---
**Author:** ![kobuseng](https://avatars.discourse-cdn.com/v4/letter/k/f0a364/32.png) [@kobuseng](https://forums.digi.com/u/kobuseng)\ **Post date:** [March 13, 2009, 8:55am UTC](https://forums.digi.com/t/while-sending-pilot-bios-timeout-while-waiting-for-response-from-target/9576/8 "2009-03-13T08:55:50Z")
Well on my system 1 or 2 stop bits doesnt seem to have an impact. Both works. For the baud rates, I would for now set them low, until you can get communications happening. Furthermore play with the comm ports, it could be that the wrong one is assigned. But I repeat that many times I have seen your problem, and it was down to a poor connection between the programming cable and the rabbit. Try to apply some shear pressure on the connector to see if it has any effect. ---
**Author:** ![Franklin97355](https://avatars.discourse-cdn.com/v4/letter/f/46a35a/32.png) [@Franklin97355](https://forums.digi.com/u/Franklin97355)\ **Post date:** [March 14, 2009, 3:48am UTC](https://forums.digi.com/t/while-sending-pilot-bios-timeout-while-waiting-for-response-from-target/9576/9 "2009-03-14T03:48:36Z")
Well, I tried a different cable on a different port and got the same message (after I changed the port in options \> project options , DUH) ---
**Author:** ![dgodrik](https://avatars.discourse-cdn.com/v4/letter/d/c68b51/32.png) [@dgodrik](https://forums.digi.com/u/dgodrik)\ **Post date:** [March 15, 2009, 8:33pm UTC](https://forums.digi.com/t/while-sending-pilot-bios-timeout-while-waiting-for-response-from-target/9576/10 "2009-03-15T20:33:01Z")
Had the same problem until I switched to the enclosed cable. Works fine. ---
**Author:** ![Franklin97355](https://avatars.discourse-cdn.com/v4/letter/f/46a35a/32.png) [@Franklin97355](https://forums.digi.com/u/Franklin97355)\ **Post date:** [March 23, 2009, 2:20am UTC](https://forums.digi.com/t/while-sending-pilot-bios-timeout-while-waiting-for-response-from-target/9576/11 "2009-03-23T02:20:53Z")
Well, this weekend I had time to pull the computer out an connected the cable to the back instead of using a port on the USB hub. It works just fine that way so I will leave it. Thanks to all for the help. ---
**Author:** ![tomwyckoff44](https://avatars.discourse-cdn.com/v4/letter/t/ecc23a/32.png) [@tomwyckoff44](https://forums.digi.com/u/tomwyckoff44)\ **Post date:** [March 27, 2009, 1:57pm UTC](https://forums.digi.com/t/while-sending-pilot-bios-timeout-while-waiting-for-response-from-target/9576/12 "2009-03-27T13:57:00Z")
I had a post on this forum a while back with pretty much the same issue. The RCM5700 doesn’t like working through a USB hub. I think it’s a timing thing, the slight extra delays mess up the data transfers. ---
**Author:** ![BobCochran](https://avatars.discourse-cdn.com/v4/letter/b/bc8723/32.png) [@BobCochran](https://forums.digi.com/u/BobCochran)\ **Post date:** [April 3, 2009, 11:42pm UTC](https://forums.digi.com/t/while-sending-pilot-bios-timeout-while-waiting-for-response-from-target/9576/13 "2009-04-03T23:42:17Z")
I had this same thing happen to me with my own 5600W. In my case, the PC is a Dell Latitude E6400 laptop docked to a Dell docking station. I had connected my USB cable from a USB port on the docking station, to the interface board carrying the 5600W. That caused the error. Solution was to take the laptop off the docking station and plug the cable directly into the laptop’s “power share” USB port on the left side. If it first you don’t succeed, try a different USB port. Bob ---
**Author:** ![tomwyckoff44](https://avatars.discourse-cdn.com/v4/letter/t/ecc23a/32.png) [@tomwyckoff44](https://forums.digi.com/u/tomwyckoff44)\ **Post date:** [April 4, 2009, 12:24am UTC](https://forums.digi.com/t/while-sending-pilot-bios-timeout-while-waiting-for-response-from-target/9576/14 "2009-04-04T00:24:17Z")
I don’t think it’s a powered vs unpowered port thing. I prefer using a powered hub rather then direct connected ports for the simple reason that I’m getting too old to be soldering them dang tiny SMT fuses on the mother board ports. It’s a lot simpler to toss out a hub and get a new one when you mess up and draw too much power. That being said, the problem with the rabbits seems to be a timing thing, they can’t deal with the extra delays involved with using a hub. Actually, I’ll place a small wager it’s not the rabbits as much as Dynamic C. Maybe they can soften up the timing a bit for the next release. ---
**Author:** ![bflusche](https://avatars.discourse-cdn.com/v4/letter/b/e480ec/32.png) [@bflusche](https://forums.digi.com/u/bflusche)\ **Post date:** [April 7, 2009, 9:26pm UTC](https://forums.digi.com/t/while-sending-pilot-bios-timeout-while-waiting-for-response-from-target/9576/15 "2009-04-07T21:26:18Z")
Ditto the earlier comments for an IBM ThinkPad. The RCM5600W would issue comms errors when I used the USB ports on my IBM ThinkPad docking station. Moved the USB to the laptop itself and it worked fine.