Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About jcleland

  • Rank
  1. Upon further examination of this problem, it appears to be isolated to messages, not warnings or errors.
  2. To recreate this error, you need to create an assembly project with a single source file. You will also need an include file that you can modify to contain an error. The source file listed in the project should include the .inc file. Any errors or warnings from the include file don't appear to be 'double-clickable' to jump to the line where the error occurs. Double clicking a message or error that occurs in the asm file takes you to the appropriate line. It seems like errors that occur in files not associated with the project can't be 'clicked' to from the build window.
  3. I'm ashamed to post this as I wrote the code that caused it This problem was discovered simulating a PIC16F690 processor with an assembly project. 1.) Create a new assembly project with a single source file that contains the appropriate #include for the desired processor as well as a __config. #include <p16F690.inc> __config (_INTRC_OSC_NOCLKOUT & _WDT_OFF & _PWRTE_OFF & _MCLRE_OFF & _CP_OFF & _BOR_OFF & _IESO_OFF & _FCMEN_OFF) org 0x00 goto Start Start dt "data",0 2.) Start debugging and step through the dt ins
  4. I'm using a 16F690 which is supported by MPASM, but I cannot select this harware as a target when I'm using the assembler tool. A BoostC project has support for this PIC. Is there some way to fix this or at least hack it so I can get the correct processor in my MPASMWIN build command?
  • Create New...