Bootloader for 16f87/88 that doesn't use UART

[bcd]

Found a couple of options:
WLOADER - http://www.voti.nl/wloader/index_1.html
this allows any pin to be used and can work with a single pin. SRC code is in ASM with a command line Windows option (with Source in Delphi) or a Wiindows based app in Python.

PIC_E - http://www.ehl.cz/pic/pic_e.htm
Uses hardware UART, but has nice Delphi front end for PC and source code for PIC in ASM.

I am now looking at re-writing the PIC_E firmware using PBP to make it work with out the UART for my specific PIC.

These two don't have 16F87/88 definitions, but looking at the source it shouldn't be too hard to add the required info.

I might also look into RomZap - I remember reading about it a few years ago when I first toyed with the idea. Anand, if you have a copy could you email it or PM me.

If I get it going I'll upload it here.

Bill

[bcd]

ROMzap - http://piclist.com/images/com/bubble...mo/ROMzap.html

Looks pretty advanced for what I need - it seems to use UART, although it does support the 16F872 which doesn't have a UART.

I am downloading it now and will dig in to the Source files (if they are in the ZIP) to see how customisable it will be.

So has anyone ever written a bootloader in PBP??

bill.

[victorf57]

Take a look at this code maybe it will help.
http://www.oshonsoft.com/picbootloader.html
victor

[bcd]

Hi Victor,

Fantastic ! That gives me a good starting point. The PC applicatin looks a lot like the PIC_E one.

Looks like I am going to spend Sunday in the shed learning how to bootload !!

With Thanks,
Bill.

[Darrel Taylor]

bcd,

If you're going to start with that bootloader for the 16F877?
There are some significant differences when writing to flash memory on the 16F87/88's.

The 877 allows you to write 1 word at a time. And when you write it, the chip automatically erases the word before writing the new data. This is the main reason why 99% of the free bootloaders use the 16F877. (it's easy)

The 16F87/88's require that you erase memory in blocks of 32-words first, then write the new data in blocks of 4-words. (more difficult)

It's still very doable.
Just thought it might help get you on the right track.
<br>

[ardhuru]

ROMzap - http://piclist.com/images/com/bubble...mo/ROMzap.html

Looks pretty advanced for what I need - it seems to use UART, although it does support the 16F872 which doesn't have a UART.

I am downloading it now and will dig in to the Source files (if they are in the ZIP) to see how customisable it will be.

bill.

Yes, the interface does look a bit complex first, but thats because its so configurable. Once you figure out the things you need, its a breeze to use. No it doesnt use the UART; you could use any pin for the bit banging.

Pity it only supports the 16F8XX chips, though; if you are able to adapt it for others, I would love to hear about it too... it was my preferred bootloader for a long time, till I had to switch over to the one from Mecanique. I still miss the flexibility and the option of not having to use a level shifter.

Regards,

Anand

[dhouston]

So has anyone ever written a bootloader in PBP??

See http://www.picbasic.co.uk/forum/showthread.php?t=4498

[dhouston]

If I get it going I'll upload it here.

That would be great. I have several applications where I'd like to use a 16F88 with a bootloader well enough documented for me to write Windows/Linux/Mac interfaces (using PureBasic) but the bootloader, itself, is beyond my skill level.

[bcd]

After a weekend in the shed I have learned more about the memory layout and programming requirements of the 16f87/88 then I think I ever wanted to know.

Darrel Taylor - Excellent piece of advice re the ERASE / Write cycle. I am investigating the best way to do this, as well as making sure we don't overwrite the bootloader at the high end.

dhouston - Thank you for the link to the thread on the 18F bootloader. There is some great info on reorganising the libary to get round some jumps to 0 that I had been seeing in some hex code I created.

There is so much to learn and so much more playing to do. Stand by everyone - its coming ! We are at 650 words, but I am trying some tricks to squish that down as there are other things I would like to add.

bill.

[dhouston]

There is so much to learn and so much more playing to do. Stand by everyone - its coming ! We are at 650 words, but I am trying some tricks to squish that down as there are other things I would like to add.

Once you post what you have, Darrel Taylor and Bruce Reynolds likely to suggest further improvements.

[Darrel Taylor]

Clarification ....

You make it WORK.
We can All add to the "squish" part.

Useful project, I promise to do my share.
<br>

[skimask]

We can All add to the "squish" part.

Shooting for a 12 byte bootloader are ya?

[mister_e]

i know 35words is doable... but 12

[dhouston]

You make it WORK.
We can All add to the "squish" part.

Useful project, I promise to do my share.
<br>

I'd offer to help squish but fear I'd squash. Once squished, I'll provide PureBasic source for Windows/Linux/Mac interfaces. I can test Windows & Linux but don't have a Mac. PB code is fairly easy to convert to VB.

[skimask]

I'd offer to help squish but fear I'd squash. Once squished, I'll provide PureBasic source for Windows/Linux/Mac interfaces. I can test Windows & Linux but don't have a Mac. PB code is fairly easy to convert to VB.

Generic question about bootloaders...since I haven't had the need to use them.
Do the bulk of the bootloaders out there do HEX files or straight binary data (assuming you're not ever changing the config registers, IDLOCs, etc.)...