CCS: Debug TMS320F2837xS blackhawk usb2000 controller

FLASH, FLASH_DEBUG, RAM and RAM_DEBUG are build configurations for your project. Build configurations have their own set of compiler/linker build options and can even have different source files. In your case I am betting that both are true.

I am assuming FLASH and FLASH_DEBUG are setup with a linker command file that puts the program in FLASH and that RAM and RAM_DEBUG have a different linker command file that puts the program in RAM. I.e. there will be 2 linker command files in your project and one of them will be getting excluded depending on which build configuration is active.

As far as the _DEBUG vs the ones without _DEBUG typically people have different optimization settings for the compiler. You can debug using any of these configurations unless you have a build option set to not include any symbolic debug information. Typically debugging with high level of optimizations is more challenging as the compiler will be more aggressive in scheduling instructions so you don't have as much source code correlation.

Note that the Blackhawk USB 2000 Debug Probe is quite old and will not work with CCSv9 and later. You will want to use CCSv8.

Sounds like you are new to using CCS. I would suggest trying the this workshop which shows the basics of using CCS on a C2000 device.
dev.ti.com/.../node

Regards,
John