It's really a nightmare to update to STM32Cube_FW_F4_V1.15.0

diverger · ‎2017-03-14

Posted on March 15, 2017 at 06:23

After upgrade to STM32Cube_FW_F4_V1.15.0, my projects broken. The SD card won't work and the Lwip won't work, wonder if ST has done some 'test' before release their lib.!!!!!!!!

Nesrine M_O · ‎2017-03-15

Posted on March 15, 2017 at 09:44

Hi

Zhang.Vincent

,

Do you mean that LWIP and FATFS applications under the STM32F4 firmwrae package are not working for you?

What are you using as STM32F4 product?

What kind of issue you are facing (compilation errors...)

Which example did you looked to?

Could you please provide more explanation on your case, so that it will be easier to understand the issue?

-Nesrine-

diverger · ‎2017-03-15

Posted on March 16, 2017 at 02:50

I finally make it compiled now. The main problem comes from SD card relevant files, such as bsp_driver_sd.c, it seems some defines changed, such as structure defines, function prototypes...

The second problem comes from Lwip, the Lwip is updated from 1.4.1 to 2.0, the guard defines in 'slipif.c' disappeared, so the compiler complains that 'sio_open, sio_read/sio_tryread and sio_send' not defined. Simply delete the file from the project can solve this problem, but every time you regenerates the project, it will be added again!!!!

The third problem exist not only in V1.15.0, but also in several previous versions. I use FreeRTOS, and I have some interrupts not handled by FreeRTOS, and have a higher priority than the RTOS kernel, such as the timebase source used by HAL. But every time I reopen the .ioc file, these NVIC irqs are marked red, and prompt me: 'Preemption priority of interrupts should be >= 5......', is it designed to behave like this?

My tool chain is ARM-MDK V5. MCU is STM32F429IGx.

--------------------------------------------------------

Update:

Today, I find the SWD can't print message to MDK's 'Debug Viewer', anyone can confirm this?

Bino · ‎2017-03-16

Posted on March 16, 2017 at 11:38

Hello,

Let me answer concerning the 'second problem':

LwIP stack files not generated but copied by CubeMX are overwritten at each CubeMX generation.

There is a workaround to avoid this: rename or remove slipif.c file in your project and also in the CubeMX repository I mean in the folder defined in CubeMX menu>Help>Updater Settings: Repository Folder and here in the right FW package folder like STM32Cube_FW_F4_V1.14.0\Middlewares\Third_Party\LwIP\src\netif\slipif.c.

By this way you will keep your update in LwIP stack at each generation.

Of course in case of update on FW package you will loose this update...

If it can helps waiting for a better solution concerning this removal of LWIP_HAVE_SLIPIF flag.

Bino · ‎2017-03-16

Posted on March 16, 2017 at 16:04

I would also add to patch the XML Config file located in C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeMX\db\mcu\config\LWIP-STM32F7xx_Configs.xml by commenting the line adding in your project the slipif.c file:

Then your project will not include the

slipif.c

file.

Think to reload the project to take into account the update in XML config file.

diverger · ‎2017-03-16

Posted on March 17, 2017 at 03:42

About the second problem, I find another solution. In MDK you can set compiling options for individual file. So just uncheck the 'include in Target Build' option, will prevent MDK from compiling it, and CubeMX will retain the settings.

Nickname14202_O · ‎2017-05-11

Posted on May 11, 2017 at 16:30

Hello,

Concerning the third point, it should be corrected in the last version of STM32CubeMX:

The third problem exist not only in V1.15.0, but also in several previous versions. I use FreeRTOS, and I have some interrupts not handled by FreeRTOS, and have a higher priority than the RTOS kernel, such as the timebase source used by HAL. But every time I reopen the .ioc file, these NVIC irqs are marked red, and prompt me: 'Preemption priority of interrupts should be >= 5......', is it designed to behave like this?

Thank you for reporting it.

Nickname14202_O · ‎2017-05-11

Posted on May 11, 2017 at 16:31

That is in version 4.21.