-
I have downloaded a sample USB ASM file which also included a lot of macros, I get a lot of syntax errors with the macros when trying to compile.
I am using gpasm-0.13.7 beta on OSX 10.6.1
I have installed MLAP 8.4 on a windows VM and it builds fine.
I downloaded the sample code from here http://pe.ece.olin.edu/ece/projects.html (lab 2 in assembler...
2009-11-08 12:46:42 UTC by suffo_b
-
Index: gpreadhex.c
===================================================================
--- gpreadhex.c (revision 569)
+++ gpreadhex.c (working copy)
@@ -136,7 +136,7 @@
}
/* inhx32 segment line*/
- page = readword()
2009-10-17 00:06:09 UTC by jimatjtan
-
The segment field in inhx32 is big-endian but gpreadhex reads it as little-endian.
(gpwritehex does the right thing when creating a file.)
Patch attached.
2009-10-17 00:05:43 UTC by jimatjtan
-
By the way, this is with 0.13.7.
2009-10-12 04:42:39 UTC by hawk777
-
By the way, this is with 0.13.7.
2009-10-12 04:42:20 UTC by hawk777
-
Compile the attached files with these commands:
$ gpasm -c -C -w2 x.asm
$ gpasm -c -C -w2 y.asm
and link them with this command:
$ gplink -oapp.hex -m x.o y.o
None of the above commands gives any error or warning (other than gplink observing that it's using the default linker script). However, opening the file "app.lst" reveals that the instruction in x.asm has ended up as "MOVLW 0"! Zero...
2009-10-12 04:39:06 UTC by hawk777
-
If a source file takes the difference of two external labels, the result is zero without any errors or warnings from the compiler or linker. I will attach example source files.
2009-10-12 04:34:25 UTC by hawk777
-
When compiling for 18F4550 in extended mode, the MOVFF instruction allows indexed literal offsets to be applied, as in "MOVFF [0], [1]". According to the datasheet, MOVFF does not support indexed-literal-offset addressing mode for either operand (which makes sense, since it works on flat addresses rather than access-or-banked addresses). The instruction the user probably intends is MOVSS, which...
2009-10-12 04:26:05 UTC by hawk777
-
My fault - the problem was not with gpasm at all, it was my running of pk2cmd. In order to program the configuration bits, I needed -MP -PC in the options, not just -MP. Please would you withdraw this bug. Thanks and regards, Steve.
2009-10-10 15:30:02 UTC by nobody
-
I have a PIC10F202 - using the code attached, when downloaded to the PIC, the device continually resets at a period which is consistent with the watchdog timer. The code tries to disable the watchdog timer.
I note that the 10f202.lkr file has:
CODEPAGE NAME=.config START=0xFFF END=0xFFF PROTECTED
And does not have any associated 'SECTION'.
The configuration, according to...
2009-10-03 13:28:30 UTC by nobody
