Bootloader Issues with Tiny Multibootloader

[JohnB]

I don't know if others have had similar problems but I have had a couple of bootloaders from Evan which only work once with my programs because my program is writing into the first 8 locations corrupting the vector to the bootloader.

This is the message (see attached) when I upload my program to my device.  The uploaded program runs fine but when I reboot it does not re-enter the bootloader.

I have bootloader = on in my declares, how many bytes does the compiler leave free when bootloader is enabled?

I dont want to waste any more money with Evan if the compiler is causing the problem.

[trastikata]

I have bootloader = on in my declares, how many bytes does the compiler leave free when bootloader is enabled?
I dont want to waste any more money with Evan if the compiler is causing the problem.

John,

How many bytes the compiler will leave depends on your declare: "Declare Compiler_Start_Address"

The problem is in the Bootloader that probably accepts FLASH addresses effectively overtiring itself.

My bootloaders will always return a write error if FLASH address will cause it to overwrite itself.

[JohnB]

I should have mentioned, I am using the 16F family of devices which it seems the compiler doesnt support the Declare Compiler_Start_Address,  Does this mean you cannot use TinyMultiBootloader with devices less than the 18F series?  Can any one recommend a bootloader which will work with 16F devices.

Further to this, discussions with Evan it appears that NOP's are inserted at the begining of the code rather than leaving erased as $3FFF