>> When the chip starts up, it executes (on the 12C508) the MOVLW
>> calibration instruction at the top of memory, a bunch of NOPs (which
>> are the old, erased code), and then the current program.
>
>Whats wrong with
>        org 0x0000
>        ; set cal data
>        org 0x0008
>        ; code start version 1
>
>That fails
>        org 0x0000
>        ; set cal data
>        org 0x0007
>        ; code start version 2
>        goto Code2

Well, the scheme I originally mentioned (let the pic execute "unprogrammed"
locations until it hits real code) was sort-of designed to have the minimal
effect on programming software.  As long as you can restrict it's
blankcheck, program and verify steps to the specific range that your
program attempt actually occupies, it shouldn't complain.  Of course, if
the programmer SW has grander ideas about blank-check and verify, it will
still complain (isn't it nice that there's so much open source programmer
software, though :-)

I guess I have enough PICs now to do some experiments :-)

BillW

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics