Init

[Charles Linquis]

And Sougata,

One other thing:

I have already modified the approach slightly to make this "bootloader write
protect" software selectable. If you have access to the program, and give it an "unlock code", it puts itself in the "OK to run bootloader" mode. On the next power-up, the bootloader will run. If the bootloader isn't used during that power-up cycle OR the program is updated using the bootloader, the program then "locks" the bootloader again. In other words, you give the unlock code, then you have ONE chance to use the bootloader on the next power-up cycle.

[sougata]

Hi Charles,

Thats a nice work around and might be very useful to me. Thanks.

[Darrel Taylor]

I have already modified the approach slightly to make this "bootloader write
protect" software selectable. If you have access to the program, and give it an "unlock code", it puts itself in the "OK to run bootloader" mode. On the next power-up, the bootloader will run. If the bootloader isn't used during that power-up cycle OR the program is updated using the bootloader, the program then "locks" the bootloader again. In other words, you give the unlock code, then you have ONE chance to use the bootloader on the next power-up cycle.

Just curious,

Does that mean the PIN is no longer used?

Was just thinking about how easy it would be, if all you had to do was lift a pin to enable the bootloader.

But if the PIN's gone, and it requires an "unlock code", it sounds pretty cool.

Any chance of sharing the modified bootloader.
or would you need approval from the pentagon?
<br>

[Charles Linquis]

I'll see what I can do...

[Charles Linquis]

Forgot to answer the first question -

Yes, it now doesn't check the state of a pin. It is pure software.
My earlier version that uses the pin was written to satisfy a customer requirement.

I want to play with the whole thing a bit before I consider releasing it to the public.