GARTHWILSON wrote:
Er... make that 7, not 8. (You'll need a value where none of them are selected, right?)
Reading from address $FF will set all 74HC574 outputs high.
Quote:
Make sure you look at our 65SIB spec which extends SPI in several directions at once.
viewtopic.php?t=1064&start=105I've seen it, thank you. Pretty slick!
Quote:
Since the data will not get fed to the SPI's shift register in the same instruction that you set the select with, then yes, it will work, and the added delay (a portion of a clock cycle) will not be any problem-- if I understand your intentions correctly.
Quote:
This part is so off-topic we might want to take it offline to discuss it, but I'll mention it here anyway. I was just working with the PIC's SSP in slave SPI mode for the first time (before has always been in master mode), and apparently there's no way to get its buffer-full bit to show the reception of more than one byte per SS\-low time, so I could not use SS\ to also indicate the start of a message. Instead, I had to select and de-select for each byte, and then have the slave determine where the end of one message and the beginning of the next is, based on what's in the bytes. Pretty mickey-mouse. Let me know if you know of a solution. I was using my 6502 workbench computer to send the data to it. (There's the 6502 content!
)
I haven't done slave mode yet, though I will be very soon. Still, that just doesn't sound right. Is your slave sending a byte, even if it's only dummy data, for each SPI transaction? Anyway, please tell me which PIC you're using and I'll take a quick look at the Datasheet and see if there's an easy way to simulate something.
Quote:
If Lattice 22V10's might be discontinued anytime soon, perhaps it would be a good time to buy a lifetime supply if you think you'll want them.
Ok, I'll get right on that (grin)...
Mike