gnupic: Re: [gnupic] Re: [orders] Re: [gnupic] gpasm hex files, compatibility with odyssey


Previous by date: 29 May 2007 19:41:44 +0100 Re: [orders] Re: [gnupic] gpasm hex files, compatibility with odyssey, Robert Pearce
Next by date: 29 May 2007 19:41:44 +0100 Re: [gnupic] Re: [orders] Re: [gnupic] gpasm hex files, compatibility with odyssey, Greg Hill
Previous in thread:
Next in thread: 29 May 2007 19:41:44 +0100 Re: [gnupic] Re: [orders] Re: [gnupic] gpasm hex files, compatibility with odyssey, Greg Hill

Subject: Re: [gnupic] Re: [orders] Re: [gnupic] gpasm hex files, compatibility with odyssey
From: Tim Allen ####@####.####
Date: 29 May 2007 19:41:44 +0100
Message-Id: <96513F52-1755-42BE-9833-B6D6B1FA5F21@integsys.biz>

Now that you mention it reading a blank chip and writing it back is  
not a good test. I will have to dig in to the Odyssey source to see  
what's really going on.

It appears that no one else uses this programmer software- can anyone  
suggest a better one. We only use Linux / Unix in the labs and I  
would prefer one that is configurable and uses the parallel port.


On May 29, 2007, at 2:22 PM, Robert Pearce wrote:

> On Tue, 29 May 2007, Tim Allen ####@####.#### wrote :
>
> First I will echo what David said - trying to re-program the chip  
> with what you've just read out of it does not actually test the  
> ability to write, especially when the data is all blank!
>
> Other than that:
>> HelloWorld.hex (the output from gpasm)...
>>
>> :020000040000FA
> Note    ^^^^^^
>> :100000000F28FF308C0000008C0B032808008E00A6
>> :10001000FF308D0001208D0B0A280E0808000030EB
>> :0E00200065006600FF30860007208609142860
>> :00000001FF
>>
>
> I checked your gpasm output against the file you saved from  
> odyssey. They use the same endianism (there are three possible  
> representations of the PIC's 14-bit word out there), but I note  
> odyssey did not include that first line I've marked above. That's  
> an Intel HEX extension for >16bit addressing, so it's rarely needed  
> on PICs (never on 14-bit ones). It's possible odyssey doesn't like  
> it, so it would be worth deleting it as a quick test.
>
> That said, if an incompatibility of HEX file format produces the  
> error message "Couldn't write to program memory" then the author of  
> that application should be severely reprimanded!
> -- 
> Rob Pearce                       http://www.bdt-home.demon.co.uk
>
> The contents of this | Windows NT crashed.
> message are purely   | I am the Blue Screen of Death.
> my opinion. Don't    | No one hears your screams.
> believe a word.      |
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####

Previous by date: 29 May 2007 19:41:44 +0100 Re: [orders] Re: [gnupic] gpasm hex files, compatibility with odyssey, Robert Pearce
Next by date: 29 May 2007 19:41:44 +0100 Re: [gnupic] Re: [orders] Re: [gnupic] gpasm hex files, compatibility with odyssey, Greg Hill
Previous in thread:
Next in thread: 29 May 2007 19:41:44 +0100 Re: [gnupic] Re: [orders] Re: [gnupic] gpasm hex files, compatibility with odyssey, Greg Hill


Powered by ezmlm-browse 0.20.