DSPRelated.com
Forums

Re: Error message while profiling

Started by Mike Dunn October 6, 2005
Li Bing,

You do not mention which c6x DSP that you are using.

The error message shows a problem at memory address
0x00083F6C. Most c6x devices do not have memory at
that address - check the map file and linker command
file.

mikedunn

--- Li Bing <libing@libi...> wrote:

> HI, DSP friends
>
> I am using XD5510PP connected with a custom DSP
> board. I can run my code
> successfully in CCS IDE. But when I try to profile a
> loop of my code, the
> following error message shows. Please give me some
> hint on it. > Breakpoint Manager: Attempting to set a hardware
> breakpoint instead
> Can't Set Breakpoint at 0x83f6c: Error
> 0x00000008/-1076 Error during: Break
> Point, Cannot set/verify breakpoint at 0x00083F6C
> sequence ID: 7 Error
> Code: -1076 Error Class: 0x00000008 > Thanks
>
> Regards
> LI Bing
>
> [This e-mail is confidential and may be priviledged.
> If you are not the
> intended recipient, please kindly notify us
> immediately and delete the message
> from your system; please do not copy or use it for
> any purpose, nor disclose
> its contents to any other person. Thank you.]
> ---ST Electronics Group--- > c6x-unsubscribe@c6x-... >
>




HI, DSP friends

I am using XD5510PP connected with a custom DSP board. I can run my code
successfully in CCS IDE. But when I try to profile a loop of my code, the
following error message shows. Please give me some hint on it. Breakpoint Manager: Attempting to set a hardware breakpoint instead
Can't Set Breakpoint at 0x83f6c: Error 0x00000008/-1076 Error during: Break
Point, Cannot set/verify breakpoint at 0x00083F6C sequence ID: 7 Error
Code: -1076 Error Class: 0x00000008 Thanks

Regards
LI Bing

[This e-mail is confidential and may be priviledged. If you are not the
intended recipient, please kindly notify us immediately and delete the message
from your system; please do not copy or use it for any purpose, nor disclose
its contents to any other person. Thank you.]
---ST Electronics Group---



Li Bing,

Please see my comments below.

--- Li Bing <libing@libi...> wrote:

> Hi ,Mike
>
> Thanks for your suggestion.
>
> I have added a simple linker command file in my
> code. As my code is not
> too large, I just put everything into ISRAM, which
> is 1M for C6416. I can
> run the code successfully, but error appear as
> following when profiling.
> Could you please give some hint on it?
>
> Thanks
> Li bing
>
> Can't Set Breakpoint at 0x43d6c: Error
> 0x00000008/-1076 Error during: Break
> Point, Cannot set/verify breakpoint at 0x00043D6C
> Sequence ID: 7 Error
> Code: -1076 Error Class: 0x00000008
> Breakpoint Manager: Attempting to set a hardware
> breakpoint instead

I actually miscounted the digits in your original
email - the error message is within the 1MB mem space
of the 6416. This error message indicates that CCS
has a problem reading or writing memory [it is most
likely not a hardware problem] when trying to set a
software breakpoint [SWBP].
When CCS tries to set a SWBP, a sequence similar to
the following occurs - read and save the memory
contents, write the SWBP to memory, read memory to
verify the SWBP. This verification is failing in your
case. Since this problem is likely sw related,
generate a map file for your program, and see what is
located at address 0x00043D6C. It is possible that
this is near a data buffer or array that is over
running or that has a cache line that is/was in both
the data and program cache. Also, even if your
program appears to be working without profiling, it
most likely contains some type of problem.

mikedunn
>
> MEMORY
> {
> ISRAM : origin = 0x0, len =
> 0x100000
>
> }
>
> SECTIONS
> {
> .vectors > ISRAM
> .text > ISRAM
> .data > ISRAM
>
> .bss > ISRAM
> .cinit > ISRAM
> .const > ISRAM
> .far > ISRAM
> .stack > ISRAM
> .cio > ISRAM
> .sysmem > ISRAM
> }
>
> -----Original Message-----
> From: Mike Dunn [SMTP:mike-dunn@mike...]
> Sent: Thursday, October 06, 2005 12:15 PM
> To: libing@libi...
> Subject: RE: [c6x] Error message while profiling
>
> Li Bing,
>
> You need to use a linker command file when compiling
> code for hardware. One of the purposes of a linker
> command file is to describe the physical memory
> layout
> to the compiler.
>
> mikedunn
>
> --- Li Bing <libing@libi...> wrote:
>
> > Hi, Mike
> >
> > More information.
> > I did not use any linker command file in my code.
> >
> >
> > Thanks
> > Li Bing
> > -----Original Message-----
> > From: Mike Dunn [SMTP:mike-dunn@mike...]
> > Sent: Thursday, October 06, 2005 11:54 AM
> > To: libing@libi...; 'C64x'; 'ccs'
> > Subject: Re: [c6x] Error message while profiling
> >
> > Li Bing,
> >
> > You do not mention which c6x DSP that you are
> using.
> >
> > The error message shows a problem at memory
> address
> > 0x00083F6C. Most c6x devices do not have memory
> at
> > that address - check the map file and linker
> command
> > file.
> >
> > mikedunn
> >
> > --- Li Bing <libing@libi...> wrote:
> >
> > > HI, DSP friends
> > >
> > > I am using XD5510PP connected with a custom DSP
> > > board. I can run my code
> > > successfully in CCS IDE. But when I try to
> profile
> > a
> > > loop of my code, the
> > > following error message shows. Please give me
> some
> > > hint on it.
> > >
> > >
> > > Breakpoint Manager: Attempting to set a hardware
> > > breakpoint instead
> > > Can't Set Breakpoint at 0x83f6c: Error
> > > 0x00000008/-1076 Error during: Break
> > > Point, Cannot set/verify breakpoint at
> 0x00083F6C
> >
> > > sequence ID: 7 Error
> > > Code: -1076 Error Class: 0x00000008
> > >
> > >
> > > Thanks
> > >
> > > Regards
> > > LI Bing
> > >
> > > [This e-mail is confidential and may be
> > priviledged.
> > > If you are not the
> > > intended recipient, please kindly notify us
> > > immediately and delete the message
> > > from your system; please do not copy or use it
> for
> > > any purpose, nor disclose
> > > its contents to any other person. Thank you.]
> > > ---ST Electronics Group---
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > to:
> > > c6x-unsubscribe@c6x-...
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
>