Cannot read VREF registers

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Cannot read VREF registers

Jump to solution
828 Views
robertpoor
Senior Contributor I

I cannot access the VREF_SC register in KDS 3.20.  When I select EmbSys Register => VREF => VREF => SC, I get the message "WARNING: Failed to read memory @ address 0x40074001"

 

My environment:

  • Mac OS X 10.12.2
  • KDS 3.2.0
  • FRDM-KL27Z development board with KL27Z64VLH4 processor
  • Segger JLINK.edu

In KDS, in the EmbSys Registers tile, it shows

Arch: SVD(CMSIS) Vendor: Freescale Chip: MLK27Z4 Board: --- none ---

... I believe this is correct.  When I select Register VREF => VREF=> SC, in the console it prints:

WARNING: Failed to read memory @ address 0x40074001

... and the result is blank.

Note that it IS capable of printing other registers, e.g. ADC control registers, etc.

 

Any idea why this is failing, or how I can read the state of VREF_SC[VREFEN]?

Labels (1)
0 Kudos
1 Solution
619 Views
HeMyFAE
NXP Employee
NXP Employee

You need to enable  the clock gate for Vref Module.

SiM_SGCG4  (VREF) bit.

View solution in original post

3 Replies
620 Views
HeMyFAE
NXP Employee
NXP Employee

You need to enable  the clock gate for Vref Module.

SiM_SGCG4  (VREF) bit.

619 Views
jorge_a_vazquez
NXP Employee
NXP Employee

Hi Robert Poor

Could you share an screenshot of your EmbSys Registers? I noticed that you have:

Arch: SVD(CMSIS) Vendor: Freescale Chip: MK207Z4

But you should have selected in Freescale Chip: MKL27Z4

So, I not sure if you have selected the correct chip, could you check it please.


Best Regards
Jorge Alcala

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos
619 Views
robertpoor
Senior Contributor I

Jorge:

That was a typo on my part: I get this error when the chip is set to MKL27Z4.  Screenshot attached.

Screen Shot 2017-02-05 at 9.52.38 PM.png

0 Kudos