??? 10/16/06 22:19 Read: times |
#126545 - pins, lost&found Responding to: ???'s previous message |
Erik Malund said:
The issue is not can I use the 8255 with 'tricks' I have yet to see that question and, in addition, if you are going to use 'tricks' (I/O mapped I/O) why use the antique in the first place? Now THIS is the question you should've asked first. 1. because my professor told so 2. because I have it on my devboard 3. because I have a handuful of them at no cost 4. because all of the above and I am a student Otherwise, not in the first place. If it should be a new board, it should NOT be the FIRST CHOICE. However, reasons are to talk about it, still. So, if somebody comes and asks, how to interface a 8255 to 8052, let us not answer him "don't do that" in the first place. Let us tell him, how, and then tell him that it's not the best thing to do and what are the alternatives. In this order and say it all. Not only a part of it. Erik said: Not quite so. Technically speaking, there are a couple of options, the easiest of them is to use the data/address bus pins for data/address and handle the chipselect/read/write "manually". Those who like complex solutions can cascade the 8255 with a memory-mapped latch, but I admit that would be sort of perverse a bit... :-)
Another important issue re "pulling by hand" is that you can not do that when you have external memory (you do not have enough pins) and THAT is when you need I/O expansion). Erik said:
Also if you do not have external memory what on earth to you need more than 32 (64) I/Os for? I have around 30 switches and 20 lights in my house. Jan Waclawek |