F28377D-SEP: CPU usage of syscfg file

Hi Reshma 

The actual RAM impact is minimal for an empty project, and it scales entirely with what you configure in SysConfig.
The best way to measure your specific build is to look at the .map file after building, CCS generates it alongside the .out. Check the board.obj and c2000ware_libraries.obj sections there for exact figures.

Files like c2000ware_libraries.cmd.genlibs are scaffolding/placeholders for optional features. They exist so the build system can unconditionally reference them without errors. Empty files consume zero memory the compiler and linker simply process them as no-ops. They do not contribute to your Flash or RAM footprint.

You're correct that Device_init() enables clocks for all peripherals by default and Device_initGPIO() unlocks all GPIO ports, which consumes more CPU cycles than strictly necessary at startup. However, this is a one-time startup cost, not an ongoing runtime penalty.

If you still want to optimize, here's what to selectively keep from Device_init()  

// 1. Disable watchdog (or conifgure it)
SysCtl_disableWatchdog();

// 2. Set system clock (mandatory)
SysCtl_setClock(DEVICE_SETCLOCK_CFG); // your PLL config

// 3. Flash wait states (if running from flash)
Flash_initModule(FLASH0CTRL_BASE, FLASH0ECC_BASE, DEVICE_FLASH_WAITSTATES);

// 4. Instead of Device_enableAllPeripherals(), call only what you need. e.g.:
SysCtl_enablePeripheral(SYSCTL_PERIPH_CLK_TIMER0); // if using CPU Timer0
SysCtl_enablePeripheral(SYSCTL_PERIPH_CLK_EPWM1); // if using ePWM1
SysCtl_enablePeripheral(SYSCTL_PERIPH_CLK_SCIA); // if using SCI-A
// ... add only what your application needs

For Device_initGPIO(), it simply calls GPIO_unlockPortConfig(GPIO_PORT_A, 0xFFFFFFFF) (and B, C, etc.) to remove the write lock on all GPIO configuration registers. If you only use ports A and B, you can call:

GPIO_unlockPortConfig(GPIO_PORT_A, 0xFFFFFFFF);
GPIO_unlockPortConfig(GPIO_PORT_B, 0xFFFFFFFF);
// Skip C, D, E, F if unused

If you hand-edit device.c, SysConfig will overwrite your changes the next time it regenerates files. To preserve your optimizations:
Copy the relevant initialization code into your own main.c or a custom init file
Remove the SysConfig-generated device.c from your build

or

Accept the default Device_init() as-is  , the extra CPU cycles are a one-time startup cost measured in microseconds, which is negligible unless you have strict boot-time requirements