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.

How .out actually works on the microcontroller.!!




Referring to udp socket example i found the .bin file size to be around 30 KB and the .out file to be very high around 400+ KB.
Now when i load the .out using CCS onto CC32000 , where is the '.out' loaded on the device. I mean will this ',out' go directly on to the ram ( only 256 KB , so not possible ) or the external flash?

Who maintains the program symbols and facilitates the debugging process? 

Basically i would like to understand how the .out gets loaded on to the device and what part of it actually goes into the RAM and where rest debug information goes in.

How the debugging process works.

Thanks 


Regards,
Sreenivasa.

  • The .out file does contain the raw data which is loaded onto the target system.  But the .out file mostly contains meta-data that is not loaded.  This includes debug information used by CCS.  You might find this wiki article helpful.

    Thanks and regards,

    -George

  • Thanks George,

    I understand that in the '.out' object file the metadata part is not loaded onto the micro controller instead used by CCS to enable debugging feature. Only the core executable binary is loaded onto the device.

    Now, say i have loaded a binary into the flash memory, on power up the program will be loaded from flash to SRAM and executed.
    Now if the same source code`s executable in .out form is present in the CCS workspace , Can i do debugging on the existing binary present in the SRAM without loading the program again.

    Regards,
    Sreenivasa
  • sreenivasa upadhyaya said:
    Can i do debugging on the existing binary present in the SRAM without loading the program again.

    Yes.  That is one of the scenarios discussed in this wiki article.

    Thanks and regards,

    -George