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.

OMAPL138 hangs in cint00 with debugger

Other Parts Discussed in Thread: OMAPL138

I have been working on a OMAPL138 project for a while and debugging the DSP side using Code Composer 4.2 successfully.  Yesterday I could run my code using the debugger, but then after some minor code changes, I tried to debug but it would never get to main().  I have tried running other projects and some get to main() and some don't.  If I halt, it's usually in one of three calls:  bcache_inv(), bcache_block(), or bcache_wait().  I retrieved my backup of the workspace from the day before and see the same problem, so it's clearly not my code changes. 

The ARM side is running Linux. I also tried stopping at U-boot then debugging the DSP ... same result.

I have reboot/reset multiple times, but can't get to main() which makes it impossible to debug.

I am using BIOS 5.  The board is the MityDSPL138.  Debugger uses USB560.

Mary

  • Further examination reveals that it is hanging in POOL_init.  I can put a breakpoint at POOL_int and it stop there.  It never reaches a breakpoint at the next line (CLK_init).

    POOLMEM is a section of memory used by DSPLink.

    ;; MODULE INITIALIZATION
    .sect ".sysinit"
    .global BIOS_init, _BIOS_init
    BIOS_init:
    _BIOS_init:
    GBL_preamble
    GBL_init
    SEM_init
    MEM_init
    OBJ_init
    BUF_init
    POOL_init
    CLK_init
    PRD_init
    RTDX_init
    IDL_init
    LCK_init
    LOG_init
    MBX_init
    PIP_init
    QUE_init
    STS_init
    SYS_init
    HWI_init
    HST_init
    ECM_init
    DEV_init
    UDEV_init
    DIO_init
    DGN_init
    DHL_init
    DPI_init
    SIO_init
    GIO_init
    MSGQ_init
    SWI_init
    HOOK_init
    TSK_init
    ISRC_init
    PWRM_init
    GBL_postamble