Skip to main content
nbobovnikov
nbobovnikov
Associate
March 19, 2016
Question

STM32Cube migration issue

  • March 19, 2016
  • 4 replies
  • 1290 views
Posted on March 19, 2016 at 14:59

Hello!

After regenerating the project created from previous version of the CubeMX, using new version (4.1), some user defined code has been lost in stm32f1xx_it.c file (image with diff is attached)

Best regards,

Nikolay Bobovnikov

!stm32-!cubemx-!bug

    This topic has been closed for replies.

    4 replies

    Nesrine M_O
    Nesrine M_O
    Associate
    March 21, 2016
    Posted on March 21, 2016 at 14:06

    Hi Nikolay Bobovnikov,

    Thank you for your feedback. The issue has been reported internally.

    -Syrine-
    stm32cube-t
    stm32cube-t
    ST Employee
    March 22, 2016
    Posted on March 22, 2016 at 14:58

    Dear user,

    Can you please provide the following additional information:

    Which MCU you  had selected.

    With which MX version  the project was initially done (4.12, 4.13, earlier)

    Which option did you  choose when loading your project in 4.13.1: migrate or continue?

    Can you also attached the .ioc configuration file of your project.

    Thank you

    nbobovnikov
    nbobovnikovAuthor
    Associate
    March 23, 2016
    Posted on March 23, 2016 at 17:44

    Hello,

    I'm sorry, now I'm not sure about exact version of CubeMX, it was probably 4.11 (definetely not earlierd). I use this MCU: STM32F103C8T6. I chose ''migration'' after installing new version of CubeMX. Project file is attached.

    ________________

    Attachments :

    stm32f103c8t6.ioc : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006Htp5&d=%2Fa%2F0X0000000aXI%2F654flIbi8mJxeibAgDIcY2GZ8Y86aIdlwUDvVvKPABA&asPdf=false
    stm32cube-t
    stm32cube-t
    ST Employee
    April 19, 2016
    Posted on April 19, 2016 at 10:52

    Dear user,

    Sorry for the inconvenience.

    The generated file stm32xxx_it.c has been enhanced and may have broken compatibility with previous version. That's why it is recommended to back up your project prior to a migration.

    On top, it looks like a bug has been fixed in latest version: On your selection you can no longer accommodate both I2C1 in I2C mode and Timer3 with TI1FP1 trigger source.

    Best regards
    Terms & ConditionsAccessibility statement