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.

Troubles in connecting to and loading program to OMAPL138

Other Parts Discussed in Thread: OMAPL138

When it connect to OMAPL138’s  ARM9_0 through SEED-XDS560PLUS Emulator in CCSv4.1.2.00027,the following error would occur :

And the main GEL codes are:

OnTargetConnect( )

{

    Clear_Memory_Map();

    Setup_Memory_Map();

 

    PSC_All_On_Experimenter();

       DEVICE_kickUnlock();

 

Core_300MHz_DDRPLL_150MHz();

    EMIFA_NAND_PINMUX();

    Wake_DSP();

}

And I used “Core_300MHz_mDDR_132MHz();”, “Core_200MHz_mDDR_126MHz();” or “Core_100MHz_mDDR_102MHz();” instead of  “Core_300MHz_DDRPLL_150MHz();”.It could only be configured successfully with “Core_100MHz_mDDR_102MHz();”.

So I’m confused.I don’t know why such a strange phenomenon happens.And what should I do to solve this problem?

 

Besides,after connect to OMAPL138’s  ARM9_0,I tried to load program “nand-writer_ccs33.out” into the processor for writing “ubl-nand.bin” and “u-boot.bin” into NANDFLASH ,like this:

However,once I clicked “OK”,the processor would be running immediately and never stop!Please look at following picture:

And if I halted it, I figured out that it’s running 2 codes at 0xFFFD397C and 0xFFED3980 in an infinite loop ,like following:

Could anyone help me to solve these problems?

  • I've solved my own problems now.

    1、I tried CCSv3.3 instead of CCSv4,and the first problem didn't appear under it;

    2、I loaded "nand-write_ccs33.out" as a program instead of as a symbol only,then it writed "ubl.bin" and "uboot.bin" into NAND Flash successfully.

    Thank all the friends who care about this post.And hope my answear could help you,too.O(∩_∩)O~

  • I figured out the essential reason for my problem today.I checked my target configuration in CCSv4,and found out that it set JTAG TCLK Frequency as 35MHz by default.However,it would better be 10MHz.So I changed it like following picture:

    Finally,the troubles I posted never show again.