gnupic: Re: [gnupic] picp .hex file problem
Subject:
Re: [gnupic] picp .hex file problem
From:
Byron A Jeff ####@####.####
Date:
13 Aug 2005 00:10:14 +0100
Message-Id: <20050812231004.GA2504@cleon.cc.gatech.edu>
On Fri, Aug 12, 2005 at 06:13:36PM -0400, Anthony Tekatch wrote:
> On Fri, 12 Aug 2005 16:47:07 -0400, Byron A Jeff ####@####.#### wrote:
> > The 16F88 must be programmed to a 4 word boundary. The purpose of the
> > multiword write is to speed up the time necessary to write the program
> > memory.
>
> That's a weird `gotcha` that MPLAB overcomes.
>
> Unfortunately my code is sectioned in many such "org x" tables. I suppose
> I'll have to concatenate them into one huge blob to overcome this issue.
Or be sure to pad each section to a word boundary.
>
>
> > > My current solution is to pad the missing space with NOPs.
> >
> > That's one solution. The other is to set up picp to auto pad to a 4
> > (or pefereably 8) word boundary.
>
> You mean modify the picp source?
Yes.
>
>
> Thanks for confirming my issue.
No problem.
BAJ
