PROCESSOR-SDK-AM64X: tiimage make process.

Part Number: PROCESSOR-SDK-AM64X

Tool/software:

Hi,

to make ti image I saw the step 


$(objcopy) --strip-all -O binary sciclient_ccs_init.debug.out sciclient_ccs_init.debug.bin

I know it strip out the debug symbol and shrink the binary.

1. But Can I skip this step?  strip

If my fsbl binary is " sciclient_ccs_init.debug.out"< 1 MB, is this strip a must?

I prefer to leave debug symbol during the boot. 


The purpose for me is to be able to boot sbl from RBL.  will debug image boot?

Thanks. 

  • Hello Jun,

    Can you provide the URL link to where you see that specific step?

    Yes, we suggest keeping the debug symbols in the binary during your development. That allows you to connect CCS to the R5F while the R5F is running, and associate the source code with the binary that is running on the R5F.

    Stripping out the debug symbols is useful after you have finished software development, and you are trying to optimize your system's memory usage.

    Regards,

    Nick

  • yes for sure, In your example:

    C:\ti\mcu_plus_sdk_am64x_09_01_00_41\examples\drivers\boot\sbl_null\am64x-evm\r5fss0-0_nortos\ti-arm-clang\Makefile

    right before the tiimage, you have this step to strip out (rip off) the symbol,  is this  a must?



  • Hi Jun,

    You should be able to boot the image even when you do not use this --strip-all option, please let me know if you are facing any issues otherwise.

    As Nick pointed out earlier, you can keep the Debug symbols in the binary during the development, stripping out the symbols helps to optimize the system's memory. --strip-all option Removes from the output all symbols and non-allocated sections not within segments, except for.ARM.attribute section and the section name table, you can read more here: 15.2. tiarmobjcopy - Object Copying and Editing Tool — TI Arm Clang Compiler Tools User's Guide. You can also choose to flash the debug.tiimage if you want to keep the debug symbols.