gnupic: Re: [gnupic] picp .hex file problem
Subject:
Re: [gnupic] picp .hex file problem
From:
Anthony Tekatch ####@####.####
Date:
12 Aug 2005 23:13:33 +0100
Message-Id: <20050812181336.1f6423df@pino>
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.
> > 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?
Thanks for confirming my issue.
AT
