on 18 Apr 98, pic microcontroller discussion list wrote... >ashley barnett wrote : > >> Hi and HELP !! > >> Has anybody had problems getting the Phoenix B firmware and the picstart B1 to >> work?? I have!! > >> I programmed a 17C43 JW with Phoenix B and plugged in a 16C84 to test it and >> the following happened, C1 errors. > >> If any body has any clues as to why I can Read and Verify a Pic but not > program >> or blank a Pic please let me know. > >> I have tried all the switches available. > >I used a 17C44 JW, and have been able to program a 16c84 without >problems. I doubt that the 17c44 is any different from a 17c43 in >this application, so it's probably something different about your PC. >Programming is different from other functions in that the handshake >lines hold off PC output for a significant time : reading will work >OK without the handshake lines connected at all. > >C1 errors are apparently UART overruns - try running the system in >the simplest possible mode (no Windows, pure DOS boot, no mouse, no >TSRs etc). Also try disabling the UART FIFO if you have one - I don't >think this should cause C1 errors, but it might (the PC thinks it's >lost characters from the programmer, when really it's not yet sent the >previous command). > >Phoenix (TM4) uses strict hardware handshaking to avoid sending more >than 1 byte ahead to the programmer .. this doesn't really work if you >use a braindamaged PC UART like the 16550 (it doesn't stop >transmitting when the handshake lines change, just generates an >interrupt while continuing to send the fifo contents). > I have done all of this and tried it on three different PCs now. I think there could be a problem with the Picstart or a problem with the Phoenix software !, It has occasionally worked and programmed half of a 16c84 program but crashed. I am still suspect about the software as when I tested the Vpp pin when reading I had a 1 sec pulse of 13.5Volts, however when attempting a program or verify I only had a 20mSec pulse of 13.5V !! I am not sure if that has anything to do with it? - It is a real pain as I need to program a 16C74 a number of times. >I've got the core of a TM4 driver for Linux running, but have been too >busy to develop it much further. If there's anyone else who's interested >in getting this going, I'd appreciate some help to try it out and make >some constructive criticism. > > >-adrian > >