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.

Issue connecting to ARM-Core on OMAP L138 eXperimenter kit

Other Parts Discussed in Thread: OMAP-L138, CCSTUDIO

 

Hi,

after "KICK Unlocked" I get the warning:

"The GEL callback "OnTargetConnect()" for the target "Texas Instruments XDS100v2 USB Emulator_0/ARM9_0" is still processing.
The function could contain an infinite loop.

Do you wish to pause the processing of this function and continue?"

after pressing "No" there's the same console output as when I connect to the DSP-Core, which to me suggests it worked.
if I press "Yes" the console reads: "ARM9_0: The GEL callback "OnTargetConnect()" is no longer running atomically".

 either way when I try downloading an OUT-File I get an error
"ARM9_0: Loader: One or more sections of your program falls into a memory region that is not writable.  These regions will not actually be written to the target.  Check your linker configuration and/or memory map." 

 

I have checked the GEL file and set it to load C6748.gel.
Also I set the "The JTAG TCLK Frequency (MHz)" to Adaptive and set the limit to 1.0 MHz as suggested by another community entry but it still won't work.

Here's a zip-folder with the gel file, and the ARM and DSP projects I set up (the target configuration file is in the comARM folder)

1031.files.zip

Thanks for any advise on how to resolve this problem.

  • Hi Kevin,

    Are you using the XDS100 on-board emulator or are you using an external XDS100v2 emulator?

    And what is the full version number of CCS that you are using?

    Thanks

    ki

  • Hi ki,

    Here are the version number of the tools I use:

    Code Composer Studio Version: 4.2.0.10017
    Code Generation Tool: v4.9.1
    Inter-processor Communication: 1.23.05.40
    SYS/BIOS: 6.32.05.54

    Emulator:
    Texas Instruments XDS100v2 USB Emulator

    Kevin

  • Kevin,

    I can reproduce the issue when I use the on-board emulation (connect to the target via mini-USB port) and try to use it as an XDS100v2. The issue may be that the on-board emulation is actually an XDS100v1. When I use my external XDS100v2 (via JTAG header on the board), It works fine. Can you confirm which emulation option you are using?

    Thanks

    ki

  • Ki,

    I did connect the mini-USB and set the Target Configuration to XDS100v2.
    So the mini-USB connection can only be used with the XDS100v1 emulator?

    Is there any way to use the v2 with the mini-usb to program the ARM-core?
    It works fine when I download an out-file to the DSP-core using the  same configuration.

    Kevin

  • The on-board emulation (mini-USB connection) is indeed an XDS100v1

    http://www.logicpd.com/products/system-on-modules/zoom-omap-l138-experimenter-kit/

    Debug

    • Connectors for JTAG interface
    • XDS100v1 emulation circuit

    While XDS100v1 does not officially support ARM, it is possible to use it as an XDS100v2 and get it to work with an ARM. But since it is not officially supported, you may run into problems like with the issue you see now.

    ki

  • Hi,

     

    I got myself an external XDS100v2 and the connection process appears to be working.
    However, there's a new error when I try to download the OUT-File:
    "ARM9_0: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map."
    I still use this Project:
    1031.files.zip
    Which is an example from TI, so I guess there's still something wrong with the configuration.

    I use the C6748.gel file from LogicPD's "OMAP-L138 SOM-M1 GEL & BSL Files (CCStudio v4.2)"

    Any thoughts on how this could be resolved?

    Thank you very much for your help so far.

    Kevin

  • Kevin - can you use the gel files for the OMAP L138 instead?

    3480.gel.zip

     

  • Ki,

    The download process works now, but there's a problem with the MessageQ example:
    "Invalid CIO command (20) in the CIO buffer at address (0xc0024870) was not recognized. Please check the device and program memory maps." 
    As suggested in the post http://e2e.ti.com/support/embedded/f/355/p/104932/382481.aspx  there could be something wrong with the emulation driver.
    Since I use a 4.2.something (4.2.0.10017) CCS there could be something to it.
    If there is a problem, which driver version is affected by this? 

    Anyway, I tried the Notify example and it worked, so I guess the connection issue has been solved and the MessageQ error has another source.

    Thanks for your help.

    Kevin