Jump to content

gbgb

EstablishedMember
  • Content Count

    60
  • Joined

  • Last visited

Posts posted by gbgb


  1. The answer to the above question is very important for me. I have been using the paid version of  BoostC for the last 14 years or so at work for commercial projects, including some recently new ones. Not that I really need improvements, but do need to know if there will still be someone backing this product, or should I begin thinking about switching to a different compiler.


  2. Is there a way to mark a code section and have it commented out n "one click"

    I know it is possible to /* at the begining and and then */ at the end but what I am looking for is a "one click" way to insert // at the beginning of each line in the section (an then removing it)

    This is a feature found in all IDEs that I know, so I either missed how to do this or it does not exist in the SB IDE editor.

     


  3. I have integrated successfully into MPLAB-X and have been working for several months.

    Due to a problem with a PICKIT3 that I am trying to resolve i installed also MPLAB 8.92 (It worked for me over there but for some  reason does not work with X)

     

    The problem is that SB is not integrating and I cannot set up the toolsuite location for it.

    What I already did:

    I reinstalled SB with specification of the MPLAB directory. Result - SB does not appear in the list of tools

    I saw that the files were not copied so copies them to the Core/MTS directory. Result - still not showing.

    While copying manually I was asked to do it as administrator and thought that this could have prevented something else from working so

    Installed SB again as administrator - still files were not copied. Copying them again manually did not help.

    Any idea how to solve this?

    If I understand correctly the integration procedure also writes into the registry - anybody know what and where?


  4. Having a licensing problem and support has not yet responded to my mail (they used to reply within ~24 hours - not this time, and I am stuck)

     

    Had to replace my PC and I am trying to install version 7.3 Pro

     

    Ran Preg (as administrator as advised above) but still get an error message that I am using the Lite version)

     

    Any advice?

     

    Note:

    On the previous PC I had a 6.X version that was later upgraded to 7.X with an upgrade license.

    Is it possible that I need first to install an old 6.X version with its key and then install 7.3 with the new key?


  5. I made a totally new project but still get errors.

    example:

    In the main file (demo.c) there is

    #include "mb.h"

     

    however, mb.h is not in the same directory as demo.c so during compilation it says that this file cannot be found.

     

    Do I have to explicitly edit all files so that the included files are specified by their relative path to the calling file (or absolute path) or is there a way to define at the project level search paths for include files in the project even if they are scattered between various directories? Otherwise I guess my only option will be to move all files to the same directory.


  6. I downloaded the Modbus example project, extracted it to a directory and opened the Sourceboost project file - All files seem to be listed in the project with their proper relative directories.

    Trying to compile - I get errors that the include files cannot be found.

    Any ideas what else I should configure?

     

    Edit - I assume that there should be somewhere to define search paths for the compiler but do not seem to find them


  7. Tried to get answer form support but no response (in previews years answers were given within 1-3 days).

     

    I have been using Sourceboost C for several years now together with MPLAB 8.

    I am trying to make a move to MPLAB X.

     

    I imported the project that I work on to MPLAB X and tried to compile it.

    Compilation works OK

    Linker fails.

     

    In the MPLAB 8 project tree I have the file libc.pic18.lib under the LIBRARY FILES folder

    I see that it is also listed in the project tree that was imported to MPLAB X

    When compiling in MPLAB X I get the following error:

    Failed to open:(x86)/SourceBoost7/Lib/libc.pic18.lib or C:\Program Files (x86)\SourceBoost7\lib/(x86)/SourceBoost7/Lib/libc.pic18.lib

     

    Any idea what is the problem and what should be done?

     

     


  8. Cosider the next code:

     

    a=1;

    switch (a)

    {

     

    case 1:

    a = a + 1;

     

    case 2:

    do_something();

    a = a + 1;

     

    case 3:

    do_another_thing();

     

    }

     

    Typically a "break" statement is inserted for each case so that once the condition is satisfied the code does not check further cases.

    Obviously if it is not inserted then all cases will be checked, however I could not find documentation for the following - If the tested variable changes value within one of the cases in the switch, will the new value be used on the next case satement or does it maintain the entry value.

    Or in this example will "a" only increase to 2 or will it also do_something(), increase to 3 and do_another_thing()?

     

     


  9. I am using the 18F6527 (18F8722 family)

    I want to implement a watchdog timer

    This seems simple enough:

    enable the WDT either by enabling WDTEN in CONFIG2H, or keep WDTEN disabled and do it in code by manipulating SWDTEN in WDTCON.

    However some things are not clear to me:

    1. How do I reset the watchdog? is it simply an asm CLRWDT within the c code?

    2. It says in the maual that reseting the watchdog also clears the prescaler. Does this mean that after each clear I have to reload the prescaler?

    3. Which brings me to - can the configuration registers be manipulated at run time via c code? I think that for the 18 family it is possible but am not sure. If so - is it simply writing to them like any other SFR or is there a special procedure? And if not - how do you reload the prescaler if it is cleared at runtime (or prevent form clearing)?


  10. 1 - workarounds are always possible (and I use them). I just thought a "built in" linker mecahnism would make life simpler.

    2 - I agree that your idea is more flexible than what I suggested, yet again this is meant for somebody who simply wants to use the -rb flag, but still have the program work without manual intervention (e.g - when developping/debugging a program that will later be loaded by a bootloader that resides in low memory)

×
×
  • Create New...