# Getting Error while sending cold loader, no rabbit processor detected on a BL4S110

**URL:** <https://forums.digi.com/t/getting-error-while-sending-cold-loader-no-rabbit-processor-detected-on-a-bl4s110/17053>\
**Category:** Rabbit Software\
**Tags:** bl4s100\
**Created:** [July 8, 2016, 10:45am UTC](https://forums.digi.com/t/getting-error-while-sending-cold-loader-no-rabbit-processor-detected-on-a-bl4s110/17053 "2016-07-08T10:45:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jayf1200](https://avatars.discourse-cdn.com/v4/letter/j/848f3c/32.png) [@jayf1200](https://forums.digi.com/u/jayf1200)\
**Post date:** [July 8, 2016, 10:45am UTC](https://forums.digi.com/t/getting-error-while-sending-cold-loader-no-rabbit-processor-detected-on-a-bl4s110/17053/1 "2016-07-08T10:45:41Z")

</div>

I am getting the error of no rabbit processor detected on a BL4S110 board. I have programmed it before about a year ago but i have to do an update to the program. I am using a 20-101-1183 USB programming cable, the Tx light turns on, but the Rx doesn’t light. I checked the Latency timer and changed it, did not help. I re-installed Dynamic C 10.72A with everything connected and still no change.

Any help is appreciated.

---

<div class="post-metadata">

**Author:** ![cpigilam](https://avatars.discourse-cdn.com/v4/letter/c/fbc32d/32.png) [@cpigilam](https://forums.digi.com/u/cpigilam)\
**Post date:** [July 12, 2016, 1:13am UTC](https://forums.digi.com/t/getting-error-while-sending-cold-loader-no-rabbit-processor-detected-on-a-bl4s110/17053/2 "2016-07-12T01:13:11Z")

</div>

Hello, Check your programming cable is connected properly or not?  
Choose below settings under Project options,  
Debug Baud Rate: 115200  
Choose “Disable Baud Negotiation”,  
Stop Bits: 2  
Choose “Enable Processor verification”,  
Choose " Use USB to serial converter"

Choose “Enable separate instruction and data space”, then compile the sample program. Still if you are facing the issues, may be there is some issue with the hardware. If you have another programming cable, try to test with the another cable.
