• State TI Thinks Resolved
  • Locked Locked
  • Replies 13 replies
  • Answers 1 answer
  • Subscribers 85 subscribers
  • Views 1508 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F28069F: How to generate one .hex file for two separate projects: boot and application code?

valeri Stoyanov
Prodigy 75 points
Part Number: TMS320F28069F
Other Parts Discussed in Thread: C2000WARE

Hello,

I've currently finishing programming my bootloader and application code, but I need to generate a single hex file that would contain both boot and application code. At the moment I can only generate two separate .hex files: 1 for boot and 1 for application code using the hex utility tool. I'm using CCS v11.

This topic is quite vague and outdated online with limited resources. Can someone give me the steps needed to create a single .hex file across different projects? 

Thanks.

  • 0
    TI__Expert 4880 points

    Hi! It sounds like you have two executables from two projects, effectively; one for bootloader and one for application.  Is that correct? The hex utility has a "load image" format mode that might be what you're looking for in that it enables you to combine multiple executables into a single image. Please search the C28x assembly tools manual for the sub-chapter titled The Load Image Format (--load_image Option) and see if it meets your needs.

    Thanks

  • 0 in reply to Alan Phipps
    Prodigy 75 points

    Hi, I have taken a look at that section however it mentions that I need to include a ROMs directive. Unfortunately, I'm not sure what content is required in the ROMs.

    I'm failing to understand if my application code and boot code are supposed to be linked in this ROMS directory. If so, how exactly is this achieved? Do I need to specify the FLASH memory addresses for my boot and application code in the ROMS?

    My hex command file looks like this at the moment: 

    Bootloader.out
--ti_txt 
--image
--map hex.map

ROMS
{
 FLASH: org = 0x3EC000, len = 0x20000, files = {Bootloader.hex}
}

    Unfortunately when I build my project using with the hex cmd file, the ti-txt file does not output in the correct format. Can you also advise on this?

    Thanks.

  • 0 in reply to valeri Stoyanov
    TI__Expert 4880 points

    Hi! The ROMS directive is documented in the section The ROMS Directive in the document to which I linked above, in which is basically says this:

    The ROMS directive specifies the physical memory configuration of your system as a list of address-range parameters. Each address range produces one set of files containing the hex conversion utility output data that corresponds to that address range. Each file can be used to program one single ROM device.

    So you should use it to describe the memory ranges on your system, and the hex utility will generate accordingly. 

    Unfortunately when I build my project using with the hex cmd file, the ti-txt file does not output in the correct format. Can you also advise on this?

    How are you invoking the tool, and can you elaborate on what you mean by "not output in the correct format". Is it not TI-TXT at all, or is it corrupted in some way, or some other effect?

    Thanks!

  • 0 in reply to Alan Phipps
    Prodigy 75 points

    Hi! Thank you for the reply. From what you are saying am I right to think that if I want to combine my boot and application code sections into one hex file, I would only need to select the "--load_image:combine_sections" to true? And in the ROMS directive you can specify an arbitrary memory address range?

    Yes, apologies I did not elaborate on my last question. 

    When I generate a TI-TXT hex file using the ROMS directive, the hex utility tool outputs the following:

      f¦@         FLASHD   }  }     ¦                   @      FLASHC  €} €}                         €       FLASHA   €~  €~                         €       ªø                ? ö4 ? $Iÿÿˆ   Nÿÿˆ    ÿÿˆ    þÿˆ    ´Bþÿˆ   @{Dÿÿˆ   þÿ ˆ      þÿ"ˆ      þÿ(ˆ  H? þÿ*ˆ  H? ÿÿˆ         ?  @vðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V€â¾ ñÿvvvðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v oþUšvªCv $¨$ƒVÕÜ“©=A–‚þ þA–"viÿvÐDvÛDvóDšvÁDvéDA’vÁDvéD švÁDvéD švÁDvéD švÁDvéDvÐDv  – švÁDvéDvÐDv – švÁDvéDvÐDv – švÁDvéDvÐDv – švÁDvéDvÐDv – švÁDvéDvÐDv – švÁDvéDvÐDv – švÁDvéDvÐDv – švÁDvéDvÐDv – švÁDvéDvÐDv 	– švÁDvéDvÐDv 
– švÁDvéDvÐDv – švÁDvéDvÐDv – švÁDvéDvÐDv 
– švÁDvéDvÐDv – švÁDvéDvÐDv –vóDvâDv  ˆiÿ‚þ "vv¾ÌüÿP–ÌóÿP–ÌÏÿP–   
þÿ
ýÿ
ûÿ

    But when I generate the TI-TXT hex file without using the ROMS directive (for individual projects) the hex utility tool outputs the following:

    @0000
AA 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 3F 00 F6 7F 34 00 3F 00 24 49 FF FF 10 88 
00 00 20 4E FF FF 11 88 00 00 00 00 FF FF 12 88 
00 00 00 00 FE FF 14 88 00 00 00 00 B4 42 FE FF 
16 88 00 00 00 40 7B 44 FF FF 1E 88 00 00 01 00 
FE FF 20 88 00 00 00 00 00 00 FE FF 22 88 00 00 
00 00 00 00 FE FF 28 88 00 00 14 48 3F 00 FE FF

    I'm not sure why this is happening. I know this text display format is correct because I can flash my program via the serial interface.

    In my hex utility command line I have the following line, "${CG_TOOL_HEX} ${BuildArtifactFileName} -boot -sci8 -a -o ${BuildArtifactFileBaseName}.txt", which I copied from this application note.

    Thanks!

  • 0 in reply to valeri Stoyanov
    TI__Expert 4880 points

    I would only need to select the "--load_image:combine_sections" to true? And in the ROMS directive you can specify an arbitrary memory address range?

    Yes, though there are some restrictions on what other options you can do when you use load_image, as documented in the Load Image Characteristics section.  However, if you need more assistance with this, one of our hex utility experts will be available next week and can address this in more detail.

    But when I generate the TI-TXT hex file without using the ROMS directive (for individual projects) the hex utility tool outputs the following:

    I would be curious what is in your ROMS directive; the TI-TXT format also has some restrictions, supporting 8-bit physical memory width and 8-bit ROM width. Anything that changes that could impact the output.

  • 0 in reply to Alan Phipps
    Prodigy 75 points
    Alan Phipps said:
    I would be curious what is in your ROMS directive; the TI-TXT format also has some restrictions, supporting 8-bit physical memory width and 8-bit ROM width. Anything that changes that could impact the output.

    I believe the memwidth and ramwidth parameters are ignored when using a TI-TXT format which is mentioned in the C28x assembly tools manual. I'm also not altering these parameters, so I don't think that is the issue.

     This is what is in my ROMS directive currently:

    Bootloader.out
Application.out

--image
--map hex.map
--ti_txt

ROMS
{
 FLASHA: org = 0x00004000, len = 0x2000
 FLASHC: org = 0x00006000, len = 0x2000
}

  • 0 in reply to valeri Stoyanov
    TI__Expert 4880 points

    You've noted your command line options; would it be possible to send us your executables as well so that we can try to reproduce what you're seeing?  

  • 0 in reply to Alan Phipps
    Prodigy 75 points

    Yes, I'm attaching my ccs project now.

    TI_help_query_w_hex_file.zip

    * Note that my hex.cmd file is located under Bootloader/Debug. I build the Bootloader project to generate my TI_TXT hex file.

    I have the following commands added in the hex tool:

        - command line :   "${CG_TOOL_HEX} ${BuildArtifactFileName} -boot -sci8 -a -o ${BuildArtifactFileBaseName}.txt"

        - command line pattern:   ${command} ${flags} ${output_flag} ${output} ${inputs}     ./hex.cmd

    And I have the following options selected in the hex tool:  

    --diag_wrap=off --ti_txt --load_image --load_image:combine_sections=true

    Let me know if you need anything more.

  • 0 in reply to valeri Stoyanov
    TI__Expert 4880 points

    OK thank you for providing this. FYI I will include one of our hex utility experts to assist, so it may be a few days before one of us comes back with a response.

  • 0 in reply to Alan Phipps
    TI__Guru**** 251230 points

    At the risk of greatly annoying you, I'm going to come at this a very different way.

    Please consider that this ...

    valeri Stoyanov said:
    I need to generate a single hex file that would contain both boot and application code

    ... might be the wrong approach.  Are you using C2000Ware, or some other similar package?  How do the examples in that package solve this problem?  However that works, it is likely to be the best solution.  I lack knowledge in this area, so I am unable to be of more help .  Let me know if you want to pursue this further.  If so, I will notify those experts about this thread.

    From this point on, I presume creating a single hex file is the overall best approach.

    Do it in two steps.  In the first step, create a single executable file.  Use a command similar to ...

    hex2000 --load_image -o combined.out application.out boot.out

    Then convert combined.out into a hex file.  Given what I know at this point, I don't see why you need a ROMS directive.

    valeri Stoyanov said:
    In my hex utility command line I have the following line, "${CG_TOOL_HEX} ${BuildArtifactFileName} -boot -sci8 -a -o ${BuildArtifactFileBaseName}.txt", which I copied from this application note.

    The options -boot -sci8 are needed only if you rely on the bootloader built-in to your device.  Is that the case?

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 75 points

    Hi George, 

    It's not annoying at all, thank you for the input. 

    George Mock said:
    Are you using C2000Ware, or some other similar package?  How do the examples in that package solve this problem?  However that works, it is likely to be the best solution.  I lack knowledge in this area, so I am unable to be of more help .  Let me know if you want to pursue this further.  If so, I will notify those experts about this thread.

    I'm indeed using C2000Ware package. I've not come about with any specific examples on how that is solved. The only information available is in the C28x assembly tools manual, but that only documents the "The Load Image Format (--load_image Option) ".

    George Mock said:

    From this point on, I presume creating a single hex file is the overall best approach.

    Do it in two steps.  In the first step, create a single executable file.  Use a command similar to ...

    hex2000 --load_image -o combined.out application.out boot.out

    Then convert combined.out into a hex file.  Given what I know at this point, I don't see why you need a ROMS directive.

    That is correct. I want a single hex file generated that would contain boot and application code. In the manual I linked before it specifies that a ROMS directive is required if you are using the --load_image Option. Also CCS does not allow me to build my project without a ROMS directive, if the --load_image option is selected.

    After running the command you suggested, this is what I generate in the combined.out file: 

      Úufv@         FLASHA              v                   @       FLASHC   @   @                          €       ªø                ? ‘A ? ºBÿÿ ˆ   þÿˆ      þÿˆ      þÿˆ  B? þÿˆ  B?     ›?  @v$@"vvÀ ýv€|iÿg>vÀ÷ÿviÿv6Aš›v,@v®@ "vvÀ¿V%U¿V%ªviÿ "vvÀ¿V)hviÿ þB—A–vÀCl"v v%vÌ€Æÿa"vþvA¦!’©€¦§a"v@ A’!Íàÿ¨Ê!–viÿv$@’Rý`"v¿ÿvB’RaR	`"vÍþ†ÿ¨Ê–vB’R`"vÌþ© –iÿ ÿ‚@v€vÀ€v‚þiÿ þC|B—A–"vv" Nlÿ¿vÀ0 0Íüÿ¨Ê0–B’2Íðÿ¨Ê2–iÿv$@4’Rý`v" C’Íÿ¿ÿ¨Ê–viÿ„þ "vv¾0 vÀ+ÌüÿP–       @ €    @ €                        @  €      @ viÿ þ"vv+  (ÿÿ!(ÿÿ"(ÿÿ#(ÿÿ$(ÿÿ%(ÿÿ&(ÿÿ'(ÿÿvvÿý8’A–9’A–:’A–;’A–<’A–=’A–>’A–?’A–v+ /@mšo š‚þiÿ "vvÀÿþþÿ   @ viÿ "vvÀ `ÿŸ `ÿŸ `ÿû  ûÿÿþviÿ "vvÀÿ¿ ÿNFiÿ@v€vÀ  ýÿ ûÿ ÿþviÿ "vvÀ@  @ÿßýÿ ûÿ ÿþviÿ ­(P iÿVVVæ @)v  )vv˜B RBa"v©(ºB¨(? 	aÿvºB)o ›©$ßl)¨$ߦ¡÷†$§¡	§©$c\ÿ;©Yß	 ìÿ©(ÿÿ¨(ÿÿ	a?ÿÿv4BvvšB©(ÿÿ¨(ÿÿ	aÿvÿÿo߽çg>¾Å©$ߨ$Xÿ÷`vuBvéA w o½²v ©Y ’
a«(ÿÿª(ÿÿ©(ÿÿ¨(ÿÿ«avÿÿv Åg>v a§¡’g>v a§g>vçA¾‹ v  ›B  €vXB@v €v @"vv¾ v¿ viÿv,B š þ> ÀB¨BÅg>‚þ ½²½ª½¢þ¤‚ ÑËZo­\)V¡£ˆÜ	¤\©ƒvXBBaDŠFƒvXBËZÙ¢’¡Têfˆþ¾‚¾†¾‹  R«¨¤Åa©ˆÞ…\‡| þÿ©ˆ¦a S
aÿ¨\¿vþÿ…’‡– þÿ…’‡– øÿ¤©  «(ÿÿª(ÿÿ«` š Ôo¤©Ä’¤©ÜvB v ¨ v ¨  V"vÀ¹)(h v ‘Aš   ? ö B ? ›B"vv*   Ìÿð© –ÌðÿP–ÌàÿP–ÿÿvö wiÿ ÃVÿÿ  ? øÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿv ? €                                                                                                                                                                                                                                             > MÆÿÿ     þÿ       þÿ       þÿ   "Æ> þÿ   "Æ>     ,> Àvðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V€â¾ ñÿvvvðÿ â½ 0æ B)V%v ovðÿ â½ 0æ B)V%v o~vÁÃ"vvÀ ýv€|iÿg>vÀ÷ÿviÿ~vÓÄš›~vÉÃ~vKÄ "vvÀ¿V%U¿V%ªviÿ "vvÀ¿V)hviÿ þB—A–vÀCl"v v%vÌ€Æÿa"vþvA¦!’©€¦§a"v@ A’!Íàÿ¨Ê!–viÿ~vÁÃ’Rý`"v¿ÿvB’RaR	`"vÍþ†ÿ¨Ê–vB’R`"vÌþ© –iÿ ÿ‚@v€vÀ€v‚þiÿ þC|B—A–"vv" Nlÿ¿vÀ0 0Íüÿ¨Ê0–B’2Íðÿ¨Ê2–iÿ~vÁÃ4’Rý`v" C’Íÿ¿ÿ¨Ê–viÿ„þ "vv¾0 vÀ+ÌüÿP–       @ €    @ €                        @  €      @ viÿ þ"vv+  (ÿÿ!(ÿÿ"(ÿÿ#(ÿÿ$(ÿÿ%(ÿÿ&(ÿÿ'(ÿÿvvÿý8’A–9’A–:’A–;’A–<’A–=’A–>’A–?’A–v+ /@mšo š‚þiÿ "vvÀÿþþÿ   @ viÿ "vvÀ `ÿŸ `ÿŸ `ÿû  ûÿÿþviÿ "vvÀÿ¿ ÿNFiÿ@v€vÀ  ýÿ ûÿ ÿþviÿ "vvÀ@  @ÿßýÿ ûÿ ÿþviÿ ­(P iÿVVVæ @)v  )v~v+Æ RBa"v©(Mƨ(> 	aþvMÆ)o ›©$ßl)¨$ߦ¡÷†$§¡	§©$c\ÿ;©Yß	 ìÿ©(ÿÿ¨(ÿÿ	a?ÿÿ~v­Åv~v-Æ©(ÿÿ¨(ÿÿ	aÿvÿÿo߽çg>¾Å©$ߨ$Xÿ÷`~vÆ~v†Å w o½²v€©Y ’
a«(ÿÿª(ÿÿ©(ÿÿ¨(ÿÿ«avÿÿv€Åg>v€a§¡’g>v€a§g>~v„ž‹ ½²½ª½¢þ¤‚ ÑËZo­\)V¡£ˆÜ	¤\©ƒ~vÑÅBaDŠFƒ~vÑÅËZÙ¢’¡Têfˆþ¾‚¾†¾‹  R«¨¤Åa©ˆÞ…\‡| þÿ©ˆ¦a S
aÿ¨\¿vþÿ…’‡– þÿ…’‡– øÿ¤© v  ~.Æ  €~vÑÅ@v €~vÃ"vv¾ v¿ viÿ š  «(ÿÿª(ÿÿ«` š Ôo¤©Ä’¤©Ü~vîÅ v€¨ v€¨  V"vÀ¹)(h v~ .Åš   >  À~ #Æ > .Æ"vv*   Ìÿð© –ÌðÿP–ÌàÿP–ÿÿvö wiÿ ÃVÿÿ  ? øÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿv ? €

    Interestingly, the content of that .out file is identical to what I'm seeing in the .txt hex file I'm generating. So perhaps that is an indicator the .out file is not converting into a hex file at all.... 

    Additionally, I'm not sure how to convert the generated combined.out file to into a hex file in TI_TXT format. Do you just replace the combined.out to combined.txt in the command you sent above? Is there a command available that would allow me to generate the hex file without this post-build step? 

    George Mock said:
    The options -boot -sci8 are needed only if you rely on the bootloader built-in to your device.  Is that the case?

    Yes that is correct. My final product would need to be downloaded and flashed via the SCI serial interface, and to accomplish that I need a single .hex file. 

    I'd like to pursue this further please, so maybe it's best to consult one of your experts on this topic.

    Thanks.

  • 0 in reply to valeri Stoyanov
    TI__Guru**** 251230 points
    valeri Stoyanov said:
    My final product would need to be downloaded and flashed via the SCI serial interface, and to accomplish that I need a single .hex file. 

    I lack the knowledge needed to understand whether this is the best overall solution.  

    valeri Stoyanov said:
    I'd like to pursue this further please, so maybe it's best to consult one of your experts on this topic.

    I agree.  I have notified those experts about this thread.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 75 points

    Hi, 

    Is there any update on this? 

    Thanks.