I just build a FAST board and tried to program the PIC.
I got the following errors:
Executing: "C:\Program Files\Microchip\MPASM Suite\MPASMWIN.exe" /q /p16F688 "FAST_Snowfall_Tube_Segment_(Diag)_20110926.asm" /l"FAST_Snowfall_Tube_Segment_(Diag)_20110926.lst" /e"FAST_Snowfall_Tube_Segment_(Diag)_20110926.err"
Message[302] D:\CHRISTMAS\PCB\FAST\FAST_SNOWFALL_TUBE_SEGMENT_(DIAG)_20110926.ASM 42 : Register in operand not in bank 0. Ensure that bank bits are correct.
Message[302] D:\CHRISTMAS\PCB\FAST\FAST_SNOWFALL_TUBE_SEGMENT_(DIAG)_20110926.ASM 351 : Register in operand not in bank 0. Ensure that bank bits are correct.
Message[302] D:\CHRISTMAS\PCB\FAST\FAST_SNOWFALL_TUBE_SEGMENT_(DIAG)_20110926.ASM 352 : Register in operand not in bank 0. Ensure that bank bits are correct.
Message[302] D:\CHRISTMAS\PCB\FAST\FAST_SNOWFALL_TUBE_SEGMENT_(DIAG)_20110926.ASM 356 : Register in operand not in bank 0. Ensure that bank bits are correct.
Message[302] D:\CHRISTMAS\PCB\FAST\FAST_SNOWFALL_TUBE_SEGMENT_(DIAG)_20110926.ASM 360 : Register in operand not in bank 0. Ensure that bank bits are correct.
Got this with the diag code, if I use the tube with tail code random, same errors, just more of them. I have built Renards for a few years and programmed many PICS, so it's not like I haven't done it before.
I just programmed PICS for another Ren48LSD, they were fine.
Using a clone PICKIT2 and MPLab 8.6
I have seen similar errors and the solution (for me) was to put the source files in the root (or 1 level deep) on c:
I couldn't get my renard firmware to go until I did this.
I found on other posts at the time that if you were more than a few directories deep mplab wouldn't always run properly as well as it seems to want to be on the c: (windows drive).
Hope this may help.
Jason
Try to assemble it with mpasm. That's what I've been using for the FAST and get no errors. It's easier to use too.
n8huntsman wrote:Try to assemble it with mpasm. That's what I've been using for the FAST and get no errors. It's easier to use too.
+1 on that. I had terrible luck with mplab, but been good using mpasm.
The messages in the first post in this thread appear to be warnings, not error messages, and are harmless by themselves. There are techniques that I've used in the Renard code to minimize (or eliminate) these warnings, which is why you are not used to seeing them.
MPASM has (or had) a limit to the number of characters in a filename (including the path), which may be the source of some problems. This is what jcross is referring to, but I don't think that the messages in the first post would be caused by hitting this limit. And for assembling to other drives (besides C: ), I do this all the time (to a USB flash stick) without any problem.
