gnupic: [GNUPIC:] gpsim
Subject:
Re: [GNUPIC:] gpsim
From:
Scott Dattalo ####@####.####
Date:
29 Oct 2001 22:09:06 -0000
Message-Id: <Pine.LNX.4.33.0110291319200.23448-100000@ruckus.brouhaha.com>
On Mon, 29 Oct 2001, Michael Shiloh wrote:
> what i meant was that the program memory window shows a
> value of 0 at each address. however, my hex files shows
> otherwise. for instance, the first line in my .hex file is:
>
> :10000000830100308A002328A00003088301D40064
>
> which, if my interpretation is correct, says that starting at
> address 0000 i should have the data
>
> 830100308A002328A00003088301D400
>
> however, the program memory window shows 0 at every
> location.
I recall from a thread on the PICLIST that the hitech compiler puts the
code at the end of the code space. This doesn't answer your question, but
perhaps what's happening is there is a linker/locater issue here. You may
wish to try gpdasm, the gnupic disassembler, and see what it produces.
>
>
> > I'd be surprised if gpsim could load the hitech generated .cod files.
> > Someone once sent a patch that would hack the DOS paths into unix paths.
> > The "C:" (or D:, etc) is just stripped, and the '\' are converted to '/'.
>
> guess i'll have to skip the source window for now. by the
> way, i am using hitech in linux, so i don't have any
> issues with dos paths.
Hmm. I don't know what hitech does with the paths in Linux. What does gpvc
say?
Scott
