Post by thread:[OT]: Programmer design..

part 0 44 bytes his is a multi-part message in MIME format. part 1 598 bytes content-type:text/plain; charset=koi8-r (decoded 7bit) Hello! I am going to start to design a simple serial EEPROM programmer for LPT port. Due that i have never design anything with LPT port i need a few tips.. 1. Is there pins on LPT port that can be on same Input and Output (not only I or O) 2. So, is better to use LPT port and a mass of logic devices (aka 74HC....) or use COM port and some uC device to setup IO lines 3. Or, best variant maybe to use LPT port with a few uC and then to get a full 40 pin universal programmer :| What is best choice to use? THANKS! p.s. Didnt i say "simple design" :) part 2 201 bytes content-type:text/x-vcard; charset=koi8-r; (decoded 7bit) begin:vcard n:Pavlica;Milan x-mozilla-html:FALSE org:SuperSonic Systems adr:;;;;;; version:2.1 email;internet:spam_OUTmpavlicaTakeThisOuTptt.yu title:Chief fn:Milan Pavlica end:vcard part 3 154 bytes -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads

On Mon, Aug 05, 2002 at 08:11:23PM +0000, Milan Pavlica YU7XW wrote: > Hello! > I am going to start to design a simple serial EEPROM programmer for LPT > port. What type of serial EEPROM?. What kind of interface (SPI,I2C)? > Due that i have never design anything with LPT port i need a few tips.. > 1. Is there pins on LPT port that can be on same Input and Output (not > only I or O) Not on a standard parallel port. In EPP mode all of the data lines become bidirectional. However the SPP is inputs or outputs only. > 2. So, is better to use LPT port and a mass of logic devices (aka > 74HC....) or use COM port and some uC device to setup IO lines Well it depends on your application. Unless you're doing master I2C I can't see how it would be a mass of logic. For SPI, like the 9366 style EEPROMs, you should only need one simple buffer chip. > 3. Or, best variant maybe to use LPT port with a few uC and then to get > a full 40 pin universal programmer :| > What is best choice to use? You haven't given enough information to formulate a reasoned reponse. You need to answer a bunch of questions: * What capacity? * What interface * Does the part need to be programmed in-circuit? The answers to your design questions are in the answers to those questions. BAJ -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads

Tip #1. Fully study and understand the LPT parallel protocol. There are books by Que and others that will explain the LPT architecture. Tip #2 Understand that LPT interfacing won't work with NT/2000/XP without a LOT of driver headaches. Tip #3 Know that there are several serial EEPROM programmers out there. Are you sure you want to make one from scratch? Answer to #1 - This all depends on your particular hardware printer port. Early PC's had fixed i/o lines. Data were output only, handshake were bi-directional. Later computers had the data lines programmable for i/o. Even later motherboards had different mode configuration(s) EPP, ECP, anticipating uses other than printers....... As I stated above, you will need to be proficient in understanding all the different types and, if this is going to be just a project for you, or if you are going to design this into a product. Answer to #2 - Serial port will be more universal and a little more forgiving if hooked up wrong, but will involve serial to parallel (and back) conversion. Not really a big problem. Could be handled within the uC with some efficient code. From that point on, the uC can probably handle the actual EEPROM reading and writing. Answer to #3 - I'd recommend the serial port for compatibility to PC OS. If you can right good code, a 16F876/877 will finish out the hardware, although there's going to be a good bit of code in your PC too. Simple design???? depends on your perseverance. Good Luck - Rick Milan Pavlica YU7XW wrote: {Quote hidden}> Hello! > I am going to start to design a simple serial EEPROM programmer for LPT > port. > Due that i have never design anything with LPT port i need a few tips.. > 1. Is there pins on LPT port that can be on same Input and Output (not > only I or O) > 2. So, is better to use LPT port and a mass of logic devices (aka > 74HC....) or use COM port and some uC device to setup IO lines > 3. Or, best variant maybe to use LPT port with a few uC and then to get > a full 40 pin universal programmer :| > What is best choice to use? > THANKS! > p.s. Didnt i say "simple design" :) -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads

part 0 44 bytes his is a multi-part message in MIME format. part 1 1034 bytes content-type:text/plain; charset=koi8-r (decoded 7bit) Byron A Jeff wrote: > > What type of serial EEPROM?. What kind of interface (SPI,I2C)? SPI, I2C and microwire > Not on a standard parallel port. In EPP mode all of the data lines become > bidirectional. However the SPP is inputs or outputs only. EPP is OK. I am designing for new comps. :) > Well it depends on your application. Unless you're doing master I2C I can't > see how it would be a mass of logic. For SPI, like the 9366 style EEPROMs, > you should only need one simple buffer chip. Yes, but i want programmer which will have all-in-one without any jumpers or other hardware mods. simple 8pin ZIFF and all other is software job! {Quote hidden}> > You haven't given enough information to formulate a reasoned reponse. You need > to answer a bunch of questions: > > * What capacity? > * What interface > * Does the part need to be programmed in-circuit? > > The answers to your design questions are in the answers to those questions. > > BAJ part 2 231 bytes content-type:text/x-vcard; charset=koi8-r; (decoded 7bit) begin:vcard n:Pavlica;Milan x-mozilla-html:FALSE url:http://www.supersonicsystems.org org:SuperSonic Systems adr:;;;;;; version:2.1 email;internet:.....mpavlicaKILLspam@spam@ptt.yu title:Chief fn:Milan Pavlica end:vcard part 3 154 bytes -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads

part 0 44 bytes his is a multi-part message in MIME format. part 1 1313 bytes content-type:text/plain; charset=koi8-r (decoded 7bit) "Rick C." wrote: {Quote hidden}> Tip #1. Fully study and understand the LPT parallel protocol. There are > books by Que and others that will explain the LPT architecture. > > Tip #2 Understand that LPT interfacing won't work with NT/2000/XP without a > LOT of driver headaches. > > Tip #3 Know that there are several serial EEPROM programmers out there. Are > you sure you want to make one from scratch? > > Answer to #2 - Serial port will be more universal and a little more > forgiving if hooked up wrong, but will involve serial to parallel (and > back) conversion. Not really a big problem. Could be handled within the uC > with some efficient code. From that point on, the uC can probably handle > the actual EEPROM reading and writing. That's and of idea which i had... > Answer to #3 - I'd recommend the serial port for compatibility to PC OS. If > you can right good code, a 16F876/877 will finish out the hardware, > although there's going to be a good bit of code in your PC too. Sure, that's will be maybe the best idea.. If there are interests i can send a schematic which i draw with a simple explain how-it-work. See ya... > > Simple design???? depends on your perseverance. > Good Luck - Rick > part 2 231 bytes content-type:text/x-vcard; charset=koi8-r; (decoded 7bit) begin:vcard n:Pavlica;Milan x-mozilla-html:FALSE url:http://www.supersonicsystems.org org:SuperSonic Systems adr:;;;;;; version:2.1 email;internet:mpavlicaKILLspamptt.yu title:Chief fn:Milan Pavlica end:vcard part 3 154 bytes -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads