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.

GEL FIle Errors with AM1808 eXperimenter Kit BSL files

Other Parts Discussed in Thread: AM1808

I've been trying to use the external DDR SDRAM memory on the AM1808 eXperimenters kit and have problems. Using the LED-DIP test program that is supplied with the BSL support package. In CCS v4.2.4 I've modified the AM1808.gel file that LogicPD supplies with the kit for the board test to try and enable the external DDR SDRAM at location 0xc0000000. I modify the gel file as show below per the notes in the gel file

------------------------ Modified GEL file -----------------

OnTargetConnect( )

{

Clear_Memory_Map();

Setup_Memory_Map();

/* You can choose to run this if you only have the experimenter kit */

/* It will not turn PSC on for the peripherals on the user interface board */

/* But it does not hurt if you choose to run PSC_All_On_Full_EVM() even if */

/* you only have the experimenter kit */

PSC_All_On_Experimenter();

/* PSC_All_On_Full_EVM(); */

Core_300MHz_mDDR_132MHz();

}

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

Gives this error with CCS v4.2.4

ARM9_0: Output: Angel Guard Memory Map Cleared.

ARM9_0: Output: ---------------------------------------------

ARM9_0: Output: Angel Guard Memory Map Setup Complete.

ARM9_0: Output: ---------------------------------------------

ARM9_0: Output: Enabling Experimenter PSCs...

ARM9_0: Output: PSC Enable Complete.

ARM9_0: Output: ---------------------------------------------

ARM9_0: GEL: Error while executing OnTargetConnect(): Target failed to write memory at 0x01C11138.

The GEL file and the LED_DIP test program are files contained in the "1020489B_CCSv-4-2-4 with_SOM-M1_BSL_WS.zip" file from the LogicPD website.

Any ideas on how to correct this error or does an newer GEL file exist?

 

  • The GEL file that comes with the experimenter kit should work and initialize the DDR without having to modify it. What happens if you just run it without any changes?

    If you still see the error it is probably a problem with the board itself.

    Jeff

  • Ok assuming that the GEL file is OK I tried running the expermineter RAM test to verify the hardware. When I compile and run the RAM test I get the following errors in the console window.

    RM9_0: Output: Memory Map Cleared.

    ARM9_0: Output: ---------------------------------------------

    ARM9_0: Output: Memory Map Setup Complete.

    ARM9_0: Output: ---------------------------------------------

    ARM9_0: Error: (Error -1034 @ 0x400) Data bus is 'not ready'. Choose 'Abort' to try to abort the pending transaction. Choose 'Force' to try to force the bus ready state. (Release 5.0.429.0)

    ARM9_0: Warning: (Error -1035 @ 0x2EE0) Device state appears corrupt after a hung bus. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Release 5.0.429.0)

    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). (Release 5.0.429.0)

    ARM9_0: Warning: (Error -1034 @ 0x400) Data bus is 'not ready'. Choose 'Abort' to try to abort the pending transaction. Choose 'Force' to try to force the bus ready state. (Release 5.0.429.0)

    ARM9_0: Warning: (Error -1035 @ 0x2EE0) Device state appears corrupt after a hung bus. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Release 5.0.429.0)

    ARM9_0: Warning: (Error -1034 @ 0x400) Data bus is 'not ready'. Choose 'Abort' to try to abort the pending transaction. Choose 'Force' to try to force the bus ready state. (Release 5.0.429.0)

    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). (Release 5.0.429.0)

    ARM9_0: Warning: (Error -1033 @ 0x3FF) Instruction bus is 'not ready'. Choose 'Abort' to try to abort the pending transaction. Choose 'Force' to try to force the bus ready state. (Release 5.0.429.0)

    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). (Release 5.0.429.0)

    ARM9_0: Warning: (Error -1034 @ 0x400) Data bus is 'not ready'. Choose 'Abort' to try to abort the pending transaction. Choose 'Force' to try to force the bus ready state. (Release 5.0.429.0)

    ARM9_0: Error: (Error -1033 @ 0x3FF) Instruction bus is 'not ready'. Choose 'Abort' to try to abort the pending transaction. Choose 'Force' to try to force the bus ready state. (Release 5.0.429.0)

    ARM9_0: Warning: (Error -1034 @ 0x400) Data bus is 'not ready'. Choose 'Abort' to try to abort the pending transaction. Choose 'Force' to try to force the bus ready state. (Release 5.0.429.0)

    ARM9_0: Warning: (Error -1035 @ 0x2EE0) Device state appears corrupt after a hung bus. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Release 5.0.429.0)

    ARM9_0: Warning: (Error -1034 @ 0x400) Data bus is 'not ready'. Choose 'Abort' to try to abort the pending transaction. Choose 'Force' to try to force the bus ready state. (Release 5.0.429.0)

    ARM9_0: Warning: (Error -1035 @ 0x2EE0) Device state appears corrupt after a hung bus. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Release 5.0.429.0)

    ARM9_0: Warning: (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). (Release 5.0.429.0)

    ARM9_0: Error: (Error -1033 @ 0x3FF) Instruction bus is 'not ready'. Choose 'Abort' to try to abort the pending transaction. Choose 'Force' to try to force the bus ready state. (Release 5.0.429.0)

    ARM9_0: Warning: (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). (Release 5.0.429.0)

    ARM9_0: Error: (Error -1033 @ 0x3FF) Instruction bus is 'not ready'. Choose 'Abort' to try to abort the pending transaction. Choose 'Force' to try to force the bus ready state. (Release 5.0.429.0)

    ARM9_0: Warning: (Error -1035 @ 0x2EE0) Device state appears corrupt after a hung bus. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Release 5.0.429.0)

    ARM9_0: Warning: (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). (Release 5.0.429.0)

    Reseting the target and JTAG did not help. Perhaps I have a bad board. I try getting a replacement and see if the same thing happens.

    In the mean time how do I lower TCLK for the JTAG? I'm using the Blackhawk USB 100v2.

     

  • As a follow up to this problem.

    Apparently the problem is not with the GEL file. The problem was resolved by turning on adaptive clocking for the XDS100 emulator as specified here http://processors.wiki.ti.com/index.php/XDS100#Q:_How_can_I_turn_on_adaptive_clocking.3F

    Once adaptive clocking was enabled the GEL file worked as expected.