• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 80 subscribers
  • Views 2097 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.

MSP430F6638: BSL-Scripter Intel Hex Extended

Stefan Huseyinoff
Prodigy 110 points
Part Number: MSP430F6638
Other Parts Discussed in Thread: MSP430F5659

I have just started working on a custom bootloader for my MSP430F6638 design and am looking at using the BSL-Scripter software.  Using the IAR IDE I usually generate an extra output file in intel-extended format for device programming.  It seems the BSL-Scripter does not support the extended format as I get the following error: [ERROR_MESSAGE]Record type is not valid for the Scripter!

I am able to get the scripter working with the intel-standard format which is fine for small programs that just reside within the 16bit address space.  However for larger programs needing to be programmed in 32bit address space the Intel-Extended option needs to be used.

I am just wondering if there are there any plans for the BSL-Scripter to support the Intel-Extended format in the near future?

  • 0
    TI__Guru**** 219677 points
    Can you please provide the hex image that produces the error? I am alerting our BSL-SCRIPTER experts so that they can further address your inquiry.

    Regards,
    Ryan
  • 0 in reply to Ryan Brown1
    Prodigy 110 points

    Hi Ryan,

    Please find the hex file attached.  It was created with the latest version of IAR. Output Format: intel-extended, Format variant: None.  The hex code 0x02 (Extended segmet address) looks to not be recognised.

    This was just a simple test program I wrote to flash a LED and receive a command to launch the BSL.

    TEST_CODE_1.zip

  • 0 in reply to Stefan Huseyinoff
    Guru 34773 points

    And here is 512 KByte P1.0 blink example for MSP430F5659, generated by IAR in txt / hex format...

    C:\msp430>flash -e -f test_msp430f5659.hex -ws -f test_msp430f5659.txt -v

    Found SBW+ at COM23

    Get Device
    # JTID Fuse Device Core Hard Soft LotWafer DieX DieY
    0  91   OK   3081  2106  10   10  B7A50951 0A00 1100

    Erase
    Time: 35 ms

    File: "test_msp430f5659.hex"
    Address: 08000  Words: 262144
    Size: 524288 bytes
    Time: 42 ms

    Write Smart
    Time: 2604 ms  Speed: 196,6 KB/s

    File: "test_msp430f5659.txt"
    Address: 08000  Words: 262144
    Size: 524288 bytes
    Time: 46 ms

    Verify
    Time: 2330 ms  Speed: 219,7 KB/s

    Release Device

    Total Time: 5117 ms

    C:\msp430>

    test_msp430f5659.zip

  • 0 in reply to Stefan Huseyinoff
    TI__Intellectual 2460 points

    Hi Stefan, Hi Zrno,


    thank you for reaching us. I received your hex-file and you are right, the BSL-Scripter 3.2.x handles the Record type of:

    00 - data

    01 - end of file

    04 - extended linear address only


    There is a thread regarding the record type 03 before, and this is actually setting the PC register with certain address. Using the BSL, you can instead use the SET_PC or SET_PC_32 to setup the PC register.

    Looking to the firmware image you created, the first line is :020000020000FC, which actually means the extended address is 0. if you remove this line, the next line is executed correctly since the first address being programmed is 0x8000. But when we reach the address above the 0xFFFF, this will bring problem again because it has the record type 02.

    I would like to try to generate the some firmware image using the intel-standard output instead of intel-extended. I'll get back to you soon once I get the result.

  • 0 in reply to Fatmawati_Santosa
    TI__Intellectual 2460 points

    Hi Stefan, Hi Zrno,

    I come back again with some results here:

    1. Using IAR for MSP430 version 6.40, I chose the Intel-Standard output, and this should generate the record data 04 instead of 02. If the IAR you are using does not have the option for intel-standard, could you please here mention the version of the IAR, so we use the same version and I can reproduce your case.
    2. Using IAR for EWARM MSP432 version 8.11, I chose the Intel-extended output, since this is only the available option (captured in the attachment), the Intel hex file that I got from the build also using the 04 instead of 02, so I am able to download it using BSL-Scripter.

    Please let me know if you still face failure on this. And apologize for my late response, since tomorrow until May 7th 2017, I am out of office.

  • 0 in reply to Fatmawati_Santosa
    Prodigy 110 points
    I am using the latest 7.10.1. There is the option for Intel-Standard and this works fine. I have successfully got the BSL working on the MSP-TS430PZ100USB board with an FTDI USB converter.

    I am however now facing another problem with the BSL-Scripter and COM1. I have added the details to a similar post:
    e2e.ti.com/.../2174944

**Attention** This is a public forum