Hi There, Looking at current posts it seems like I have been asleep for a very long time.....
I have a CSR8645 on a HY-BTM875 carrier. I am trying to connect it to an FTD232H board.
I have read through most of the relevant posts on this forum and scraped up bits of info
from wherever, but none of it has brought me a result.
The only signal that I cannot correctly identify is SPI_PCM# on the HY-BTM875 carrier.
It's almost as if they haven't brought it out from the CSR8645 pad J4.
The unlabelled connections on the back of the carrier board that I have traced are:
3.3V, GND, MISO, MOSI, CLK, CSB and RTS...
I cannot make sense of how RTS got there. Its not related to the PCM interface.
I have spent days trying to get this connection to work, but with no luck.
Any advice/info you can share would be appreciated.
Paul.
I have a CSR8645 on a HY-BTM875 carrier. I am trying to connect it to an FTD232H board.
I have read through most of the relevant posts on this forum and scraped up bits of info
from wherever, but none of it has brought me a result.
The only signal that I cannot correctly identify is SPI_PCM# on the HY-BTM875 carrier.
It's almost as if they haven't brought it out from the CSR8645 pad J4.
The unlabelled connections on the back of the carrier board that I have traced are:
3.3V, GND, MISO, MOSI, CLK, CSB and RTS...
I cannot make sense of how RTS got there. Its not related to the PCM interface.
I have spent days trying to get this connection to work, but with no luck.
Any advice/info you can share would be appreciated.
Paul.
Attachments
IIUC you want to program your module. Maybe you could try asking for help this user https://www.diyaudio.com/community/...ware-and-tons-of-csr-info.349336/post-6546902
Per the HY-BTM875 datasheet, pin 13 is SPI_CSB (Chip select for SPI,active low). You seem to have it labelled already on the 7-pin header.
https://www.hyxkiot.com/upload/202112/17/202112171903506413.pdf
https://www.hyxkiot.com/upload/202112/17/202112171903506413.pdf
Hi there, Thanks for your reply.
So are you saying that SPI_PCM in the CSR8645 product sheet and SPI_CSB in the HY-BTM875 datasheet are one and the same?
So are you saying that SPI_PCM in the CSR8645 product sheet and SPI_CSB in the HY-BTM875 datasheet are one and the same?
No, but the board might already have SPI_PCM pulled high even though there isn't a breakout for it?
I would ground SPI_CSB and try communicating with it. Worth trying at least.
I would ground SPI_CSB and try communicating with it. Worth trying at least.
Hm, I wonder what SPI bus they mean in that datasheet. Looking at the CSR8645 datasheet https://www.laskakit.cz/user/related_files/bluetooth__csr8645_.pdf I see fast QSPI for some flash memory (i.e. with audio tracks) alternated with PIO10-13 and debug/config SPI alternated with PIO2-5 and I2S. This SPI can be alternated with I2S using the pin SPI_PCM. It would make sense to me to switch PIO2-5 to SPI with pulling the SPI_PCM to high, configure the module with the software provided by CSR, and release to be pull down by its internal pulldown to switch back to I2S.
But the Hyxkiot module datasheet shows to offer separate SPI pins AND (almost) all the PIO/I2S ports separately. By almost I mean the module UART pins correspond to the missing PIOs. But that is not the case for both the debug SPI and the memory QSPI.
But the Hyxkiot module datasheet shows to offer separate SPI pins AND (almost) all the PIO/I2S ports separately. By almost I mean the module UART pins correspond to the missing PIOs. But that is not the case for both the debug SPI and the memory QSPI.
Hi Mr. Hofman, Many thanks for the thought that you have put into this. I have put this aspect of my project to one side for the moment.
I have made myself tired from trying to resolve this issue. I should have done a little more research before buying items that the electronics community
have not proven to work together. I will complete another part of my project and then return to this with your observations foremost in my mind..
Once again, thanks.
I have made myself tired from trying to resolve this issue. I should have done a little more research before buying items that the electronics community
have not proven to work together. I will complete another part of my project and then return to this with your observations foremost in my mind..
Once again, thanks.