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.

DM8168 debugging(Execution GEL file issue)

In one of our Custom DM8168 board,while connecting JTAG through Code compressor studio executing "GEL file"

We are observed the following issue

-----------------------------------------------------------------------------------------------------------------------------------------------------------

CortexA8: GEL Output: EVM816x Startup Sequence 

CortexA8: GEL Output: PRCM Setup Complete

CortexA8: Output:     Main PLL Init is in Progress, Please wait ..... 

CortexA8: Trouble Writing Memory Block at 0x48140400 on Page 0 of Length 0x4: (Error -2130 @ 0x48140400) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.507.0)  CortexA8: GEL: Error while executing OnTargetConnect(): Target failed to write 0x48140400     at *((unsigned int *) (0x48140000+0x400))=(unsigned int) main_pll_ctrl [CABS_AVRM_sd_SW_level_allCS.gel:325]     at mainPLL(64, 0x1, 0x8, 0x800000, 0x2, 0xE, 0x0, 0x1, 0x8, 0xAAAAB0, 0x3, 0x9, 0x55554F, 0x3, 0x9, 0x374BC6, 0xC, 0x48, 0x4) [CABS_AVRM_sd_SW_level_allCS.gel:877]     at Setup_MainPLL() [CABS_AVRM_sd_SW_level_allCS.gel:46]     at OnTargetConnect() . CortexA8: Trouble Reading Register CP15_Registers_CP15_CONTROL_REGISTER: (Error -2131 @ 0x20013F00) Unable to access device 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 5.1.507.0)  CortexA8: Failed CPU Reset (HW): (Error -1141 @ 0x3D58) 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 5.1.507.0)  CortexA8: Trouble Halting Target CPU: (Error -1260 @ 0x0) Requested operation failed for security violation. Check security/priviledge settings, and retry the operation. (Emulation package 5.1.507.0)  CortexA8: Trouble Halting Target CPU: (Error -1260 @ 0x0) Requested operation failed for security violation. Check security/priviledge settings, and retry the operation. (Emulation package 5.1.507.0)  CortexA8: Trouble Halting Target CPU: (Error -1260 @ 0x0) Requested operation failed for security violation. Check security/priviledge settings, and retry the operation. (Emulation package 5.1.507.0).

----------------------------------------------------------------------------------------------------------------------------------------------------------

We have checked power sequence & system clk seems to be ok. we even tried with reducing JTAG TCLK also, the same GEL file executing properly in remaining boards. Kindly let me know your suggestions/Inputs

Thanks & Regards,

Vijay Varma

  • Vijay,

    Vijay Varma said:
    CortexA8: Trouble Writing Memory Block at 0x48140400

    The register that is mapped at 0x48140400 address is the MAINPLL_CTRL. Could you check if this CCS error occur on the first access of the main PLL:

    mainPLL(...)
    {

    unsigned int main_pll_ctrl=0, k=0;
     
        /* Put the Main PLL in Bypass Mode */
        main_pll_ctrl = RD_MEM_32(MAINPLL_CTRL);  ------> CCS issue occur at that point?

    ........

    }

    Make sure that the clock input to the Main DPLL is valid and stable. Make sure you are not using u-boot and/or linux kernel to mess up with the GEL file, remove bootable SD card if any. Also this issue can be caused by unstable operation of the DDR3, try to reduce the DDR3 frequency and/or do software leveling.

    Regards,
    Pavel

  • Pavel,

    We have checked onceagain System clk (27MHZ) seems to be fine. We are facing this issue in one board only remaining two boards seems to be fine.

    Please find the updated log file

    -----------------------------------------------------------------------------------------------------------

    CortexA8: GEL Output: EVM816x Startup Sequence

    CortexA8: GEL Output: PRCM Setup Complete
    CortexA8: GEL Output: Configuring Pad Functions...
    CortexA8: Trouble Writing Memory Block at 0x48140ad8 on Page 0 of Length 0x4: (Error -2130 @ 0x48140AD8) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.507.0)

    Kindly let me know your suggestions.

    Thanks & Regards,

    Vijay Varma

  • Vijay,

    Vijay Varma said:
    CortexA8: GEL Output: Configuring Pad Functions...
    CortexA8: Trouble Writing Memory Block at 0x48140ad8 on Page 0 of Length 0x4: (Error -2130 @ 0x48140AD8) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.507.0)

    Now you stuck at accessing (writing) into the PINCTRL183 (at addr 0x48140AD8):

    Setup_PADCTRL( )
    {
        GEL_TextOut( "Configuring Pad Functions...\n" );
         
        /* GPMC NOR */
        WR_MEM_32(conf_tim7_out      , 1);  // GPMC A12
        WR_MEM_32(conf_uart1_ctsn    , 1);  // GPMC A13
        WR_MEM_32(conf_uart1_rtsn    , 1);  // GPMC A14  ---> stuck here

    Vijay Varma said:
    We are facing this issue in one board only remaining two boards seems to be fine.

    When one SW works fine on one HW, and the same SW fail in other HW, this is most often indication of HW malfunction. Please double check your HW design of the failing board, using the below resources:

    - DM816x datasheet and silicon errata

    - DM816x EVM schematic

    - working boards schematics

     - http://processors.wiki.ti.com/index.php/AM389x_C6A816x_DM816x_Hardware_Design_Guide

    - the issue can be caused by unstable operation of the DDR3, try to reduce the DDR3 frequency and/or do software leveling

    Regards,
    Pavel