Embsys Register viewer not showing any values in kinetis design studio

[sameerarvikar]

I am using Kinetis Design Studio 3.0

Mk70fn1m0vmj12 kinetis k70 controller  (twr k70 120 MHz board)

i did not found above chip in embsys register view so i used MK70F15

i shows list of all peripherals and there reset value ,address and description , but shows nothing of there current value in there registers(the bin and hex columns are empty)

I tried debugging using lots of break points still no value

What am i doing wrong ?

[BlackNight]

You have to double-click on the entry, see "using the plugin" in How to Add Register Details View in Eclipse | MCU on Eclipse 

I hope this helps,

Erich

PS: I would recommend that you use KDS 3.2 (not 3.0, as 3.0 is outdated), or better consider MCUXpresso IDE, see MCUXpresso IDE: Unified Eclipse IDE for NXPs ARM Cortex-M Microcontrollers | MCU on Eclipse 

[720adams]

Eric I'm having this exact same issue using a FRDM-64F board with KDS 3.2.0.  I need to be able to get into the internal registers to debug this SPI0 problem I'm having.  Help please

[BlackNight]

I works fine for me with above description and files in KDS 3.2.0.

Just in case: make sure your SPI0 peripheral is clocked so you can access it.

I hope this helps,

Erich

[720adams]

I've been thinking about one other thing on this issue today.  Why is it

that when I try to use my memory window to read locations within the

chip all I get are ???? showing up.  This seems like some register is

set that is blocking the ability read internal registers.  Thoughts?

[BlackNight]

Hi Mike,

if you get ???? in the memory view it means that the debugger is not able to read from that location.

This is expected if that peripheral register is not clocked (clock not enabled for it).

Erich

[720adams]

Erich:

I am running some code that is blinking my Red LED on the FRDM-K64F

board.  As you can see from the "portMem.png" image attached while the

code is running and blinking the LED I try to read memory.  All I get

are ?????.  The other two images attached are of the same region

attempting to be read through the Emb Sys Registers window, and of the

Emb Sys Registers window trying to read the port configuration memory area.

I am still thinking there is a setting in my code that may be the

culprit so I will try running your example next to see if I get the same

results.

Mike

[BlackNight]

Hi Mike,

not sure, but maybe the fact that you are not using Windows does have somehow an impact?

Erich

[720adams]

Neither of your messages had any code attached.  Thoughts?

Mike

[720adams]

I'm sorry but I must be missing something fundamental.  Those values

shown in your .png file show up green just like mine do, but there are

no register values in the BIN and HEX columns.  Shouldn't this be where

the values of these registers are filled in indicating the data that is

in theses registers and the bits thereof?

I must not be understanding something.  I'm sorry for being dense if it

is simple and I'm just not seeing it.

Mike

[BlackNight]

Hi Mike,

ah, now I'm getting your point. I thought your point was that you are not able to see the register value at all.

Yes, it would be good if that plugin would show the bit details. It does it for other peripherals as for the GPIO:

I have not checked the implementation fot hat plugin which is maintained by the community (SourceForge https://sourceforge.net/projects/embsysregview/files/embsysregview/0.2.6/  is down for maintenance right now, but there is Eclipse Embedded Systems Register View / Code / [r195] /trunk ).

I had contributed in the past a few fixes because that plugin did not correctly parse the ARM SVD files, so I think this is the case here as well. What I have been using so far is the 32bit hex values for my debugging. I agree that this is not ideal, but has worked for me. The other consideration would be to use the MCUXpresso IDE as it has replaced KDS, and the MCUXpresso comes with a NXP maintained peripheral registers view (The Peripherals+ view, see Overview of MCUXpresso IDE v10.2.0 | MCU on Eclipse  and Peripherals Viewer | MCU on Eclipse ).

I hope this helps,

Erich

[720adams]

Thanks Eric:

I've always appreciated how well you support this community when I post

something for my full time job.  It's nice to see when I'm posting for

myself you are the same helpful guy.

I tried the PTA registers in my FRDM-K64F through the OpenSDA USB port. 

Unfortunately, I do not get the same result as you.  I still see the

name turn green in the KDS tool, but nothing is filled in for the hex or

binary columns regarding the register's data.  Additionally the data

that appears to be going to the OpenSDA port--(when viewing the

transactions in the Console window) appear to be returning a negative

1.  I'm assuming the reset column is what the register will be set to

out of reset and not the current value, right?

I have tried upgrading the KDS embsysregview tool from the eclipse

marketplace and the sourceforge trees.  Unfortunately, KDS would not

update even when trying to do this as the root user.  I'd be happy to

try other locations if it will fix this issue.

As for switching to MCUXpresso, I'd be happy to install this tool if NXP

would create an RPM version of the tool.  Without this, I cannot install

it on my Centos 7.4 version I am using without a lot of extra work I

cannot spare right now.  Additionally, windows is not really an option

for our development environment.

Any other thoughts or ideas for how to move forward are greatly appreciated.

Mike

[BlackNight]

Just in case, if this helps.

I have used for the above screenshot the example project I have in

mcuoneclipse/Examples/KDS/FRDM-K64F120M/FRDM-K64F_Demo at master · ErichStyger/mcuoneclipse · GitHub 

Erich

[720adams]

I imported the repo from GitHub and then imported the FRDM-K64F_Demo

project into KDS 3.2.0.  When I tried to build it I got the results that

can be seen in the attached image.  Thoughts?

[BlackNight]

It looks you did not generate code or you don't have all the needed components. Anyway, I have attached for you the project you hopefully can compile as-is.

I hope this helps,

Erich

[BlackNight]

Hi Mike,

the first column is the actual value, followed by the same value in binary, followed by the reset value.

I suggest that you load an example project which say blinks an LED, then inspect the registers for that LED.

If the LED blinks, the port is clocked and you should be able to read and see it.

Otherwise, can you post a screenshot of what you see?

Erich

[sameerarvikar]

I am using kinetis design studio 3.2 only

I put the patch as per given in the link ,but still same issue