|
From: kitts <kit...@gm...> - 2008-02-18 16:49:51
|
On Monday 18 Feb 2008 8:59:27 pm you wrote: > > I would like to know if i can > > follow this method with openocd as it would save a lot of development > > time. I would request anyone with any knowledge on this to guide me as i > > was unable to find any openocd examples that followed this method. > > openocd implements the required functionality, or at least it's meant to > ;-). So it's up to you to drive GDB to use it. You will only be able to do > it from kdevelop if kdevelop gives you a GDB command line you can use. > Note that the feature is only available in GDB 6.6 and later. Thanks for replying. Yes KDevelop does provide a GDB command line but why do i need that? > The key is to define your memory map in GDB correctly to indicate which > memory regions are flash. Then when you do a 'load' it automatically > reprograms the flash. Do you have any example? How do i specify memory regions? Would this mean that my gdbinit script mostly remains the same for RAM and FLASH operation except for the memory region information (and the hardware/software breakpoints config)? -- Cheers! kitts |