I checked the compiler settings - they are different in Debug and Release modes. We speak about an "image" in memory.Īnd here you gave me a good hint with your optimisation links.
The MSPDEBUG reports me all info with particularities about each section (_interrupt_vector. I meant not the file size but the binary loaded to MCU. So, the E2E forum answer is: this is another domain problem. com/./Optimization_Techniques_for_the_TI_C6000_CompilerĪs a matter of fact I counted 3 apps with the blurring already: CCS, P圜harm and DipTrace (EDA software). Despite talking about C6000, several basic concepts are applicable to the optimization process in general.
Also, an optimized code does not necessarily mean it is smaller - if you are looking for absolute speed, the optimizer will unroll loops, inline functions to gain the extra cycles wasted with context switching, for example.Ī very thorough page that talks about optimization is in the link below. out file size in the filesystem does not reflect the actual code size loaded to the target - the debug information is not loaded at all to the device. To actually compare the files and verify the differences you can check the utility mentioned in the thread below:Īs a general statement, the. Regarding the size differences between each build configuration, the thread below mentions what is included in a typical. Therefore in this particular case I don't know what could possibly be happening in your system.
Regarding the drawing errors: I found out that my old netbook Acer AO751h had Linux Mint 17.2 and I installed CCSv6.2 there but was unable to reproduce the problems.
0 kommentar(er)
