![]() | ![]() | ![]() |
| | |||||||
| General Electronics Chat This forum is for general chat about electronics, eg: Dont know what a part does? Dont know how to read a circuit? Want to get an opinion? |
| | LinkBack | Thread Tools | Display Modes |
| | (permalink) |
| Does anyone know if PIC 16C54 can be programmed with JDM ?? Also, is it similar to 16F84?? Thank you | |
| |
| | (permalink) | |
| Quote:
| ||
| |
| | (permalink) |
| | |
| |
| | (permalink) | |
| Quote:
| ||
| |
| | (permalink) |
| And it is indeed parallel programmed, so you need another (more complicated) programmer. | |
| |
| | (permalink) |
| Good day folks, I've been looking at a concept which involves a 16C54 as seen here: http://www.apogeekits.com/frequency_counter.htm Looking around the forums and the folks who kindly offer programming software / schematics, I'm noticing that the 16C54 isn't a widely supported microcontroller. Does anyone know of a frequency counter schematic which uses a more common uC? Possibly a FLASH uC? or a programmer which supports the 16C54? I don't know much about the assembly code or uC applications yet, so I'm looking to learn through experimenting with a frequency counter. I've run through some very basic items such as flashing LED's and such, but I'm looking for something more practical (such as a frequency meter, YAY!). I realize that this post is in the wrong forum topic, but I wanted to add on to this discussion for reference. Thanks for your time! | |
| |
| | (permalink) |
| http://www.kuskov.com/electronics/pic54pro.php a programmer for 16C54. It is the only thing I found.. I have a problem now, because I need to read the code of a code protected 16C54 ... I believe it is not possible to do it.. is it?? It is a very valuable code that I cannot find elsewhere.. | |
| |
| | (permalink) |
| It's pretty much impossibe to readout a code protected device. There was a rumour once that by using a certain trick the older pic's could be read, even when code protected, but I wouldn't put much faith into it. | |
| |
| | (permalink) | |
| Quote:
| ||
| |
| | (permalink) | |
| Quote:
The more likely reason is that the code isn't your's, and you've bought a preprogrammed code protected device - so you've no right to the code at all. Historically the 16C84 had poor code protection, there was supposed to be fairly simple ways to break the protection - this was the main reason for it being replaced by the 16F84, essentially the same device with the code protection flaw removed. Code protection on any device is only safe against fairly limited attack, enough money can break anything! - dissolving the encapsulation and reading the chip with a microscope is one (very expensive) way of doing it, but apparently needs a fairly large number of chips to experiment with. | ||
| |
| | (permalink) | |
| Quote:
Thanks for the 16C54 link Patroclus! | ||
| |