Profile

|

vanmierlo

Profile Data

Screen Name: vanmierlo

Screen Name*

Title

First Name

Address:

Last Name

URL (i.e. Company, Github, LinkedIn)

Email

LinkedIn account

Company

Phone number

Country

Bio

Indicates required field*

My Activities
Following

Member	Action	Date
vanmierlo	Replied to How to create a empty c project in ssv5? File -> New -> Project... -> Silicon Labs MCU Project -> Empty Program will give you a decent empty project. Beware that you must set the compiler settings yourself (defines, include dirs, etc.) Show more	41 days ago
vanmierlo	Updated Cannot post when I use a certain keyword in the text on General Interest Forum Hi, When I try to post a forum entry with the word A S S E R T (without the spaces obviously) in it, even when it is inside a Code Block, the Ask or Answer button just does not respond. Can this please get fixed? Maarten Show more	41 days ago
vanmierlo	Posted Cannot post when I use a certain keyword in the text on General Interest Forum Hi, When I try to post a forum entry with the word A S S E R T in it, even when it is inside a Code Block, the Ask or Answer button just does not respond. Can this please get fixed? Maarten Show more	41 days ago
vanmierlo	Posted How to set the TAB width in Simplicity Studio 5? on Simplicity Studio Forum Hello, When I open my C files in Simplicity Studio 5 I see a TAB width of 2, even though the TAB setting is 4. What am I doing wrong? Preferences->General->Editors->Text Editors->Displayed tab width: 4 Maarten Show more	41 days ago
vanmierlo	Updated to Bug when using custom memory range with default linker script @jpitt This most certainly is a bug! And that it is not resolved after 5 years is a disgrace! The ASSERT compares LENGTH(FLASH) with the end address of required flash. Thus it ASSUMES that ORIGIN(FLASH) equals zero, which often needs not be the case. A correct ASSERT would be: Now the question is: Where should we fix this if SiLabs is not capable of fixing this for us? I believe for SS5 it is enough to fix: ...\SiliconLabs\SimplicityStudio\v5\configuration\org.eclipse.osgi\1181\0\.cp\linker_scripts\linker_script_efm32_v4.ld ...\SiliconLabs\SimplicityStudio\v5\developer\sdks\gecko_sdk_suite\v3.0\.studio\linkerScripts\linker_script_efm32_v4.ld But all .ld files in platform/Device/SiliconLabs are affected as well. ...\SiliconLabs\SimplicityStudio\v5\developer\sdks\gecko_sdk_suite\vx.x\platform\Device\SiliconLabs\<EFx32xx>\Source\GCC\*.ld Maarten Show more	41 days ago
vanmierlo	Replied to Bug when using custom memory range with default linker script And that it is not resolved after 5 years is a disgrace! The ASSERT compares LENGTH(FLASH) with the end address of required flash. Thus it ASSUMES that ORIGIN(FLASH) equals zero, which often needs not be the case. A correct ASSERT would be: Now the question is: Where should we fix this if SiLabs is not capable of fixing this for us? I believe for SS5 it is enough to fix: ...\SiliconLabs\SimplicityStudio\v5\configuration\org.eclipse.osgi\1181\0\.cp\linker_scripts\linker_script_efm32_v4.ld ...\SiliconLabs\SimplicityStudio\v5\developer\sdks\gecko_sdk_suite\v3.0\.studio\linkerScripts\linker_script_efm32_v4.ld But all .ld files in platform/Device/SiliconLabs are affected as well. ...\SiliconLabs\SimplicityStudio\v5\developer\sdks\gecko_sdk_suite\vx.x\platform\Device\SiliconLabs\<EFx32xx>\Source\GCC\*.ld Maarten Show more	41 days ago
vanmierlo	Updated to Bug when using custom memory range with default linker script @jpitt This most certainly is a bug! And that it is not resolved after 5 years is a disgrace! The ASSERT compares LENGTH(FLASH) with the end address of required flash. Thus it ASSUMES that ORIGIN(FLASH) equals zero, which often needs not be the case. A correct ASSERT would be: `/* Check if FLASH usage exceeds FLASH size /` / Check if FLASH usage exceeds FLASH size / Now the question is: Where should we fix this if SiLabs is not capable of fixing this for us? I believe for SS5 it is enough to fix: ...\SiliconLabs\SimplicityStudio\v5\configuration\org.eclipse.osgi\1181\0\.cp\linker_scripts\linker_script_efm32_v4.ld ...\SiliconLabs\SimplicityStudio\v5\developer\sdks\gecko_sdk_suite\v3.0\.studio\linkerScripts\linker_script_efm32_v4.ld But all .ld files in platform/Device/SiliconLabs are affected as well. ...\SiliconLabs\SimplicityStudio\v5\developer\sdks\gecko_sdk_suite\vx.x\platform\Device\SiliconLabs\<EFx32xx>\Source\GCC\.ld Maarten Show more	41 days ago
vanmierlo	Updated to Bug when using custom memory range with default linker script @jpitt This most certainly is a bug! And that it is not resolved after 5 years is a disgrace! The ASSERT compares LENGTH(FLASH) with the end address of required flash. Thus it ASSUMES that ORIGIN(FLASH) equals zero, which often needs not be the case. A correct ASSERT would be: `/* Check if FLASH usage exceeds FLASH size / ASSERTION( (ORIGIN(FLASH) + LENGTH(FLASH)) >= (__etext + SIZEOF(.data)), "FLASH memory overflowed !")` Now the question is: Where should we fix this if SiLabs is not capable of fixing this for us? I believe for SS5 it is enough to fix: ...\SiliconLabs\SimplicityStudio\v5\configuration\org.eclipse.osgi\1181\0\.cp\linker_scripts\linker_script_efm32_v4.ld ...\SiliconLabs\SimplicityStudio\v5\developer\sdks\gecko_sdk_suite\v3.0\.studio\linkerScripts\linker_script_efm32_v4.ld But all .ld files in platform/Device/SiliconLabs are affected as well. ...\SiliconLabs\SimplicityStudio\v5\developer\sdks\gecko_sdk_suite\vx.x\platform\Device\SiliconLabs\<EFx32xx>\Source\GCC\.ld Maarten Show more	41 days ago
vanmierlo	Updated to Bug when using custom memory range with default linker script @jpitt This most certainly is a bug! And that it is not resolved after 5 years is a disgrace! The ASSERT compares LENGTH(FLASH) with the end address of required flash. Thus it ASSUMES that ORIGIN(FLASH) equals zero, which often needs not be the case. A correct ASSERT would be: /* Check if FLASH usage exceeds FLASH size / Now the question is: Where should we fix this if SiLabs is not capable of fixing this for us? I believe for SS5 it is enough to fix: ...\SiliconLabs\SimplicityStudio\v5\configuration\org.eclipse.osgi\1181\0\.cp\linker_scripts\linker_script_efm32_v4.ld ...\SiliconLabs\SimplicityStudio\v5\developer\sdks\gecko_sdk_suite\v3.0\.studio\linkerScripts\linker_script_efm32_v4.ld But all .ld files in platform/Device/SiliconLabs are affected as well. ...\SiliconLabs\SimplicityStudio\v5\developer\sdks\gecko_sdk_suite\vx.x\platform\Device\SiliconLabs\<EFx32xx>\Source\GCC\.ld Maarten Show more	41 days ago
vanmierlo	Updated to Bug when using custom memory range with default linker script @jpitt This most certainly is a bug! And that it is not resolved after 5 years is a disgrace! The ASSERT compares LENGTH(FLASH) with the end address of required flash. Thus it ASSUMES that ORIGIN(FLASH) equals zero, which often needs not be the case. A correct ASSERT would be: `/* Check if FLASH usage exceeds FLASH size / / Check if FLASH usage exceeds FLASH size / ( (ORIGIN(FLASH) + LENGTH(FLASH)) >= (__etext + SIZEOF(.data)), "FLASH memory overflowed !")` Now the question is: Where should we fix this if SiLabs is not capable of fixing this for us? I believe for SS5 it is enough to fix: ...\SiliconLabs\SimplicityStudio\v5\configuration\org.eclipse.osgi\1181\0\.cp\linker_scripts\linker_script_efm32_v4.ld ...\SiliconLabs\SimplicityStudio\v5\developer\sdks\gecko_sdk_suite\v3.0\.studio\linkerScripts\linker_script_efm32_v4.ld But all .ld files in platform/Device/SiliconLabs are affected as well. ...\SiliconLabs\SimplicityStudio\v5\developer\sdks\gecko_sdk_suite\vx.x\platform\Device\SiliconLabs\<EFx32xx>\Source\GCC\.ld Maarten Show more	41 days ago

Level 7

Level 2

Pathfinder

Following 1

erikm

Followers 4