Firewing

How come supported devices between these two don't match up?

Plan WAS to get Mechanique Bootloader and Firewing supported device and have it supported

in Program menu.

That doesn't look like it will work now.

If you buy a Firewing board what happens if bootloader file on device gets corrupted and stops working?

Is the bootloader file in one of the Firewing directories?

Firewing 8 http://www.firewing.info/downloads/loader/firewing-08-loader-r2.zip
Firewing 16 R2 http://www.firewing.info/downloads/loader/firewing-16-loader-r2.zip
Firewing 16 R1 http://www.firewing.info/downloads/loader/firewing-16-loader-r1.zip
Firewing 32 http://www.firewing.info/downloads/loader/firewing-32-loader-r2.zip

Coccoliso

Thanks!

Okay. Bootloader files exist.

Now we have to guess what devices they support.

http://geoffg.net/Downloads/Micromite/G ... romite.pdf

That show's you how to breadboard a Micromite and then program it.

I think Firewing page would benefit from page like that for Firewing.

Get the user's into Firewing that want to build a breadboard for Firewing.

...

Coccoliso

I think what I'm getting from you post is:

You are related to somebody.

We are not in Disneyland.

Looks like you enjoyed Mircomite article.

I have PIC18F14K50.

I think it is off supported list.

Should I get PIC that is used on Firewing board to make things easier?

There is something that escapes me in your reasoning, why are you asking here if the PIC device you have can work with the above interpreter?

Coccoliso

I came to my senses about this.

No need for a bootloader or a USB interface at all.

Long as I can get to the directory in Firewing with the compiled .hex file.

I can breadboard the PIC18F14K50 with a PICKit 3 connection.

Then just download .hex file.

Of course can add other stuff later.