Hi,
I used to have a version 2 development board and was able to program PIC16C711's, using PPP v2.7, via parallel port, with no issues.
Due to hardware problems with the board I was upgraded to a v3 board (with USB). (Thanks for sorting that out Ian) ...but now with the new board and PPP v3.5.8.21 (that I am forced to use due to the USB) I find the list of devices PPP is able to program is much reduced and consequently I am not able to program my 16C711's.
Are there any plans to get the new version of PPP up to the same level, in terms of devices it can program, as the older version? Or are there any other ways around this problem?
Thanks.
PPP v3.5.x ability to program a PIC16C711?
-
Steve
- Matrix Staff
- Posts: 3422
- Joined: Tue Jan 03, 2006 3:59 pm
- Has thanked: 114 times
- Been thanked: 422 times
- Contact:
Hi CW,
Yes - I see your problem. We were hoping to keep 16C compatibility with the new USB board design but for some reason, the same programming routines that were working for the 16C devices on the old parallel port programming system were failing when used in the new USB port system.
We spent a little while looking into this issue, but could not find a solution. At the same time, we can see a general move by Microchip to gradually phase out the 16C parts in favour of the 16F or 18F devices. After all, they are much easier to work with in terms of development, and I'm pretty sure that the flash memory chips will soon become cheaper than their equivalent ROM-based counterparts (if that is not the case already).
We knew that practically all of our customers were using flash devices, so we though that removing support for the 16C chips would not cause anyone a problem. Obviously it has in your case, so apologies for that.
Unfortunately I cannot see us revisiting this issue in the near future (we have a lot of important development going on at the moment), so I guess that the best option for you is to either move your development to a flash chip, or to try to resurrect an old PC with a parallel port (or even buy a parallel port expansion card) and continue using the old parallel port board.
Yes - I see your problem. We were hoping to keep 16C compatibility with the new USB board design but for some reason, the same programming routines that were working for the 16C devices on the old parallel port programming system were failing when used in the new USB port system.
We spent a little while looking into this issue, but could not find a solution. At the same time, we can see a general move by Microchip to gradually phase out the 16C parts in favour of the 16F or 18F devices. After all, they are much easier to work with in terms of development, and I'm pretty sure that the flash memory chips will soon become cheaper than their equivalent ROM-based counterparts (if that is not the case already).
We knew that practically all of our customers were using flash devices, so we though that removing support for the 16C chips would not cause anyone a problem. Obviously it has in your case, so apologies for that.
Unfortunately I cannot see us revisiting this issue in the near future (we have a lot of important development going on at the moment), so I guess that the best option for you is to either move your development to a flash chip, or to try to resurrect an old PC with a parallel port (or even buy a parallel port expansion card) and continue using the old parallel port board.