cancel
Showing results for 
Search instead for 
Did you mean: 

STM32C011J4M - issue with pin overlapp

engeneering_sockpuppet
Associate II

Hello to whom this might concern,

I was recently experimenting with STM32C011J4M for a small hobby project (I am trying to fit into a about coin size) and want to comunnicate with other chip over I2C. Due the size of the package I cannot use debugging to find core of the issue, so I used multimeter and legs 4 to 7 as signal outputs. 


I let CubeMx to generate signal configuration and try to use PA8 as output signal (overlaping with PA11[PA9]). The resulting behavior is that the physical leg 4 is stuck on 1.2V and output is not detectable. If I leave PA11 set as analog-nopull, but remove PA11 from 'HAL_SYSCFG_SetPinBinding' the output becomes readable.

 

From rading on the other pins, I can see, that the communication doesn't work. The I2C is also on overlaping pins (default generation put the pins on PC14[leg 1] and PB6[leg8], which also overlaps with programming connections). I try to communicate with lp5817 and am wondering, if I should also remove pins PB7, PA14 and PC15 form 'HAL_SYSCFG_SetPinBinding' for communication to start working, or if I should look for the mistake somewhere else?

Thank you for the response in advance and best regards,

Martin

1 ACCEPTED SOLUTION

Accepted Solutions
drakeshawn
Associate II

Fix CubeMX by removing all the pin overlaps and using only valid STM32C011J4M I2C pins, then regenerate code don’t manually edit SYSCFG.

View solution in original post

3 REPLIES 3
drakeshawn
Associate II

Fix CubeMX by removing all the pin overlaps and using only valid STM32C011J4M I2C pins, then regenerate code don’t manually edit SYSCFG.

Thanks for the response, but I am unsure, where in the cubeMX do I do that. I attached ioc file, which generated me the non-working code. I touched only parts, I'll need to use, but this led to non-working behaviour described above.

In the end I needed to change gpio.c, for all to work.