[SOLVED] Upgrade Issue w/ STM32F103xB + IAR from 3.86d to 3.88c

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] Upgrade Issue w/ STM32F103xB + IAR from 3.86d to 3.88c

    We have been successfully running embOS on multiple STM32F103 processors but recently have some pains on a single processor when upgrading to the newest versions (3.88c).

    The processor in question is a STM32F103RBH7 which is set in IAR 6.60.2.5507 as the family STM32F103xB and memory model STM32F10X_MD. We are using the embOS CMSIS setup files with the IAR "Use CMSIS" option. The only modification is changing the include for device.h to stm32f10x.h.

    This setup was working wonderfully on our boards with embOS version 3.86d but we decided to upgrade to get the new reset configurations for timers/counters.

    On our two other STM32 variants the new OS went in without any problems.

    On the STM32F103RBH7 with the same files it immediately fails during the assembly startup code -- it never gets to main(). If we change the RTOS.h file to include OS_TASK_EVENT (so that it go back to OS_TASK_EVENT OS_U8) we can get through to main but as soon as we try call OS_CreateTimer_EX() the code hangs within the library.

    Is there any new configurations we need to consider for this part? I looked through the BoardSupport for the STM32 but all the files are the same other than the Init and the differences between the CMSIS implementation and the STM32 specific are fairly major so I can't identify anything obvious.

    Thanks in advance for your help

    Bill Frank
    MSA

    The post was edited 1 time, last by bill.frank ().

  • Hello,

    Is there any new configurations we need to consider for this part?

    No, the only major difference between this device and other STM32F103 devices is the flash memory size.
    Could you please check if the linker file is set accordingly?

    Could you please send us your project so that we can try to reproduce this issue?

    Best regards,
    Til
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Thanks. As soon as we looked at our ICF files we saw a problem. We had changed processors and we have custom memory ranges so we can have both application and bootloader. We updated the ROM when switching to the smaller processor but missed the RAM. Stupid. Thanks.