Jump to content

etl17

EstablishedMember
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About etl17

  • Rank
    Newbrie
  1. I cannot install 7.30 on Windows 10. I am getting a Runtime Error (at 74:9000) Internal error: Failed to expand shell folder constant "userdocs" Any ideas?
  2. Hi, I couldn't find any information regarding what are the new features on the 7.0 release. I am considering upgrading my 6.x Pro license to 7.x, but I couldn't find any benefits doing so. --Stefanos.
  3. Thank you Dave. Do you anticipate that support will be included in the 6.90 final release? --Stefanos.
  4. Any plans to support PIC18F13K50/14K50 in the near future?
  5. Great! I noticed that my Pro key doesn't unlock the goodies.exe anymore. Am I doing something wrong?
  6. Dave, I see. Makes perfect sense. Thank you. -- Stefanos.
  7. Hi Dave, Thank you for your quick response. You were right. After rebuilding with Ctrl-F7 the lib file worked great. Thank you, -- Stefanos.
  8. My compiled libc.pic18.lib (using the supplied project file under libc) is getting rejected by the linker when I try to build a PIC18 based project. Is there any special switch that needs to be supplied to the linker or compiler when building the libc libraries? If so, can you please update the supplied project files (libc.pic16.__c and libc.pic18.__c) under the libc directory? Thank you in advance for looking into this, -- Stefanos (boostc pro license).
  9. Hi there, I recently upgraded my full boostc license to pro. After rebuilding the libc.pic16.lib and libc.pic18.lib (using the two projects files under the libc directory) I realized that my newely generated library files are bigger in size than the ones provided in the lib directory. My new libc.pic16.lib is 188KB vs. the original which is 186KB and my new libc.pic18.lib is 188KB vs. 167KB for the original. I am wondering if the supplied library files are compiled with special flags (such as -Oa or -Op). Please advice. Kind regards, -- Stefanos.
  10. etl17

    Cof File Inconsistency...

    Hi there, I have recently purchaced the full license for the BoostC compiler. After using Proteus VSM (latest build v7.1SP2) to simulate circuits with a PICF877A device, I am experiencing the following problem. When I compile the lcd project (from the /Samples/C/BoostC directory) and loading the .COF generated file on a virtual PIC16F877A device on Proteus, during debugging I am getting two files listed as source: lcd_driver.h and lcd.c, however while debug stepping through the code, Proteus indicates the wrong file. It looks like the file lcd_driver.h and lcd.c are swapped and Proteus is stepping through the wrong file. I am not sure if I described the problem correctly. Please let me know if additional clarification is required. Please note that the operation of the code is correct. Also, debugging through the IDE, as well as MPLab seems to be fine. Is it possible that the .COF file is not correct? The same version of Proteus loads .COF files generated using PICC Lite and WinAVR without any issues. I have used both the 6.60 and the 6.70 release candidate versions and verified the same problem.
  11. etl17

    .cof File Inconsistency...

    Hi there, I have recently purchaced the full license for the BoostC compiler. After using Proteus VSM (latest build v7.1SP2) to simulate circuits with a PICF877A device, I am experiencing the following problem. When I compile the lcd project (from the /Samples/C/BoostC directory) and loading the .COF generated file on a virtual PIC16F877A device on Proteus, during debugging I am getting two files listed as source: lcd_driver.h and lcd.c, however while debug stepping through the code, Proteus indicates the wrong file. It looks like the file lcd_driver.h and lcd.c are swapped and Proteus is stepping through the wrong file. I am not sure if I described the problem correctly. Please let me know if additional clarification is required. Please note that the operation of the code is correct. Also, debugging through the IDE, as well as MPLab seems to be fine. Is it possible that the .COF file is not correct? The same version of Proteus loads .COF files generated using PICC Lite and WinAVR without any issues. I have used both the 6.60 and the 6.70 release candidate versions and verified the same problem.
×