-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chip select and SPI clock not working correctly #49
Comments
I have tested it with another FTDI chip that I just bought as well as via a linux VM. All results in the same behaviour. |
I have found a FT2232HL which should definitively be a genuine part and it shows nearly exactly the same behaviour as above. Just with fixed 25kHz output clock instead of 77kHz, |
https://www.eevblog.com/forum/microcontrollers/ftdi-gate-2-0/msg859741/#msg859741 |
Sadly not so much. The signals I get look fine but the number of clock cycles is odd. I am not sure whether some at the beginning or end are missing or whether more clocks are output than should be. |
Any updates? |
I also measure the clock frequency at 80KHz, even if the output says 20kHz
|
Nothing from my side. I sadly never got it working... |
Hello,
I got an issue with communicating with a CSR8645 using a FTDI232R (A94FFLDD) and BlueSuite 2.5.8. I can't get any proper communication and the following error is always returned:
"20:49:41.151676: err:basics.cpp:481:spifns_sequence_read: Unable to start read (invalid control data)"
Because of this I decided to measure the SPI interface using an oscilloscope which resulted in the following signals:
The chip select is low most of the time and only high for a short pulse in the beginning of an SPI frame. Also the SPI frequency is always ~77kHz independed from which value I set via command line.
Do you know what might cause this issue and how I can solve this?
Thank you very much in advance!
Kind regards,
kcl_93
The text was updated successfully, but these errors were encountered: