On Thu, 2009-12-17 at 15:24 +, Spencer Oliver wrote:
> Øyvind Harboe wrote:
> > This is a small regression where Zach postponed (good!) registering
> > the flash commands until they were actually used.
> >
> > The solution that comes to mind would be to check if the commands are
> > already re
Øyvind Harboe wrote:
> This is a small regression where Zach postponed (good!) registering
> the flash commands until they were actually used.
>
> The solution that comes to mind would be to check if the commands are
> already registered. That should amount to a few simple lines of code.
>
The c
This is a small regression where Zach postponed (good!) registering
the flash commands until they were actually used.
The solution that comes to mind would be to check if the commands are
already registered. That should amount to a few simple lines of code.
I'm more concerned that there might be
I get the following on any device that has multiple flash banks, eg.
flash bank pic32mx.flash pic32mx 0xbd00 0 0 0 pic32mx.cpu
flash bank pic32mx.flash pic32mx 0xbfc0 0 0 0 pic32mx.cpu
The second flash bank causes the error msg:
Error: 256 16 command.c:370 register_command(): command 'pi
