SPI: The serial peripheral interface [video]
youtube.com
SPI: The serial peripheral interface [video]
1–10 of 32 posts
Re: SPI: The serial peripheral interface [video]
#2Ben's videos are some of the most interesting content on Youtube. The build an 8-bit computer from scratch tutorial has been around this site a few times, as has the 6502 series. But what really gets interesting are these peripheral videos where he digs into a specific system or concept. His videos about how error correction works were a real eye-opener for me. It's the right level of zoomed in.
Re: SPI: The serial peripheral interface [video]
#3I wish more devices simply used RxTx (or COM/RS-232) so that the protocol was defined inside the character payload instead. Simplicity is worth sacrificing bandwidth for.
Re: SPI: The serial peripheral interface [video]
#4I wish more devices simply used RxTx (or COM/RS-232) so that the protocol was defined inside the character payload instead. Simplicity is worth sacrificing bandwidth for.
Do you mean implicit clock to save the third line? Other than that SPI is about as simple as it gets. Plus there's a protocol for practically every requirement: i2c for simple slowish shared bus with clock, 1-wire shared bus without clock, SPI fast and simple, serial single ended (RS232) or differential (RS485) for stuff outside of your PCB...
Re: SPI: The serial peripheral interface [video]
#5I wish more devices simply used RxTx (or COM/RS-232) so that the protocol was defined inside the character payload instead. Simplicity is worth sacrificing bandwidth for.
Simplicity of what exactly? From the perspective of the device/hardware, SPI is much simpler. A UART based solution tends to be relatively much more complex on the hardware/device side. You can implement a basic compliant SPI slave in a tiny bit of silicon - like a handful of flip flops simple. Moreover, you realize many of the simplest SPI devices don't have an oscillator, so you're still going to need a clock line - and if its truly a UART/asynchronous it may not be convenient to get a high enough speed external clock.
Re: SPI: The serial peripheral interface [video]
#6I wish more devices simply used RxTx (or COM/RS-232) so that the protocol was defined inside the character payload instead. Simplicity is worth sacrificing bandwidth for.
Given that I2C and SPI are addressable replacing them with a bare TTL serial interface would be horrendous because now everyone needs to invent their own addressing scheme which they already had with the other two.
0/10 suggestion
Re: SPI: The serial peripheral interface [video]
#7I wish more devices simply used RxTx (or COM/RS-232) so that the protocol was defined inside the character payload instead. Simplicity is worth sacrificing bandwidth for.
Given that I2C and SPI are addressable replacing them with a bare TTL serial interface would be horrendous because now everyone needs to invent their own addressing scheme which they already had with the other two. 0/10 suggestion
SPI isn't addressable.
Re: SPI: The serial peripheral interface [video]
#8Earlier quoted context omitted.
Given that I2C and SPI are addressable replacing them with a bare TTL serial interface would be horrendous because now everyone needs to invent their own addressing scheme which they already had with the other two. 0/10 suggestion
SPI isn't addressable.
Yes it is - that's what /SS is for.
Re: SPI: The serial peripheral interface [video]
#9Earlier quoted context omitted.
SPI isn't addressable.
Yes it is - that's what /SS is for.
Chip selects are optional. You can daily chain multiple spi devices and push the data out in a contiguous block. All the chip selects are tied together and only one cs line is used from the cpu.