The difference with CW

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

The difference with CW

Jump to solution
1,182 Views
haidong_zheng
NXP Employee
NXP Employee

My KDS in running on ArchLinux 64bit.

 

1: In CW, when I view the memory, there is a view render as HEX Integer format, while in KDS, I only can see HEX format, HEX format is byte array, while HEX Integer is integer array, please see below picture:

I thinks HEX integer is very useful in view the memory, could KDS team as this way in new KDS release ?

2: In CW, when I need a breakpoint I will enter this breakpoint in Debug Console likely this command  : bp khci.c 1024, while in KDS I can't find this Debug Console, this is also a very useful feature.

 

 

   KDS memory view:

11715_11715.pngKDS1.png

CW memory view:

11716_11716.pngKDS2.png

 

CW Debug Console:

11717_11717.pngKDS3.png

Labels (1)
0 Kudos
1 Solution
983 Views
BlackNight
NXP Employee
NXP Employee

There are two different views for memory in Eclipse:

  1. Memory View
  2. Memory Browser View

Each has its pros and cons. For 'embedded' memory views the 'traditional' rendering can be used:

pastedImage_2.png

Then you can specify the cell size, or the radix (signed, unsigned, hexadecimal, ...)

pastedImage_3.png

As KDS is using GDB, you can use the normal GDB command line debugging. For this, open the corresponding arm-none-eabi-gdb console:

pastedImage_4.png

help breakpoints

gives you a quick help. Have a look as well at Debugging with GDB

For example 'break main' will set a breakpoint at main:

pastedImage_6.png

I hope that helps as a starter?

Erich

View solution in original post

0 Kudos
4 Replies
984 Views
BlackNight
NXP Employee
NXP Employee

There are two different views for memory in Eclipse:

  1. Memory View
  2. Memory Browser View

Each has its pros and cons. For 'embedded' memory views the 'traditional' rendering can be used:

pastedImage_2.png

Then you can specify the cell size, or the radix (signed, unsigned, hexadecimal, ...)

pastedImage_3.png

As KDS is using GDB, you can use the normal GDB command line debugging. For this, open the corresponding arm-none-eabi-gdb console:

pastedImage_4.png

help breakpoints

gives you a quick help. Have a look as well at Debugging with GDB

For example 'break main' will set a breakpoint at main:

pastedImage_6.png

I hope that helps as a starter?

Erich

0 Kudos
983 Views
haidong_zheng
NXP Employee
NXP Employee

Thanks Erich!

That is the correct way just like in CW.

For GDB console, TAB key seem can't do auto completing the comamnd like in real GDB console. Is there a way do this ?

0 Kudos
983 Views
BlackNight
NXP Employee
NXP Employee

No, tab auto completion is not supported in the Eclispe GDB console, see c++ - Is there any enhanced gdb console for Eclipse? - Stack Overflow

0 Kudos
983 Views
haidong_zheng
NXP Employee
NXP Employee

Hi Erich, Got it, Thanks!

0 Kudos