- Fri Mar 16, 2007 5:12 am
#27289
I have a small but annoying issue when using the USB JTAG Tiny with an Olimex P149 Proto board.
I have an application where the bulk of the code resides in Flash @ 0x7000, but has an algorithm currently located in RAM @ 0x200 because it's continually evolving and I'm simply saving Flash wear cycles.
The issue is whenever code is changed resulting in different code length the first JTAG download fails to verify because the memory word at 0x200 is overwritten with the value 0x200 instead of the mov #0A00h,sp instruction.
Cancelling the Kickstart debug session and restarting it always succeeds.
The first debug download of the day always succeeds.
If the code is unchanged in length the download always succeeds even if the code is different.
Can anybody shed some light on things?
Host System: Win XP
Kickstart: v3.40.1.9
JTAG Tiny drivers: 1.011
2.0m USB cable
Debugger options: Verify download & Retain Memory
--
I have an application where the bulk of the code resides in Flash @ 0x7000, but has an algorithm currently located in RAM @ 0x200 because it's continually evolving and I'm simply saving Flash wear cycles.
The issue is whenever code is changed resulting in different code length the first JTAG download fails to verify because the memory word at 0x200 is overwritten with the value 0x200 instead of the mov #0A00h,sp instruction.
Cancelling the Kickstart debug session and restarting it always succeeds.
The first debug download of the day always succeeds.
If the code is unchanged in length the download always succeeds even if the code is different.
Can anybody shed some light on things?
Host System: Win XP
Kickstart: v3.40.1.9
JTAG Tiny drivers: 1.011
2.0m USB cable
Debugger options: Verify download & Retain Memory
--
Steve