Hi all, I'm trying to debug my application but there's something
strange. When I compile my application targetless it does compile ok without
problems but when I try to compile it to flash to debug through the stdio I
receive the "While debugging..Timeout while waiting for response from target"
error after loading the image in flash. Any ideas of what could be the cause of
this strange behaviour??? I'm sure it has to do with my application, but I
dont know what it could be.....thanks in advance
Alejandro Islas
Ingeniero de Desarrollo
[a...@softel.net.mx](mailto:a...@softel.net.mx)
Softel SA de CV
Camino a Santa Teresa 187C Piso 5
Parques del Pedregal
Mexico DF 14010
Mexico
+52 (55) 5665 5577
Running in debug mode Timeout while waiting for response from target
Started by ●March 8, 2004
Reply by ●March 8, 20042004-03-08
If you receive "Timeout...." during download process, then this is entirely
different problem. If you receive "Timeout" after you start you application,
most probably you've something messed up.
Make sure you're not disabling interrupts in some way, and you don't use Port A for STDIO redirection. During debugs, printf()'s are rerouted to debug window "behind scenes".
HTH, George
Make sure you're not disabling interrupts in some way, and you don't use Port A for STDIO redirection. During debugs, printf()'s are rerouted to debug window "behind scenes".
HTH, George
Reply by ●March 8, 20042004-03-08
I receive the "Timeout..." after complete sending all the packets to the target,
just beforethe green prompt appears at the beginning of my application. In
other words, I'm not able to click the Run icon after compiling to flash,
but I do see that all the packages are sent. What kind of things I could be
messing up???
Reply by ●March 8, 20042004-03-08
Check the following:
(1) You are not using a hacked bios.
(2) RST28's are enabled in compiler options
(3) There is not a #nodebug or a debug in front of main.
(4) Remove all #GLOBAL_INIT's and change it to a function chain
#makechain MyInit
main() {
MyInit();
.
.
.
}
void MyFunction() {
segchain MyInit {
// Code here instead of global init
}
}
The reason for #4 is that if you have initialization inside a #nodebug
function, it may fail. When a program is downloaded, it runs, even without
your permission, to the first RST28 it finds. The GLOBAL_INIT's are
executed until one is found that has a breakpoint in it.
(5) Check that nothing unusual is set in the defines section of the
compiler options.
(1) You are not using a hacked bios.
(2) RST28's are enabled in compiler options
(3) There is not a #nodebug or a debug in front of main.
(4) Remove all #GLOBAL_INIT's and change it to a function chain
#makechain MyInit
main() {
MyInit();
.
.
.
}
void MyFunction() {
segchain MyInit {
// Code here instead of global init
}
}
The reason for #4 is that if you have initialization inside a #nodebug
function, it may fail. When a program is downloaded, it runs, even without
your permission, to the first RST28 it finds. The GLOBAL_INIT's are
executed until one is found that has a breakpoint in it.
(5) Check that nothing unusual is set in the defines section of the
compiler options.
Reply by ●March 8, 20042004-03-08
Reply by ●March 18, 20042004-03-18
Hi,
I had the same problem. Used a brand new cable from a college and it
worked. I did replace the tiny 10 pin ribbon cable connector and
still had problems. After checking the programming cable I decided to
replace the DB9 connecor and it worked like a charm. I had this
problem not only with one pragramming cable but with two.
I had the same problem. Used a brand new cable from a college and it
worked. I did replace the tiny 10 pin ribbon cable connector and
still had problems. After checking the programming cable I decided to
replace the DB9 connecor and it worked like a charm. I had this
problem not only with one pragramming cable but with two.
Reply by ●March 22, 20042004-03-22
Hai i think u r getting the error because of port a which is used for
programming since the programming cable is connected to the port a and trying
for listening to that port u r getting this error no problem carry on when u
code the rabbit and now remove the power supply and the programming cable and
run then it will run fine. I tried out this and got the output
