How to put a 74HC165 on an SPI bus?

Question

If I want to read a (bunch of) 74HC165 chip(s) over an SPI port on a microcontroller, this is simple enough. Connect them through Q7 to DS on each, apply the final Q7 to MISO, notCE to SS and CP to SCK. This works fine.

But now how do I share the SPI bus with other devices that I want to read? The 165's Q7 output is never hi-Z, so I can't share the MISO pin with other devices. I'd need some way to "detach" it - a buffer of some kind.

I know there are 74-series chips that have various buffers that can be made hi-Z (such as a 74HS240) but that's a whole additional chip just to be able to share the shift register. Perhaps some cunning way to put a transistor between the final Q7 and the microcontroller's MISO, controlled by the SS line?

---

Edit: Alternatively, can someone suggest some other parallel-in serial-out shift register that does have a tristate serial output line, and therefore suitable to use on an SPI bus?

Answer 1

can someone suggest some other parallel-in serial-out shift register that does have a tristate serial output line, and therefore suitable to use on an SPI bus?

Mouser, Newark, and a few other distributors and suppliers have a selection filter that helps when I'm looking for "something like a 74HC165, but with tristate serial output":

74HC589: 8-bit serial or parallel input; serial output; shift register with 3-state output. "The HC589A directly interfaces with the SPI serial data port on CMOS MPUs and MCUs."

-- On Semiconductor datasheet; Fairchild datasheet (So it meets the "must have a second source" criteria that some projects have, as mentioned by Jason S).

Answer 2

As you noted, the 165 is not a 'full' SPI device because it doesn't tri-state its output.

If you have a single 165 on your SPI bus and speed is not a big issue you could place a resistor (10k?) between the 165 output and the uC MISO pin. Other SPI chips (that do tri-state their output) will override the weak drive through the resistor, but without other chips active the weak drive will prevail, but you might need to slow the clock down (for the 165 only).

If you have multiple 165's you could use a multiplexer chip (151). This costs extra select lines for the mux chip, but you can share the 165's notCE lines (which otherwise would have been separate), and use one of the inputs for the 'real' SPI chips.

Answer 3

The 74xx125 and '126 are quad buffers with tri-state outputs, individually controlled - you could use one package to buffer four 165s...

Answer 4

You described how you can cascade a bunch of 74HC165 chips into a long chain. A bunch of the 74HC595 chips also can be cascaded together into a similar daisy-chain.

One way to "share the SPI bus with other devices" is to chain all your chips into one long SPI daisy chain. It's been a while since I did it, but I seem to remember that I could put 74HC165 chips, 74HC595 chips, and similar chips into one long loop. No matter how many chips were in the daisy chain loop, or what order they were in, I only required 4 pins on the microcontroller.

The microprocessor MOSI pin drives the MOSI pin of the first chip in the chain, each chip is cascaded so its serial output drives the serial input of the next chip in the chain, and the MISO pin of the last chip in the chain drives the MISO pin of the microprocessor.

The microprocessor clocks in / clocks out a full loop's worth of data every time it want to change any output or read any input.

That's how JTAG works, right?

Such a long daisy-chain loop is slower, but requires fewer pins on the microcontroller than the "Independent slave SPI configuration". Unfortunately, some chips that claim to support SPI cannot be daisy-chained.

The whole reason you are even considering SPI is because you are running out of pins on the microcontroller and you are connected to something that doesn't need high speeds, right?