Collapse all in memory view

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Collapse all in memory view

2,472件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by madid87 on Fri Aug 17 05:21:29 MST 2012
Hi,

how can I collapse register tree in memory view? For example, I select IOCON register and all fields are expanded by default which is a mess to navigate.

I simple cant find it.

Thanks.
0 件の賞賛
返信
14 返答(返信)

2,464件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Brutte on Sat Sep 15 15:00:03 MST 2012
Here is how a multilevel Register View is organized in Code Composer Studio from Texas Instruments:

[IMG]http://knowledgebase.nxp.com/attachment.php?attachmentid=839&stc=1&d=1347744095[/IMG]

A mouse pointer disappeared during PrintScreen, but it hovers over [-] icon in the upper-right. Clicking the icon, or with "Ctrl+Shift+/" the whole tree is being collapsed. LPCXpresso's "core registers" view also has this option.

On the other hand other keyboard shortcuts that work with EmbSysRegView do not work as described with this box..
Seems that keyboard shortcuts w.r.t. trees are not unified.
0 件の賞賛
返信

2,464件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Tue Aug 21 01:44:11 MST 2012

Quote: Brutte

It would be great if for example "/" collapsed whole tree down to the trunk :(


As I said this is a workaround provided by using standard Windows keyboard shortcuts for open/closing "Treeviews" (it is not something explicitly implemented as such within the tools).

The only way to collapse the treeview of registers/bitfields down to a register only view that I can see at present is as follows...

[LIST]
[*]Select the top level peripheral name.
[*]Down arrow to move to the first register
[*]If this register is opened up to display bitfields, press the left arrow to close it.
[*]Down arrow to next register, and repeat until you have progressed through all registers.
[/LIST]
Again, we recognise that this is not ideal and improvements to the peripheral viewer are under investigation for future releases.

Regards,
CodeRedSupport
0 件の賞賛
返信

2,464件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by graynomad on Mon Aug 20 20:06:57 MST 2012
I don't find any of those very useful, not much easier than using the mouse and I have to have NUMLOCK enabled (it seems).

Personally I think that normally seeing two levels is right, the peripheral and the registers. The bitfields should be hidden until you need to examine a particular register or two.

If we take IOCON for example, maybe I want to look at IOCON_PIO0_18 and IOCON_PIO0_19, they are miles apart and to see both at once you have to close about 30 registers.

I think that...

a) Maybe a command like ^1, ^2 to set the tree level to display, and
b) Remember the display across debugging sessions, and
c) Display the entries in Port/reg order, not address order because in general you are looking at related ports and pins and don't care about the physical address.
0 件の賞賛
返信

2,464件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Brutte on Mon Aug 20 12:12:20 MST 2012

Quote: CodeRedSupport
In the meantime, you will find that on Windows,(...)



You are a genius! Why didn't I think about numerical keyboard earlier?


[LIST]
[*] "+" expands tree one level deep
[*] "-" collapses tree one level deep
[*] "*" expands whole tree up to the leafs (default CR misbehaviour)
[*] "backspace" jumps to the trunk (no collapsing/expanding)
[*] "enter" toggles sniffing<->unsniffing (same as double-clilck). Works also for whole branches.
[*]left/right/up/down arrows,
[/LIST]

It would be great if for example "/" collapsed whole tree down to the trunk :(
Unsniffing a whole branch is also not implemented (yet), only toggling is available, so it requires some attention to turn a whole sniffing off. That is especially important for "read register to clear a flag" type resources.

edit: adding new errors
0 件の賞賛
返信

2,464件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by madid87 on Mon Aug 20 10:50:29 MST 2012

Quote: CodeRedSupport
This is an area that we are looking at enhancing in the future.

In the meantime, you will find that on Windows, the standard Windows Explorer keyboard shortcuts will allow you to quickly open up/close down/step through the register/bitfields within a peripheral using the numeric keypad /arrow keys/home+end keys.

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/keys_general.mspx?mfr...

Regards,
CodeRedSupport



I appreciate your answer.
It would be an improvement in usability if you could implement a command to collapse all subfolders inside the main folder (e.q. NVIC). I haven't been able to do it with standard windows shortcuts.
0 件の賞賛
返信

2,464件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Sun Aug 19 03:15:38 MST 2012

Quote: madid87

how can I collapse register tree in memory view? For example, I select IOCON register and all fields are expanded by default which is a mess to navigate.



This is an area that we are looking at enhancing in the future.

In the meantime, you will find that on Windows, the standard Windows Explorer keyboard shortcuts will allow you to quickly open up/close down/step through the register/bitfields within a peripheral using the numeric keypad /arrow keys/home+end keys.

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/keys_general.mspx?mfr...

Regards,
CodeRedSupport
0 件の賞賛
返信

2,464件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by madid87 on Sat Aug 18 02:59:58 MST 2012

Quote: Brutte
Use EmbSysRegView.

It opens as expected and remembers the view, position, expanding and sniffing through debugging sessions. What is more, unlike CR's, its (xml) format is not proprietary - you can add/remove any view or register you like.

http://embsysregview.sourceforge.net/

EmbSys has some ~disadvantages (like no alphabetical/address sorting and hex format only), but it is much better than CRs "sparse register bushes" (IMHO). Works like a charm, when detached to a secondary LCD.

I use it under Eclipse Indigo with STM32 but should work with presso as well (not tested).



Thanks for the tip.
I'll try.
0 件の賞賛
返信

2,464件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Brutte on Fri Aug 17 16:03:15 MST 2012

Quote:
No M0 by the looks of it

How do you know OP loves M0-s :confused:

Just take an xml of some LPC-ish M3, remove most of registers and options, and your M0 should be fine. I didn't go into details of memory maps but peripherals of ARMv6 and ARMv7 from NXP look compatible. The core is almost the same, except that M0 lacks half of OCD and all of the diagnostics (anything unexpected falls into HardFault there - absolutely entertaining).

As mentioned, I use EmbSys with ARMv7, neither with presso nor with tinys.

Edit: M0 is supported and this is even mentioned on the very first thing on their homepage:

Quote: EmbSys homepage
cortex-m0: stm32f050x + stm32f051x


so you should not have problems with xml-s of other tinys.
0 件の賞賛
返信

2,464件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by graynomad on Fri Aug 17 14:54:13 MST 2012
No M0 by the looks of it :(
0 件の賞賛
返信

2,464件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Brutte on Fri Aug 17 10:55:05 MST 2012
Use EmbSysRegView.

It opens as expected and remembers the view, position, expanding and sniffing through debugging sessions. What is more, unlike CR's, its (xml) format is not proprietary - you can add/remove any view or register you like.

http://embsysregview.sourceforge.net/

EmbSys has some ~disadvantages (like no alphabetical/address sorting and hex format only), but it is much better than CRs "sparse register bushes" (IMHO). Works like a charm, when detached to a secondary LCD.

I use it under Eclipse Indigo with STM32 but should work with presso as well (not tested).
0 件の賞賛
返信

2,464件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by madid87 on Fri Aug 17 08:47:46 MST 2012

Quote: kayoda
'They' have a website: http://www.support.code-red-tech.com/CodeRedWiki

and 'they' are reading this forum :eek:



Forgive my ignorance :)
0 件の賞賛
返信

2,464件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by ex-kayoda on Fri Aug 17 07:22:46 MST 2012
'They' have a website: http://www.support.code-red-tech.com/CodeRedWiki

and 'they' are reading this forum :eek:
0 件の賞賛
返信

2,464件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by madid87 on Fri Aug 17 06:58:08 MST 2012

Quote: graynomad
It appears that there's no way to "collapse all" which is a bit annoying if it's true.

I found that adding a filter (any old crap, say "x") then removing it collapses all fields, but next debug session they are all back again.



Thanks for the answer.
This is a bit disappointing. Your trick works but it's not a permanent solution.

I hope they will implement this in a future revision. Is there a known way to contact them regarding this issue?

Ivan
0 件の賞賛
返信

2,464件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by graynomad on Fri Aug 17 06:43:22 MST 2012
It appears that there's no way to "collapse all" which is a bit annoying if it's true.

I found that adding a filter (any old crap, say "x") then removing it collapses all fields, but next debug session they are all back again.
0 件の賞賛
返信