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.

NDK Client Demo Problems

Hello,

After compiling and loading the NDK Client demo that ships with the MCSDK_02_00_00_beta2 package, nothing happens.  I've run a previous version of this binary before and am familiar with the System_printf statements that usually accompany the beginning of execution.

Any ideas why nothing prints to the screen when the program is run?

  • EVM6678
  • CCSv5.02
  • MCSDK_02_00_00_beta2

Thanks for the help!

  • P.S. This problem seems to have appeared out of the blue.  Also, I just tried the previous binary file (that is known to work) with no luck.  Other programs seem to have no trouble running.

  • Hello,

    Can you please check if:

    1. the dip switches are set properly, if you are using CCS to load the program, you need to set it to no-boot mode, refer to the Technical Reference Mannual/User's Guide for details

    2. the gel file is loaded and run properly, be sure you load the gel file before you connect the target, you can view memory at 0x8000 0000 (start of DDR) to check if the data are written properly

    3. you can step through from main, or add a printf() in the main to check if you can print anything from the main().

     

    Regards,

    Hao.

  • Hao, thank you very much.  You've saved me from a large headache.  My problem ultimately came down to the fact that I was loading the GEL before the file load, but after connecting to the target.

     

    Thanks again!

  • r_robotics,

    Can you tell me which Demo program you are running?  Also, you said the previous version worked?  Have you made any changes to the program?

    Thanks,

    Jack

  • Hi Jack, sorry for the long delay.

    I am running the NDK "client" demo that ships with the MCSDK_2_00_00_beta2 (and beta1) software package, located at <mcsdk_2_00_00_beta1>\examples\ndk\evmc6678l\client.  The previous version did work without any problems, and I have not modified the software.  As mentioned earlier however, both versions stopped working.

    Stepping through the procedure given by Hao, I found that when debugging the software, the GEL file was not properly being loaded automatically for some reason.  When I manually launched the target configuration (as opposed to pressing the debug button) and loaded the GEL file, all seems well.  So this seems like it turned out to be a CCS issue.  Not sure why CCS stopped loading the GEL file.  To my knowledge I haven't changed anything that would affect that.  Oh well, at least there is a work-around.

    Thanks,

    r_robotics

  • Just FYI there was a related post in which a similar issue was happening and the GEL not loading  properly with the "launch" button was determined to be the cause.

    I filed a bug for this:

    SDSCM00039929 CCSv4 "debug launch" button lack of GEL reset leading to example failures, customer confusion

     Here's the other thread: http://e2e.ti.com/support/embedded/f/355/p/105671/376247.aspx#376247

    Steve

  • good to know.  Thanks for the update.