S32 Design StudioのトピックRe: S32DS Compilation error : fatal error - cygheap base mismatch detected

S32DS Compilation error : fatal error - cygheap base mismatch detected

LuisCasado — Wed, 05 Feb 2020 16:37:44 GMT

Hello,

Customer: AED Engineering

SW: S32DS

Customer is having compilation error for any application created for S32DS, they have verified that they don't have that issue with private laptops but all the company PC's are getting the error. So probably is due to Windows 10 configuration but they don't know how to solve it.

As soon as they try to buid they get:

arm-none-eabi-gcc "@Project_Settings/Startup_Code/startup_S32K142.args" -o "Project_Settings/Startup_Code/startup_S32K142.o" "../Project_Settings/Startup_Code/startup_S32K142.S"

4 [main] sh (20384) C:\NXP\S32DS_ARM_v2.2\S32DS\build_tools\msys32\usr\bin\sh.exe: *** fatal error - cygheap base mismatch detected - 0x612E5408/0x1045408.

This problem is probably due to using incompatible versions of the cygwin DLL.

Search for cygwin1.dll using the Windows Start->Find/Search facility

and delete all but the most recent version. The most recent version *should*

reside in x:\cygwin\bin, where 'x' is the drive on which you have

installed the cygwin distribution. Rebooting is also suggested if you

are unable to find another cygwin DLL.

What can be the cause of error?

Luis

Re: S32DS Compilation error : fatal error - cygheap base mismatch detected

mikedoidge — Fri, 07 Feb 2020 22:20:09 GMT

Hi sito,

It seems this issue has been reported before. Please check the thread: https://community.nxp.com/message/1059626

Hope it helps,

Mike

Re: S32DS Compilation error : fatal error - cygheap base mismatch detected

LuisCasado — Mon, 10 Feb 2020 07:43:01 GMT

Hi Mike Doidge ,

I already shared the community doc you mention and it doesn't fix the issue.

Luis

Re: S32DS Compilation error : fatal error - cygheap base mismatch detected

jiri_kral — Mon, 10 Feb 2020 10:33:47 GMT

Hi Luis,

I was facing this issue in past and to be honest - never find general solution. Sometimes helps regular power OFF and ON (no reboot), sometimes helps run autorebase script:

And sometimes it just disappear next day. I'll ping S32DS dev team with your issue. May be they already figured it out.

Jiri

Re: S32DS Compilation error : fatal error - cygheap base mismatch detected

LuisCasado — Mon, 10 Feb 2020 14:25:23 GMT

Hi Jiri Kral ,

In this case they have tried both and is happening in all the computers at customer.

Luis

Re: S32DS Compilation error : fatal error - cygheap base mismatch detected

winsmen — Thu, 03 Nov 2022 16:44:35 GMT

Posted this on the other thread linked earlier here too.

Managed to get rid of this error by using an externally installed copy of make in place of the one found within the NXP folder.

In the project Properties (File > Properties, or right click on project > Properties) expand C/C++ and go to Environment. Edit (or add) the PATH variable to include the path to the bin folder of your external Make installation at the beginning of the list. This bin folder would be the one containing the make.exe executable. Apply and Close. Rebuild.

Re: S32DS Compilation error : fatal error - cygheap base mismatch detected

GaryRK — Wed, 29 Nov 2023 11:11:18 GMT

Thanks winsmen, this is the only workaround that solved the problem on my system.

This is a recurring issue I face with S32DS 3.5. In the past it seemed to eventually resolve itself after some time (perhaps Windows or antivirus policy updates), however on this occasion I had urgent work to do and I could not force it to function via system shutdown/restart or the autorebase.bat script.

Here is the exact procedure I used:

Open project properties in S32DS.
- Presently this needs to be done for all projects that are affected (which is anything built in S32DS managed make context).
Expand C/C++ Build and select Environment.
Select the PATH variable and click the Edit... button.
Pre-pend the path to external directory (outside of S32DS installation) containing make.exe, for example I installed a separate instance of msys64 which includes make.exe at the default path of: C:\msys64\usr\bin.
Click OK then Apply and Close.
Attempt to repeat the build or clean operation and it should now work.

I tried to apply this workaround at S32DS workspace level by defining the PATH variable in Window -> Preferences -> C/C++ -> Build -> Environment but this does not work. It only seems to support appending of environment variables to the project-local environment, meaning the non-functional S32DS make.exe will supersede the external instance and be invoked first leading to the error. I will update this thread if I find a way to apply the workaround in a general way.

Best regards,

Gary