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.

CCS/TMS320F28069: binary file generated with first 4 bytes wrong @ 0xFF

Part Number: TMS320F28069
Other Parts Discussed in Thread: CONTROLSUITE

Tool/software: Code Composer Studio

Hi everybody , 

please  due to  project setting ( started quite long ago )    I am on CCS 5.3   , and I must stay on this one .

now  when I generate  binary file  ( needed  to  later load in bootloader )  in CCS    the file  genarated  is wrong , since  first 4 byte are  0XFF .

now  same project  the .out file is working  ( i can debig /program etc  ) , and if I convert this file to HEX and then to binary it works  perfectly  

please what shoudl I check  /change to have it working ? 

here is the linking command :

 

-v28 -ml -mt --cla_support=cla0 --float_support=fpu32 --vcu_support=vcu0 -O2 -g --define=DEBUG --define=ENABLE_TRACE=1 --diag_warning=225 --display_error_number --asm_listing --obj_directory="C:/Users/ITENPIE/Desktop/Software/TI/CC_5/28069/EVCI_SW/obj/output/ti-debug/dev_Resonant" -z --stack_size=0x300 -m"C:/Users/ITENPIE/Desktop/Software/TI/CC_5/28069/EVCI_SW/obj/output/ti-debug/dev_Resonant/dev_Resonant.map" --warn_sections -i"C:/ti/ccsv5/tools/compiler/c2000_6.1.0/lib" -i"C:/TI/controlSUITE/libs/math/FPUfastRTS/V100/lib" -i"C:/ti/ccsv5/tools/compiler/c2000_6.1.0/include" --reread_libs --priority --display_error_number --xml_link_info="C:/Users/ITENPIE/Desktop/Software/TI/CC_5/28069/EVCI_SW/obj/output/ti-debug/dev_Resonant/dev_Resonant_linkInfo.xml" --absolute_exe --entry_point=code_start --rom_model

 thank you 

regards

carlo

  • Please show exactly you create the binary file.  For now, I'll presume you use C:/ti/ccsv5/utils/tiobj2bin/tiobj2bin.bat .  Please zip up dev_Resonant.out and attach it to your next post.  I'll try to reproduce this ...

    Colombo Carlo said:
    the file  genarated  is wrong , since  first 4 byte are  0XFF

    By the way, your link command does not use the -o option to name the output file.  I presume this a simple copy-n-paste oversight.

    Thanks and regards,

    -George

  • This issue was resolved offline.

    Thanks and regards,

    -George