Jump to content

L de vries

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About L de vries

  • Rank

Profile Information

  • Gender
  • Location

Recent Profile Visitors

572 profile views
  1. Quick search on google: "The machine is missing the correct C++ runtime components for your type of system." In the SourceBoost install process you can check the boxes to install visual 2008, 2009 and 2010, did you ?
  2. Free, does that mean you abandon it, or is this a new business model? Anyway, i have told my wife to donate you $4 so you can have a beer. I used Sourceboost a lot, learned how to program with it (C4 PIC16 Matrix multimedia) later on got the Pro V6 and V7 licences, but if it gets abandoned, (no new target support) it becomes nice for hobby projects and for learning to program on older controllers. For commercial projects on new controllers you can ask yourself if it is a good choice or not. Cheers!
  3. Sb plugin did work in MPLABX v5.00 (and lower). project did also compile. Installed MPLABX 5.10 today, installed SB plugin as in MPLAB v5.00, installation works ok, like in MPlabX v5.00. restart MPLABX, toolchain is added to list in tools/options/embedded tab in MPLABx 5.10. open project is ok, Hit clean and build project button in MPlabx, Information window opens: Compiler toolchain "BoostC" of type "BoostC" does not exist.Please visit Tools/Options/Embedded to locate an installation of this toolchain or to select another compiler toolchain. Project is not cleaned, and compiler does not start. Embedded Build Tools tab: Type: SourceBoost Language Toolchain Base Directory: C:\Program Files (x86)\Sourceboost C Compiler: C:\Program Files (x86)\SourceBoost\xlaunch.exe Make Command: C:\Program Files (x86)\Microchip\MPLABX\v5.10\gnuBins\GnuWin32\bin\make.exe
  4. I see that the document " MplabX_Plugin.pdf " in the source boost install is chanced. On page 9 is an explanation how to force the compiler: To force BoostC or BoostC++ use command line argument -force_c or -force_cpp. To force Chameleon use command line argument -force_chameleon To add command line argument right click on the project inside MPLAB-X and open project properties dialog. this is a far better method , so forget about chancing "build tools" file names Lieuwe
  5. hello, I have source boost v7.41 installed, when I look to the download http://www.sourceboost.com/Products/IdePlugins/Download.html There is no V7.41 plug-in pack yet. Although v7.40 plug-in seem to work with 7.41 IDE, is the upgrade to 7.41 on the way, or must I use the 7.40 plug-in with the 7.41 IDE ? Lieuwe
  6. Installed V7.41 with new souceboost MPLABX - plugin. into MPLABX v3.65 When I open a project in MPLABX , I can get to File>Project Properties. It would be nice that i can switch between compiler Toolchains: (screenshot print screen copy paste not allowed in this forum,) "You are not allowed to use that image extension on this community." The XC8 compiler in this example is selectable v1.42 or v1.43. The Sourceboost compiler has just one taste. It would be nice to have the option in this screen to switch between C, C++ and Chameleon. A way that works is: Go to Tools>Options>Embedded>Build Tools. Default the C Compiler is : C:\Program Files (x86)\SourceBoost\xlaunch.exe Click on the .... box after the line C:\Program Files (x86)\SourceBoost\xlaunch.exe , so you can chance this to : C:\Program Files (x86)\SourceBoost\c_pic16.exe and Apply Now this project, and al other sourceboost projects, compiles with Chameleon, without altering file names. To switch back, just select C:\Program Files (x86)\SourceBoost\xlaunch.exe again. Lieuwe
  7. Just curious about "Chameleon" The fact that there is c_pic16.exe (2064Kb), boostc++_pic16.exe (2124Kb) and that c_pic16.exe (4156Kb), in combination with the name "Chameleon", does this mean that the new compiler is a C and C++ combined ? Microchip does have / borrows this, for their 8 bits Atmel parts (avr8-gnu-toolchain), but does not have it for their 8 bits (PIC16 and PIC18) parts. Nice move, Pavel ! The compiler message: "WARNING: Try our new Chameleon C compiler. It's fast, free and 95% backward compatible with BoostC." What is the 5% that is not?, what are the differences?
  8. It works. " BoostC compiler executable in a safe place, rename the Chameleon executable into BoostC " That will be boostc_pic16. exe / boostc_pic18.exe VS c_pic16.exe / c_pic18.exe. Compiling works, it looks like Chameleon is more restrictive on the same code, i get errors, while i do not see those with BoostC. Errors were the result of " extern volatile char eedata ; " in the code, of course there was already a declaration in the header file (include map in source boost installation). " ..\EEprom16F87XA.c(30): error: failed to add variable 'eedata', variable with this name already declared on C:\Program_Files\SourceBoost\include\PIC16F877A.h:399 "
  9. New targets supported in version 7.40: PIC16F1459, PIC16F1788 and PIC16F1789 are now supported !
  10. After some time, a lot of upgrades in Sourceboost V7.40, thanks for that. When I build a project with MplabX, i get messages in the Output window of MPlabX: C:\Program_Files\SourceBoost\include\system.h(40): WARNING: Try our new Chameleon C compiler. It's fast, free and 95% backward compatible with BoostC. I would like to try this, I see in the Sourceboost IDE "Active Tollsuite Selection" where I can choose "Chameleon" "normal" use of the MPlabx plugin works fine, with BoostC version 7.40. Also I removed and installed the MPlabX plug-in (in Sourceboost 7.40 the version seems the same as in 7.3 (plug-in version 1.0) The document "MplabX_Plugin.pdf" in the Sourceboost 7.40 directory does not describe the use of "Chameleon" either. So how do I manage to use Chameleon in MplabX ?
  11. UPDATE: Problem disappeared in new MPlabx Version 3.35
  12. Situation 2 computers: win7 32 bit, another computer win10 64bit. SITUATION BEFORE: Sourceboost v7.30 installed in "C:\Program_Files\Sourceboost" on both systems. (no spaces in path name). MPlabx 3.26 installed by default settings and sourceboost plugin installed. Source boost projects compile, and link without problems. After UN-install MPlabx 3.26, and installation of MPlabx 3.30 Sourceboost plugin installation works without warnings. but... when I restart MPlabx, MPlabx v3.30 gives a warning: "Could not generate makefiles for configuration default" and compiling Sourceboost projects in MPlabx is not possible any more. Switching back to "Situation before" (MPlabx 3.26) does solve the problem. This situation behaves the same on both systems (win7 and win10) Is an update of the Sourceboost plug-in necessary ? Or is there a work around to use Sourceboost in combination of MPlabx v3.30. I have re-installed MPlab 8.92 for use with Sourceboost now (with use of ICD2 and pickit 2) For new projects with new target chips, I use MPlabx v3.30 in combination of XC8 compiler with ICD3. I hope Sourceboost comes with updates for the plug-in and the many new pic16F1xx targets. Sourceboost is a great product,specially in combination with the 16F1 targets running small but reliable firmware. Suggestion : keep source boost simple and do not try to defeat XC8 with complexity, beet it with small reliable software for a fair price, for an MCU that suits it , focus on the new small 16F1 targets. Leave the complexity and the frameworks for the ARM processors and compilers. I am afraid Sourceboost is going out of support, but I hope that I am wrong on that. And if Source boost is a dead end, well, then I thank Pavel and Dave for the great software I used so many years with satisfaction.
  13. It has been more than a year ago, since new targets were added. To stay competitive to the XC compilers it would be really nice to take advantage of the many new PIC16F1 chips. Like the PIC16F1789. I do not expect to have all the library’s to work with this new devices, I can write my own functions. But it would be a good thing to have a sort of upgrade / expansion pack for new target support, so we can get the include files for those new targets.
  14. Hello, The MplabX plugin does work now, that is great. But.. it still points to the "old linker name". (ok, it's only the message, after the message and clicking OK, the linker does work.) How can this be chanched, it would be nice that you can point MplabX to the right linker location for sourceboost, like you can set the locations of the xc8 compiler and linker. Or that the .nmb file uses the right linker location. Lieuwe
  15. Look at the toppic: Pinned Problems And Workaround When Trying To Add Sourceboost Toolchain In Mplabx Fails you can find this toppic at: SourceBoost support forum → PIC and SX Embedded Programming → BoostC and C2C compilers programming It is a work around, I hope it will be fixed in the next relaese. Lieuwe
  • Create New...