| ??? 02/10/07 08:30 Read: times |
#132463 - Yes, a lot of thinking to do! Responding to: ???'s previous message |
Richard Erlacher said:
Why use the parallel port? Mike Stegmaier said:
I avoid any port that involves bit-for-bit processing like the serial port and USB port. I just want to send byte-for-byte. I don't want to convert bits to bytes, or I will introduce synchronization problems. Richard Erlacher said:
Clearly, you've no idea how the serial ports work. Nor the USB port. Nor a USB-to-Serial adaptor (or "bridge") Richard Erlacher said:
Why build a ROM in discrete hardware?
Mike Stegmaier said:
I want a system that is guaranteed to perform any useful function How is that any more guaranteed by using discrete logic than by using a ROM? In fact, one technique uses ROM to implement any arbitrary logic function! A ROM is far more flexible than building discrete, hard-wired logic. A ROM will also be far more reliable than anything hand-built - especially if you ignore device specifications and operate them outside their defined limits! Mike Stegmaier said:
If the eeproms were damaged, whether it be software or hardware, and I didn't have this hard-coded "ROM", then the system will be useless and possibly unpredictable. Again, why is it any more likely that a ROM will fail than that a mass of discrete logic will fail? Basic reliability theory tells us that the mass of discrete logic is bound to have the higher failure probability! With the hardware rom onboard, I can be certain that my system will start up every single time. See above |
