# MPU: EWARM warnings **URL:** \ **Category:** Kernel\ **Created:** [June 18, 2018, 1:46pm UTC](https://forums.freertos.org/t/mpu-ewarm-warnings/7286 "2018-06-18T13:46:03Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\ **Post date:** [June 18, 2018, 1:46pm UTC](https://forums.freertos.org/t/mpu-ewarm-warnings/7286/1 "2018-06-18T13:46:03Z")
**[rahmanih](https://sourceforge.net/u/rahmanih/)** wrote on [Monday, June 18, 2018](https://sourceforge.net/p/freertos/discussion/382005/thread/d83a2060/#0d8b): Hi, using the MPU feature within the FreeRTOS v10, I’m getting the following warnings from IAR/EWARM IDE: ```auto Warning[Be006]: possible conflict for segment/section "privileged_data": FreeRTOS\Source\timers.c 137 variable "xTimerQueue" (declared at line 137 of "FreeRTOS\Source\timers.c") is an initialized variable (2 more variables like this) variable "xActiveTimerList1" (declared at line 131 of "FreeRTOS\Source\timers.c") is a zero-initialized variable (3 more variables like this) tasks.c Warning[Be006]: possible conflict for segment/section "privileged_data": FreeRTOS\Source\tasks.c 348 variable "pxCurrentTCB" (declared at line 348 of "FreeRTOS\Source\tasks.c") is an initialized variable (14 more variables like this) variable "pxReadyTasksLists" (declared at line 351 of "FreeRTOS\Source\tasks.c") is a zero-initialized variable (7 more variables like this) ``` any Idea how to fix them? regards Haithem. ---
**Author:** ![rtel](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/rtel/32/31_2.png) [@rtel](https://forums.freertos.org/u/rtel)\ **Post date:** [June 18, 2018, 4:22pm UTC](https://forums.freertos.org/t/mpu-ewarm-warnings/7286/2 "2018-06-18T16:22:15Z")
**[rtel](https://sourceforge.net/u/rtel/)** wrote on [Monday, June 18, 2018](https://sourceforge.net/p/freertos/discussion/382005/thread/d83a2060/#0d8b/7ff3): > any Idea how to fix them? I will have to take a look and report back. ---
**Author:** ![rtel](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/rtel/32/31_2.png) [@rtel](https://forums.freertos.org/u/rtel)\ **Post date:** [June 19, 2018, 1:13am UTC](https://forums.freertos.org/t/mpu-ewarm-warnings/7286/3 "2018-06-19T01:13:21Z")
**[rtel](https://sourceforge.net/u/rtel/)** wrote on [Tuesday, June 19, 2018](https://sourceforge.net/p/freertos/discussion/382005/thread/d83a2060/#0d8b/8777): Ok - just coming to test this and can’t see an official IAR port for FreeRTOS MPU - is this a project you created yourself? ---
**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\ **Post date:** [June 19, 2018, 9:00am UTC](https://forums.freertos.org/t/mpu-ewarm-warnings/7286/4 "2018-06-19T09:00:44Z")
**[rahmanih](https://sourceforge.net/u/rahmanih/)** wrote on [Tuesday, June 19, 2018](https://sourceforge.net/p/freertos/discussion/382005/thread/d83a2060/#50a1): well! actually this is officially released in the [STM32 Cube FW F4](https://my.st.com/content/my_st_com/en/products/embedded-software/mcus-embedded-software/stm32-embedded-software/stm32cube-mcu-packages/stm32cubef4.license=1529396371175.html#getsoftware-scroll), but based on FreeRTOS 9, but when integrating it with FreeRTOS 10, I’m getting the abovementioned warnings. ---
**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\ **Post date:** [June 19, 2018, 9:00am UTC](https://forums.freertos.org/t/mpu-ewarm-warnings/7286/5 "2018-06-19T09:00:52Z")
**[rahmanih](https://sourceforge.net/u/rahmanih/)** wrote on [Tuesday, June 19, 2018](https://sourceforge.net/p/freertos/discussion/382005/thread/d83a2060/#ded0): Could you please have a look at it? thanks in advance. ---
**Author:** ![richard-damon](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/richard-damon/32/38_2.png) [@richard-damon](https://forums.freertos.org/u/richard-damon)\ **Post date:** [June 20, 2018, 12:18am UTC](https://forums.freertos.org/t/mpu-ewarm-warnings/7286/6 "2018-06-20T00:18:00Z")
**[richard\_damon](https://sourceforge.net/u/richard_damon/)** wrote on [Wednesday, June 20, 2018](https://sourceforge.net/p/freertos/discussion/382005/thread/d83a2060/#59f4): STM32 Cube is NOT the official release, but a modified version by ST Micro. You might check if their version 9 was ‘stock’ or if it was modified. ---
**Author:** ![rtel](https://d3iykfbgfh8zhg.cloudfront.net/user_avatar/forums.freertos.org/rtel/32/31_2.png) [@rtel](https://forums.freertos.org/u/rtel)\ **Post date:** [June 20, 2018, 12:23am UTC](https://forums.freertos.org/t/mpu-ewarm-warnings/7286/7 "2018-06-20T00:23:10Z")
**[rtel](https://sourceforge.net/u/rtel/)** wrote on [Wednesday, June 20, 2018](https://sourceforge.net/p/freertos/discussion/382005/thread/d83a2060/#59f4/d464): Turns out there is a FreeRTOS MPU port for IAR in the official SVN repository, but there doesn’t seem to be a demo project for it, hence I missed it when I looked the first time, and I don’t recall how it was tested. ---
**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\ **Post date:** [June 20, 2018, 2:32pm UTC](https://forums.freertos.org/t/mpu-ewarm-warnings/7286/8 "2018-06-20T14:32:27Z")
**[rahmanih](https://sourceforge.net/u/rahmanih/)** wrote on [Wednesday, June 20, 2018](https://sourceforge.net/p/freertos/discussion/382005/thread/d83a2060/#59f4/4e6d): O.K., but what is strange is that the warnings are thrown from the FreeRTOS official source code not from a modified part.(BTW the FreeRTOS 9 doesn’t have any warning in the Cube FW) regards haithem. ---
**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\ **Post date:** [September 10, 2019, 8:52pm UTC](https://forums.freertos.org/t/mpu-ewarm-warnings/7286/9 "2019-09-10T20:52:47Z")
**[kg7hf](https://sourceforge.net/u/kg7hf/)** wrote on [Tuesday, September 10, 2019](https://sourceforge.net/p/freertos/discussion/382005/thread/d83a2060/#c618): Was there any resolution to this? I just leaped to 10.2 from 9.0 and have the same warnings. ---
**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\ **Post date:** [September 10, 2019, 8:52pm UTC](https://forums.freertos.org/t/mpu-ewarm-warnings/7286/10 "2019-09-10T20:52:59Z")
**[kg7hf](https://sourceforge.net/u/kg7hf/)** wrote on [Tuesday, September 10, 2019](https://sourceforge.net/p/freertos/discussion/382005/thread/d83a2060/#d49d): Was there any resolution to this? I just leaped to 10.2 from 9.0 and have the same warnings. ---
**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\ **Post date:** [September 10, 2019, 9:04pm UTC](https://forums.freertos.org/t/mpu-ewarm-warnings/7286/11 "2019-09-10T21:04:47Z")
**[gaurav-aws](https://sourceforge.net/u/gaurav-aws/)** wrote on [Tuesday, September 10, 2019](https://sourceforge.net/p/freertos/discussion/382005/thread/d83a2060/#5edf): We have examined the generated code and those warnings are harmless. You can supperss them by following these steps: - Right click on the project and click options. - Go to C/C++ Compiler --\> Extra Options. - Add --diag\_suppress Be006 Thanks. ---
**Author:** ![system](https://d2v6vdsk2p900z.cloudfront.net/original/1X/7fc8fdb729c645aab5b20282bbe34e57cb407be6.jpeg) [@system](https://forums.freertos.org/u/system)\ **Post date:** [September 10, 2019, 9:30pm UTC](https://forums.freertos.org/t/mpu-ewarm-warnings/7286/12 "2019-09-10T21:30:07Z")
**[kg7hf](https://sourceforge.net/u/kg7hf/)** wrote on [Tuesday, September 10, 2019](https://sourceforge.net/p/freertos/discussion/382005/thread/d83a2060/#6d72): Thanks Gaurav, I too have analyzed the code and yes, I believe they are caused by the linker thinging they are placed outside of the data segemtn or the .bss. and having to initialize them to values. If you remove the initialization (not recomended), the warning will not be thrown.