Hi,
I've just uploaded a new version of my "P2B" PIC18Fxxx bootloader to my
website. It fixes a major bug in the hexfile loader which would cause the hex
file to be rejected as corrupt if any hex line had a checksum of 0x00. This
is an incredibly big "oops" and I can't believe I didn't catch it before I
released v1.0b2...
I've also added more error checking code - the loader will no longer
blindly program the chip if the hexfile was corrupted or read incorrectly.
This - again - should have been in v1.0b2, but wasn't (hey, it was a beta
version, betas aren't generally supposed to be stable anyway 8^).
Please let me know if you use P2B or if you find any bugs in it.
Um, oops. It seems I missed the zero off the end of the filename of the
bootloader link - this has now been fixed. If you tried to download it
before, please try again :)
On Wed, 15 Sep 2004 23:41:15 +0100, Philip Pemberton wrote:
> Please let me know if you use P2B or if you find any bugs in it.
I just downloaded it to have a look, and despite being called 1.3 in the README and so on, boot18.asm has 1.0a
as its version (in the comments at the front and in the actual VERSION_* data).
Doesn't worry me, but I thought you'd like to know!
> I just downloaded it to have a look, and despite being called 1.3 in the README and so on, boot18.asm has 1.0a
> as its version (in the comments at the front and in the actual VERSION_* data).
>
> Doesn't worry me, but I thought you'd like to know!
It's supposed to be like that - there's more than one version number:
Release number (v1.3) -- the entire pack as a whole
Uploader version (v1.3) -- the uploader's version number
PIC code version (1.0a) -- the PIC bootloader code's version number
The PIC code hasn't changed since release 1.0a, so I didn't bother updating
the version number tag. The uploader *has* changed, so I incremented its
version number. Simple, no? :)
philpem.me.uk | ViewFinder, 10BaseT Ethernet, 2-slice,
