Search found 106 matches
- Thu Sep 24, 2009 3:07 pm
- Forum: Compiler
- Topic: movlw 4294967295 compiler bug
- Replies: 59
- Views: 33381
The saga continues.... My bug is back. Except this time it's not a MOVLW 4294967295. The compiler keeps insisting that I'm missing and EndIf, but I'm not. I tried to compile it on a different machine and it worked just fine. Something on my system is interfering the SF compiler, even after a clean i...
- Tue Sep 15, 2009 11:42 am
- Forum: Compiler
- Topic: movlw 4294967295 compiler bug
- Replies: 59
- Views: 33381
I did notice that there was one instance of SwordfishICC.exe (2136 KB) located in C:/ but a different one in C:\Program Files\Mecanique\Swordfish\Bin which is 2013 KB. However, it didn't matter if a switched them or even copied them from another machine. It was almost as if something external to Swo...
- Mon Sep 14, 2009 9:22 am
- Forum: Compiler
- Topic: movlw 4294967295 compiler bug
- Replies: 59
- Views: 33381
- Mon Sep 14, 2009 8:41 am
- Forum: Compiler
- Topic: movlw 4294967295 compiler bug
- Replies: 59
- Views: 33381
All the Library, UserLibrary and Include directories are identical. Both compilers were up to date. It not like my dev machine was buggy or full of viruses. It's a very stable computer. As a matter of fact, I rarely ever had a need to restarted. It's 64 bit CPU, but I have 32 bit Windows XP on it. I...
- Mon Sep 14, 2009 4:39 am
- Forum: Compiler
- Topic: movlw 4294967295 compiler bug
- Replies: 59
- Views: 33381
- Fri Sep 11, 2009 7:53 pm
- Forum: Compiler
- Topic: compiler bug?
- Replies: 1
- Views: 2073
- Fri Sep 11, 2009 3:02 pm
- Forum: Compiler
- Topic: movlw 4294967295 compiler bug
- Replies: 59
- Views: 33381
I played around with it a little more and found that it appears to be related to conditional statements. A MOVLW 4294967295 with always occurs right after a If X <> 0 Then or While X <> 0 sound like the same kind of bug as this one i reporter earlier If you really think you have the same issue, comp...
- Thu Sep 10, 2009 11:13 pm
- Forum: Compiler
- Topic: movlw 4294967295 compiler bug
- Replies: 59
- Views: 33381
Finally, some evidence! :shock: I was cleaning up some code today (mostly cosmetic changes) and suddenly my code started behaving badly again. However this time, I dug a little deeper into the asm and I cannot figure out what is going on. First the background: I'm using the ethernet stack on a 18F4...
- Thu Sep 10, 2009 3:52 am
- Forum: Compiler
- Topic: Indirect addressing conflict?
- Replies: 0
- Views: 2714
Indirect addressing conflict?
I'm starting to better understand the concept of indirect addressing but I wonder if it's possible to have a conflict. The device I use has 3 resisters FSR0, FSR1, FSR2. I've looked through all the library files and noticed that sometimes FSR0 is used, but other times FSR1 is instead. Is there any r...
- Thu Sep 03, 2009 5:02 pm
- Forum: Compiler
- Topic: movlw 4294967295 compiler bug
- Replies: 59
- Views: 33381
- Thu Sep 03, 2009 3:10 pm
- Forum: Compiler
- Topic: movlw 4294967295 compiler bug
- Replies: 59
- Views: 33381
Ok, at least I know I'm not going crazy now. I have noticed the strange behavior when declaring bits . I avoid them at all cost now. I should look through the TCP/IP stack and make sure there are none in it as well. I've been hesitant to change anything in that library since it was ported by David h...
- Wed Sep 02, 2009 11:14 pm
- Forum: Compiler
- Topic: movlw 4294967295 compiler bug
- Replies: 59
- Views: 33381
movlw 4294967295 compiler bug
* I've changed the title of this thread since this has turned out to be an actual compiler problem I've been hesitant to post this because up until now, I've just assumed I was doing something wrong in my code. But let me ask the question anyway. Does anyone else get quirky results when compiling la...
- Sun Aug 30, 2009 3:48 pm
- Forum: User Modules
- Topic: when to use memset function
- Replies: 1
- Views: 3065
- Fri Jul 31, 2009 12:20 pm
- Forum: IDE
- Topic: IDE errors
- Replies: 13
- Views: 8129
- Thu Jul 30, 2009 2:40 pm
- Forum: Compiler
- Topic: EEPROM bug or feature?
- Replies: 1
- Views: 1953
EEPROM bug or feature?
From the example in the help files:
will produce O, n, e, 0, T, w, o, 0 in the EEPROM like it's supposed to.
however,
will give a, b, c, 0 instead of a, 0, b, 0, c, 0
Is that the way it's supposed to be?
Code: Select all
eeprom = ("One", "Two")
however,
Code: Select all
eeprom = ("a", "b", "c")
Is that the way it's supposed to be?