2020-10-16 08:04 AM
Hi everyone,
We have discovered a bug with the STMCubeMX'S Pinout compatible feature between STM32F030C8 and STM32F030CC.
Attaching images for your reference.
Thank you,
PS. We have create some prototypes assuming both MCU are fully pinout compatible but, after HW troubleshooting, we had to use some jumpers/wires to solve this pinout incompatibility issue.
2020-10-19 08:49 AM
Hi @Carlos Andrés Serna Anduquia
Could you please specify the datasheet version you are using.
I checked in the datasheet DS9773 Rev 4, Figure 5 shows LQFP64 64-pin package pinout (top view), for STM32F030RC devices not STM32F030CC. So, i think that the issue (solved) occurs at the datasheet not STM32CubeMX.
Best regards,
Nesrine
2020-10-21 02:42 AM
Hi @Carlos Andrés Serna Anduquia ,
If the answer of Nesrine answered your question, please mark it as "best answer".
Imen
2020-10-21 12:44 PM
Hi @Nesrine.JLASSI,
We are using the same datasheet you have checked (DS9773 Rev 4).
As you can see, figures #6 and #7 show a pinout difference between STM32F030C8 and STM32F030CC.
The confusion/issue is on STMCubeMX, If you compare both MCUs (STM32F030C8 and STM32F030CC) using the STMCubeMX, both are classified as "full pinout compatible", as shown in the image right below:
Issue: There is an incongruence on STMCubeMX, these MCUs (STM32F030C8 and STM32F030CC) should not be classified as "full pinout compatible" based on datasheet (DS9773 Rev 4).
Q. Are we using the STMCubeMX wrong? or Is the issue located on the SMTCubeMX ?
@Imen DAHMEN , the question has not been answered yet :grinning_face_with_sweat: .
2020-10-21 12:50 PM
PS. The system did not allow me to add the images on my last comment, please find attached them in the following link:
2020-10-22 01:36 AM
Hi @Carlos Andrés Serna Anduquia
Thanks for your post. I have raised your feedback internally to be reviewed and treated accordingly to the priority. We will give you an update as soon as possible.
Thanks for your contribution
Best regards,
Nesrine
2020-10-22 07:30 AM
Noted @Nesrine.JLASSI , Thanks for your attention.
Best regards.