03.08.2013 Views

MC9S12VR-Family - Data Sheet - Freescale Semiconductor

MC9S12VR-Family - Data Sheet - Freescale Semiconductor

MC9S12VR-Family - Data Sheet - Freescale Semiconductor

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

4.3.2 Register Descriptions<br />

<strong>MC9S12VR</strong> <strong>Family</strong> Reference Manual, Rev. 2.8<br />

S12 Clock, Reset and Power Management Unit (S12CPMU_UHV)<br />

This section describes all the S12CPMU_UHV registers and their individual bits.<br />

Address order is as listed in Figure 4-3<br />

4.3.2.1 S12CPMU_UHV Synthesizer Register (CPMUSYNR)<br />

The CPMUSYNR register controls the multiplication factor of the PLL and selects the VCO frequency<br />

range.<br />

0x0034<br />

R<br />

W<br />

Read: Anytime<br />

7 6 5 4 3 2 1 0<br />

VCOFRQ[1:0] SYNDIV[5:0]<br />

Reset 0 1 0 1 1 0 0 0<br />

Figure 4-4. S12CPMU_UHV Synthesizer Register (CPMUSYNR)<br />

Write: If PROT=0 (CPMUPROT register) and PLLSEL=1 (CPMUCLKS register), then write anytime.<br />

Else write has no effect.<br />

NOTE<br />

Writing to this register clears the LOCK and UPOSC status bits.<br />

If PLL has locked (LOCK=1)<br />

f VCO<br />

= 2× f<br />

REF<br />

× ( SYNDIV + 1)<br />

NOTE<br />

f VCO must be within the specified VCO frequency lock range. Bus<br />

frequency f bus must not exceed the specified maximum.<br />

The VCOFRQ[1:0] bits are used to configure the VCO gain for optimal stability and lock time. For correct<br />

PLL operation the VCOFRQ[1:0] bits have to be selected according to the actual target VCOCLK<br />

frequency as shown in Table 4-1. Setting the VCOFRQ[1:0] bits incorrectly can result in a non functional<br />

PLL (no locking and/or insufficient stability).<br />

Table 4-1. VCO Clock Frequency Selection<br />

VCOCLK Frequency Ranges VCOFRQ[1:0]<br />

32MHz

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!