Anyone found a Bootloader for 18F26K22?

[Dave]

Timmers, I have NO problem using the two ports, in fact, that's why I chose the 18F26K22 for the application. I am running 3 ports, one is DEBUG. The application code is working just fine but it is Annoying to have to remove the part from the product each time to reprogram it when making development changes. I have always used the boot loader with MicroCode Studio, in fact thats why I purchased the product. I used to use the boot loader from Mel Labs but they also decided to stop supporting it a few years ago. Thats why I chose MicroCode Studio as my developement platform. Now that they are showing no interest in supporting the newer Pic's with there product (probably due to lower priority between Proton support, Amicus support and MicroCode studio support) I don't know what to do....

[HenrikOlsson]

Dave,
This won't help but I always include a ICSP header on my boards so I can connect the PICKit3 and flash the chip if I don't have access to a bootloader.

I'm currently working on a board with a 46K22, I'll see if I can get that going with the DS30 loader but I'm currently having difficulties with the FT232RL USB<->UART bridge (first time using it in my own desing) and I need to get that going before continuing. I know you're using the 26K22 but perhaps it will help you - IF I get it going that is....


/Henrik.

[timmers]

Dave,
Glad you are (port) sorted.
I allways put an ICSP header in. If PortB.6 or b.7 are inputs you need to put a 1K-ish resistor in series and ICSP connections go directly to the PIC, that way you can overdrive the attached components.
For some older designs that do not have ICSP, I have a jig to insert between the socket and the PIC with the ICSP connections made to the jig.

I am also trying to implement a bootloader and was only aware of the Microchip one. Keep me posted should you have any success.
Tim.

[Dave]

Henrik, I have been working with David Barker the last 2 days with an open source Bootloader that comes with the new MCSPX 5.0 IDE. We got it working this morning and it performs is just like the old one. It allows you to build your own Bootload hex files for any of the new PIC's. I finally got that 18F26K22 running for the new LoadShed processor.

[HenrikOlsson]

Hi Dave,
That's excellent news! A saw the UMC Firmware button in the new MCLoader and went on short search for information about what it was without much success. I found the UMC folder in the MCSPX install folder but there's very little information on how it works and how to configure it - especially for an ASM rookie like myself.

I thought more info would boil to the surface soon enough - and sure enough...
Anything you can, want and are allowed to share?

/Henrik.

[Dave]

Well Henrik, Where do I start? I left a request for a new bootloader file to Microcode Studio a few weeks ago. That's when I posted "Anyone found a Bootloader for 18F26K22?" I havent heard anything for the last week or so. I just purchased PBP3 last week. I was contacted by David Barker in responce to my email about a bootload hex file for the 18F26K22. He had mentioned that he was writing an open source hex file generator for the Microcode studio bootloader program and if I would like to test the beta version. So I have been working with him for the last 2 days getting it working and some verification. You will need to get an updated version of the UMCLoader.exe as he made a few changes to it. It is now 1.0.0.1. I have also made a few changes to the template for the open source .asm build file to be used with MPLAB to generate the .hex bootload file for the processor. I suppose the update will be available soon for the purchased MCSPX package. I would email Microcode studio and see when it will be available.

[HenrikOlsson]

That sounds excelent! During my own short research I did try to run the UMC loader application (UMCLoader.exe) but when I ran it nothing at all happend so I thought it was internal to the standard MCLoader application or something.

Are you saying it's a stand alone application for the open source firmware? If so I wonder why it doesn't run on my machine - perhaps I just need the new version you mention.

Anyway, thanks a lot for the information - I'll keep my eyes and ears open for any information that may surface.

/Henrik.