Sign in

username:

password:



Not a member?

Search c6x



Search tips

Subscribe to c6x



c6x by Keywords

AD535 | BIOS | Booting | Bootloader | C621 | C6211 | C6415 | C671 | C6711 | C6711DSK | C6713 | CCS | Chassaing | COFF | DAT | DM64 | DM642 | DMA | DSK671 | DSK6711 | EDM | EDMA | EMIF | Emulator | EVM | EVM620 | FFT | FIR | GPIO | Halting | HPI | HWI | IDK | JTAG | LDB | LDH | LDW | Linker | LMS | LOG_printf | Matlab | McBSP | MEM_alloc | MIPS | PCI | PCM3003 | Pipeline | Profiling | QDM | Reset | ROM | RTDX | Sampling | SDRAM | Stack | TEB | THS1206 | TMS320C621 | TMS320C6416 | TMS320C6711 | TMS320C6713 | UART | Vector Table | XBUS | XDS560

Ads

Discussion Groups

Discussion Groups | TMS320C6x | Re: EMIF CLOCK

Technical discussions about the TI C6000 DSPs (including the c62x, c64x and c67x DSPs).

  

Post a new Thread

Re: EMIF CLOCK - cman...@emona.com.au - Jun 16 11:01:16 2008




Hi everyone,
>I need some regarding EMIF. I am usign DSK6713. How can i
>determine/set my EMIF clock frequency?
>
>thanks in advance,
>pramod.
>------------------------------------
>
>Check Out Industry's First Single-Chip, Multi-Format, Real-Time HD Video Transcoding
Solution for Commercial & Consumer End Equipment: www.ti.com/dm6467

For any other newbies like me out there, here are some simple steps for experimenting with the
ECLKOUT and read/write strobe rates of your hardware manually....if using 6713DSK with the
6713dsk CCS provided.

I found it handy for tweaking my hardware.

Once your code is running, you can vary the ECLKOUT rate by selecting "View Memory"
in CCS, then go to address 0x01b7c120 (which is the PLLDIV3 setting) and you can change the
values to divide the 450MHz clock by various divisors, while your code is running.

To vary the setup-strobe-hold times of your EMIF read/write strobes, select "view >
registers" and find the registers CECTL2 and CECTL3, and you can directly, on the fly,
vary the strobe timing, while viewing the results on a scope connected to your design.(if you
are using hardware connected to CE2 & 3 that is).

Similarly, using "view > registers" allows you to vary most of the other registers
to fine tune your design.

Hope that is helpful,
Carlo

------------------------------------

OMAP35x EVM jump-starts low-power apps
------------------------------------
The modular and extensible OMAP35x Evaluation Module (EVM) enables developers to start building
applications based on the OMAP35x architecture:http://www.DSPRelated.com/omap35x



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

Re: Re: EMIF CLOCK - Michael Dunn - Jun 17 9:29:13 2008

Carlo,

On 6/16/08, c...@emona.com.au <c...@emona.com.au> wrote:
>
> Hi everyone,
> >I need some regarding EMIF. I am usign DSK6713. How can i
> >determine/set my EMIF clock frequency?
> >
> >thanks in advance,
> >pramod.
> >------------------------------------
> >
> >Check Out Industry's First Single-Chip, Multi-Format, Real-Time HD Video
> Transcoding Solution for Commercial & Consumer End Equipment:
> www.ti.com/dm6467
> >
> > For any other newbies like me out there, here are some simple steps for
> experimenting with the ECLKOUT and read/write strobe rates of your hardware
> manually....if using 6713DSK with the 6713dsk CCS provided.
>
> I found it handy for tweaking my hardware.
>
> Once your code is running, you can vary the ECLKOUT rate by selecting "View
> Memory" in CCS, then go to address 0x01b7c120 (which is the PLLDIV3 setting)
> and you can change the values to divide the 450MHz clock by various
> divisors, while your code is running.
>
> To vary the setup-strobe-hold times of your EMIF read/write strobes, select
> "view > registers" and find the registers CECTL2 and CECTL3, and you can
> directly, on the fly, vary the strobe timing, while viewing the results on a
> scope connected to your design.(if you are using hardware connected to CE2 &
> 3 that is).
>
> Similarly, using "view > registers" allows you to vary most of the other
> registers to fine tune your design.
>

Thanks for posting the feedback. I use this technique when I deal with a new
peripheral. Peeking and poking some registers while looking at the
datasheet/documentation [and sometimes a scope] helps me get a better
understanding before I start writing code. The better that you understand
the hardware behavior, the easier it is to write robust code.

mikedunn

   Hope that is helpful,
> Carlo
>

-- 
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php



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