Target Devices Supported By Boostc

[peter s 0]

Hi Dave,

how can i use PIC16LF1847? There is an 16LF1847.h - File in the include-Directory, but this type doesn't appear in the Target-List (or i can't find it)

I'm using Boost-C Version 7.01.

Greetings Peter

[Dave 0]

Peter,

how can i use PIC16LF1847? There is an 16LF1847.h - File in the include-Directory, but this type doesn't appear in the Target-List (or i can't find it)

I'm using Boost-C Version 7.01.

Upgrade to BoostC V7.10.

 

Regards

Dave

[hyperion007 0]

When will PIC18F97J94 be supported by BoostC?

[Kallevik 0]

I need boostc support for the PIC16F1459.

 

ASAP...Please !

[CuoreDiGhiaccio 0]

I need boostc support for PIC16F1788 and PIC16F1789

 

Best Regards

Johnny

[QMESAR 0]

I need boostc support for PIC16F1788 and PIC16F1789

Please guys add support for the PIC16FXX Family ,I want to add specifically the PIC16F1786 to the above list

[John P 0]

And I want the PIC16F1619!

[L de vries 0]

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.

[redkooga 0]

Hi I would like PIC16F1619 added to be able to use microchip discovery.

 

Thanks

[soft2 0]

I see there is a header file for PIC18F45K50 (although somewhat incomplete) and a .TDF file as well. But MPLABX won't allow me to use the Sourceboost toolsuite for this device. Is there a list that MPLABX scans to see what devices are supported by SourceBoost toolsuite? Can I manually add this device to the list? If not, how long before you will formally support it?

[DTPIC 0]

I am planning a project for a customer targetting PIC 18F67K40.

 

This CPU doesn't appear to be supported in the current release (7.30). Can you please provide an update to allow me to use this part?

 

In general, how is BoostC tracking the appearance of new processors? Is anybody producing new support files for them? Either within the Sourceboost company or the community? Is there some other community support site that I should be looking at?

 

(I have in the past edited the _PIC18Fxxx.TDF, map.txt and other include files, to add a CPU, but its a tricky process - is there a guide published for "how to" add a CPU to the list? Or could you write one? Or should I write one based on what i have done in the past for you to edit?)

 

Is there a mechanism for users to contribute "mods" they have made for new CPUs, so they can be sent back into the community?

 

Still using your product after many years (back to early 6.xx) - many thanks for a great little compiler & IDE. Just wish you would do a PIC32MX one...(!)

[RJS 0]

Since I have not seen any updates or responses in some time could you please let us know if your products are still supported and if the newer devices will be added soon or should we start looking at other compliers?

 

Thanks!

 

Randy

[L de vries 0]

New targets supported in version 7.40:

PIC16F1459, PIC16F1788 and PIC16F1789 are now supported !

Edited July 16, 2017 by L de vries

[Pavel 0]

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

[JorgeF 0]

Hi Pavel

 

 

What exactly means "limited support" in the version log?

 

Its something to do with the core processor or its only a libraries thing?

 

 

 

Best regards

Jorge

Edited August 8, 2017 by JorgeF

[Pavel 0]

...What exactly means "limited support" in the version log?...

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 files. Missing information in the TDF files is used in debugging under SourceBoost IDE and if you use Mplab or Mplab X you don't need it.

 

For example look at the Port B support that is not defined in the limited support targets but is fully supported in PIC18F8722. This target has the following information in its system header file PIC18F8722.h (used in compilation):

...
#define PORTB                  0x00000F81 
...
volatile char portb            @PORTB;
..

and in PIC18F8722.tdf file (used for debugging):

 

 

Configure PORTB
{
    // create
    PinNames = "RB0|INT0","RB1|INT1","RB2|INT2","RB3|INT3|ECCP2|P2A","RB4|KBI0","RB5|KBI1|PGM","RB6|KBI2|PGC","RB7|KBI3|PGD";
}


RegisterSF PORTB
{
    Description = "PORTB","";
    Address = F81h;
    BitNames = "RB7","RB6","RB5","RB4","RB3","RB2","RB1","RB0";
}

[JorgeF 0]

Hi

 

Thank you Pavel.

 

So, if I understood it correctly all the important things are acounted for, its only missing optionals.

All the registers relating to oscillator configurations, interrupts, memory paging/banking and other core features are defined.

The compiler and linker do handle interrupts (context), the memory maps (ROM pages / RAM banks) and config words correctly, including the tricky dispatching code used by Novo.

All I have to take care by myself are the peripherals.

 

 

Good enought for me!

 

 

EDIT ADD:

BTW, I mostly use MPLAB 8/X

 

 

Best regards

Jorge

Edited August 9, 2017 by JorgeF

[jartim 0]

On 09/08/2017 at 12:52 AM, Pavel said:

Missing information in the TDF files is used in debugging under SourceBoost IDE and if you use Mplab or Mplab X you don't need it.

Pavel, I don't think this is correct?

 I'm using MPLAB-X and I've added a new header for a PIC16F570 device and modified the MPLAB jar files to allow me to use SourceBoost with that device (it doesn't by default).

I haven't created a .tdf file for the same device because I don't use the SourceBoost IDE, but when I try to build under MPLAB-X, I get this message -

main.cpp
error: could not open input file 'C:\Program Files (x86)\SourceBoost\config\PIC16F570.tdf'

So it appears as though the build process needs the .tdf file as part of the build as well (this is using the C++ compiler under MPLAB-X).  I will have a go at creating one for my new device.  If it's successful, is there somewhere I can post it on the forum to make it available to other users?

[EDIT] Pavel, is there a full list of the options that can be used in the .tdf file entries?  I found a .txt file in the config folder that partly explains the .tdf file format, but it does not give a complete list of all the possible options?  

Rgds

Tim

Edited October 26, 2017 by jartim

[Pavel 0]

A TDF file is required for build but only the core data from it is used. You need to have a TDF file that has at least minimal data like in _PIC18minimal.TDF

 

There is no document that lists all options that can be used in TDF. You need to check the existing TDF files for examples.

 

Regards,

Pavel

 

[Doggy 0]

When might there be support for 18F26K42?

 

Regards,

David