Skip to main content
added 184 characters in body
Source Link
Dmitry Grigoryev
  • 28.2k
  • 6
  • 54
  • 145

There is a big difference between 6..9 MHz clock speed (which according to the BCM2835 datasheet is possible onderived from 150MHz core_clk with a power-of-two 16-bit integer divider CDIV, I assume the Pi 4 is similar) and 6..9 Mbit/s data rate which you won't achieve if you can only read 2-3 bytes at a time. The overhead of IO library and drivers will limit you to tens of thousands SPI transfers per second.

If you find an ADC that can be configured to buffer samples and them stream them over SPI in large chunks, it may just work with a direct SPI connection. However, ADCs which require you to read out the last sample before they can produce a new one will require external buffering.

Look at FT42XX products: those are USB to SPI/Quad SPI bridges supporting up to 30 Mbit/s clock rates. FTDI offers drivers for ARMv7 and ARMv8 as a part of their libft4222 package, so there's a good chance those bridges will work with a Pi.

Digikey sells FT4222H modules for $18 a piece.

There is a big difference between 6..9 MHz clock speed (which is possible on a Pi) and 6..9 Mbit/s data rate which you won't achieve if you can only read 2-3 bytes at a time. The overhead of IO library and drivers will limit you to tens of thousands SPI transfers per second.

If you find an ADC that can be configured to buffer samples and them stream them over SPI in large chunks, it may just work with a direct SPI connection. However, ADCs which require you to read out the last sample before they can produce a new one will require external buffering.

Look at FT42XX products: those are USB to SPI/Quad SPI bridges supporting up to 30 Mbit/s clock rates. FTDI offers drivers for ARMv7 and ARMv8 as a part of their libft4222 package, so there's a good chance those bridges will work with a Pi.

Digikey sells FT4222H modules for $18 a piece.

There is a big difference between 6..9 MHz clock speed (which according to the BCM2835 datasheet is derived from 150MHz core_clk with a power-of-two 16-bit integer divider CDIV, I assume the Pi 4 is similar) and 6..9 Mbit/s data rate which you won't achieve if you can only read 2-3 bytes at a time. The overhead of IO library and drivers will limit you to tens of thousands SPI transfers per second.

If you find an ADC that can be configured to buffer samples and them stream them over SPI in large chunks, it may just work with a direct SPI connection. However, ADCs which require you to read out the last sample before they can produce a new one will require external buffering.

Look at FT42XX products: those are USB to SPI/Quad SPI bridges supporting up to 30 Mbit/s clock rates. FTDI offers drivers for ARMv7 and ARMv8 as a part of their libft4222 package, so there's a good chance those bridges will work with a Pi.

Digikey sells FT4222H modules for $18 a piece.

added 70 characters in body
Source Link
Dmitry Grigoryev
  • 28.2k
  • 6
  • 54
  • 145

There is a big difference between 6..9 MHz clock speed (which is possible on a Pi) and 6..9 Mbit/s data rate which you won't achieve if you can only read 2-3 bytes at a time. The overhead of IO library and drivers will limit you to something like 20'000tens of thousands SPI transfers per second.

If you find an ADC that can be configured to buffer samples and them stream them over SPI in large chunks, it may just work with a direct SPI connection. However, ADCs which require you to read out the last sample before they can produce a new one will require external buffering.

Look at FT42XX products: those are USB to SPI/Quad SPI bridges supporting up to 30 Mbit/s clock rates. FTDI offers drivers for ARMv7 and ARMv8 as a part of their libft4222 package, so there's a good chance those bridges will work with a Pi.

Digikey sells FT4222H modules for $18 a piece.

There is a big difference between 6..9 MHz clock speed (which is possible on a Pi) and 6..9 Mbit/s data rate which you won't achieve if you can only read 2-3 bytes at a time. The overhead of IO library and drivers will limit you to something like 20'000 SPI transfers per second.

If you find an ADC that can be configured to buffer samples and them stream them over SPI in large chunks, it may just work with a direct SPI connection. However, ADCs which require you to read out the last sample before they can produce a new one will require external buffering.

Look at FT42XX products: those are USB to SPI/Quad SPI bridges supporting up to 30 Mbit/s clock rates. FTDI offers drivers for ARMv7 and ARMv8 as a part of their libft4222 package, so there's a good chance those bridges will work with a Pi.

Digikey sells FT4222H modules for $18 a piece.

There is a big difference between 6..9 MHz clock speed (which is possible on a Pi) and 6..9 Mbit/s data rate which you won't achieve if you can only read 2-3 bytes at a time. The overhead of IO library and drivers will limit you to tens of thousands SPI transfers per second.

If you find an ADC that can be configured to buffer samples and them stream them over SPI in large chunks, it may just work with a direct SPI connection. However, ADCs which require you to read out the last sample before they can produce a new one will require external buffering.

Look at FT42XX products: those are USB to SPI/Quad SPI bridges supporting up to 30 Mbit/s clock rates. FTDI offers drivers for ARMv7 and ARMv8 as a part of their libft4222 package, so there's a good chance those bridges will work with a Pi.

Digikey sells FT4222H modules for $18 a piece.

added 581 characters in body
Source Link
Dmitry Grigoryev
  • 28.2k
  • 6
  • 54
  • 145

There is a big difference between 6..9 MHz clock speed (which is possible on a Pi) and 6..9 Mbit/s data rate which you won't achieve if you can only read 2-3 bytes at a time. The overhead of IO library and drivers will limit you to something like 20'000 SPI transfers per second.

If you find an ADC that can be configured to buffer samples and them stream them over SPI in large chunks, it may just work with a direct SPI connection. However, ADCs which require you to read out the last sample before they can produce a new one will require external buffering.

Look at FT42XX products: those are USB to SPI/Quad SPI bridges supporting up to 30 Mbit/s clock rates. FTDI offers drivers for ARMv7 and ARMv8 as a part of their libft4222 package, so there's a good chance those bridges will work with a Pi.

Digikey sells FT4222H modules for $18 a piece.

Look at FT42XX products: those are USB to SPI/Quad SPI bridges supporting up to 30 Mbit/s clock rates. FTDI offers drivers for ARMv7 and ARMv8 as a part of their libft4222 package, so there's a good chance those bridges will work with a Pi.

Digikey sells FT4222H modules for $18 a piece.

There is a big difference between 6..9 MHz clock speed (which is possible on a Pi) and 6..9 Mbit/s data rate which you won't achieve if you can only read 2-3 bytes at a time. The overhead of IO library and drivers will limit you to something like 20'000 SPI transfers per second.

If you find an ADC that can be configured to buffer samples and them stream them over SPI in large chunks, it may just work with a direct SPI connection. However, ADCs which require you to read out the last sample before they can produce a new one will require external buffering.

Look at FT42XX products: those are USB to SPI/Quad SPI bridges supporting up to 30 Mbit/s clock rates. FTDI offers drivers for ARMv7 and ARMv8 as a part of their libft4222 package, so there's a good chance those bridges will work with a Pi.

Digikey sells FT4222H modules for $18 a piece.

added 50 characters in body
Source Link
Dmitry Grigoryev
  • 28.2k
  • 6
  • 54
  • 145
Loading
Source Link
Dmitry Grigoryev
  • 28.2k
  • 6
  • 54
  • 145
Loading