gnupic@linuxhacker.org

I freely admit to being derelict in my picp duties.  I does everything 
*I* need it to do, so additional features and updates have lagged 
somewhat (very selfish, I know).

I'm happy to integrate any improvements anyone has to offer.  If 
someone feels very strongly about it and wants to take on the 
responsibility of maintaining the whole thing, I'd be happy to turn 
over the reins.  The truth is that I don't use PICs much anymore 
(nothing more sophisticated than the 12C508), so I'm probably not the 
best person to be maintaining it at this point, given the size of the 
user base.

I'll even look the other way if that person decides to destroy all my 
beautiful, legible source code formatting and replaces it with that 
horrible K&R format :).

   -Andrew



On Wednesday, September 10, 2003, at 01:51 PM, Alexandre Pereira Nunes 
wrote:

> Hi all, I just subscribed.
>
> I've been working on some modifications to picp, mainly to support 
> pic18fxx2, as pointed out by Antonio TodoBom, which is sponsoring this 
> effort.
>
> I'm close to declaring some of these changes as stable, Antonio is 
> already testing most of the work already implemented.
>
> As soon as it shows some results, I'll be posting patches against the 
> original picp.
>
> To the concerns of forking the project, I don't plan to, since I 
> planned into making these changes as to add more resources to the 
> original picp, and both Antonio and I would be glad of the changes 
> would appear on the original program.
>
> Speaking in terms of programming, I would like to perform several 
> changes to picp, in order to make it more easy to maintain, and to 
> ressemble more closely to the traditional command line behaviour and 
> the source code indentation of most gnu tools, which eventually could 
> be easier to do by rewriting it almost from scratch, indeed, but 
> currently I lack the time to do it (and even if I supposedly did not, 
> I don't think it would necessarily be a fork, since I would prefer to 
> coordinate with picp authors. They did a great job on reverse 
> engineering the protocol, and deserve all credit for that).
>
> But back to the subject, here is what is working so far (on pic18f252):
>
> reading program memory, eeprom, id locations, configuration bits;
> writing to program memory.
>
> Soon I'll finish preliminary support for writing to configuration 
> bits, id locations and eeprom (both from the command line and from the 
> hex files, where applicable). That should take a few days yet. As long 
> as testing seems ok, the patch will be posted
>
> Thank you all,
>
> Alexandre (AKA Alex).
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: gnupic-unsubscribe@linuxhacker.org
> For additional commands, e-mail: gnupic-help@linuxhacker.org