TM4C1294KCPDT: Does erasing a block of flash memory affects the timers running in background?

void timer4_init(void) {
    //
    // Enable the peripherals used by this example.
    //
    SysCtlPeripheralEnable(SYSCTL_PERIPH_TIMER4);

    //
    // Configure the 32-bit periodic timer.
    //
    TimerConfigure(TIMER4_BASE, TIMER_CFG_PERIODIC);
    TimerLoadSet(TIMER4_BASE, TIMER_A, ui32SysClock/1000);   //Clock at 120 MHz

    IntPrioritySet(INT_TIMER4A, 0x00);

    //
    // Setup the interrupts for the timer timeouts.
    //
    IntEnable(INT_TIMER4A);
    TimerIntEnable(TIMER4_BASE, TIMER_TIMA_TIMEOUT);

    //
    // Enable the timers.
    //
    TimerEnable(TIMER4_BASE, TIMER_A);
}


#define FLASH_EVENT_START	0x6C000	//Address of the first block of flash to be used for storing events.475136 0x6C000									// 524288-16384(boot)-16384(params)-16384(events)=475136
#define FLASH_EVENT_END		0x70000	//Address of the last block of flash to be used for storing events.
#define FLASH_BLOCK_SIZE	0x4000	//Flash erases in 16k block increments. //4000 DR
#define FLASH_BLOCKS_TO_ERASE  1	// Number of blocks to erase.

long Event_Schedule_Save(DIGITAL_EVENT_SCHEDULE* einfo) { // Save Event Info

	long error = 1;
	tFlashProtection state;
	int i;
	FLASH_EVENT_START=

	ASSERT((FLASH_EVENT_START % 4) == 0);    // Starting address must be a multiple of 4. 
	ASSERT((sizeof(einfo) % 4) == 0);		// Number of bytes to be programmed must be a multiple of 4.

	state = FlashProtectGet(FLASH_EVENT_START);  // Get protection setting for block of memory to be used.
	if (state == FlashReadWrite) { // States are r/w, ro, xo, must r/w.
	    error = FlashErase(FLASH_EVENT_START);	// Erase flash in 16k block increments.
	} else
		error = -1;							// Error if state is not r/w.

	if (!error)
		error = FlashProgram((uint32_t*) einfo, FLASH_EVENT_START, sizeof(DIGITAL_EVENT_SCHEDULE));

	return (error);  // -1 indicates programming error, 0 is success.
}

typedef struct {
	union {
		struct {
			EVENT_SCHEDULE_HEADER 	HEADER;
			DIGITAL_EVENT 		EVENTS[EVENT_COUNT];
		};
		unsigned char Byte[DIGITAL_EVENT_SCHEDULE_SIZE + EVENT_SCHEDULE_HEADER_SIZE];
	};
} DIGITAL_EVENT_SCHEDULE;

/******************************************************************************
 *
 * qs_weather_ccs.cmd - CCS linker configuration file for qs_weather.
 *
 * Copyright (c) 2013-2014 Texas Instruments Incorporated.  All rights reserved.
 * 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.
 *
 * This is part of revision 2.1.0.12573 of the DK-TM4C129X Firmware Package.
 *
 *****************************************************************************/

--retain=g_pfnVectors

/* The following command line options are set as part of the CCS project.    */
/* If you are building using the command line, or for some reason want to    */
/* define them here, you can uncomment and modify these lines as needed.     */
/* If you are using CCS for building, it is probably better to make any such */
/* modifications in your CCS project and leave this file alone.              */
/*                                                                           */
/* --heap_size=0                                                             */
/* --stack_size=256                                                          */
/* --library=rtsv7M3_T_le_eabi.lib                                           */

/* The starting address of the application.  Normally the interrupt vectors  */
/* must be located at the beginning of the application.                      */
#define APP_BASE 0x00000000
#define RAM_BASE 0x20000000

/* System memory map */

MEMORY
{
    /* Application stored in and executes from internal flash */
    FLASH (RX) : origin = APP_BASE, length = 0x00100000
    /* Application uses internal RAM for data */
    SRAM (RWX) : origin = 0x20000000, length = 0x00040000
}

/* Section allocation in memory */

SECTIONS
{
    .intvecs:   > APP_BASE
    .text   :   > FLASH
    .const  :   > FLASH
    .cinit  :   > FLASH
    .pinit  :   > FLASH
    .init_array : > FLASH

    .vtable :   > RAM_BASE
    .data   :   > SRAM
    .bss    :   > SRAM
    .sysmem :   > SRAM
    .stack  :   > SRAM
}

__STACK_TOP = __stack + 1024;