TM4C1290NCPDT: Finding ROM version

There is no need to know the ROM version. The ROM code is permanently programmed to the ROM memory during silicon fabrication. It may be more than 10 years since ithe code was frozen. What we recommend customers is to call MAP_xyz instead of ROM_xyz directly. Some of the APIs in ROM are deprecated. Calling MAP_xyz instead will result in calling ROM_xyz if the API in the ROM is still valid or otherwise will call xyz which is part of the library in the driverlib.lib. In your CCS project, you just need to define which device and which silicon version you have. 

Refer to the below description.

34.3 Mapped ROM Calls
When code is intended to be shared between projects, and some of the projects run on devices with
a ROM and some run on devices without a ROM, it is convenient to have the code automatically
call the ROM or the flash version of the API without having #ifdef-s in the code. rom_map.h
provides an automatic mapping feature for accessing the ROM. Similar to the ROM_Function()
APIs provided by rom.h, a set of MAP_Function() APIs are provided. If the function is available in
ROM, MAP_Function() simply calls ROM_Function(); otherwise it calls Function().
In order to use the mapped ROM calls, the following steps must be performed:
Follow the above steps for including and using driverlib/rom.h.
Include driverlib/rom_map.h.
Continuing the above example, call MAP_GPIODirModeSet() in the source code.
As in the direct ROM call method, the choice of calling ROM versus the flash version is made at
compile-time. The only APIs that are provided via the ROM mapping feature are ones that are
available in the ROM, which is not every API available in the peripheral driver library.
The following is an example of calling a function in shared code, where the device in question is
defined in the project file:

#include "driverlib/rom.h"
#include "driverlib/rom_map.h"
#include "driverlib/systick.h"
void
SetupSysTick(void)
{
MAP_SysTickPeriodSet(0x1000);
Map_SysTickEnable();
}
When built for a device that does not have a ROM, this example is equivalent to:
#include "driverlib/systick.h"
void
SetupSysTick(void)
{
SysTickPeriodSet(0x1000);
SysTickEnable();
}
When built for a device that has a ROM, however, this example is equivalent to:
#include "driverlib/rom.h"
#include "driverlib/systick.h"
void
SetupSysTick(void)
{
ROM_SysTickPeriodSet(0x1000);
ROM_SysTickEnable();