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
NUCLEO-F429ZI SPI SCLK unexpected signal #3541
Comments
@mbartling Have you modified resistors of your X-nucleo board as described in the below page ? Also have you made sure that your program doesn't use LED1 ? (as LED1 is defined as D13 and it would conflict with SPI usage) ? Otherwise that could be a reason for unwanted signal behavior. |
I am confused by the wording of the modified resistor page, am I supposed to perform the hardware hack if I am using pin D13? Also, please note that this is an issue with the F429ZI board itself as I cannot get any of the SPI1_SCLKs to initialize using the mbed API. |
I haven't tried it myself, but here is my understanding. From https://developer.mbed.org/teams/ST/code/X_NUCLEO_IDB0XA1/: The X-NUCLEO-IDB04A1 and X-NUCLEO-IDB05A boards are using D3 pins by default. Those boards need to be HW modified (resistors change) to use D13 instead of D3. For NUCLEO_F401RE, the resistor change is not required, because SPI1 pin SPI_SCLK can be routed to D3 as shown here: https://developer.mbed.org/platforms/ST-Nucleo-F401RE/ But in case of NUCLEO_F429ZI, it is mandatory to make this change, because D3 pin does not offer possibility to mux SPI_SCLK to D3. You can see muxing options here: https://developer.mbed.org/platforms/ST-Nucleo-F429ZI/ So in order to have the example working ok with NUCLEO_F429ZI, I think that you need to:
One more question: when you did the SPI trace "Expected behavior Tested on NUCLEO-F401RE". Where have you put the probes ? hope this helps ... |
+cc @apalmieriGH |
cc @avilei |
Hi, Hope that helps, |
I meant there is a HW conflict between Ethernet and the BLE expansion board. And Ethernet support is enabled by default on NUCLEO-F429ZI mbed port. |
@mbartling Hey - have you got any news about this issue ? |
@LMESTM - Took over this bug report from @mbartling. Made the hardware switch by moving zero resistor R4 to R6. Additionally removed the LED initialization from example code https://developer.mbed.org/teams/ST/code/BLE_HeartRate_IDB0XA1/. After both changes were made, the bluetooth interaction now works. Did not have to disable the Ethernet in order to get it to work. |
@mray19027 thanks a lot for the feedback |
Based on the comments from @mray19027 , this is what I've done and it seems to work (no guarantees of course).
"NUCLEO_F429ZI": {
|
Description
Bug
Target
NUCLEO-F429ZI
Toolchain:
GCC_ARM
Toolchain version:
arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 6.2.1 20161205 (release) [ARM/embedded-6-branch revision 243739]
mbed-cli version:
1.0.0
mbed os version
MBED_LIBRARY_VERSION 127
MBED 2
Expected behavior
Tested on NUCLEO-F401RE
Actual behavior
Steps to reproduce
The text was updated successfully, but these errors were encountered: