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/OMAPL138B-EP: OMAPL138

Part Number: OMAPL138B-EP
Other Parts Discussed in Thread: OMAPL138

Tool/software: Code Composer Studio

Sir,

I wanted to program for ARM-DSP communication. I have the following doubts:

1. I am using MityDSPL138 module for my project, i connected it using JTAG XDS100V3 to CCS and i tried accessing to the UART1 registers to try for sending and receiving data through serial console. I am not able to send or receive data through teraterm, actually teraterm black screen is not giving any response.

2. According to the memory mapping shown in datasheet for both ARM and DSP the UART registers are at same address location, and i saw these registers in L1D, when i ran the code. How can ARM access these L1D registers ?

3. If i need to code ARM can i do it through JTAG ? I tried running the UART_ECHO code, but its not giving results. What should i do ?

  • Hello,

    Have you tried using a working example first? This will help us isolate whether it's a hardware or software issue. I found these examples on the web for the MityDSPL138 module:

    support.criticallink.com/.../1500

    Can you give the uart example a try?

    By default the ARM has access to most on and off chip memory areas, including the DSP Internal memories, EMIFA, DDR2, and the additional 128K byte on chip shared SRAM. Likewise almost all of the on chip peripherals are accessible to the ARM by default.

    Yes, you can program the ARM through JTAG just as you do for the DSP. Which software package is the UART_ECHO code from?
  • OMAPL138_StarterWare_1_10_03_03\examples\MityDSPL138\uart. This is the path of the uart code which i tried running. Before running a code do i have to do something with boot?
    printing hello world i tried, modifying UART registers also i tried, both were possible.
    Through JTAG why cant i access the ARM registers then ?
    I will try the example what you gave too.
  • Please see the following page. It looks like some modifications are needed to get the examples running on the MityDSP-L138.

    support.criticallink.com/.../StarterWare
  • ARM9_0: Trouble Removing Breakpoint with the Action "Finish Auto Run" at 0xc2080a3c: (Error -1066 @ 0x3332) Unable to set requested breakpoint in memory. Verify that the breakpoint address is in writable memory. (Emulation package 8.0.27.9)

    Its showing like this while debugging
  • I think this is an issue with the GEL file not properly initializing the device. Can you share which GEL file you are using? (Double-click on your target configuration file, go to the "Advanced" tab, select ARM9_0, and copy and paste the path in the "initialization script" field.

    Please also share the console output when connecting to the Arm core.
  • It looks like there is a GEL file specifically for the MityDSP-L138 in Critical Link's BSP:

    support.criticallink.com/.../Board_Support_Package
  •  This dhows linux package, Is mitydspl138 having linux os

  • Initialization script field is empty. Console output shows build is finished successfully. After building, the debug takes infinite time, but no result.

  • We're interested in just the GEL file:

    Are you able to download this and add the gel file to the initialization script field?

  • That critical link page about bsp is mentioning about cygwin and then linux.run file. Do i have to follow that whole procedure ? Else how to get those files ?

  • ARM9_0: Output: Memory Map Cleared.
    ARM9_0: Output: ---------------------------------------------
    ARM9_0: Output: Memory Map Setup Complete.
    ARM9_0: Output: ---------------------------------------------
    ARM9_0: Output: Enabling Full EVM PSCs...
    ARM9_0: Output: PSC Enable Complete.
    ARM9_0: Output: ---------------------------------------------
    ARM9_0: GEL: Error while executing OnTargetConnect(): Target failed to write 0x01C11100
    at (*((unsigned int *) (0x01C11000+0x100))&=~(0x00000001)) [MityDSP-L138_ARM.gel:5]
    at device_PLL0(0, 24, 1, 0, 1, 3, 5) [MityDSP-L138_ARM.gel:401]
    at Set_Core_300MHz() [MityDSP-L138_ARM.gel:453]
    at Core_300MHz_mDDR_132MHz() [MityDSP-L138_ARM.gel:247]
    at OnTargetConnect()
    ARM9_0: Trouble Writing Memory Block at 0xc2080000 on Page 0 of Length 0x15f4
    ARM9_0: File Loader: Verification failed: Target failed to write 0xC2080000
    ARM9_0: GEL: File: C:\ti\CL_MityDSPL138_StarterWare_06_11_12 (1)\OMAPL138_StarterWare_1_10_03_03\build\armv5\cgt_ccs\omapl138\MityDSPL138\uart\Debug\uartEcho.out: Load failed.
    ARM9_0: Unable to terminate memory download: NULL buffer pointer at 0x320
    ARM9_0: Error: (Error -1060 @ 0x2E18) Device is not responding to the request. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.0.27.9)
    ARM9_0: Error: (Error -1029 @ 0x2B5F) Invalid data read from ICECrusher register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.0.27.9)
    ARM9_0: Unable to determine target status after 20 attempts
    ARM9_0: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging


    I tried loading the gel file for ARM, but its giving error.
  • Hello,

    There was a thread with a similar issue reported here: https://e2e.ti.com/support/processors/f/791/p/692068/2550808

    Can you see if the solution posted there helps resolve your issue?