RE: Re: Problems are about the MPC566's CLOCK

"Dobbin Allan-r11834" <[email protected]>
Newsgroups gmane.comp.hardware.motorola.microcontrollers
Message-ID <4147ED8B92A864498825C07E53594E4AD4878A@az33exm20.fsl.freescale.net>
This generally indicates that the PLL has not locked.  As well as the
PLL circuitry, please check you are not coming out of reset too early -
this can be caused by too high a pull-up on HRESET - try reducing to a
1K if you have a higher value.
 
 

	-----Original Message-----
	From: [email protected] [mailto:[email protected]] On
Behalf Of illtll801021
	Sent: Friday, June 09, 2006 11:34 PM
	To: [email protected]
	Subject: [MPC500] Re: Problems are about the MPC566's CLOCK
	
	

	Thank you! 
	The associated clock circuitry as you indicated is the same to
the 
	MPC566EVB. I did not use the MC33394, this is different to the 
	MPC566EVB in the power, reset and clock circuit.MODCLK is 010.
	Yestoday, I wrote a simple programe with MPC500_Quick_Start's
API, 
	to set the SCCR and PLPRCR, then use two variables circularly
read 
	the value of these two registers. 
	
	UWord32 clkReg;
	UWord32 pllReg;
	void main(void)
	{
	clkReg=0x00000000;
	pllReg=0x00000000;
	ioctl( USIU, USIUCLK_WRITE_SYSCLK_CONTROL_REG, 0x81210000L );
	ioctl(USIU,USIUCLK_WRITE_PLL_LP_RESET_CONTROL_REG,0x00900001L );
	clkReg = ioctl( USIU, USIUCLK_READ_SYSCLK_CONTROL_REG, NULL );
	pllReg = ioctl(USIU,USIUCLK_READ_PLL_LP_RESET_CONTROL_REG,NULL);
	while (1) 
	{
	clkReg = ioctl( USIU, USIUCLK_READ_SYSCLK_CONTROL_REG, NULL );
	pllReg = ioctl(USIU,USIUCLK_READ_PLL_LP_RESET_CONTROL_REG,NULL);
	}
	
	}
	
	I found that the value of SCCR always became 0x81290000, it 
	showed that the BUCS is 1. Why did it differ with the value I
set? 
	Why did it not be found in the MPC566EVB? 
	
	--- In [email protected] <mailto:MPC500%40yahoogroups.com>
, "Dobbin Allan-r11834" 
	<Allan.Dobbin@...> wrote:
	>
	> You have to verify not only the cycstal circuit, but also the 
	associated
	> clock circuitry i.e. MODCLK, Vddsyn, Xfc, etc. Make sure your 
	board is
	> coming out of reset. Obviously the sysclock/clkout depend on 
	values
	> programmed into SCCR (EBDF allows a clkout /2 option) and MF 
	withing
	> PLPRCR.
	> 
	> 
	> -----Original Message-----
	> From: [email protected] <mailto:MPC500%40yahoogroups.com>

	[mailto:[email protected] <mailto:MPC500%40yahoogroups.com>
] On
	> Behalf Of illtll801021
	> Sent: Thursday, June 08, 2006 11:01 PM
	> To: [email protected] <mailto:MPC500%40yahoogroups.com> 
	> Subject: [MPC500] Problems are about the MPC566's CLOCK
	> 
	> 
	> 
	> Hi everyone:
	> I'm puzzled by the MPC566's CLOCK. I used the Axiom 
	MPC566EVB
	> and 
	> Codewarrior. I used MPC500_Quick_Start's GCT to set the 
	system
	> clock on 
	> 40Mhz,and the same to Clockout. I debuged it in internal 
	flash
	> and the 
	> crystal oscillator is 4 Mhz. When I debuged it with the
	> MPC566EVB, it 
	> is all right. But when I debuged it with my board that the
	> circuit of 
	> crystal is same to the MPC566EVB, the Clockout output 2Mhz. 
	Why?
	> Please 
	> help me! What should I do? Thanks!!!
	> liulong
	> 
	> 
	> 
	> 
	> 
	> 
	> 
	> 
	> [Non-text portions of this message have been removed]
	>
	
	

	 



[Non-text portions of this message have been removed]



------------------------ Yahoo! Groups Sponsor --------------------~--> 
Get to your groups with one click. Know instantly when new email arrives
http://us.click.yahoo.com/.7bhrC/MGxNAA/yQLSAA/dN_tlB/TM
--------------------------------------------------------------------~-> 

-----------------------------------------------------------
To learn more about Freescale Microcontrollers, please visit
http://www.freescale.com/mcu


 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/MPC500/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.