Mar 27, 2018
12:52 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 27, 2018
12:52 AM
Hi all,
I found a bug in CPU_CTRL_XMC4 App (all versions) about the settings of FLASH wait states for XMC4300:
At first lines the define is incomplete:
#if ((UC_SERIES == XMC48) || (UC_SERIES == XMC47))
#define PMU_FLASH_WS (0x4U)
#elif ((UC_SERIES == XMC45) || (UC_SERIES == XMC44))
#define PMU_FLASH_WS (0x3U)
#else
#define PMU_FLASH_WS (0x2U)
#endif
shoud be:
#if ((UC_SERIES == XMC48) || (UC_SERIES == XMC47) || (UC_SERIES == XMC43))
#define PMU_FLASH_WS (0x4U)
#elif ((UC_SERIES == XMC45) || (UC_SERIES == XMC44))
#define PMU_FLASH_WS (0x3U)
#else
#define PMU_FLASH_WS (0x2U)
#endif
Otherwise any XMC4300 projects will run with only 2WS (as for XMC4100-4200 running at 80Mhz) and this will lead to unpredictable results. The software could run on some devices, and on others would fail.
Regards,
Andrea Taglietti
I found a bug in CPU_CTRL_XMC4 App (all versions) about the settings of FLASH wait states for XMC4300:
At first lines the define is incomplete:
#if ((UC_SERIES == XMC48) || (UC_SERIES == XMC47))
#define PMU_FLASH_WS (0x4U)
#elif ((UC_SERIES == XMC45) || (UC_SERIES == XMC44))
#define PMU_FLASH_WS (0x3U)
#else
#define PMU_FLASH_WS (0x2U)
#endif
shoud be:
#if ((UC_SERIES == XMC48) || (UC_SERIES == XMC47) || (UC_SERIES == XMC43))
#define PMU_FLASH_WS (0x4U)
#elif ((UC_SERIES == XMC45) || (UC_SERIES == XMC44))
#define PMU_FLASH_WS (0x3U)
#else
#define PMU_FLASH_WS (0x2U)
#endif
Otherwise any XMC4300 projects will run with only 2WS (as for XMC4100-4200 running at 80Mhz) and this will lead to unpredictable results. The software could run on some devices, and on others would fail.
Regards,
Andrea Taglietti
- Tags:
- IFX
1 Reply
Apr 10, 2018
03:46 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 10, 2018
03:46 AM
Hi,
Thanks for reporting the issue.
We will fix it in the up coming release.
Regards,
Jesus
Thanks for reporting the issue.
We will fix it in the up coming release.
Regards,
Jesus