• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Subscribers 79 subscribers
  • Views 5924 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.

CCS/MSP430F1121: Generating TI.TXT file with MSP430-GCC in CCSv8

Nicole Ward
Intellectual 300 points
Part Number: MSP430F1121


Tool/software: Code Composer Studio

Hi,

I am trying ot generate a TI.TXT file for programming my part over BSL. The format I am using MSP430-GCC in CCSv8 but I have not been able to generate the correct format. I have tried using

Project->Properties->CCS Build->Steps(Tab), but I do not see the option (or it will not allow me to choose the TI.txt format).  Any tips on how to do this would be appreciated. Thanks, and apologies if this was already addressed. I could not find it.

Best Regards,

Nicole

  • 0
    TI__Mastermind 49692 points

    Hello Nicole,

    Thanks for your detailed post. Under the Project Properties, go to "Build" > "MSP430 Hex Utility [Disabled]". Click "Enable MSP430 Hex Utility", and there will be several menus that now appear under "MSP430 Hex Utility". Under there, click "Output Format Options" and in the "Output format" drop-down menu, click "Output TI-TXT hex format (--ti_txt)". Then, click "Apply and Close" at the bottom to save these settings.

    Hope this helps!

    Regards,

    James

    MSP Customer Applications

  • 0 in reply to James Evans
    Intellectual 300 points

    Hi James,

    Thanks for your response. As I mentioned before, I am using CCSv8 (I'm not sure if this matters), with the MSP430-GCC (GNU compiler) option. With this option, I am not seeing the same windows as you are when using the TI MSP430 Compiler. Have you seen this before? Do you have thoughts on how to fix it if possible. Please see my window below.

    Thanks,

    Nicole

  • 0 in reply to Nicole Ward
    Intellectual 300 points

    Hi James,

    Here is the picture I was referring to. It did not get attached previously.

    Best Regards,

    Nicole

  • 0 in reply to Nicole Ward
    Genius 4350 points

    If you don't find an answer, you're welcome to use a .vbs script I wrote to convert an Intel-hex file to a TI-TXT file.  Only works for 64K address space.

    https://github.com/gbhug5a/MSP430-BSL/tree/master/Intel-HEX-to-TI-TXT

  • 0 in reply to George Hug
    Intellectual 300 points

    Hi George,

    Thanks for this. I tried it, but I wasn't able to get it to work. I  got the error message below. What might I be doing wrong?

    Thanks,

    Nicole

  • 0 in reply to Nicole Ward
    Intellectual 300 points

    Hopefully the picture attaches this time.

  • 0 in reply to Nicole Ward
    Genius 4350 points

    That's the 64K limit.  Technically it's an Intel-hex Record Type other than 00 or 01,  Usually that's used for extended addresses or segments where the address space is more than 16 bits.  I don't know how Ti-Txt would deal with those, so I made the scipt error out if it encounters one.  But I'm curious why the F1121 would have such an intel-hex line.  Any chance you could post your intel-hex file, or the offending part?  The record type is the value following the beginning address of the data on the line.  It will be 00 for normal data, or 01 for the last line of the file.

    This example shows a file that has four data records followed by an end-of-file record:


    :10010000214601360121470136007EFE09D2190140
:100110002146017E17C20001FF5F16002148011928
:10012000194E79234623965778239EDA3F01B2CAA7
:100130003F0156702B5E712B722B732146013421C7
:00000001FF
           ^^
  • 0 in reply to George Hug
    Intellectual 300 points

    Hi George,

    The content of my Hex file is below. For some strange reason, the last few lines have white space (not sure if that may be causing the problem).

    Nicole

    :0CF0000000000000FFFF0000FFFF000008
    :10F00C00314000033C4000020D433E401200B01260
    :10F01C0054F33C4000023D409EF30D9C04243E40C2
    :10F02C000000B0121CF3B01282F30C43B0127EF14C
    :10F03C00344000F0354000F02643304068F0344056
    :10F04C0000F0354000F02643304068F0344000F0CA
    :10F05C00354000F03640FEFF304068F00594052442
    :10F06C0027440456A7121040F4FF30413C409EF355
    :10F07C003C909EF307243D4000000D9303243C403C
    :10F08C009EF38D1230410A123A409EF33A809EF361
    :10F09C000A110C4AB01268F20C5A0D4C0D110D935A
    :10F0AC0007243E4000000E9303243C409EF38E1236
    :10F0BC003A4130410A120912C293000217203A4019
    :10F0CC000AF03A8008F00A113A53394008F01C4211
    :10F0DC0002020C9A0D28B01278F03D4000000D93FE
    :10F0EC0003243C4000F08D12D2430002304062F207
    :10F0FC001C53824C02020C5C0C592C4C8C12304070
    :10F10C00DAF03E4000000E9305243D4004023C40E2
    :10F11C0000F08E12B01292F03041034330414E4356
    :10F12C004F430E9C03200F9D0120304103430343AA
    :10F13C001E530F6330402EF13CF0FF007D424C9388
    :10F14C000D34E2C329004C5C3CF0FF00D2C3290013
    :10F15C00D2D329003D530D93F2233041E2D3290041
    :10F16C00304052F1F2F0EFFF2100F2D010002100FC
    :10F17C0030410A120912081207120612B240805AC4
    :10F18C002001F240ACFF2100C2432900C2432600FB
    :10F19C00C2432E00F2432200F240F7FF2A00C24382
    :10F1AC002400C2432C00C2432500C2432D00F2D0E0
    :10F1BC0040002100374044F1384000304943F2F020
    :10F1CC007F0021005C4228007CF23CF0FF003A40BA
    :10F1DC002AF1364070F10C931224E2D22100F2F0A5
    :10F1EC007F002100D2C32100F2F0EFFF29000C4870
    :10F1FC000D498A12F2B22800F0233040CAF16C4259
    :10F20C0087128612D2D32100F2D0100029003C4084
    :10F21C0000064D438A125C422800F2D080FF210088
    :10F22C00E2D22100F2C221006C43871286123C40CC
    :10F23C0000034D438A125C4228007CF23CF0FF0034
    :10F24C00F2D22100E2C221003040E2F134413541DA
    :10F25C0036413741384139413A41304112C30C10E3
    :10F26C0012C30C1012C30C1012C30C1012C30C10CE
    :10F27C0012C30C1012C30C1012C30C1012C30C10BE
    :10F28C0012C30C1012C30C1012C30C1012C30C10AE
    :10F29C0012C30C1012C30C1030413D5312C30C108E
    :10F2AC000D93FB23304112C30D100C1012C30D1023
    :10F2BC000C1012C30D100C1012C30D100C1012C335
    :10F2CC000D100C1012C30D100C1012C30D100C10DD
    :10F2DC0012C30D100C1012C30D100C1012C30D1014
    :10F2EC000C1012C30D100C1012C30D100C1012C305
    :10F2FC000D100C1012C30D100C1012C30D100C10AD
    :10F30C0030413E5312C30D100C100E93FA233041B2
    :10F31C000D9C0A280F4C0E5C0E9F0D24EF4D000027
    :10F32C001F531D53304024F30F4D0F5E0C9FF22FD3
    :10F33C003E533E93012030410B4C0B5E0F4D0F5E44
    :10F34C00EB4F000030403CF30F4C0E5C0F9E012045
    :10F35C003041CF4D00001F53304058F30A123A4051
    :10F36C0004F02C4A3C9302203A4130418C123A5022
    :10F37C00FEFF30406EF3B0120EF1B01268F3B01213
    :10F38C004AF0B0123CF03041B01258F0B012C0F05C
    :02F39C003041FE
    :02FFFE000CF005
    :040000030000F00CFD
    :00000001FF

  • 0 in reply to Nicole Ward
    Genius 4350 points

    The problem is the next-to-last line, or as we say in Oklahoma, the penultimate line:

    :040000030000F00CFD

    The record type is 03.  According to Wikipedia that is::

    "03 Start Segment Address

    For 80x86 processors, specifies the initial content of the CS:IP registers. The address field is 0000, the byte count is 04, the first two bytes are the CS value, the latter two are the IP value.

    :0400000300003800C"

    So apparently you are trying to jump to 0xF000C after flashing by writing to the Program Counter.  Not sure why you would want to do that, but in the antepenultimate line you set the reset vector to that same address:

    :02FFFE000CF005

    so all you would have to do is reset after flashing using the +r specifier in BSLDEMO.  In any case, I know of nothing in the Ti-TXT protocol that is equivalent to that 03 record type.  You might try just removing that line, then running my script, and see if flashing the Ti-TXT file with +r gives you what you want.

    .

  • 0 in reply to George Hug
    Intellectual 300 points
    Hi George,

    As always, thanks again for your pointer. As you recommended, removed the penultimate line (I use that word too sometimes :)) and your script generated the TI.txt file. then I flashed the part with BSLDEMO, however I didn't use the +r specifier, and it programmed ok. I also checked the output and it appears to be correct. I want to try it once more, just to be sure, but I think this is it.

    Best Regards,
    Nicole
  • 0 in reply to Nicole Ward
    Genius 4350 points

    You're quite welcome.  I'm glad you've got it all working.  But it would have been nice if the TI guys had participated instead of giving you a bad answer and then marking it solved.  Just saying.

    Oh, and don't forget "antepenultimate" for those occasions when you want to appear particularly pretentious.

**Attention** This is a public forum