Pic 16f1847

[tcop]

Hi All,
I just decided to move from 16F648A to 16F1847. It is sad that I can't program it from inside MPLAB IDE using PicKit2 but any way I'll use the PicKIT2 v 2.61 software to do it (by the way,isn't there any way to do it using MPLAB, add a device file or something as I did with the pickit2 software?)
Apart from the rich memory that 1847 has, the basic reason for switching, is to take advantage of the hardwary I2C and the faster internal oscilator. The datasheet though, is not very rich in this area since it has no I2C sample routines. Is there any sample code, to make the 1847 work as master for I2C?
rgds

 

[Nigel Goodwin]

I moved to the 16F1827, and simply bought a PICKit3 as the 2 didn't support it at all back then.

However, the PICKit2's own software does support it now, but it's not as convenient as using the PICKit3.

 

[tcop]

Thanks Nigel. PicKit2 supports it after installing the new device file, so I can get the job done using the pickit2 companion software programmer but not using the MPLAB IDE. I didn't bought the pickit3 programmer since I had read so many "bad" stuff about it, in the net. Actually, now it is the first time I hear that it feels "convinient".
How about the I2C routnes. I've read in your site about the software implemantation of I2C. Have you done any hardware implamentation of I2C?
Since 16f1847 fully supports it as a slave and master, there should be no need for software I2C any more.

 

[Nigel Goodwin]

Thanks Nigel. PicKit2 supports it after installing the new device file, so I can get the job done using the pickit2 companion software programmer but not using the MPLAB IDE. I didn't bought the pickit3 programmer since I had read so many "bad" stuff about it, in the net. Actually, now it is the first time I hear that it feels "convinient".
How about the I2C routnes. I've read in your site about the software implemantation of I2C. Have you done any hardware implamentation of I2C?
Since 16f1847 fully supports it as a slave and master, there should be no need for software I2C any more.

I've not ever looked at I2C on it, I haven't had any reason to.

I've had no problems with my PK3 at all, it works just as the PK2 did.