Forums

JTAG loses connection with target and flash problem.

Started by embeddeddes October 8, 2004


Hi everyone,

This is a two part question but I believe they may be related. I
have a board designed around the 56F807 using the evm as a
reference. The board has the same external memory configuration as
the evm and we program it using Codewarrior IDE 5.1.1 with a bit of
the SDK 3.0. With the target set to internal flash, we use the
external memory for data. We have been using the board for a while
but recently I been having a couple of problems as follows.

Problem 1: When I download to the board with the target set to
external or internal memory, the board appears to work fine but the
I may lose the JTAG connection with the board. I can stop the
process a couple of times but eventually It loses the target. The
strange thing is the board appears to be running the program still
and has not halted. I'm not sure if this is a common problem or
just with this board and its JTAG circuitry. I have also noticed a
couple of times that the JTAG likes to reset the board. I know the
reset pin of the LPT port can toggle a couple of times when the
computer starts up but is it still possible for the reset pin to
toggle while debugging?

Problem 2: I'm having a problem with one of my bigger applications
when I set the target for internal memory (p in flash and x in
int/ext memory). I can run the application both in external and
internal memory but when I send it to internal memory and allow the
power to cycle, it ceases to run properly. I have tested smaller
application and they are running properly but this one doesn't and
its kinda the important one. I have payed close attention to stack
sizes and memory allocation but I have not been able to pinpoint the
problem. I'm not certain but I believe that it may have something
to do with the application initialized data but how can I check this
after I cycle the power. I have also found something weird in
the 'flash.elf.xMAP' file.

In the '# .ApplicationInitialzedData' section this variable appears
to be using 20 words of data but what is it ->

00000040 00000014 .data F@605 (main.c) Finally why would I think these two problems are related. I was
thinking that it may be my program that causes the debug session to
stop working. I'm not certain but since the COP is included as a
subset of the BSP, could my program be reseting the board causing
the JTAG to lose communication.





Problem 1: I've seen the same problem in my application, it was
caused by external electrical noise (a welder thermoswitch
commutation, a switch turned on or off etc).Theese events generates
an error in the comunication protocol. The codewarrior gives me an
error but the application contnue to run

--- In , "embeddeddes" <embeddeddes@y...>
wrote:
>
>
> Hi everyone,
>
> This is a two part question but I believe they may be related. I
> have a board designed around the 56F807 using the evm as a
> reference. The board has the same external memory configuration as
> the evm and we program it using Codewarrior IDE 5.1.1 with a bit of
> the SDK 3.0. With the target set to internal flash, we use the
> external memory for data. We have been using the board for a while
> but recently I been having a couple of problems as follows.
>
> Problem 1: When I download to the board with the target set to
> external or internal memory, the board appears to work fine but the
> I may lose the JTAG connection with the board. I can stop the
> process a couple of times but eventually It loses the target. The
> strange thing is the board appears to be running the program still
> and has not halted. I'm not sure if this is a common problem or
> just with this board and its JTAG circuitry. I have also noticed a
> couple of times that the JTAG likes to reset the board. I know the
> reset pin of the LPT port can toggle a couple of times when the
> computer starts up but is it still possible for the reset pin to
> toggle while debugging?
>
> Problem 2: I'm having a problem with one of my bigger applications
> when I set the target for internal memory (p in flash and x in
> int/ext memory). I can run the application both in external and
> internal memory but when I send it to internal memory and allow the
> power to cycle, it ceases to run properly. I have tested smaller
> application and they are running properly but this one doesn't and
> its kinda the important one. I have payed close attention to stack
> sizes and memory allocation but I have not been able to pinpoint
the
> problem. I'm not certain but I believe that it may have something
> to do with the application initialized data but how can I check
this
> after I cycle the power. I have also found something weird in
> the 'flash.elf.xMAP' file.
>
> In the '# .ApplicationInitialzedData' section this variable appears
> to be using 20 words of data but what is it ->
>
> 00000040 00000014 .data F@605 (main.c) > Finally why would I think these two problems are related. I was
> thinking that it may be my program that causes the debug session to
> stop working. I'm not certain but since the COP is included as a
> subset of the BSP, could my program be reseting the board causing
> the JTAG to lose communication.