Does MICROCODE support PIC16LF88?

Printable View

- 24th March 2009, 21:43
flotulopex

Does MICROCODE support PIC16LF88?

Hello,

Does anyone know if MICROCODE does support (program) 16LF88 µc?

I would need to use one of those because of their low VDD but can't find them in the device list.
- 24th March 2009, 23:16
tenaja

the low power "L" parts are programmed using the standard part number.
- 25th March 2009, 05:38
flotulopex

1 Attachment(s)

Thank you.

This is what I also assume.

I just wonder why the device list in MICROCODE shows some "L" devices then.

<img src="http://www.picbasic.co.uk/forum/attachment.php?attachmentid=3280&stc=1&d=123795932 1">
- 25th March 2009, 13:59
Byte_Butcher

Dunno about the 16LF88, but I've programmed 16LF727's with MCS and PICkit2, using the 16F727 setting and it seems to work fine.

steve
- 25th March 2009, 20:18
Darrel Taylor

Quote:

Originally Posted by flotulopex

I just wonder why the device list in MICROCODE shows some "L" devices then.

How old is your version of MicroCode Studio?

The original versions had a PIC.INI file that listed the available PIC's. Then you had to manually add any that weren't in the list.

Later versions search the PBP folder and populate the drop-down box with all the *.INC files it finds. That way it always has the correct list for whatever version of PBP you have.

There are no .INC files specifically for LF parts. So I'm guessing you have a really old version of MCS.
<br>
- 25th March 2009, 23:22
Archangel

Along similar lines Does PBP work for RFPICs like RFPIC12F675KT-I/SS ?
- 26th March 2009, 00:48
Darrel Taylor

Quote:

Originally Posted by PBP - Current PICmicro® MCU support

rfPIC12C509AF, rfPIC12C509AG: Limited support as base device PIC12C509A (more information) .

rfPIC12C509AF, rfPIC12C509AG, rfPIC12F675F, rfPIC12F675H, rfPIC12F675K: Supported as base device PIC12F675

The rfPIC's are like 2 separate chips in a single package.

The rfPIC12F675F is a standard 12F675, with an ASK/FSK transmitter module in the same package. To send data from the 12F675, you have to actually use a PIN as output, and connect it to either the DATAask or DATAfsk of the same chip. If you want to turn the carrier on/off it takes another output pin from the 675, connected to the RFEN pin of the transmitter.

There are no registers in the PIC half that have any control over the transmitter half.

As far as PBP or MCS is concerned, it's just a 12F675.
<br>
- 26th March 2009, 01:03
mister_e

In theory MicroCode should update it's own PIC supported list, case not you may need to add it by yourself. PIC.INI file is the one to edit. You can even create aliases to specific PIC, you just need to copy the right INC file and rename it the same way you have define it in PIC.ini.
- 26th March 2009, 05:34
Archangel

Quote:

Originally Posted by Darrel Taylor

The rfPIC's are like 2 separate chips in a single package.

The rfPIC12F675F is a standard 12F675, with an ASK/FSK transmitter module in the same package. To send data from the 12F675, you have to actually use a PIN as output, and connect it to either the DATAask or DATAfsk of the same chip. If you want to turn the carrier on/off it takes another output pin from the 675, connected to the RFEN pin of the transmitter.

There are no registers in the PIC half that have any control over the transmitter half.

As far as PBP or MCS is concerned, it's just a 12F675.
<br>

Great, Thank You.
- 26th March 2009, 08:23
flotulopex

let's try

I'm going to try the LF version then.

It is not a question of cost since they are almost the same price as standard PICs; I just don't want to store PICs I wouldn't be able to program.

BTW, I use Microcode Studio version 3-0-0-5.
- 26th March 2009, 20:49
flotulopex

It does work

So, I tried to program a "LF" device and it worked like a charm.