gnupic: picp 0.5
Subject:
Re: picp 0.5
From:
Scott Dattalo ####@####.####
Date:
2 Nov 2002 18:44:01 -0000
Message-Id: <Pine.LNX.4.44.0211021009010.9392-400000@ruckus.brouhaha.com>
On Fri, 1 Nov 2002, Craig Franklin wrote:
> Tell me more about the config word differences.
Well, I can't because I don't know how MPASM puts the config info into the
.hex file.
I've attached three files: a source, t.asm, and the resulting assembled
output for gpasm and mpasm. The diff between the two occurs in the first
line only. MPASM has this line, but gpasm doesn't:
:020000040000FA
When I added the 18F stuff to gpasm a long time ago, I made it print an
error whenever the __CONFIG directive was used (or more specifically, if
data was placed into an address beyond 64k). What's strange is that
__CONFIG directives appear to have no effect in MPASM either (although
MPASM doesn't display an error)! Configuration information is entered
either when the project is created or when you're about to program a part
- it's not part of the .asm like it is for the 14-bit cores. Hmm.
As a result, I don't know HOW or even IF the config info is stored in the
.hex file. Which I guess brings up the question, how does picp program the
configuration bits for an 18F device?
Scott
list p=18f452,t=ON,c=132,n=80
radix dec
include "p18f452.inc"
;__CONFIG _CONFIG2H, _WDT_ON_2H
;__CONFIG _CONFIG1H, _HSPLL_OSC_1H
org 0
MOVLW 'T'
dt "This is a test."
db "some bytes"
end
:10000000540E540C680C690C730C200C690C730CA6
:10001000200C610C200C740C650C730C740C2E0CF1
:0A002000736F6D65206279746573DB
:00000001FF
:020000040000FA
:10000000540E540C680C690C730C200C690C730CA6
:10001000200C610C200C740C650C730C740C2E0CF1
:0A002000736F6D65206279746573DB
:00000001FF
