Jump to content


Photo

Target Devices Supported By Boostc


64 replies to this topic

#31 AlexR

AlexR

    Regular

  • EstablishedMember
  • Pip
  • 58 posts

Posted 27 February 2009 - 07:57 AM

The "LF" PICs can operate at a lower voltage than the normal F series at the expense of a restricted top clock rate. They have the same instruction and features set as the normal F PICs so just use the normal non-LF part when writing your program.
Alex

#32 Panvadee

Panvadee

    Newbrie

  • Members
  • 4 posts

Posted 01 March 2009 - 10:48 PM

The "LF" PICs can operate at a lower voltage than the normal F series at the expense of a restricted top clock rate. They have the same instruction and features set as the normal F PICs so just use the normal non-LF part when writing your program.



Thanks Alex. I had a programming problem before I thought it might be the LF series problem, but it was just a dodgy cable.

#33 Shree

Shree

    Regular

  • EstablishedMember
  • Pip
  • 71 posts
  • Gender:Male
  • Location:India

Posted 15 June 2009 - 12:19 PM

I've just ammended this list (by editing this post 7th December 2007), so that you don't need to search further down this topic to find devices, they are all in this post.

Please let is know of any new PIC12, PIC16 (sorry only 14bit instruction types) or PIC18 targets you want added.

Here is the current list:

PIC12
PIC12C671, PIC12CE673, PIC12CE674, PIC12F609, PIC12HV609, PIC12F615, PIC12HV615, PIC12F629, PIC12F635, PIC12C672, PIC12F675, rfPIC12F675h, rfPIC12F675k, rfPIC12F675f, PIC12F683

PIC16
PIC16CE623, PIC16CE624, PIC16CE625, PIC16C432, PIC16C433, PIC16C554, PIC16C557, PIC16C558, PIC16C61, PIC16F616, PIC16HV616, PIC16C62, PIC16C62A, PIC16C62B, PIC16CR62, PIC16C620, PIC16C620A, PIC16CR620A, PIC16C621, PIC16C621A, PIC16C622, PIC16C622A, PIC16F627, PIC16F627A, PIC16F628, PIC16F628A, PIC16C63, PIC16C63A, PIC16CR63, PIC16F630, PIC16F631, PIC16F636, PIC16F639, PIC16C64, PIC16C64A, PIC16CR64, PIC16C642, PIC16F648A, PIC16C65, PIC16C65A, PIC16C65B, PIC16CR65, PIC16C66, PIC16C662, PIC16C67, PIC16F676, PIC16F677, PIC16F684, PIC16F685, PIC16F687, PIC16F688, PIC16F689, PIC16F690, PIC16C71, PIC16C710, PIC16C711, PIC16C712, PIC16C715, PIC16C716, PIC16F716, PIC16C717, PIC16C72, PIC16C72A, PIC16CR72, PIC16F72, PIC16C73, PIC16C73A, PIC16C73B, PIC16F73, PIC16F737, PIC16C74, PIC16C74A, PIC16C74B, PIC16F74, PIC16C745, PIC16F747, PIC16C76, PIC16F76, PIC16C765, PIC16F767, PIC16C77, PIC16F77, PIC16C770, PIC16C771, PIC16C773, PIC16C774, PIC16F777, PIC16C781, PIC16C782, PIC16F785, PIC16HV785, PIC16F818, PIC16F819, PIC16CR83, PIC16F83, PIC16C84, PIC16CR84, PIC16F84, PIC16F84A, PIC16F87, PIC16F870, PIC16F871, PIC16F872, PIC16F873, PIC16F873A, PIC16F874, PIC16F874A, PIC16F876, PIC16F876A, PIC16F877, PIC16F877A, PIC16F88, PIC16F883, PIC16F884, PIC16F886, PIC16F887, PIC16F913, PIC16F914, PIC16F916, PIC16F917, PIC16C923, PIC16C924, PIC16C925, PIC16C926, PIC16F946

PIC18
PIC18C242, PIC18C252, PIC18C442, PIC18C452, PIC18C601, PIC18C658, PIC18C801, PIC18C858, PIC18F1230, PIC18F1320, PIC18F1330, PIC18F2220, PIC18F2221, PIC18F2320, PIC18F2321, PIC18F2331, PIC18F2410, PIC18F242, PIC18F2420, PIC18F2423, PIC18F2431, PIC18F2439, PIC18F2450, PIC18F2455, PIC18F2458, PIC18F248, PIC18F2480, PIC18F24J10, PIC18F24K20, PIC18F2510, PIC18F2515, PIC18F252, PIC18F2520, PIC18F2523, PIC18F2525, PIC18F2539, PIC18F2550, PIC18F2553, PIC18F258, PIC18F2580, PIC18F2585, PIC18F25J10, PIC18F25K20, PIC18F2610, PIC18F2620, PIC18F2680, PIC18F2682, PIC18F2685, PIC18F26K20, PIC18F4220, PIC18F4221, PIC18F4320, PIC18F4321, PIC18F4331, PIC18F4410, PIC18F442, PIC18F4420, PIC18F4423, PIC18F4431, PIC18F4439, PIC18F4450, PIC18F4455, PIC18F4458, PIC18F448, PIC18F4480, PIC18F44J10, PIC18F44K20, PIC18F4510, PIC18F4515, PIC18F452, PIC18F4520, PIC18F4523, PIC18F4525, PIC18F4539, PIC18F4550, PIC18F4553, PIC18F458, PIC18F4580, PIC18F4585, PIC18F45J10, PIC18F45K20, PIC18F4610, PIC18F4620, PIC18F4680, PIC18F4682, PIC18F4685, PIC18F46K20, PIC18F6310, PIC18F6390, PIC18F6393, PIC18F63J11, PIC18F63J90, PIC18F6410, PIC18F6490, PIC18F6493, PIC18F64J11, PIC18F64J90, PIC18F6520, PIC18F6525, PIC18F6527, PIC18F6585, PIC18F65J10, PIC18F65J11, PIC18F65J15, PIC18F65J50, PIC18F65J90, PIC18F6620, PIC18F6621, PIC18F6622, PIC18F6627, PIC18F6680, PIC18F66J10, PIC18F66J11, PIC18F66J15, PIC18F66J16, PIC18F66J50, PIC18F66J55, PIC18F66J60, PIC18F66J65, PIC18F6720, PIC18F6722, PIC18F6723, PIC18F67J10, PIC18F67J11, PIC18F67J50, PIC18F67J60, PIC18F8310, PIC18F8390, PIC18F8393, PIC18F83J11, PIC18F83J90, PIC18F8410, PIC18F8490, PIC18F8493, PIC18F84J11, PIC18F84J15, PIC18F84J90, PIC18F8520, PIC18F8525, PIC18F8527, PIC18F8585, PIC18F85J10, PIC18F85J11, PIC18F85J15, PIC18F85J50, PIC18F85J90, PIC18F8620, PIC18F8621, PIC18F8622, PIC18F8627, PIC18F8628, PIC18F8680, PIC18F86J10, PIC18F86J11, PIC18F86J15, PIC18F86J16, PIC18F86J50, PIC18F86J55, PIC18F86J60, PIC18F86J65, PIC18F8720, PIC18F8722, PIC18F8723, PIC18F87J10, PIC18F87J11, PIC18F87J50, PIC18F87J60, PIC18F96J60, PIC18F96J65, PIC18F97J60, PIC18LF2423, PIC18LF2523, PIC18LF4423, PIC18LF4523, PIC18F1220, PIC18F6628

Regards
Dave


I've noticed that in the BoostC (sourceboost) supported device list there is no SX's (which was supported by c2c) , have you totally abandoned this chip - or will you be supporting it in the future? - maybe a separate compiler?. Checking around there is not many choices (SXC from CCS [$199] & SXC from Bytecraft [$795 - DOS] / [$1495 - WIN]). And it is quite a nice micro. :D

Kind regards Henrik

Hello Dave,
I am trying to design a timer for 3 phase motor and I have zerod down on a device 12F510. Could this device be included in the above list?
Thanks in advance
Shree

Edited by Shree, 15 June 2009 - 12:32 PM.


#34 Reynard

Reynard

    Maniac

  • EstablishedMember
  • PipPipPipPip
  • 629 posts
  • Gender:Male
  • Location:Scotland
  • Interests:Archery - target and field

Posted 15 June 2009 - 01:50 PM

Shree,

Pick-a-PIC (sorry) that has at least an 8 level stack. Devices with only a 2 level stack are possibly not suited to high level languages like C.

Cheers

Reynard

#35 ra68gi

ra68gi

    Super Enthusiast

  • EstablishedMember
  • PipPipPip
  • 228 posts
  • Gender:Male
  • Location:India

Posted 29 November 2009 - 04:47 PM

Hi Dave,
Do you intend to support the 16F193X series devices ?
If so How soon?

Regards
Raghunathan.

#36 Reynard

Reynard

    Maniac

  • EstablishedMember
  • PipPipPipPip
  • 629 posts
  • Gender:Male
  • Location:Scotland
  • Interests:Archery - target and field

Posted 29 November 2009 - 05:09 PM

Raghunathan,

Have you checked out the latest V6.97 Beta release yet ?

Cheers

Reynard

#37 ra68gi

ra68gi

    Super Enthusiast

  • EstablishedMember
  • PipPipPip
  • 228 posts
  • Gender:Male
  • Location:India

Posted 30 November 2009 - 02:54 PM

Raghunathan,

Have you checked out the latest V6.97 Beta release yet ?

Cheers

Reynard


Thanks to Dave & Pavel,
The 16F1937 is very attractively priced, so planning of using them in my new projects.

Regards
Raghunathan.

#38 Thermal Runaway

Thermal Runaway

    Regular

  • EstablishedMember
  • Pip
  • 23 posts
  • Gender:Male
  • Location:South Wales, United Kingdom

Posted 12 December 2009 - 01:31 PM

Just to let the developers know I also came here searching for support on the PIC16F193X series.

I've just downloaded the beta release as previously suggested so hopefully that's one problem sorted out. In the meantime I've noticed that the PICKIT 2 does not support these devices so now I'm going to have to upgrade. Drat.

Thanks for the device support BoostC team.

Brian

#39 IanM

IanM

    Enthusiast

  • EstablishedMember
  • PipPip
  • 161 posts
  • Gender:Male
  • Location:UK

Posted 12 December 2009 - 04:29 PM

...
Midrange/1.8V Min Devices
----------------
PIC16F722 PIC16LF722
PIC16F723 PIC16LF723 PIC16F724 PIC16LF724
PIC16F726 PIC16LF726 PIC16F727 PIC16LF727

PIC16F1933 PIC16F1934 PIC16F1936 PIC16F1937
PIC16F1938 PIC16F1939
PIC16LF1933 PIC16LF1934 PIC16LF1936 PIC16LF1937
PIC16LF1938 PIC16LF1939

...

So they are supported stand-alone by the GUI software (and also by PK2CMD) and you will find them in 'Device Family' -> 'Midrange' -> '1.8V Min' but you will have to wait for MPLAB to catch up before you can debug on them or program from the MPLAB IDE.

#40 Shree

Shree

    Regular

  • EstablishedMember
  • Pip
  • 71 posts
  • Gender:Male
  • Location:India

Posted 08 February 2010 - 07:42 AM

Hello Dave/Pavel,
Got some 16F1826s at really cheap price, but was dissappointed only to know that SB only supports 16F1827(Pin compatible with the former. Only diff is mem, 2 more timers and a CCP modules). Any plans for the support of 16F1826?
Regards
Shree

#41 davidb

davidb

    Enthusiast

  • EstablishedMember
  • PipPip
  • 134 posts
  • Location:Essex, UK

Posted 08 February 2010 - 08:21 AM

What can I do if I use PIC16LF648a? It doesn't have any of the PIC16LFxxx on the list above.

Shree,

AFAIK, apart from the different working voltage range and lower maximum operating frequency, the PIC16LF648A is functionally identical to the PIC16F648A so just use the PIC16F648A.

Regards

davidb

#42 Ian Harris

Ian Harris

    Regular

  • EstablishedMember
  • Pip
  • 87 posts
  • Location:London, UK

Posted 08 February 2010 - 09:52 AM

Panvadee,

The LF and F devices are identical from a code perspective - they only differ in that the LF devices can typically handle lower voltages and/or higher clock speeds at lower voltages.

As far as sourceboost is concerned, pick the pic16f648a and you'll be fine.

cheers
Ian.

What can I do if I use PIC16LF648a? It doesn't have any of the PIC16LFxxx on the list above.



#43 Shree

Shree

    Regular

  • EstablishedMember
  • Pip
  • 71 posts
  • Gender:Male
  • Location:India

Posted 09 February 2010 - 12:42 PM

Hello Dave/Pavel,
Got some 16F1826s at really cheap price, but was dissappointed only to know that SB only supports 16F1827(Pin compatible with the former. Only diff is mem, 2 more timers and a CCP modules). Any plans for the support of 16F1826?
Regards
Shree

Any news guys?????

#44 TomF

TomF

    Enthusiast

  • EstablishedMember
  • PipPip
  • 112 posts

Posted 02 March 2010 - 09:45 AM

Looking to use the 16F1827 soon, will this be added within a month?

Edited by TomF, 02 March 2010 - 09:45 AM.


#45 Pavel

Pavel

    Super Maniac

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

Posted 02 March 2010 - 09:36 PM

Looking to use the 16F1827 soon, will this be added within a month?


Yes PIC16F1827 will be supported starting from soon to be released 6.97.

Regards,
Pavel

#46 John S

John S

    Newbrie

  • EstablishedMember
  • 19 posts
  • Gender:Male
  • Location:UK
  • Interests:Money, Peace

Posted 12 March 2010 - 10:27 AM

Looking to use the 16F1827 soon, will this be added within a month?


Yes PIC16F1827 will be supported starting from soon to be released 6.97.

Regards,
Pavel


Hello Dave/Pavel,

I have C Compiler Version 6.97 and Sourceboost IDE 6.97
I'm using 16F1936 but have to deal with these errors

C:\DEVEL\PIC work\PIC16F1936\work.c(155:2): error: unknown identifier 'sspadd'
C:\DEVEL\PIC work\PIC16F1936\work.c(155:2): error: unknown identifier 'sspstat'
C:\DEVEL\PIC work\PIC16F1936\work.c(184:9): error: unknown identifier 'sspbuf'


and lot more errors on registers associated with MSSP module.
I have to manually add following lines on PIC16f1936.h file to sort the errors

volatile char sspadd @SSPADD;
volatile char sspbuf @SSPBUF;
volatile char sspcon2 @SSPCON2;
.... few more lines..


I just wonder if the header file is incomplete or this is the way it ment to be.

Also Interrupt won't work for MSSP module. (may be my code fault)

Thankyou
John

#47 John S

John S

    Newbrie

  • EstablishedMember
  • 19 posts
  • Gender:Male
  • Location:UK
  • Interests:Money, Peace

Posted 12 March 2010 - 10:53 AM

Looking to use the 16F1827 soon, will this be added within a month?


Yes PIC16F1827 will be supported starting from soon to be released 6.97.

Regards,
Pavel


hi Dave and Pavel,
Sorry If this post comes up twice..somethin happen to my comuter last time wen I posted.

I'm using Sourceboost V6.97 and C Compiler Version 6.97 (for PIC16 architecture).

I'm using PIC16f1936 and I found the following errors

C:\DEVEL\PIC work\PIC16F1936\work.c(122:7): error: unknown identifier 'sspadd'
C:\DEVEL\PIC work\PIC16F1936\work.c(155:2): error: unknown identifier 'sspstat'
C:\DEVEL\PIC work\PIC16F1936\work.c(156:2): error: unknown identifier 'sspcon1'
C:\DEVEL\PIC work\PIC16F1936\work.c(184:9): error: invalid operand 'sspbuf'

and lot more..

Then I added the following lines on PIC16F1936.h

volatile char sspadd @SSPADD;
volatile char sspbuf @SSPBUF;
volatile char sspcon2 @SSPCON2;
volatile char sspcon1 @SSPCON1;


and few more to registers which deals with MSSP module.

I just wonder if the header file is incompelete or this is the way it meant to be..

I also have problems with interrupts on mssp module (may be my code error)

thankyou
John

#48 Dave

Dave

    Super Maniac

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

Posted 12 March 2010 - 11:04 AM

John,

Sorry If this post comes up twice..somethin happen to my comuter last time wen I posted.

I'm using Sourceboost V6.97 and C Compiler Version 6.97 (for PIC16 architecture).

I'm using PIC16f1936 and I found the following errors

C:\DEVEL\PIC work\PIC16F1936\work.c(122:7): error: unknown identifier 'sspadd'
C:\DEVEL\PIC work\PIC16F1936\work.c(155:2): error: unknown identifier 'sspstat'
C:\DEVEL\PIC work\PIC16F1936\work.c(156:2): error: unknown identifier 'sspcon1'
C:\DEVEL\PIC work\PIC16F1936\work.c(184:9): error: invalid operand 'sspbuf'

and lot more..

Then I added the following lines on PIC16F1936.h

volatile char sspadd @SSPADD;
volatile char sspbuf @SSPBUF;
volatile char sspcon2 @SSPCON2;
volatile char sspcon1 @SSPCON1;


and few more to registers which deals with MSSP module.

I just wonder if the header file is incompelete or this is the way it meant to be..

I also have problems with interrupts on mssp module (may be my code error)

Some entries were missed. Attached is the header file that will be in the next release.

Regards
Dave

Attached Files



#49 John S

John S

    Newbrie

  • EstablishedMember
  • 19 posts
  • Gender:Male
  • Location:UK
  • Interests:Money, Peace

Posted 12 March 2010 - 12:07 PM

John,

Sorry If this post comes up twice..somethin happen to my comuter last time wen I posted.

I'm using Sourceboost V6.97 and C Compiler Version 6.97 (for PIC16 architecture).

I'm using PIC16f1936 and I found the following errors

C:\DEVEL\PIC work\PIC16F1936\work.c(122:7): error: unknown identifier 'sspadd'
C:\DEVEL\PIC work\PIC16F1936\work.c(155:2): error: unknown identifier 'sspstat'
C:\DEVEL\PIC work\PIC16F1936\work.c(156:2): error: unknown identifier 'sspcon1'
C:\DEVEL\PIC work\PIC16F1936\work.c(184:9): error: invalid operand 'sspbuf'

and lot more..

Then I added the following lines on PIC16F1936.h

volatile char sspadd @SSPADD;
volatile char sspbuf @SSPBUF;
volatile char sspcon2 @SSPCON2;
volatile char sspcon1 @SSPCON1;


and few more to registers which deals with MSSP module.

I just wonder if the header file is incompelete or this is the way it meant to be..

I also have problems with interrupts on mssp module (may be my code error)

Some entries were missed. Attached is the header file that will be in the next release.

Regards
Dave



Thanks Dave!

#50 joli

joli

    Regular

  • EstablishedMember
  • Pip
  • 45 posts
  • Gender:Male
  • Location:Portugal

Posted 29 April 2010 - 05:27 PM

Dave can confirm what i think that compiler does in terms of a no existing pic's in the ..\include\.

Likely others, i think if we create the appropriate pic header maybe we can have it working.

Regards,
Joli

#51 Dave

Dave

    Super Maniac

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

Posted 29 April 2010 - 08:24 PM

Dave can confirm what i think that compiler does in terms of a no existing pic's in the ..\include\.

Likely others, i think if we create the appropriate pic header maybe we can have it working.

To support a new target device you need to create new .h and new .tdf files, and add the new target device to the map.txt file.
You can find these files in the include and config folders.


Regards
Dave

#52 DTPIC

DTPIC

    Newbrie

  • EstablishedMember
  • 18 posts

Posted 13 July 2011 - 10:34 AM

I am still using BoostC Ver 6.97. I have created a project using 18F44K20, (a 3V3 CPU) but would like to move it to a 44K22 (a 5V CPU). However, 6.97 doesn't support 44K22 in its target list.

Could you please confirm for me:

1) As far as I can tell, the K20 and K22 are functionally equivalent - so can I compile for a K20 and use the code on a K22?

2) If so, I guess this also applies for 45K20/K22, 46K20/22, etc?

3) Finally, from another part of this topic, it seems I could add the K22 variants by creating (copy K20 part and edit?) a .h, and .tdf file and adding an entry to the map.txt file?


I will move up to release 7 when time allows! But I must get this job out first....

Many thanks!

#53 DTPIC

DTPIC

    Newbrie

  • EstablishedMember
  • 18 posts

Posted 13 July 2011 - 04:24 PM

...erm, have just realised that there is a difference in the K20, K22 cores - they are not "functionally equivalent" - so best ignore my last post....

#54 Dave

Dave

    Super Maniac

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

Posted 14 July 2011 - 02:20 PM

Panvadee,

What can I do if I use PIC16LF648a? It doesn't have any of the PIC16LFxxx on the list above.

Select target device PIC16F648a instead.

Regards
Dave

#55 Mike McLaren

Mike McLaren

    Regular

  • EstablishedMember
  • Pip
  • 41 posts
  • Gender:Male
  • Location:Michigan, USA

Posted 13 November 2011 - 01:06 AM

Would it be possible to get Boostc support for the relatively recent 10F320/10F322 devices which are actually 14-bit core with an interesting twist or two (would you believe there's a LATA register?)?

Thanks in advance...

Cheerful regards, Mike

#56 Dave

Dave

    Super Maniac

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

Posted 16 November 2011 - 12:36 PM

Mike,

If these devices are 14bit instruction cores then it should not be a major job for the BoostC compiler to support them.

Regards
Dave

#57 Mike McLaren

Mike McLaren

    Regular

  • EstablishedMember
  • Pip
  • 41 posts
  • Gender:Male
  • Location:Michigan, USA

Posted 27 March 2012 - 07:16 PM

May I ask if there has been any progress to support 10F320 and 10F322, please?

Cheerful regards, Mike

#58 Dave

Dave

    Super Maniac

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

Posted 28 March 2012 - 11:51 AM

Panvadee,

What can I do if I use PIC16LF648a? It doesn't have any of the PIC16LFxxx on the list above.

The LF devices are low power versions on the regular device.
This means coding for them is the same as the regular device.
So for the BoostC compiler select the PIC16F648a device instead.

Regards
Dave

#59 Mike McLaren

Mike McLaren

    Regular

  • EstablishedMember
  • Pip
  • 41 posts
  • Gender:Male
  • Location:Michigan, USA

Posted 15 April 2012 - 04:46 PM

Greetings Dave (and gang),

Please forgive the intrusion. May I ask if there are any BoostC updates since v7.051 (11-Dec-2011), please?

Cheerful regards, Mike

Edited by Mike McLaren, 15 April 2012 - 05:06 PM.


#60 Pavel

Pavel

    Super Maniac

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

Posted 16 April 2012 - 02:49 AM

Please forgive the intrusion. May I ask if there are any BoostC updates since v7.051 (11-Dec-2011), please?


We are sitting on some bug fixes/changes/improvements but have not release any new version. We planned to do this after we update the MPLAB X integration but it looks that we might to release before this happens as it takes a longer than expected to get answers for a few technical questions from Microchip.

Regards,
Pavel



Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users