cancel
Showing results for 
Search instead for 
Did you mean: 

STM32L432 nucleo I2C bootloader communication issues

MBeli.1
Associate III

Hello,

I'm trying to test FW update over I2C using RPI as host and STM32L432 nucleo board as slave on port I2C1 which according AN2606 (table 152) should be available. I've connected 4.7k pullups on PA6 + PA7 pins and perform NRST to 0 and BOOT0 to 1 and remove NRST pin. In this setup I perform i2cdetect on RPI and I'm getting i2c transfer timeouts for all addresses. When reset STM32 32 board i2cdetect command on RPI return empty table. Is that setup feasible or am I doing something wrong? Thanks.

 

4 REPLIES 4
TDK
Super User

PA6/PA7 are not supported pins for the I2C bootloader.

PB6/PB7 are supported. Perhaps you misread the table.

TDK_0-1764599302901.png

 

If you feel a post has answered your question, please click "Accept as Solution".
MBeli.1
Associate III

Sorry it was a type I have it connected to PB6 and PB7 as stated in AN2606.

Sco
ST Employee

Have you checked whether PB6 and PB7 are boot pins for I2C?

And to confirm the good/correct connection for the signals.

MBeli.1
Associate III

Connection is correct and accorrding table which TDK posted it should be available for fw upload. I've connected them to RPI GPIO2 and GPIO3 (SDA, SCL) and added 4.7k ohm pullup for both lines to 3V3. When CPU is not in bootloader mode I can see SCL and data are flowing but when enter to bootloader mode by put boot0 pin (soldered on SB12) to 3V3 and then put nRST to GND and back to 3V3 I cannot see any clocks when run i2cdetect on RPI.