Hello Rabbit group.
After searching this board and the rest of the WWW, contacting
Z-World, and finding no clues I will post a problem here.
I am using a Windows XP PC and Dynamic C Version 9.21.
The target is a 44 Mhz RCM3200, 256K + 512K SRAM, 512 Flash,
which is mounted on our custome made control board.
My application compiles and starts to download. A the bottom of the
Dynamic C screen the status reads "Sending Write Packet"
After all the code is downloaded, the status at the bottom of the
screen reads "Writing Debug Tag", and then a pop up dialog appears
with the message :
"While Sending User Program:
Timeout while waiting for response from target"
If I power cycle the RCM (I have to have it off for more than 60
seconds)the problem goes away, the application starts and I can debug
it normally. However, the next time I perform a compile/download the
problem re-appears.
The problem does not happen when using an RCM development system, so I
am assuming there is something in the way we have connected it to our
control board.
I know this is not a lot of detail, but I was looking for some
direction as to why this may be happening.
Timeout while waiting for response from target ???
Started by ●January 5, 2006
Reply by ●January 5, 20062006-01-05
At 03:05 PM 1/5/2006 +0000, you wrote:
>
>Hello Rabbit group.
>
>After searching this board and the rest of the WWW, contacting
>Z-World, and finding no clues I will post a problem here.
>
>I am using a Windows XP PC and Dynamic C Version 9.21.
>The target is a 44 Mhz RCM3200, 256K + 512K SRAM, 512 Flash,
>which is mounted on our custome made control board.
>
>My application compiles and starts to download. A the bottom of the
>Dynamic C screen the status reads "Sending Write Packet"
>After all the code is downloaded, the status at the bottom of the
>screen reads "Writing Debug Tag", and then a pop up dialog appears
>with the message :
>
>"While Sending User Program:
>Timeout while waiting for response from target"
>
>If I power cycle the RCM (I have to have it off for more than 60
>seconds)the problem goes away, the application starts and I can debug
>it normally. However, the next time I perform a compile/download the
>problem re-appears.
>
>The problem does not happen when using an RCM development system, so I
>am assuming there is something in the way we have connected it to our
>control board.
>
>I know this is not a lot of detail, but I was looking for some
>direction as to why this may be happening.
Not sure if this helps you or not, but my 2x5 connector that connects to
the Rabbit started to wear out and I started getting occasional errors
where the IDE lost contact with the core. Replacing the header fixed the
problem.
>
>Hello Rabbit group.
>
>After searching this board and the rest of the WWW, contacting
>Z-World, and finding no clues I will post a problem here.
>
>I am using a Windows XP PC and Dynamic C Version 9.21.
>The target is a 44 Mhz RCM3200, 256K + 512K SRAM, 512 Flash,
>which is mounted on our custome made control board.
>
>My application compiles and starts to download. A the bottom of the
>Dynamic C screen the status reads "Sending Write Packet"
>After all the code is downloaded, the status at the bottom of the
>screen reads "Writing Debug Tag", and then a pop up dialog appears
>with the message :
>
>"While Sending User Program:
>Timeout while waiting for response from target"
>
>If I power cycle the RCM (I have to have it off for more than 60
>seconds)the problem goes away, the application starts and I can debug
>it normally. However, the next time I perform a compile/download the
>problem re-appears.
>
>The problem does not happen when using an RCM development system, so I
>am assuming there is something in the way we have connected it to our
>control board.
>
>I know this is not a lot of detail, but I was looking for some
>direction as to why this may be happening.
Not sure if this helps you or not, but my 2x5 connector that connects to
the Rabbit started to wear out and I started getting occasional errors
where the IDE lost contact with the core. Replacing the header fixed the
problem.
