Bootloader in production

ljbeng · Joined: 10 Feb 2004 Posts: 205

How do you guys handle programming the chip with both the bootloader and the application in a production environment?

Can you only program the chip with the bootloader and then have to program the application through the serial port?

or

Can you put both the bootloader and application into the chip during first production?

I was experimenting with the CCS bootloader example and it works with my application program. We have a board house build the boards and program the chips so the board are ready to run when we get them. The bootloader will be needed in the field for future updates.

Thanks.

mskala · Joined: 06 Mar 2007 Posts: 100 Location: Massachusetts, USA

My production is fairly small so maybe this won't work for you, but all the good programmers should have a setting for erase or not erase before burning an image. They have a separate erase-only selection as well.

If the chip is not brand new, erase it. Then, with programmer set to not erase, burn bootloader. Then, similarly, burn application.

I have tried to find an easy way to combine the two hex files but haven't found it. The bootloaders I've used require each line to increase in address location, and the files also modify eeprom.

Ken Johnson · Joined: 23 Mar 2006 Posts: 197 Location: Lewisburg, WV

My bootloader is built into my app, so they both burn together. Later, if the software is updated using the bootloader, I just don't re-write the bootloader. Don't remember the details just now, and I'm leaving town for a few hours. If you don't have something worked out when I return, I'll try to look it up

You can do it !

Ken