gnupic: gpasm and gpsim trouble
Subject:
gpasm and gpsim trouble
From:
John Duncan ####@####.####
Date:
26 May 2000 00:37:49 -0000
Message-Id: <392DC73A.F575C741@bom.gov.au>
Hello,
I am hoping that someone on thwe list maybe able to help me. I have
recently installed gpasm-0.8.9 and gpsim 0.19.0. I have all the
prerequisite packages installed and both programmes built and installed
OK. But.... I have a small flashing LED program that I have written.
It assembles fine with mpasm but won't with gpasm. I get the following.
condamine:~/pic$ gpasm bauble2.asm
gpasm: main.c:185: main: Assertion `state.pass == 2' failed.
Aborted
condamine:~/pic$
Would perhaps mean that all the symbols couldn't be resolved in 2
passes?? Just a guess.
Another trivial little test program will assemble with gpasm. The .cod
.hex and .lst files a generated. I can simulate this programme with
gpsim when I specify using the .hex file but if I specify to use the
.cod file I get a segmentation fault. gpsim will initialise, all the
gui windows are displayed and then it falls over. This is what I get :
condamine:~/pic$ gpsim -p p16f84 -s test.cod
gpsim - the GNUPIC simulator
version: 0.19.0
type help for help
useage:
gpsim [-h] [-p <device> [<hex_file>]] [-c <stc_file>]
-h : this help list
-p <device> : processor (e.g. -pp16c84 for the 'c84)
<hex_file> : input file in "intelhex16" format
-c <stc_file> : startup command file
-s <cod_file> : .cod symbol file
-v : gpsim version
gpsim> Initialized
c84 construct
pinspacing 20
Loading test.cod
processing cod file test.cod
cpu is non NULL
setting cfg_word and cfg_modes ffff 1
couldn't open p16f84.inc
cblock 0x0c
reg1
reg2
reg3
endc
org 0
mo (or any upper/lower case variation)
--- Reset
POR
config_modes = 1
Enabling WDT
New program
New program
0
1
Segmentation fault
condamine:~/pic$
The only thing that I can see that could be wrong is that the p16f84.inc
couldn't be found. It is in the current directory. I have tried
putting it in my home dir, /usr/local/share/gpasm (where special.inc
lives) and /usr/local/lib just to see what it did. It still can't be
opened.
I hope someone can help me sort this out. I am using Slackware 7. I
hope someone can help me out. Sorry about the length of the email, but
I like to include as much information as I can.
Cheers
John
