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.

TM4C129ENCPDT: Problem configuring CCS10 + Segger Jlink

Part Number: TM4C129ENCPDT
Other Parts Discussed in Thread: SEGGER, TM4C1294NCPDT

I tried creating a new configuration from the Target Configurations and when I launch selected configuration and then connect to target it keeps coming up as no symbols are defined.  I am not sure how to get this working.  Does anyone have experience that could help?

Thanks,

Rick

  • Hi,

      Can you show a screenshot of the message you see?

      Can you connect to the target successfully?

      Did you load you code to the flash successfully?

      Is the no symbols seen only during debug? If you can connect to the target and already have some code in the flash then you need to load the symbols in order to debug as to view all the symbols. Go to Run -> Load -> Load Symbols using the .out file you generated for your prior code. You can also do Load Program. If this is not your issue then show a screenshot of what happened. 

  • Initially I tried debugging by going through the steps manually.  This morning after getting your response I tried just using the debug icon and it appears to work on the first try to debug.  I stopped it and tried to load code and that failed as did the subsequent debug attempt using the icon.  

  • Hi,

    Initially I tried debugging by going through the steps manually.  This morning after getting your response I tried just using the debug icon and it appears to work on the first try to debug.

      I assume you were able to 1) connect and 2) load your program and 3) debug the program at least one time? Is that a correct statement? 

      Can you do some experiments:

      - Can you load a simple blinky code? Will it work? Let's start with a simpler program. The error message complains about writing to 0x1FFC0 which is 128kB. I wonder if a smaller program size will make a difference. 

      - Is this your custom board? Do you have another board that you can try?

      - Can you try the same setup (same target configuration file with Jlink and your original program) on the LaunchPad? Do you see any problem?

      - I also want to see what GEL file you load. See below. 

     - Can you try the attached target configuration file? Does it make a difference?

    JLink_TM4C129.ccxml

  • Hi Charles,

    I cycled power on my custom board, and disconnected/reconnected the jlink USB and restarted CCS.  This time it did not work as it did once before with the debug icon.  I saved your JLink_TM4C129.ccxml to the project/targetConfigs directory.

    I am working on a custom board.  It seems to have trouble loading the fw and stalls at about 22-35% before saying cannot load code. 

    I am not sure I am doing the manual steps correctly.  

    1. Launch target configuration  (new ccxml you provided)

    2. Right click on SEGGER Jlink Emulator in debug tab and select connect target

    3. Load symbols using project name.out.  (this step does not appear to do anything most of the time)

    I did try another of my boards with the same result of it looking like it failed the load step.  It also failed by dropping into the fault handler.  One time it also seemed to work and I was able to set a breakpoint and catch it.  

    I am having trouble finding the dialog you show above to get the gel file.  I am looking for the examples in ccs now.

    Thanks,

    Rick

  •   - Can you load a simple blinky code? Will it work? Let's start with a simpler program. The error message complains about writing to 0x1FFC0 which is 128kB. I wonder if a smaller program size will make a difference. 

    With CCS 10.4.0.00006 and SEGGER J-Link Support (Linux) 6.88.2.0 have been testing downloading a TM4C1294NCPDT with a Segger J-Link and a program which uses 938kB in flash.

    Have tried downloading the program at least 10 times and haven't seen any failures reported. I.e. can't see any obvious issue with Segger J-Link support in CCS 10.

    In the CCS Target Configuration just used the defaults: