OK..so more info.  His machine he builds on, he can take the hex file and r=
eflash (doing the same process...moving to a new directory, importing the f=
ile and defining the chip in the config tab) so, unless its getting somethi=
ng from another place...the file is complete?  Its a head scratcher

--- On Thu, 10/15/09, Dave Tweed <pic@dtweed.com> wrote:

> From: Dave Tweed <pic@dtweed.com>
> Subject: [PIC] Builds from C18 and importing fails on flash
> To: piclist@mit.edu
> Date: Thursday, October 15, 2009, 12:52 PM
> alan smith wrote:
> > Strange issue came up from another project a friend is
> working on.
> > Building and flashing within the C18 compiler, its
> just fine.=A0 Now if I
> > take the .hex to another PC and try and flash it says
> its doing it,
> > verifies...but the target does not run.=A0 To
> validate the setup, I can
> > flash other targets built in assembly with that other
> PC and ICD3 by
> > importing the hex file.=A0 It appears ONLY when
> built with the C18, it
> > won't flash correctly.=A0 I am using MPLAB 8.3,
> ICD3 and current version of
> > the C18 release.
> =

> It sounds like the hex file hasn't captured the complete
> configuration of
> the chip.
> =

> -- Dave
> -- =

> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
> =



      =


-- =

http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist