Mikorians

I'm using an older version of the software and I didn't see it listed in the gui. I will check the chip list today.

Wow! You folks have always been right on top of things. I meant that the version of GCB gui doesn't seem to show it in its list of chips. If it would compile for it, the fact that the developer board acts as a USB thumb drive would be keen if it would just let me copy the hex file without a big mplab install. (?) Thanks!

Ok: WinXP, GCB 0.96, PicKit, and a 16F15376 (Needed 2 HW Com ports, 40 pin DIP) Chip isn't listed in either GCB or the standalone PicKit3 gui. Fortunately, haven't actually PURCHASED said chip yet. Whew! Am I stuck?

Hi again! I know I'm probably doing everything all wrong again. Using PIC16F887 and 18F4680. Version 0.96 on WinXP SP3, 32Bit. I've been messing around trying to get what I found about this .H include on Google. I just can't seem to get it to run. I've got incomplete mixed documents and versions of things. There's 3 versions to pick from... gcbasic.chm hi2c slave isr.h another .h also said to replace the existing hi2c.h file. Things are seeming conflicting and sort of hodge podge to me. I know it...

OK Works now!

Hardware, .96 Saw timeout of MSSP. Look just before. Current problem: I must reset I2C Bus. On/Off/On/Off...? Is it Repeated HI2CStop, HI2CStart or repeated HI2CRestart? Or was it address 0 HI2CSend 0 ???

Months of agony... Our robot (lots of RFI/EMI) kept locking up. We couldn't figure out why. We had become stack paranoid. But the assumption: Wait UNTIL In hi2c.h was found. We backed it up and added both a timeout and error flag to it just as we did in usart.h. Now we just have one question- Do you know the generic technique for waking up the I2C bus? I've forgotten it...

I can understand why. It's merely that it might've been more useful to US as a sort of multi-line #Define. (The pin dir was an input by the end of a very long line) Normally we are quite tidy in our coding and conform to OOP practices, but the limited stack on these inexpensive mass purchased PICs nearly DEMANDS violating those practices. Plus with Or/And being iffy, we have to bust 'em up. (So we're glad Goto's there :)