Bootloader won't write start address [solved]

[Rick Booth]

Mikael, thanks for the feedback and the excellent support throughout. I now understand how the bootloader vectors to the user code - the bit I didn't realise was that the bootloader start code is called every time the PIC restarts and then vectors onto the user code after the Receive function times out. I believe on the previous version the zero addressed goto was changed to start the user code directly with the bootloader just sitting at the top out of the way. You were right by the way, the config settings were the problem.

Anyway, the whole process works now with a user code erase of the FDFC goto to re-invoke the bootloader. I assume this is the recommended method.

Thanks again!