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.

TMS320F28075: TI .txt file format issue

Part Number: TMS320F28075
Other Parts Discussed in Thread: C2000WARE

Hello Team,

In our project we using secondary boot loader and Application code concept. We are generating .txt file of our application firmware and keeping  it on external SRAM. And use this file for boot loading.

 So this text file is having correct data in it but the flash address is wrong 

  

Application code is placed from Sector E to N and. Sector E address is 0x88000. But the address mentioned in .txt file is @110000 which looks wrong.

I have made changes in properties->  c2000 hex utility -> output format options  to generate this .txt file.

Can anyone guide me in this.

Regards,

Sandeep Chavan

 

  • Sandeep

    You're seeing the address represented in terms of byte addressing (0x110000), it is 0x88000 when converted to word addressing. Is it behaving as expected? I don't know why it is shown in that format, but I've seen it before and it didn't cause any issue.

    Best regards
    Chris
  • Chris,

    can you please help me in understanding this byte addressing and word addressing . Also how to convert byte addressing to word addressing.

    if this format is not consistent during .txt file generation then customized bootloader will not act as per actual functionality required.

    bootloader has to confirm whether its byte addressing or word addresing to understand exact address of flash to write firmware.

    Regards,
    Sandeep
  • Sandeep

    F28075 only does memory addressing by words. For the byte-to-word conversion, I just divided 0x110000 by 2.
    You will either have to modify the values before storing to external memory or convert your application using different HEX utility options. If you use HEX utility options (such as -boot -sci8 -a) that are compatible with our bootloaders, then these already have destination address, block, etc information. This is would be the method I recommend.
    Refer to the SCI kernel (under device_support/) or boot ROM bootloaders (under libraries/boot_rom) in C2000Ware.

    Best regards
    Chris
  • Thanks Chris. This is really helpful.