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.

CODECOMPOSER: When I debug the same project for the second time, the interrupts do not work until power reset or switch another project

Part Number: CODECOMPOSER
Other Parts Discussed in Thread: TM4C123GH6PM, SEGGER

Tool/software:

I have a very simple project for TM4C123GH6PM microcontroller. I am controlling a GPIO based on SysTick Timer. Every 5 seconds the GPIO turns off and on.

My problem is as follows, when I power on for the first time, the SysTick_Handler function, i.e. interrupt, works properly in the first debug session I do, but when I close the debug session without powering off and open a new one, the interrupts no longer work. I need to power down and debug again to get it working again. In addition, I have tried CPU Reset, Core Reset, System Reset, Board Reset, Load Program, ReLoad Program and the result is the same. In reset based operations the program goes to ResetISR and then stays in IntDefaultHandler...

I have also observed that when I switch to another project, upload its code and come back to the old project again, the interrupts work in the first debug I did, but as I said, when I close and open the session again, the interrupts no longer work...


I experimented with these features/equipment:
-I tried with versions 11.2 and 12.7 of CCS.
-I am using JLink Segger(7.96), TivaWare C SDK 2.1.4, Windows 10 x64.

Code:
-main.c

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
#include <stdint.h>
#include <stdbool.h>
#include "inc/hw_ints.h"
#include "inc/hw_memmap.h"
#include "inc/hw_nvic.h"
#include "inc/hw_types.h"
#include "driverlib/rom.h"
#include "driverlib/rom_map.h"
#include "driverlib/sysctl.h"
#include "driverlib/gpio.h"
#include "driverlib/fpu.h"
#include "driverlib/systick.h"
bool is_active = false;
uint32_t last_tick = 0;
uint32_t current_tick = 0;
void Update_LEDs(void)
{
if (is_active)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

-tm4c123gh6pm_startup_ccs.c

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
//*****************************************************************************
//
// Startup code for use with TI's Code Composer Studio.
//
// Copyright (c) 2011-2014 Texas Instruments Incorporated. All rights reserved.
// Software License Agreement
//
// Software License Agreement
//
// Texas Instruments (TI) is supplying this software for use solely and
// exclusively on TI's microcontroller products. The software is owned by
// TI and/or its suppliers, and is protected under applicable copyright
// laws. You may not combine this software with "viral" open-source
// software in order to form a larger program.
//
// THIS SOFTWARE IS PROVIDED "AS IS" AND WITH ALL FAULTS.
// NO WARRANTIES, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING, BUT
// NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
// A PARTICULAR PURPOSE APPLY TO THIS SOFTWARE. TI SHALL NOT, UNDER ANY
// CIRCUMSTANCES, BE LIABLE FOR SPECIAL, INCIDENTAL, OR CONSEQUENTIAL
// DAMAGES, FOR ANY REASON WHATSOEVER.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Settings:

-Arm Compiler Summary:
mv7M4 --code_state=16 --float_support=FPv4SPD16 -me --include_path="C:/Users/UNK/workspace_v11/systick_example" --include_path="C:/dev/ti/ccs1120/ccs/tools/compiler/ti-cgt-arm_20.2.5.LTS/include" --include_path="C:/dev/ti/tivaware_c_series_2_1_4_178" --define=ccs="ccs" --define=PART_TM4C123GH6PM -g --gcc --diag_warning=225 --diag_wrap=off --display_error_number --abi=eabi

-Arm Linker Summary:
-mv7M4 --code_state=16 --float_support=FPv4SPD16 -me --define=ccs="ccs" --define=PART_TM4C123GH6PM -g --gcc --diag_warning=225 --diag_wrap=off --display_error_number --abi=eabi -z -m"systick_example.map" --heap_size=0 --stack_size=512 -i"C:/dev/ti/ccs1120/ccs/tools/compiler/ti-cgt-arm_20.2.5.LTS/lib" -i"C:/dev/ti/ccs1120/ccs/tools/compiler/ti-cgt-arm_20.2.5.LTS/include" --reread_libs --diag_wrap=off --display_error_number --warn_sections --xml_link_info="systick_example_linkInfo.xml" --rom_model

  • Hi,

      I just tried your exact same code. After the code is loaded and running and I see the processor jump to SysTick_Handler as I put a breakpoint in the ISR. I then stop and disconnect the debugger without power off the device. After that, I reconnect with the device again. I will first load symbol again. Load symbols does not reflash the device but merely loading the symbols. Once I do that, if I place the breakpoint on SysTick_Handle, I will see the processor break as it enters SysTick_Handle. Note I run on a LaunchPad with a ICDI debug probe on it. I don't have a Jlink. As far as I can tell, I don't see a problem with your code. 

  • First of all, i appreciation for your effort. It is very important for me that you try.

    You verified my personal opion. I don't think there is any error in my code. But i think it can in debug settings or related with debug probe. Because of that, i will try XDS100 debug probe in the next couple days. At least i can eliminate that option...

    By the way, can you send me debug settings (My settings are as in the picture below. Maybe there is a setting here that provides it...) ?

  • Hi,

      My settings are the same as yours.