Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
10/25/08 16:11
Read: times


 
#159353 - Danger to use block sizes not n*8 bits
Responding to: ???'s previous message
Yes, most things are possible - and allowed - with SPI. And no standard organization (or copyright, trademark, ...) to limit what is allowed.

Most SPI controllers are unable to communicate in other chunk sizes than 8 bits. Some SPI controllers can do 16-bit or 32-bit communication (including internal byte-swapping) to allow simple transfer of larger data types. A few SPI controllers do have the ability to specify a specific bit count out of a 8-bit, 16-bit or 32-bit integer written into the send register.

But to not force people into having to switch to bit-banged communication, companies producing SPI peripherials really have to think very much about using transfer sizes that are not a multiple of 8 bits.

On the other hand - there is absolutely no limitation to what the actual bits will mean when doing SPI communication. Every single device may be totally unique. This is not a problem since you normally talk with only one device at a time, and any other device will ignore anything on the signal lines. In some situations my may talk to more than one slave device (but limited to one-way communication) but in that case the separate slave devices just has to use an identical protocol.

List of 18 messages in thread
TopicAuthorDate
SPI is a free for all ??            01/01/70 00:00      
   Danger to use block sizes not n*8 bits            01/01/70 00:00      
      The non-standard, standard            01/01/70 00:00      
         Master is easy, slave is pure hell            01/01/70 00:00      
         control by chip select            01/01/70 00:00      
            Correct            01/01/70 00:00      
   Now you know why Philips (now NXP) ...            01/01/70 00:00      
   Yes.            01/01/70 00:00      
      What was the incompatibility?            01/01/70 00:00      
         Instruction length.            01/01/70 00:00      
            Bad knowledge of that EEPROM manufacturer            01/01/70 00:00      
               Oh the irony.            01/01/70 00:00      
                  No Analogue Irony At All            01/01/70 00:00      
                     I have company..            01/01/70 00:00      
                        Your T7            01/01/70 00:00      
                           Simple interpretation            01/01/70 00:00      
                        FTDI            01/01/70 00:00      
                           I have company            01/01/70 00:00      

Back to Subject List