• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 3 answers
  • Subscribers 99 subscribers
  • Views 1646 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/OMAP-L138: How do I get started?

Adam Wozniak66
Intellectual 920 points
Part Number: OMAP-L138
Other Parts Discussed in Thread: TMDSLCDK138,

Tool/software: Code Composer Studio

I've got a TMDSLCDK138 dev board.  It came with truly ancient CCSv5, which I actually finally got running... inside a 32 bit VirtualBox VM running ubuntu 12.04.  Except I cannot get the debugger I have to work (TMS320-XDS100-V3).  (ARM9_0: GEL: Error executing OnTargetConnect(): Attempted to read unmapped virtual memory...)

So I tried CCSv8 on my Windows 10 machine, which doesn't seem to have any L138 related example projects, which makes it pretty useless to me.

What is the preferred / expected way to develop with these devices in 2018?

  • 0
    TI__Guru**** 463481 points
    Hi Adam,
    I would recommend checking out the Getting Started Guide that comes withe the Processor SDK:

    www.ti.com/.../PROCESSOR-SDK-OMAPL138

    I will also move this thread to the device forum. The experts there can provide additional tips to get you started

    Thanks
    ki
  • 0
    TI__Mastermind 27355 points

    Hello Adam,

    Processor SDK is our current, supported software offering. The SDKs come with examples and demos that can be run out of the box. Within SDK RTOS, there are driver examples that can be built into CCS projects using the provided scripts. Please note the latest CCS version that's been validated with the SDK is v7.4.

    As Ki mentioned, we recommend going through the Getting Started Guide first.

    I also recommend taking a look at our Processor SDK training series for more info on the SDK in general.

    Latest documentation for Processor SDK RTOS:

    Latest documentation for Processor SDK Linux:

    If you have any questions please let me know. 

  • 0 in reply to Sahin Okur
    Intellectual 920 points
    I installed CCSv7.4 and "PROCESSOR-SDK-RTOS-OMAPL138 04_03_00_05" on my Windows 10 machine.
    There did not appear to be a windows .exe installer for "PROCESSOR-SDK-LINUX-OMAPL138 04_03_00_05".

    When I start CCSv7.4 and go to "Resource Explorer", I still do not see any example projects for the TMDSLCDK138.

    What am I missing here?
  • 0 in reply to Adam Wozniak66
    TI__Mastermind 27355 points

    Processor SDK Linux is available only on Linux OS.

    I'm not sure why they don't show up in Resource Explorer, but you can go to Resource Explorer Classic -> SYS/BIOS-> OMAP-L1x to find generic TI-RTOS examples. If you are looking to use a peripheral, you will want to look at the device driver examples. They can be built by following the steps under "PDK Example and Test Project Creation"  in the Processor SDK RTOS Guide.

  • 0 in reply to Sahin Okur
    TI__Guru**** 463481 points

    Sahin Okur said:
    I'm not sure why they don't show up in Resource Explorer

    The processor SDK is not supported by the new Resource Explorer (CCSv7+). But as you mentioned, it can be browsed via "Resource Explorer Classic" (which was simply called "Resource Explorer" in earlier version of CCS (6.1.2 and earlier)

  • 0 in reply to Ki
    Intellectual 920 points

    I'm still not all the way home with this set up.

    I'm getting errors trying to debug.  In CCS5 there was a window with tabs where I could tweak debugger settings to fix things like this.

    I can't find that window anywhere in CCS7.4

    Where is the window that allows changing settings for the JTAG debugger?  What are the correct settings for a TMS320-XDS100-V3 ?

    ARM9_0: Output: Target Connected.
    ARM9_0: Output: ---------------------------------------------
    ARM9_0: Output: Memory Map Cleared.
    ARM9_0: Output: ---------------------------------------------
    ARM9_0: Output: Memory Map Setup Complete.
    ARM9_0: Output: ---------------------------------------------
    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)) [OMAP-L138_LCDK.gel:4]
    at device_PLL0(0, 24, 1, 0, 1, 11, 5) [OMAP-L138_LCDK.gel:403]
    at Set_Core_300MHz() [OMAP-L138_LCDK.gel:468]
    at Core_300MHz_mDDR_150MHz() [OMAP-L138_LCDK.gel:245]
    at OnTargetConnect()
    ARM9_0: Trouble Writing Memory Block at 0xc3000000 on Page 0 of Length 0x7ff0
    ARM9_0: File Loader: Verification failed: Target failed to write 0xC3000000
    ARM9_0: GEL: File: C:\Users\awozniak\workspace_v7\bigtime_LCDKOMAPL138_ARM9\Debug\bigtime_LCDKOMAPL138_ARM9.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 7.0.188.0)
    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 7.0.188.0)
    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

  • 0 in reply to Adam Wozniak66
    TI__Mastermind 27355 points

    Adam,

    Are you referring to this window?

    You can get here by double clicking on your target config file (.ccxml) and navigating to the advanced tab. 

    Make sure you have your boot switches set to UART or EMU mode (all OFF) to ensure code is not already running when trying to connect. 

    Also, there was a thread where the same error was reported when using an XDS110 debug probe. Please take a look and see if it helps.

    From this thread,

    "If your XDS does not support adaptive clocking an adapter may be required to achieve the device's full JTAG operating rate. Running the XDS with a TCK rate that is less than 1/8th the ARM's functional clock rate is also an option if adaptive clocking is not supported by your XDS." 

    So, try lowering your TCK rate and if that doesn't work then you will need to modify your GEL file to prevent PLLCMD from being set as suggested by Rafael in the thread.