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.

Running the RDK-IDM sample applications using CCS v4.2.4

Other Parts Discussed in Thread: LM3S6918, LM3S8962

Does anybody know how to run and debug the sample applications in Stallarisware for the RDK-IDM board?

I can get the code and teh libraries to compile and load into the LM3S6918, but when debugging, teh applications do not run.

Thanks in advance.

  • Hello,

    Have you tried the example in the Stellaris Quick Start Guide?

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_ccstudio/CCSv4/CCS_4_1_0/Quickstart-Eval-Kit-CCS.pdf

    It walks you through building, loading and running an example program

    ki

  • Hello Ki-Soo!

    I met you at one of the Arrow seminars in south florida.

    The method outlined in the Stellaris Quick Start Guide is teh method I followed, except I used the RDK-IDM instead of the EK-LM3S9B90. The code compiles and loads, but does not run in the debugger.

    I have tried the same method with the 8962 and 3748 eval boards and all works fine.

    I have noticed that the linker command file that comes with the RDK-IDM examples places FLASH at 0x00001000 while the linker command file that comes with the example applications for the other boards places FLASH at 0x00000000. Is there a reason for that?

    As an experiment, I modified the linker command file for one of the example applications for teh RDK-IDM to place the Flash at 0x00000000 and then the code ran fine. But I do not think this is teh correct way to do it.

    I appreciate your help on this as I am new to teh Stellaris and I have a project that could use the part.

    Best regards,

    José

  • Hello Ki-Soo:

    Even though I had tried the Stellaris Quick Start guide example before, I decided to try it again with a fresh installation of the StellarisWare 8264 and CCS v4.2.4.

    I chose the RDK-IDM board, and the driverlib-cm3 and grlib-cm3.

    The project compiled OK.

    The loading seemed to progress OK and the execution pointer stopped at main() as it is supposed to.

    But running the problem did notwork, notihing was visible on the screen.

    I need to resolve this or I will not be able to use any Stellaris processor in my project.

    Best regards,

    José

  • Jose,

    It sounds like you may have erased the bootloader image on the device that resides at address 0x0. Please see these related threads where users have similar symptoms to yours, that also tell you how to reprogram the bootloader.

    http://e2e.ti.com/support/microcontrollers/stellaris_arm_cortex-m3_microcontroller/f/471/t/90817.aspx
    http://e2e.ti.com/support/microcontrollers/stellaris_arm_cortex-m3_microcontroller/f/471/t/45002.aspx

  • AartiG:

    Thanks for the help.

    I did erase the bootloader.

    But I have reloaded the bootloader at 0x0000 several times and I still cannot load an execute applications using CCS V4.

    Could you try duplicating the problem using StellarisWare 8264, an RDK-IDM and CCS v4.2.4?

    There may be something wrong with StellarisWare 8264.

    Thanks,

     

    José

  • AartiG:

    I read the references you mentioned in your last e-mail and I still have the same problem with my RDM. Here is what I did:

    1) Using LM Flash I loaded the boot_eth binary into my RDM. I am using a LM3S8962 EV board for JTAG connection. The binary loaded and verified OK at address 0x0000.

    2) Loaded the hello.bin at adress 0x1000. The program loaded, verified and ran perfectly.

    3) Repeated step 1.

    4) Fired up my CCS v4.2.4. The StellarisWare software for the IDM, the driverlib-cm3 and grlib-cm3 were already setup.

    5) Compiled and loaded the hello application.

    6) Got a GEL message: "Warning debug port error occurred"

    7) Program did not run.

    I have done this several times and the same problem occurs. This is whay I had asked you to duplicate the steps above and see if you get teh same results.

    Thanks again.

     

    José

  • For the benefit of others that might come across this thread, the issue was resolved as per this post.