Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: [lpc2000] file upload: Modified ISP tool

2004-03-16 by capiman@t-online.de

Hello Charles, hello Soeren,

first again many thanks for your changes ! I sent you an email, that i merge
your changes in. And doing this as hobbyist restricts my working time mainly
to weekends...

Since yesterday evening, there is a new version (1.07) on the website
http://www.clibb.de
Main changes were for Linux (thanks to Charles), a bugfix for certain file
length which don't work (thanks to Soeren),
some more error message output and control Reset / Bootline, like the
original LPC2000 tool from philips.

I released again the windows / cygwin / linux version. Hopefully linux
version is running (please give me some feedback), i have no linux to test
with. I also uploaded the latest sources.

Any feedback is welcome !

Regards,

        Martin

----- Original Message ----- 
From: "embeddedjanitor" <manningc2@...>
To: <lpc2000@yahoogroups.com>
Sent: Tuesday, March 16, 2004 8:43 AM
Subject: [lpc2000] file upload: Modified ISP tool


> Hi All
>
> I modified Martin's lpc21isp ISP tool a few days back and emailed him,
> but didn't get a response so I've posted the modified version on the
> group. Martin: I hope that's OK with you...
>
> Anyway, the reason I modified the ISP loader was mainly because it
> would not synchronise effectively with my LPC2106 board. What I found
> was that the ISP tool, like the Philips Windows-based tool, would only
> send out one '?' to attempt the synchronisation but sometimes needed
> more. I found that sometimes up to 75 '?' were required to start up
> properly.
>
> The code is also set up to work under Windows (though I've only used
> it under Linux) so it might be of help to people who are having
> problems with the Philips Windows tool.
>
> -- CHarles
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.