gnupic: Re: [gnupic] picp .hex file problem
Subject:
Re: [gnupic] picp .hex file problem
From:
Jeff ####@####.####
Date:
12 Aug 2005 23:46:47 +0100
Message-Id: <200508122246.j7CMkf4J013908@ylpvm53.prodigy.net>
On Friday 12 August 2005 03:13 pm, 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.
>
> > > 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?
>
>
I'll be looking into the issue later today. I'll email you directly when I
have a solution.
Jeff
Picp maintainer
