You need to add a tag to subject otherwise many people here would not be
able to see your message. You have posted it twice, I believe that is
because neither you saw your own post, so you might thought your message got
rejected?
Anyway, added [PIC] tag...
Tamas
---------- Forwarded message ----------
From: David Novak <David...@dajac.com>
Date: Sat, Jun 19, 2010 at 12:16 AM
Subject: p1.exe has stopped working
To: pic...@mit.edu
I have the following setup:
HI Tech PICC 8.02PL1
MPLAB v8.53
Windows 7
When I build, I get the message "p1.exe has stopped working". Does
anyone know how to solve this issue?
I can build on the command line without any problems and I could live
with building on the command line, but I've not been able to get MPLAB
to step through the source code using the ICD2. If I import the hex
file, it steps through the disassembled Program Memory just fine, but I
want to step through the C source code. If I build on the command line,
can I still debug at the C source code level?
The build output for the p1.exe crash is provided below.
Thanks,
David
----
Clean: Deleting intermediary and output files.
Clean: Deleted file "C:\source\startup.obj".
Clean: Deleted file "C:\source\startup.ase".
Clean: Deleted file "C:\source\dp4.obj".
Clean: Deleted file "C:\source\dp4.cce".
Clean: Deleted file "C:\source\DP4.mcs".
Clean: Done.
Executing: "C:\HT-PIC\BIN\PICC.EXE" -C -E"startup.ase" "startup.as"
-O"startup.obj" -Q -MPLAB -16F877 -ICD -V -O -X
aspic.exe -v -x -E1 -EC:\Users\David\AppData\Local\Temp\_498.AAA -o
-R2000 -CC:\HT-PIC\LIB\picinfo.ini -16F877 -ver=V8.02PL1 -icd
-ostartup.obj startup.as
del C:\Users\David\AppData\Local\Temp\_498.AAA
del C:\Users\David\AppData\Local\Temp\_498.AAB
del C:\Users\David\AppData\Local\Temp\_498.AAC
del C:\Users\David\AppData\Local\Temp\_498.AAD
del l.obj
del C:\Users\David\AppData\Local\Temp\_498.AAE
Executing: "C:\HT-PIC\BIN\PICC.EXE" -C -E"dp4.cce" "dp4.c" -O"dp4.obj"
-Q -MPLAB -16F877 -ICD -V -Zg1 -O -X
clist.exe dp4.c dp4.lst
cpp.exe -DHI_TECH_C -D_MPC_ -SP1,1,1,1,1,1,1 -IC:\HT-PIC\INCLUDE
-S1,2,2,4,3,3 -E1 -EC:\Users\David\AppData\Local\Temp\_1P0.AAA -D_16F877
-D_PIC14 -D_COMMON_=1 -DMPLAB_ICD -D_PROGMEM_=2 -D_HTC_VER_MAJOR_=8
-D_HTC_VER_MINOR_=2 -D_HTC_VER_PATCH_=1 -D_BANKBITS_=2 -D_GPRBITS_=2
C:\dp4_tc\source\dp4.c C:\Users\David\AppData\Local\Temp\_1P0.AAB
p1.exe -E1 -EC:\Users\David\AppData\Local\Temp\_1P0.AAA -D -M -B
-QTi,fastcall -QX,bank1 -QY,bank2 -QZ,bank3 -Gstrings,const -Y -r -u
C:\Users\David\AppData\Local\Temp\_1P0.AAB
C:\Users\David\AppData\Local\Temp\_1P0.AAC
C:\Users\David\AppData\Local\Temp\_1P0.AAD
del C:\Users\David\AppData\Local\Temp\_1P0.AAA
del C:\Users\David\AppData\Local\Temp\_1P0.AAB
del C:\Users\David\AppData\Local\Temp\_1P0.AAC
del C:\Users\David\AppData\Local\Temp\_1P0.AAD
del l.obj
del C:\Users\David\AppData\Local\Temp\_1P0.AAE
The instruction at 0040918b referenced memory at 2e315f77
The memory could not be read fromHalting build on first failure as
requested.
BUILD FAILED: Fri Jun 18 10:44:29 2010
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
--
int main() { char *a,*s,*q; printf(s="int main() { char *a,*s,*q;
printf(s=%s%s%s, q=%s%s%s%s,s,q,q,a=%s%s%s%s,q,q,q,a,a,q); }",
q="\"",s,q,q,a="\\",q,q,q,a,a,q); }
--
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
Was this working with a previous version of MPLAB IDE? Why are you
using such an old version of the compiler? I don't know how
compatible the recent MPLAB IDE language plugins would be with this
version.
> I can build on the command line without any problems and I could live
> with building on the command line, but I've not been able to get MPLAB
> to step through the source code using the ICD2. If I import the hex
> file, it steps through the disassembled Program Memory just fine, but I
> want to step through the C source code. If I build on the command line,
> can I still debug at the C source code level?
You need to import the .COF file for debugging (or given the age of
the compiler, it might be a .COD file).
--
John W. Temples, III
This is an old project that needs a small number of changes. The build
works on a different computer with this compiler and MPLAB v8.5 and
Windows XP. I started with v8.5, but it had the same failure, so I
upgraded to 8.53 to see of that would fix the problem, but it didn't
help.
>
> You need to import the .COF file for debugging (or given the age of
> the compiler, it might be a .COD file).
I did import the cof, but it acts the same as importing the hex.
Should the C file automatically open and show the execution point when
I halt execution and single step?
Thanks,
David
>> You need to import the .COF file for debugging (or given the age of
>> the compiler, it might be a .COD file).
>
> I did import the cof, but it acts the same as importing the hex.
> Should the C file automatically open and show the execution point when
> I halt execution and single step?
Yes.
--
John W. Temples, III