Pavel

Sorry about the confusion and let's try to sort this out. What product is the key for? Based on the screenshot that you provided it seems that the product is BoostC Pro but you try to register either plugins or IDE. Keys are valid only for products they were issued for and will not work with other products. Please email details to support@sourceboost.com and we'll sort this out. Regards, Pavel

If your license is for version 7.x it should be valid for 6.x as well. What is wrong with your 7.x installation? Regards, Pavel

Looks like a bug. Will take a look. Pavel

Plugins have not changed and we don't plan to release 7.41 plugins. You can use 7.40 plugins with this release.

Limited support means that only core information that is necessary to compile and debug for this target is included into system headers and TDF files:- only core registers are defined in the system header files, if you need other registers you need to add your own defines to either your code or system header - full config data is added to the system headers (PIC16) or TDF(PIC18) files - target architecture is fully described in the TDF files but non-core registers and register groups are not. You are welcome to add missing information. To compile it's only necessary to add it to system header

The reason we use xlaunch.exe instead of the actual compiler in the MplabX plugin is to allow different programming languages to be used in the same project. Xlaunch analyses the command line and based on the extension of the input source file launched a relevant compiler For example a project can consist of .c, .c++ and .bas files an when compiling xlaunch.exe will use C, C++ and Basic compilers to compile these files.

When you assign an integer to a float like in float fnum = 0x41bba752; you expect compiler to do copy number into the float directly byte by byte. This is not what's happening. Behind the scene compiler generates code like fnum = float32_from_int32(1102817106); so you get the same value but presented as a float.

Use either this: asm { movlw 0x52 movwf _fnum+0 movlw 0xa7 movwf _fnum+1 movlw 0xbb movwf _fnum+2 movlw 0x41 movwf _fnum+3 } or this: union { unsigned long l; float f; } f; f.l = 0x41bba752; fnum = f.f;

Check http://forum.sourceboost.com/index.php?showtopic=1456&do=findComment&comment=20995

Make sure you start preg.exe as administrator and make sure you select the correct product inside the preg.exe dialog (for example a BoostC++ key won't work with BoostC). If this fails try to register from command line. This can be done for any product that is an executable (so this method won't work for plugins and those are DLLs).Do do this: - open command prompt as administrator - navigate into SourceBoost installation directory - start the product executable followed with the "register" command line argument. For example for the BoostC compiler issue the command line like : C:\Program F

That's sounds like a compiler bug. We'll look into this. Chameleon does not support C++ classes but has a very good support of data and function templates up to the point when template based meta programming can be done. In fact its code generation logic is based on this. For an example check very bottom of include\sys\sys_assign.h file where meta programming is used to generate code for assigning structs. It also supports auto data type and explicit enum types (like in the latest C++ standard). From the top of my head: - rom type specifier is ignored - dynamic memory allocati

You can download support files for PIC18F6xK40 from: http://www.sourceboo...PIC18F6xK40.zip 7.40 also includes instructions how to add support for new targets. Look into the readme.txt files inside include and config directories and how_to_add_new_target.txt file in the root of SourceBoost installation. Pavel

Currently the Chameleon compiler is in beta stage and does not have a corresponding MplabX plugin yet. The only way I can think of how to work around this is to save the BoostC compiler executable in a safe place, rename the Chameleon executable into BoostC and use MplabX with BoostC plugin. The command lines between these 2 is mostly compatible and this makes it possible for this approach to work. Pavel

No difference. GOTO is ok as well. My point was to use built-in assembler rather than C but whatever you use CALL or GOTO doesn't matter. Regards, Pavel

I's tricky to call a function that is not linked to an application. The way to proceed is to use built in assembler like 'call 0x70'. The only issue with this approach is that it's impossible to use call arguments so the solution is to declare a fixed address array to pass data to your bootloader function. Regards, Pavel

Please explain why your method is more preferable? Regards, Pavel

There is no known way to do this under MPLAB And MPLABX should work just fine

Running preg as admin may not be enough. One option is to log in as admin and that run preg and register. Another way is to log in as admin and start compiler from command line followed by the 'register' command line argument like 'boostc_pic16.exe register'. This will show a dialog where you can enter your license info.

Isn't this issue fixed in 7.x release? Regards, Pavel

Here is working sample code that sets up custom characters that represent battery status and that cycles trough them. Enjoy. Regards, Pavel #include <system.h> // Configure LCD connections // If using this code under SourceBoost simulator (for PIC18F97J60), configure the LCD plugin as follows: // RS to RH2 // R/W to RH1 // E to RH0 // DB0 to RE0 // DB1 to RE1 // DB2 to RE2 // DB3 to RE3 // DB4 to RE4 // DB5 to RE5 // DB6 to RE6 // DB7 to RE7 // #define LCD_ARGS 0, /* Interface type: mode 0 = 8bit, 1 = 4bit(low nibble), 2 = 4bit(upper nibble) */ \ 1,

I spent more time on the PicPack library and eventually was able to build the usb_serial project. Here is a list of additional to my previous post changes that needs to be done: 1. Seems that some define names are a bit inconsistent. This fix will take care of this. In config.h add these code after the line '#define USB_EP0_IN_ADDR 0x0508': #define USB_EP0_OUT_O_SIZE USB_EP0_OUT_SIZE #define USB_EP0_OUT_O_ADDR USB_EP0_OUT_ADDR #define USB_EP0_OUT_E_SIZE USB_EP0_IN_SIZE #define USB_EP0_OUT_E_ADDR USB_EP0_IN_ADDR 2. For the value of PLATFORM_CLOCK defined in the project there are

...Unfortunately it gets numerous compiler and preprocessor errors with 7.30 while attempting to compile the demo projects (using whatever chip the demos were meant for, I didn't change their target) ... I just tried to build couple of the USB projects from the PicPackLib 3.09 from www.embeddedadventures.com with 7.30 and here is what you need to change to make the project build: Project ea_plt1003_usb2serial or ea_plt1003_usb_keyboard or usb_joy_mouse: 1. The project file contains path to the compiler that may be different from what is on your computer. After opening the project y

No SourceBoost does not include any USB libraries Regards, Pavel

SourceBoost is alive and well. Just released a new version 7.30 with a number of improvements and fixes including a new IP library that implements basic IP stack (ARP/IP/UDP/DHCP/ICMP) which was quite fun to develop. We still support and develop it albeit not as active as before. Regards, Pavel

I tried SourceBoost installation on a 'clean' Windows 8.1 64bit computer that had never SourceBoost installed. The installation went fine and after installation I was able to register goodies using preg just fine (remember that after you select 'goodies' inside preg you need to press 'OK' and that will bring up another dialog where you enter your goodies license name and key). After that I started goodies and they extracted files (including Novo) without any problems. Regards, Pavel