Sign in

username:

password:



Not a member?

Search c55x



Search tips

Subscribe to c55x



c55x by Keywords

AIC23 | C5509 | CCS | CSL | EMIF | EVM | GEL | GPIO | HPI | Interfacing | JTAG | McBSP | OMAP | Omap15 | OMAP59 | RTDX | SDRAM | TMS320VC5509 | USB | XDS5

Ads

Discussion Groups

Discussion Groups | TMS320C55x | Re: c5510 System Register

Technical discussions about the TI C55x DSPs (including the c5501, c5502, c5503, c5507, c5509, c5510 and OMAP5910).

  

Post a new Thread

c5510 System Register - Paul DeBuigne - Feb 4 18:46:00 2002



Hello,

If anyone is using C5510 Rev 2 silicon and has a SDI515 connected, or
any emulator, can you check the contents of the System Register (SYSR)
located at port address 0x07fd. According to TI's migration notes the
reset state is 0x0200, (HPE bit set). I am seeing 0.

Thanks,
Paul DeBuigne
Cadwell Labs






(You need to be a member of c55x -- send a blank email to c55x-subscribe@yahoogroups.com )

Re: c5510 System Register - Author Unknown - Feb 5 15:56:00 2002


        /**** Read the values back from the codec to check if they were written correctly */
           check = 0;
           for(mcbsp=0;mcbsp<NUM_CW_QUE;mcbsp++)                
                 for(addr=0;addr<NUM_CODECS_PER_MCBSP;addr++)                        
                        for(i=0;i<CW_INIT_SIZE;i++)                        
                        {
                                while(CheckCWque(mcbsp));            
                                QueControlWord(mcbsp,(CWInitbuffer[i]&0x7fff)|(addr<<CODEC_AD0),&CWInitcheckbuffer[check++] );  
                        }

Hello group, I'm having some strange behavior with breakpoints and certain code segments. First of all, I presume I'm doing something wrong, but it isn't evident right now.

What is happening is that if I set a breakpoint in or very near after this particular code segment, this code will not function... i.e. the buffers do not fill with returned codec data.
I'm baffled, because if I let it run it works fine, if I set a breakpoint further down the same routine it  gathers all the data correctly.

This particular code segment is in a SWI that gets posted in main(), before bios starts.

Not sure if the number of nested loops (with a BP) is the issue or that it is in a SWI and there is an exception I'm not aware of.... sorry for the "strange" question.

If there is anyone who could shed some light on this strange behavior, I would be very grateful.

thanks

Perry Howell




(You need to be a member of c55x -- send a blank email to c55x-subscribe@yahoogroups.com )

RE: c5510 System Register - Kevin Powell - Feb 6 19:23:00 2002

Perry,

You'll want to check the settings of the FREE and SOFT bits in the SPCR2
register of each McBSP that you are using. These bits control how the
ports behave when debugging.

Kevin Powell > Date: Tue, 5 Feb 2002 09:56:31 -0600
> From:
> Subject: Re: c5510 System Register
>
> /**** Read the values back from the codec to check if
> they were written
> correctly */
> check = 0;
> for(mcbsp=0;mcbsp<NUM_CW_QUE;mcbsp++)
> for(addr=0;addr<NUM_CODECS_PER_MCBSP;addr++)
> for(i=0;i<CW_INIT_SIZE;i++)
> {
> while(CheckCWque(mcbsp));
>
> QueControlWord(mcbsp,(CWInitbuffer[i]&0x7fff)|(addr<<CODEC_AD0
> ),&CWInitcheckbuffer[check++] );
> }
>
> Hello group, I'm having some strange behavior with
> breakpoints and certain
> code segments. First of all, I presume I'm doing something
> wrong, but it
> isn't evident right now.
>
> What is happening is that if I set a breakpoint in or very
> near after this
> particular code segment, this code will not function... i.e.
> the buffers
> do not fill with returned codec data.
> I'm baffled, because if I let it run it works fine, if I set
> a breakpoint
> further down the same routine it gathers all the data correctly.
>
> This particular code segment is in a SWI that gets posted in main(),
> before bios starts.
>
> Not sure if the number of nested loops (with a BP) is the
> issue or that it
> is in a SWI and there is an exception I'm not aware of....
> sorry for the
> "strange" question.
>
> If there is anyone who could shed some light on this strange
> behavior, I
> would be very grateful.
>
> thanks
>
> Perry Howell





(You need to be a member of c55x -- send a blank email to c55x-subscribe@yahoogroups.com )