Jump to content


Photo

Target Devices Supported By Boostc


76 replies to this topic

#61 peter s

peter s

    Newbrie

  • Members
  • 4 posts

Posted 18 October 2012 - 09:58 AM

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

#62 Dave

Dave

    Super Maniac

  • Administrators
  • PipPipPipPipPip
  • 2,091 posts
  • Gender:Male
  • Location:UK
  • Interests:How things work, Electronics, Software, Cycling.

Posted 18 October 2012 - 11:59 AM

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

#63 hyperion007

hyperion007

    Newbrie

  • Members
  • 4 posts

Posted 06 May 2014 - 10:22 AM

When will PIC18F97J94 be supported by BoostC?



#64 Kallevik

Kallevik

    Newbrie

  • Members
  • 1 posts
  • Gender:Male
  • Location:Norway

Posted 21 August 2014 - 11:54 AM

I need boostc support for the PIC16F1459.

 

ASAP...Please !



#65 CuoreDiGhiaccio

CuoreDiGhiaccio

    Newbrie

  • EstablishedMember
  • 11 posts
  • Gender:Male
  • Location:Italy

Posted 03 September 2014 - 04:25 PM

I need boostc support for PIC16F1788 and PIC16F1789

 

Best Regards

Johnny



#66 QMESAR

QMESAR

    Newbrie

  • Members
  • 1 posts

Posted 08 February 2015 - 01:59 PM

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



#67 John P

John P

    Newbrie

  • EstablishedMember
  • 17 posts

Posted 11 February 2015 - 03:25 PM

And I want the PIC16F1619!

#68 L de vries

L de vries

    Regular

  • EstablishedMember
  • Pip
  • 22 posts
  • Gender:Male
  • Location:Holland

Posted 14 February 2015 - 10:26 PM

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.



#69 redkooga

redkooga

    Newbrie

  • Members
  • 1 posts
  • Gender:Male
  • Location:north walsham uk

Posted 04 April 2016 - 05:04 AM

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

 

Thanks



#70 soft2

soft2

    Regular

  • EstablishedMember
  • Pip
  • 71 posts
  • Location:Vermont

Posted 04 August 2016 - 01:44 AM

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?



#71 DTPIC

DTPIC

    Regular

  • EstablishedMember
  • Pip
  • 23 posts

Posted 22 May 2017 - 01:50 PM

 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...(!)



#72 RJS

RJS

    Regular

  • EstablishedMember
  • Pip
  • 25 posts
  • Gender:Male
  • Location:Denver

Posted 24 May 2017 - 01:07 AM

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 



#73 L de vries

L de vries

    Regular

  • EstablishedMember
  • Pip
  • 22 posts
  • Gender:Male
  • Location:Holland

Posted 16 July 2017 - 10:00 PM

New targets supported in version 7.40:
PIC16F1459, PIC16F1788 and PIC16F1789 are now supported !

Edited by L de vries, 16 July 2017 - 10:10 PM.


#74 Pavel

Pavel

    Super Maniac

  • Administrators
  • PipPipPipPipPip
  • 1,451 posts
  • Gender:Male
  • Location:Melbourne, Australia

Posted 17 July 2017 - 08:19 AM

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



#75 JorgeF

JorgeF

    Super Enthusiast

  • EstablishedMember
  • PipPipPip
  • 276 posts
  • Gender:Male
  • Location:ES @ Europe, third rock from the Sun

Posted 08 August 2017 - 04:55 PM

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 by JorgeF, 08 August 2017 - 04:57 PM.


#76 Pavel

Pavel

    Super Maniac

  • Administrators
  • PipPipPipPipPip
  • 1,451 posts
  • Gender:Male
  • Location:Melbourne, Australia

Posted 08 August 2017 - 11:52 PM

...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";
}


#77 JorgeF

JorgeF

    Super Enthusiast

  • EstablishedMember
  • PipPipPip
  • 276 posts
  • Gender:Male
  • Location:ES @ Europe, third rock from the Sun

Posted 09 August 2017 - 04:30 PM

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 by JorgeF, 09 August 2017 - 04:30 PM.




Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users