56303 | 563xx | 5680 | 56805 | 5680x | 56F80 | 56F800DEMO | 56F805 | 56f807 | 56F830 | ADC | Bootloader | Codec | CodeWarrior | CW5 | CW6 | Debugger | DSP56303 | DSP56303EVM | DSP563xx | DSP5680 | DSP56800 | DSP56807 | DSP56858 | DSP56858EVM | DSP56F803 | DSP56F805 | DSP56F807 | DSP56F80x | DSP56F826 | DSP56F827 | DSP56F8xx | EVM | FFT | Flash_over_jtag | GPIO | Interrupt | Interrupts | JTAG | LCD | Linker | MCF5307 | Metrowerks | Modulus | MSCAN | PCMaster | PWM | Quad | Rif | RTOS | SDK | SPI

Hi,

I am using the DSP56858. Is there a way to turn off the EOnCE module 
once the board has been programmed? The reason I am asking this is to 
determine whether and/or how much current is being consumed with it 
on. I have created a project in which I put the DSP into Wait mode 
(wait for interrupt) with no interrupts enabled (other than the core 
interrupts that may occur) so that I can measure the current 
consumption while it is in wait mode. However, the measured current 
consumption does not fall within what is specified on the spec sheet. 
Could the EOnCE be causing this extra current consumption as it is the 
only other module actually running in my program? 

Thank you.
Hardeep

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

1) Tie /TRST to ground and set EOnCE_EBL bit = 0 will
disable EOnCE.
2) To further reduce the current consumption, disable
PLL and clock the CPU core by prescale clock.

Charlie 

--- Hardeep <h...@verichipcorp.com> wrote:

> Hi,
> 
> I am using the DSP56858. Is there a way to turn off
> the EOnCE module 
> once the board has been programmed? The reason I am
> asking this is to 
> determine whether and/or how much current is being
> consumed with it 
> on. I have created a project in which I put the DSP
> into Wait mode 
> (wait for interrupt) with no interrupts enabled
> (other than the core 
> interrupts that may occur) so that I can measure the
> current 
> consumption while it is in wait mode. However, the
> measured current 
> consumption does not fall within what is specified
> on the spec sheet. 
> Could the EOnCE be causing this extra current
> consumption as it is the 
> only other module actually running in my program? 
> 
> Thank you.
> Hardeep
>

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