Hello Denny,

Denny >>Best I can say is you're not understanding the nature of a PIC chip. Modern PICs such as (I asume) the 16F675 your working with have FLASH memory for program storage, EEPROM for constants and data and the like, and a small amount of RAM for the variables. <<

I am working with the 12F675. And I do not want to use that crazy UV eraser <g> Like I had to use with the Philips 750 and 752.

I am extremely new to the PIC series of chips. My knowledge is zelch on these chips.

I would like to program these chips on the fly, and be able to reprogram them on the fly. Without having to purchase chips again and again. The UV only lasted about 25 times or so on the philips, and I had to sit under that UV for 30 min, and sometimes 45 min.(towards the end).


Denny>>All of this is good for thousands of write cycles, you can't "ruin" a PIC by programming it. <<

Good, I was hoping it wasn't a OTP chip, and presto...you are out of luck.

Denny>>And you can't put "program" code in the EEPROM. (well, technicaly you could, but there's no way for the PIC to run code stored in the EEPROM, so it'd be pointless anyway.)<<

I read that the 12f675 and 1k of Eprom 126 byes of EEprom, and a small amount of RAM. this puzzled me, because this told me that the 1k of Eprom is programmable, but has to be erased by a UV... or something else. Could you set me straight on this please?

I have looked over kingdom come, and MPASM doesn't exist. there is a MPASM IDE, but that is not a assembler. I guess I may have to fork out 300 dollars for the basic language... Which I am not sure I like that or not. Relying upon this tells me I cannot streamline my code the way I want.

Dwayne