This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Compiler/66AK2G02: Heap allocation error

Part Number: 66AK2G02
Other Parts Discussed in Thread: MATHLIB

Tool/software: TI C/C++ Compiler

Hi, 

I am compiling pdk_k2g_1_0_6. I am following this link to build the pdk : http://processors.wiki.ti.com/index.php/Rebuilding_The_PDK 

How to resolve this ?

  • Hi,

    Can you place the pdk in a directory with no spaces? Additional make sure your workspace does not have spaces.

    Todd
  • Did this get resolved?
  • Hi Todd,

    There is no spaces in pdk directory name. I am compiling from C:\ti\pdk_k2g_1_0_6\packages folder. Still the error persists. We were able to compile pdk_k2g_1_0_8 without any issues. But we need pdk_k2g_1_0_6.
  • Hi,

    I'm also facing same issue.. can you please suggest to resolve this issue.

     3 [main] sh 5196 C:\ti\xdctools_3_32_01_22_core\bin\sh.exe: *** fatal error - fork: can't reserve memory for stack 0x2BC770 - 0x2C0000, Win32 error 487
          3 [main] sh 5196 C:\ti\xdctools_3_32_01_22_core\bin\sh.exe: *** fatal error - fork: can't reserve memory for stack 0x2BC770 - 0x2C0000, Win32 error 487

    Regards,

    Dinesh

  • Dinesh/Saseendranath,

    Can you make sure there is no other shell in your environment (e.g. cygwin, MKS, etc.). Note: I've seen a different shell instead of git sometimes also. The issue is that shell is getting used instead.

    Todd
  • Hi Todd,

    There is no other shell is present. 

    We tried restarting the system, then ran gmake. It will run to some point, then this error will come. Is it is because of any memory issue?. Here in that error message, we could see that, the reserve_size is less that allocsize. Could we reset or increase any related memory?. (This is just a thought process).

  • We've seen issue with other shells that cache information that will cause errors like this. So after a reboot, it seems to work, but then the other shell does something (unrelated) and "bang" the build breaks. Can you do a "set" from a command line and attach the output? Also, which OS (and version) are you using?

    Todd

  • Hi Todd,

    We are using Windows 10. 

    This is the output of set command in the same window.

    C:\ti\PDK_K2~1\packages>set
    ALLUSERSPROFILE=C:\ProgramData
    APPDATA=C:\Users\User1\AppData\Roaming
    BIOS_INSTALL_PATH=C:/ti/bios_6_46_05_55
    BIOS_VERSION=6_46_05_55
    C6X_GEN_INSTALL_PATH=C:/ti/ti-cgt-c6000_8.1.3
    CGTOOLS=C:/ti/ti-cgt-c6000_8.1.3
    CGT_ARM_VERSION=16.9.2.LTS
    CGT_ARP32_VERSION=1.0.8
    CGT_PRU_VERSION=2.1.5
    CGT_VERSION=8.1.3
    CL_PRU_INSTALL_PATH=C:/ti/ti-cgt-pru_2.1.5
    CommonProgramFiles=C:\Program Files\Common Files
    CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
    CommonProgramW6432=C:\Program Files\Common Files
    COMPUTERNAME=CPU-310
    ComSpec=C:\Windows\system32\cmd.exe
    CROSS_TOOL_PRFX=arm-none-eabi-
    DEFLOGDIR=C:\ProgramData\McAfee\DesktopProtection
    DSPLIB_INSTALL_PATH=C:/ti/dsplib_c66x_3_4_0_0
    DSPLIB_VERSION=c66x_3_4_0_0
    EDMA3LLD_BIOS6_INSTALLDIR=C:/ti/edma3_lld_2_12_04_28
    EDMA_VERSION=2_12_04_28
    FPULIB_PATH=C:/ti/gcc-arm-none-eabi-4_9-2015q3/lib/gcc/arm-none-eabi/4.9.3/fpu
    GCC_CROSS_TOOL_PREFIX=arm-none-eabi-
    GCC_VERSION=arm-none-eabi-4_9-2015q3
    GCC_VERSION_ARM_A15=arm-none-eabi-4_9-2015q3
    GCC_VERSION_ARM_A8=arm-none-eabi-4_9-2015q3
    GCC_VERSION_ARM_A9=arm-none-eabi-4_9-2015q3
    GCC_VERSION_FPULIB=4.9.3
    HOMEDRIVE=C:
    HOMEPATH=\Users\User1
    IMGLIB_INSTALL_PATH=C:/ti/imglib_c66x_3_1_1_0
    IMGLIB_VERSION=c66x_3_1_1_0
    IPC_INSTALL_PATH=C:/ti/ipc_3_46_00_02
    IPC_VERSION=3_46_00_02
    LIMIT_BOARDS=evmK2G iceK2G
    LIMIT_SOCS=k2g
    LOCALAPPDATA=C:\Users\User1\AppData\Local
    LOGONSERVER=\\RPLDMN
    MATHLIB_INSTALL_PATH=C:/ti/mathlib_c66x_3_1_1_0
    MATHLIB_VERSION=c66x_3_1_1_0
    NDK_INSTALL_PATH=C:/ti/ndk_2_25_01_11
    NDK_VERSION=2_25_01_11
    NUMBER_OF_PROCESSORS=4
    OneDrive=C:\Users\User1\OneDrive
    OS=Windows_NT
    PARTNO=AM
    Path=C:/Windows/System32;C:/ti/ti-cgt-c6000_8.1.3/bin;C:/ti/xdctools_3_32_01_22_core;C:/ti/xdctools_3_32_01_22_core\bin;C:/ti/xdctools_3_32_01_22_core\packages\xdc\services\io\release
    PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
    PDK_INSTALL_PATH=/ti/PDK_K2~1/packages
    PROCESSOR_ARCHITECTURE=AMD64
    PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 94 Stepping 3, GenuineIntel
    PROCESSOR_LEVEL=6
    PROCESSOR_REVISION=5e03
    ProgramData=C:\ProgramData
    ProgramFiles=C:\Program Files
    ProgramFiles(x86)=C:\Program Files (x86)
    ProgramW6432=C:\Program Files
    PROMPT=$P$G
    PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
    PUBLIC=C:\Users\Public
    SDK_INSTALL_PATH=C:/ti
    SESSIONNAME=Console
    SOC_FAMILY=AM
    SystemDrive=C:
    SystemRoot=C:\Windows
    TEMP=C:\Users\User1~1.D\AppData\Local\Temp
    TMP=C:\Users\User1~1.D\AppData\Local\Temp
    TOOLCHAIN_PATH_A15=C:/ti/gcc-arm-none-eabi-4_9-2015q3
    TOOLCHAIN_PATH_A8=C:/ti/gcc-arm-none-eabi-4_9-2015q3
    TOOLCHAIN_PATH_A9=C:/ti/gcc-arm-none-eabi-4_9-2015q3
    TOOLCHAIN_PATH_Arm9=C:/ti/ti-cgt-arm_16.9.2.LTS
    TOOLCHAIN_PATH_EVE=C:/ti/arp32_1.0.8
    TOOLCHAIN_PATH_GCC=C:/ti/gcc-arm-none-eabi-4_9-2015q3
    TOOLCHAIN_PATH_M4=C:/ti/ti-cgt-arm_16.9.2.LTS
    TOOLS_INSTALL_PATH=C:/ti
    UIA_INSTALL_PATH=C:/ti/uia_2_00_06_52
    UIA_VERSION=2_00_06_52
    USERNAME=User1
    USERPROFILE=C:\Users\User1
    UTILS_INSTALL_DIR=C:/ti/xdctools_3_32_01_22_core/bin
    VSEDEFLOGDIR=C:\ProgramData\McAfee\DesktopProtection
    windir=C:\Windows
    XDCCGROOT=C:/ti/ti-cgt-c6000_8.1.3
    XDCPATH=../../..;C:/ti/xdctools_3_32_01_22_core/packages;/ti/PDK_K2~1/packages/.;C:/ti/edma3_lld_2_12_04_28/packages;C:/ti/bios_6_46_05_55/packages;C:/ti/ipc_3_46_00_02/packages;C:/ti/ndk_2_25_01_11/packages;C:/ti/uia_2_00_06_52/packages
    XDC_INSTALL_PATH=C:/ti/xdctools_3_32_01_22_core
    XDC_VERSION=3_32_01_22_core

    C:\ti\PDK_K2~1\packages>

  • Hi Todd,

    Could you please help us to resolve this issue ?

    Thanks,
    Dinesh

  • The bolded text looks strange. Can you correct that?

    XDCPATH=../../..;C:/ti/xdctools_3_32_01_22_core/packages;/ti/PDK_K2~1/packages/.;C:/ti/edma3_lld_2_12_04_28/packages;C:/ti/bios_6_46_05_55/packages;C:/ti/ipc_3_46_00_02/packages;C:/ti/ndk_2_25_01_11/packages;C:/ti/uia_2_00_06_52/packages

  • Did this get resolved?

    Todd
  • We set up the pdk in a new system, where there is no newer version of pdk exists. Here we didn't faced any issue like this.