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.

CCS/PGA970EVM: ccsv8 & XDS110 & Error -1006: Unable to allocate memory

Part Number: PGA970EVM
Other Parts Discussed in Thread: PGA970, TMDSEMU110-U, CCSTUDIO, PGA900

Tool/software: Code Composer Studio

Hi,

I'm trying to get the PGA970EVM up and running, but failing miserably. Configuration is: 

- CCSv8 (latest updates)

- TI v18.1.4.LTS compiler

- XDS110

- PGA970_FW_Release_1_5_Generic

Following the procedure in sldu025 as closely as possible, I can build the code, but get a warning: 

warning: section PGA970.out(.text) was padded by 2 to a size of 2404 to satisfy

Setting up the target configuration as per instruction, Test Connection suceeds no problems. However, when I attempt to launch code to the target (either debug or Launch Config), I get the error: 

Cortex_M0_0: Error initializing emulator: (Error -1006 @ 0x0) Internal error: Unable to allocate memory. Restart the application. If error persists, please report the error. (Emulation package 8.0.903.4)

Anyone any ideas why the warning and why the Error -1006? 

Mat

  • Mat,

    Unfortunately I couldn't reproduce this issue; I am building the same firmware version but with the original ARM compiler (version 5.2.6).

    Regardless of the compiler, the Debug Probe shouldn't throw this error - these are two different things. 

    Did the tool request you to update the firmware of your TMDSEMU110-U? That would be the only thing that could possibly throw a Debug Probe error. 

    I will try to "break" my system on Monday and report back to this thread if I find anything relevant.

    What OS are you using?

    Regards,

    Rafael

  • Running Windows 10. The debug probe didn't request a firmware update upon connection to this board. However, its one that has been in active use on a C2000 platform, I believe it did a firmware update connecting to that last month. 

    Looking at some of the other posts on issues like this, there seems to be a discrepency on target config. Some have CS_DAP connections whereas mine doesn't (and I can't seem to force it to either): 

  • Mat,

    Hah, interesting. You are onto something. It seems the file you are using is not quite correct - the file I am using has the CS_DAP.

    Can you try to manually re-create the target configuration according to the instructions below and re-launch it?
    software-dl.ti.com/.../ccs_debug-main.html

    Regards,
    Rafael
  • ok, I manually created a new target config to include CS_DAP which looks like this:

    again, "Test Connection" works fine but when I attempt to load code / debug then code composer disappears in a puff of smoke! 

    perhaps you could share your test project & target file?

    I'm supposed to be evaluating this chip, but it doesn't bode well at the moment (I can only imagine the kind of horrors we'll see on a custom hardware platform)!!

    Mat

  • Mat,

    A passing Test Connection is a guarantee that the electrical connections are fine. However, usually when CCS "vanishes" without a trace is due to an unhandled memory exception on the host (usually Java related). Can you copy and paste the contents of the file ccstudio.ini in this thread? That may help uncover some possible invalid or insufficient Java settings.

    The reference below has a few troubleshooting tips, but the most important at this moment is to re-open CCS and try to create a new workspace.  This will reset many settings of the CCS environment and may overcome a lingering invalid setting. 

    http://dev.ti.com/tirex/#/?link=Development%20Tools%2FIntegrated%20Development%20Environments%2FCode%20Composer%20Studio%2FUser's%20Guide%2FTroubleshooting 

    What is the OS version you are using? I will try to test this later today on a Windows 10 Build 1809 just to be sure nothing related to the surrounding environment is influencing this.

    As for the project, I am using the standard PGA970 project shown in the SLDU025 document.

    Hope this helps,

    Rafael

  • 
    

    Code composer is actually pretty stable at the moment and working well for other jobs. ccstudio.ini contents below but I doubt its a systematic problem as everything else works well (C2000 and MSP430 projects). 

    I've created a new workspace and went through the install instructions again: by the letter this time :). Alas, the same result ensues. It's very confusing because,  when I create the target config, I get exactly what the instructions show on-screen - aka no CS_DAP! Something very perculiar to the PGA/Arm M0

    Running Windows 10 build 1803. 

    Mat

    ccstudio.ini contents are: 

    -startup
    plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
    --launcher.library
    plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.551.v20171108-1834
    -product
    com.ti.ccstudio.branding.product
    -showsplash
    com.ti.ccstudio.branding
    --launcher.defaultAction
    openFile
    --launcher.appendVmargs
    -vmargs
    -Dosgi.instance.area.default=@user.home/workspace_v8
    -Djxbrowser.ipc.external=true
    -Dorg.eclipse.equinox.http.jetty.customizer.class=com.ti.ccstudio.gui.composer.http.jetty.MaqettaJettyCustomizer
    -Dccs.minXDCVersion=3.25.5.1
    -Dorg.eclipse.ecf.provider.filetransfer.retrieve.readTimeout=30000
    -Dorg.eclipse.ecf.provider.filetransfer.retrieve.closeTimeout=10000
    -Dsun.net.client.defaultReadTimeout=30000 
    -Dsun.net.client.defaultConnectTimeout=10000 
    -Xms128m
    -Xmx768m
    -XX:ErrorFile=C:\Users\maherm\AppData\Local\TEXASI~1\CCS\ti\2\dmp\\hs_err_%p.log
  • Mat,

    Thanks for sending the details;

    I am a bit confused; you mentioned you successfully created a target configuration file that has the CS_DAP, but you also mention that you that is quite troubling that you keep getting a configuration without the CS_DAP

    So, how exactly are you creating the target configuration? The short clip below shows how I am creating mine in CCSv8.2.0:

    My target configuration file follows at the end of this post. 

    I would have to send the project in a private messaging, but at this point it does not look like it is very relevant, given you do not have a successful connection.

    Regards,

    Rafael

    PGA970_XDS110.zip

  • Hi Rafael,

    The confusion is on both sides :)

    To clarify:

    1. if I create a target config automatically, CS_DAP doesn't appear and I get the "Unable to allocate memory" error when connecting.

    2. if I create a target config manually, then I can put CS_DAP in fine, but code composer crashes when attempting a connection.

    Your latest files have only added confusion, namely:

    3. following the same procedure as your video, I get a different end-result, see video clip below.

    4. if I take your target config file and load it into my CCS, it also DOESN'T show CS_DAP: it looks exactly like one I created, including the same errors when connecting. (I triple-checked this to be sure).

    In all instances, "Test Connection" works fine, it debugging/loading code which doesn't. 

    My next step is to delete and re-install code composer, see if this fixes the problem. I'll let you know next year whether this works

    Merry Christmas!

    Mat

  • Mat,

    Please apologize for the delay. Thanks for sending the video; one thing that strikes me from your procedure is that you only have PGA970 as you type on the filter, while you should have the a PGA900 device as well.

    This leads me to believe that the PGA device support is ancient (perhaps 1.0.0).

    If you open the menu Help → About Code Composer Studio → Installation Details and type "PGA" on the Filter box, what version do you see for the package shown? The latest is 1.0.2.

    Regards,

    Rafael

  • you're onto something there..

  • Hi,

    Please apologize for the delay; were you able to add the proper PGA family of devices in your CCS?

    If not, check the following reference:
    software-dl.ti.com/.../ccsv7_updates.html

    Make sure you select the PGA Device support.

    Hope this helps,
    Rafael