2024-07-25 07:22 AM - last edited on 2024-08-05 06:31 AM by Amel NASRI
Hello,
For those who saw my post about SD card and FileX, I am still on that subject and encountered an issue about SPI with the STM32WBA52CG MCU.
A Cube project is available attached to this post as a simplified example of SPI communication.
While using SPI1, the clock signal outside communications is at 1.2V instead of th precedent state 0 (0V) or 1 (3.3.V)
as shown in those oscilloscope screenshots:
While using SPI3 as I thought it might not show that behavior, another strange behavior appeared, this time on the MOSI signal with a constant voltage when outside com. at 1.9V:
I suspect this behavior to be at least partly responsible for my failure at communicating with an SD Card. (btw if you have some hints on that part I would be grateful :) )
Is this related and is the cause of my lack of com. in my SD card/FileX project, does it have an impact on communication, and is it simply a bug or am I responsible for something?
I tried this with two NUCLEO-STM32WBA52CG dev cards with the same results so far.
Thanks in advance for your time and help.
(Those Labels are clearly not helping as this is unrelated to any of those proposed...)
2024-07-31 02:57 AM - edited 2024-08-22 11:05 AM
Hello @Curious_Intern ,
Could you please enable FileX usnig CubeMX in your application ? I have reviewed your attached project and noticed that the FileX files are not visible.
Also, I would recommend using pull-up resistors for SPI signals (SCK, MISO, MOSI). This can help ensure proper signal integrity and reliable operation.
Best Regards,