I would advise to upload the patch/update to somewhere else as well. My
experience is that these kind of things may just disappear one day when TI
decides to clean up and forgets about the problem.

-Sima

On Mon, Nov 15, 2010 at 8:05 PM, Jeff Brower wrote:

> All-
>
> For anyone reading this thread in the future, I will add a couple of
> notes...
>
> We did suspect a software issue, so we made the project completely portable
> between our board and the DSK 5510 board,
> in order to rule out JTAG emulator, cable, software, CCS version, etc. To
> do that we set the DSK board to HPI boot
> mode and JTAG to 14-pin external header (i.e. not USB), via user switches.
>
> Even then breakpoints worked on the DSK 5510 but not our board. So then we
> suspected a hardware issue. Fortunately
> Aditi discovered the CCS patch (good work Aditi!).
>
> Why the DSK 5510 could "get around the patch" we don't know. I might guess
> this was an issue Spectrum Digital dealt
> with back in the early days of the DSK 5510 and there is also a
> non-published hardware level solution for it.
>
> -Jeff
>
> > Finally solved the problem.
> > I was using a CCS v3.3.38.2
> > It looks like the CCS version was too old and had to be updated with the
> > latest patch.
> >
> > Here is the link for the latest patch.
> >
> >
> http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_ccstudio/CCSv3/SR/SR12_CCS_v3.3_SR_3.3.82.13.exe
> >
> > The breakpoints are now working. The only thing that I did not understand
> > was, the breakpoints worked for DSK5510 board even without the patch.
> >
> > Regards,
> > Aditi.
> >
> >> Hi,
> >>
> >> This might sound like an old issue but here is my problem.
> >>
> >> I have set breakpoints in my code, and when I run the code, the debugger
> > does not halt at any breakpoint (i have tried to set breakpoint even in
> > Disassembly window just after _c_int00_). When I single-step through the
> > code, the control enters main(), but when I run the code, the control
> > just
> >> hangs (like goes to some other point) . Does not ever go to main().
> >>
> >> I am using CCS v3.3 and BIOS v5.41 for TMS320C5510 and XDS510PP-Plus
> > emulator. And the code is just some simple thing like to fill a part of
> > SRAM with a pattern.
> >>
> >> Another strange thing is that if I run the same program in C5510 Device
> > simulator, the code runs fine. Also the debugger halts if I have
> > breakpoints in the code.
> >>
> >> Can somebody help me with this?
> >> Might be I am missing some very small thing that I have to setup or
> > something like that.
> >>
> >> Thanks,
> >> Regards,
> >> Aditi.
>
>
>

All-

For anyone reading this thread in the future, I will add a couple of notes...

We did suspect a software issue, so we made the project completely portable between our board and the DSK 5510 board,
in order to rule out JTAG emulator, cable, software, CCS version, etc. To do that we set the DSK board to HPI boot
mode and JTAG to 14-pin external header (i.e. not USB), via user switches.

Even then breakpoints worked on the DSK 5510 but not our board. So then we suspected a hardware issue. Fortunately
Aditi discovered the CCS patch (good work Aditi!).

Why the DSK 5510 could "get around the patch" we don't know. I might guess this was an issue Spectrum Digital dealt
with back in the early days of the DSK 5510 and there is also a non-published hardware level solution for it.

-Jeff

> Finally solved the problem.
> I was using a CCS v3.3.38.2
> It looks like the CCS version was too old and had to be updated with the
> latest patch.
>
> Here is the link for the latest patch.
>
> http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_ccstudio/CCSv3/SR/SR12_CCS_v3.3_SR_3.3.82.13.exe
>
> The breakpoints are now working. The only thing that I did not understand
> was, the breakpoints worked for DSK5510 board even without the patch.
>
> Regards,
> Aditi.
>
>> Hi,
>>
>> This might sound like an old issue but here is my problem.
>>
>> I have set breakpoints in my code, and when I run the code, the debugger
> does not halt at any breakpoint (i have tried to set breakpoint even in
> Disassembly window just after _c_int00_). When I single-step through the
> code, the control enters main(), but when I run the code, the control
> just
>> hangs (like goes to some other point) . Does not ever go to main().
>>
>> I am using CCS v3.3 and BIOS v5.41 for TMS320C5510 and XDS510PP-Plus
> emulator. And the code is just some simple thing like to fill a part of
> SRAM with a pattern.
>>
>> Another strange thing is that if I run the same program in C5510 Device
> simulator, the code runs fine. Also the debugger halts if I have
> breakpoints in the code.
>>
>> Can somebody help me with this?
>> Might be I am missing some very small thing that I have to setup or
> something like that.
>>
>> Thanks,
>> Regards,
>> Aditi.

Hi,

Finally solved the problem.
I was using a CCS v3.3.38.2
It looks like the CCS version was too old and had to be updated with the
latest patch.

Here is the link for the latest patch.

http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_ccstudio/CCSv3/SR/SR12_CCS_v3.3_SR_3.3.82.13.exe

The breakpoints are now working. The only thing that I did not understand
was, the breakpoints worked for DSK5510 board even without the patch.

Regards,
Aditi.

> Hi,
>
> This might sound like an old issue but here is my problem.
>
> I have set breakpoints in my code, and when I run the code, the debugger
does not halt at any breakpoint (i have tried to set breakpoint even in
Disassembly window just after _c_int00_). When I single-step through the
code, the control enters main(), but when I run the code, the control
just
> hangs (like goes to some other point) . Does not ever go to main().
>
> I am using CCS v3.3 and BIOS v5.41 for TMS320C5510 and XDS510PP-Plus
emulator. And the code is just some simple thing like to fill a part of
SRAM with a pattern.
>
> Another strange thing is that if I run the same program in C5510 Device
simulator, the code runs fine. Also the debugger halts if I have
breakpoints in the code.
>
> Can somebody help me with this?
> Might be I am missing some very small thing that I have to setup or
something like that.
>
> Thanks,
> Regards,
> Aditi.
>

Hi,

A small claification on my post.
The single-stepping works perfectly fine.
Breakpoints dont work and the debugger does not halt at the breakpoints.

Why is it that single-stepping works and breakpoints dont?

Thanks,
Aditi.

> Hi,
>
> This might sound like an old issue but here is my problem.
>
> I have set breakpoints in my code, and when I run the code, the debugger
> does not halt at any breakpoint (i have tried to set breakpoint even in
> Disassembly window just after _c_int00_). When I single-step through the
> code, the control enters main(), but when I run the code, the control just
> hangs (like goes to some other point) . Does not ever go to main().
>
> I am using CCS v3.3 and BIOS v5.41 for TMS320C5510 and XDS510PP-Plus
> emulator. And the code is just some simple thing like to fill a part of
> SRAM with a pattern.
>
> Another strange thing is that if I run the same program in C5510 Device
> simulator, the code runs fine. Also the debugger halts if I have
> breakpoints in the code.
>
> Can somebody help me with this?
> Might be I am missing some very small thing that I have to setup or
> something like that.
>
> Thanks,
> Regards,
> Aditi.

Hi,

This might sound like an old issue but here is my problem.

I have set breakpoints in my code, and when I run the code, the debugger
does not halt at any breakpoint (i have tried to set breakpoint even in
Disassembly window just after _c_int00_). When I single-step through the
code, the control enters main(), but when I run the code, the control just
hangs (like goes to some other point) . Does not ever go to main().

I am using CCS v3.3 and BIOS v5.41 for TMS320C5510 and XDS510PP-Plus
emulator. And the code is just some simple thing like to fill a part of
SRAM with a pattern.

Another strange thing is that if I run the same program in C5510 Device
simulator, the code runs fine. Also the debugger halts if I have
breakpoints in the code.

Can somebody help me with this?
Might be I am missing some very small thing that I have to setup or
something like that.

Thanks,
Regards,
Aditi.