Search found 25 matches

Thanks, I got out of sync with the posts. I agree this is only a road block to someone who is sufficiently determined.

I did it with an earlier version. 4.099 I think.

I note that your file is a .h Try making that a .c and see if that works as mine was a .c.

Otherwise you will have to fight this out with the ...

I'm sorry but I left out a critical step. You have to encrypt the file that will be included. Go to the File tab and click on the Encrypt option. Once you have the properly encrypted file then you ...

CCS fixed this but not the way implied in their documentation.

Use the form #INCLUDE filename.c.encrypted

I am using this and I think it is successful. The frequent problem these days is custom ...

I am using v4.099. I have a program that requires certain parts to be hidden due to proprietary concerns. I need to distribute the logic to my customer but want to hide the device drivers as I have ...

CCS has a reasonably priced product but there are frequent problems with backwards compatibilty. We have been using the CCS compiler for about 15 years and have seen numerous instances of this proble ...

I see this discussion has taken a positive turn. Thanks.

The reason I have used schottky since I first came across this design in 1987 is because the forward drop is about half of a junction diode ...

This is not true. Zener diodes have very poor tolerance compared to a forward biased diode junction.

Furthermore they are extremely leaky so will completely distort the signal to be measured. ...

The zener has a problem because it is more expensive and, most important, the zener tolerance is poor. Look at a zener break over curve with tolerance factored in and you will see what I mean. The z ...

The best protection scheme is a series resistor and a pair of schottky diodes (such as BAT54S) one to each power rail. The resistor should be sized to not burn out the diodes and no affect the sample ...

You can get the abbreviated SD specification at www.sdcard.org

This will tell you how to use the card for low level storage and recovery. It is quite simple. The card has its own embedded control ...

Microchip support has finally determined that the two parts have the same part ID. When the MACHX detects the part it must hit the rf version first in the sort. I assume the only way around this is ...

Microchip is sure that the ID mistake is not in the chip. After further experiment I also find problems with reading the Configuration Register so I think that this part and the Machx are having bit ...

Temporarily just say yes because it will program OK. It's a problem if you have a lot of parts to do. The part that is ID'd is a valid part so if you change your #include to that part (RFPIC12f675K) ...

I find that there is a part RFPIC12F675 that has 20 pins and includes an RF module. The parts I have are 8 pin but are identifying themselves as the 20 pin part. I am checking with Microchip to find ...