Jump to content

Jenn

EstablishedMember
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jenn

  • Rank
    Newbrie

Recent Profile Visitors

640 profile views
  1. I gave up on my attempt at upper case register names. It's something to consider however, as applications such as Microchip's "Application Maestro" generate C source code with all caps for their registers.
  2. Hi Russ: The include file is PIC16F690.h and it is where the registers are defined. I wanted to use UPPER CASE registers for variable names instead of lower case variables, maybe I'm asking too much. Jenn It looks like registers used internally by the compiler get defined with upper case names 'behind the scenes' so the linker ends up seeing multiple defininitions if you try to declare them too. You should be able to use code of the form: volatile unsigned char status@ 0x03; #define STATUS status for the variables that throw this error. Orin. Thank you O
  3. Hi Russ: The include file is PIC16F690.h and it is where the registers are defined. I wanted to use UPPER CASE registers for variable names instead of lower case variables, maybe I'm asking too much. Jenn
  4. I want to use all CAPS for my registers variables instead of lower case. I tried to upload my source files but this board will not let me. Here is the error message: -------------------------------------------------------------------------------------------------------------- Executing: "C:\Program Files\SourceBoost\boostc.pic16.exe" jenntest1.c -O1 -W1 -t 16F690 BoostC Optimizing C Compiler Version 6.81 (for PIC16 architecture) http://www.sourceboost.com Copyright© 2004-2007 Pavel Baranov Copyright© 2004-2007 David Hobday Licensed to Jenn Jacobsen under Single user Pro License
  5. I'm sure this is a bug as I took out the def's in my program and it linked fine. Then I tried: y=STATUS; and got an error "error: unknown identifier 'STATUS'" Somehow somewhere those 4 registers are being defined or at least the compiler/linker thinks they are. We should be able to build out own .h files with all caps for the vars.
  6. Here is the .c file: ///////////////////////////////////////////////////////////////////////////////////// // For a PIC 16F690 //outputs to the LEDS on the PicKit2 low count board #include <system.h> #pragma CLOCK_FREQ 8000000 // 8 mhz #pragma OPTIMIZE "a" //#pragma DATA _CONFIG, _XT_OSC & _WDT_OFF & _CP_OFF & _PWRTE_OFF void init_pic(void); void main(void){ unsigned char x; init_pic(); for(x=0;x<4;x++) { // portc=x; PORTC=x; delay_ms(50); // REMOVED FOR DEBUG ONLY wait for a while }; }; void init_pic(void) { // o
  7. Hi Dave I'm wondering why I can't replace the 16F690.h include file and define my register variables in all caps. It compiles with no errors but the linker throws, duplicate global definitions for STATUS, INDF, FSR, PCL I've only def'd them once.
  8. I did my email with my license and I did enter the key into SourceBoost Pro and it did install fine. Goodies.exe did not work and I don't know where the lib source code is.
  9. Hi Pavel: I purchased the Pro license and tried to use the key to unlock goodies.exe without success. I'm also wondering where the lib source code is. Also, wondering about the lower case register access. I know it's your standard but I wanted to make mine in all upper case. I created the replacement 16F690.h file and it compiled without an error but when it linked, it threw a duplicate global def error. These globals were defined somewhere elsewhere: STATUS,INDF,FSR,PCL Please tell me how to make all the register variables in upper case. thx
  10. I don't seem to be able to post new topics so: Subject: a couple of questions 1) I just bought the BoostC Pro compiler for Pic. I would like to get the plug-ins and goodies and I have tried both of them with my BoostC pro license key without any luck. Are they separate licenses? 2) The upper/lower case thing with registers is unique among Pic compilers. Microchip, HT, CCS, CC5X all use upper case for their defs of registers. Using upper case register defs makes the BoostC code more portable among Pic C compilers. I understand your lower case for variables and upper case for constant
×
×
  • Create New...