> > > > I thought I'd try "mem info" in GDB. Nothing. Why?
> >
> > The first thing I tried, by the way, was
> >
> > gdb_memory_map enable
> >
> > but that failed with extreme rudeness. :(
>
> How so? :)
Immediate exit during startup.
___
Ope
On Sun, 2009-12-06 at 20:34 -0800, David Brownell wrote:
> On Sunday 06 December 2009, Zach Welch wrote:
> > On Sun, 2009-12-06 at 18:05 -0800, David Brownell wrote:
> > > I thought I'd try "mem info" in GDB. Nothing. Why?
>
> The first thing I tried, by the way, was
>
> gdb_memory_map en
On Sun, 2009-12-06 at 19:55 -0800, Zach Welch wrote:
> On Sun, 2009-12-06 at 18:05 -0800, David Brownell wrote:
> > I thought I'd try "mem info" in GDB. Nothing. Why?
> >
> > Well, "flash banks" doesn't show anything any more. Why?
> >
> > Nothing calls flash_bank_add() ... handle_flash_bank_c
On Sunday 06 December 2009, Zach Welch wrote:
> On Sun, 2009-12-06 at 18:05 -0800, David Brownell wrote:
> > I thought I'd try "mem info" in GDB. Nothing. Why?
The first thing I tried, by the way, was
gdb_memory_map enable
but that failed with extreme rudeness. :(
> > Well, "flash b
On Sun, 2009-12-06 at 18:05 -0800, David Brownell wrote:
> I thought I'd try "mem info" in GDB. Nothing. Why?
>
> Well, "flash banks" doesn't show anything any more. Why?
>
> Nothing calls flash_bank_add() ... handle_flash_bank_command()
> just leaks the structure it filled out.
Whoops th
I thought I'd try "mem info" in GDB. Nothing. Why?
Well, "flash banks" doesn't show anything any more. Why?
Nothing calls flash_bank_add() ... handle_flash_bank_command()
just leaks the structure it filled out.
So I add that missing call, and now I see the various flash
commands again, and "f
