• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 1130 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.

OMAPL-138: Optimized Code is not running after flashing to NAND

Mitul Shinde
Prodigy 130 points

Hi,

I am using OMAPL-138 package for our project.

Under CCS optimization option, I have changed speed vs. size from 4 to 5 and put optimization level from off to 3(Interprocedure optimization) and along with it I have changed linker file(.cmd file) also. Some of sections i define on L2 memory (like .const, .fardata, .bss, .far and .rodata)for optimized code to be worked and remaining sections I put on DDR2 memory. After all these changes I made one image and flash it. But it seems image is not booting.  

 

Regards,

Mitul Shinde

 

  • 0
    TI__Mastermind 45025 points
    Are you using TI-RTOS (or SYS/BIOS)? If so, which version?

    Steve
  • 0 in reply to Steven Connell
    Prodigy 130 points
    Hi Steven, Thanks for reply. I am not using any TI-RTOS or SYS/BIOS. I just put partial sections on L2 memory and remaining sections on DDR2. I append cmd file content also.

    // ============================================================================
    // Linker Command File for Linking c674 DSP Programs
    //
    // These linker options are for command line linking only. For IDE linking,
    // you should set your linker options in Project Properties.
    // -c Link Using C Conventions
    // -stack 0x1000 Software Stack Size
    // -heap 0x1000 Heap Area Size
    // ===========================================================================
    -stack 0x1000
    -heap 0x1000

    // ============================================================================
    // Specify the System Memory Map
    // ============================================================================
    MEMORY
    {
    L1P: o = 0x11E00000 l = 0x00008000
    L1D: o = 0x11F00000 l = 0x00008000
    L2: o = 0x11800000 l = 0x00040000
    DDR2: o = 0xC0000000 l = 0x20000000
    }

    // ============================================================================
    // Specify the Sections Allocation into Memory
    // ============================================================================
    SECTIONS
    {
    .cinit > DDR2 // Initialization Tables
    .pinit > DDR2 // Constructor Tables
    .init_array > DDR2 //
    .binit > DDR2 // Boot Tables
    .const > L2 // Constant Data
    .switch > DDR2 // Jump Tables
    .text > DDR2 // Executable Code
    .text:_c_int00: align=1024 > DDR2 // Entrypoint

    GROUP (NEARDP_DATA) // group near data
    {
    .neardata
    .rodata
    .bss // note: removed fill = 0
    } > L2
    .far: fill = 0x0, load > L2 // Far Global & Static Variables
    .fardata > L2 // Far RW Data
    .stack > DDR2 // Software System Stack
    .sysmem > DDR2 // Dynamic Memory Allocation Area

    .cio > DDR2 // C I/O Buffer
    .vecs > DDR2 // Interrupt Vectors
    }

    When I put all sections on DDR2 and make the image to flash. It is working fine.

    Regards,
    Mitul
  • 0 in reply to Mitul Shinde
    TI__Mastermind 45025 points
    Mitul,

    Ok, thanks for that info. I'll get this thread over to the proper forum.

    Steve
  • 0 in reply to Steven Connell
    TI__Mastermind 18320 points
    Mitul,

    I went ahead and moved this thread over to the OMAP-L forum in hopes that you will get a faster response there.
  • 0 in reply to Mitul Shinde
    Guru 26430 points
    You started 3 threads with similar problems. Are the are all the same problem?
    e2e.ti.com/.../545548
    e2e.ti.com/.../545814
    e2e.ti.com/.../545813
    Please use one thread if there is just one problem.