Jump to content

Search the Community

Showing results for tags 'interrupt'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • PIC Embedded Programming
    • BoostC and Chameleon compilers programming
    • BoostC porting source code
    • BoostC++ compiler programming
    • BoostBasic compiler programming
    • Assembler programming PIC
    • Novo RTOS Programming
    • Hardware PIC
    • Enhancement Requests
    • Bug Reports

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. Hi, I am using boostC with MplabX for PIC18F67K22. I have tried to : 1. Use fixed address like " int x@0x100" . This has worked for me previously in Mplab. Do I need to include any libraries to make this work in MplabX? 2. When I add an interrupt service routine as instructed in the boosC manual " void interrupt ( ) " the compiler shows error on all code lines in the isr. it does not see it as an interrupt. Is there a particular way to declare this in the MplabX environment? 3. Even when I include the "string.h" directive, the string length function "strlen(string)" is not recognised by the compiler. Hence the corresponding line is highlighted as an error. Thanks Bade I also tried including all these files below, but it still didn't work. #include <stdio.h> #include <stdlib.h> #include <system.h> #include <boostc.h> #include <BoostCPic18.h> #include "PIC18f67k22.h" #include <float.h> #include <eeprom.h> #include <string.h>
  2. BoostC Special function: void interrupt(void) Makes MPLAB X IDE v1.20 come up with the following warning: unexpected token: ( I've currently using BoostC v7.10 and 64 bit windows 7.
  3. Hi everyone. I hope this finds you well. This is my first project with BoostC so please be gentle with me … my comfort zone has always been assembly language, when it comes to PIC … all right, let me explain what I'm trying to do … first of all, the PIC I'm using for this project is the PIC16F877A. to drive 2 stepper motors I am using the compare module in conjunction with the TMR0; due to the 19.66 MHz crystal oscillator I have to use, TMR0 must overflow 4x times to get a 40ms period. meanwhile, the compare module will clear RC1 and RC2 when TMR1 reaches the value store in CCPRxH:CCPRxL. I have implemented something similar in assembly language and it worked so it should work, right? anyway, the problem I have is that, for some reason, the interrupt never happens! I've checked flags and enable bits and it looks all good but I must have missed something. I'll be really grateful if you can spot that. I have enclosed here the source code. for testing purpose I've plugged in an LED on PORTA.0 and turn it ON within the Interrupt Service Routine (ISR) but it remains OFF thus the interrupt for TMR0 overflow never happens. thank you for your time! test.c
  4. Hi everyone. I hope this finds you well. This is my first project with BoostC so please be gentle with me … my comfort zone has always been assembly language, when it comes to PIC … all right, let me explain what I'm trying to do … first of all, the PIC I'm using for this project is the PIC16F877A. to drive 2 stepper motors I am using the compare module in conjunction with the TMR0; due to the 19.66 MHz crystal oscillator I have to use, TMR0 must overflow 4x times to get a 40ms period. meanwhile, the compare module will clear RC1 and RC2 when TMR1 reaches the value store in CCPRxH:CCPRxL. I have implemented something similar in assembly language and it worked so it should work, right? anyway, the problem I have is that, for some reason, the interrupt never happens! I've checked flags and enable bits and it looks all good but I must have missed something. I'll be really grateful if you can spot that. I have enclosed here the source code. for testing purpose I've plugged in an LED on PORTA.0 and turn it ON within the Interrupt Service Routine (ISR) but it remains OFF thus the interrupt for TMR0 overflow never happens. thank you for your time! test.c
×