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/MSP430G2744: MSP430Flasher programmer hex report issue Exit: 59 # ERROR: File type could not be identified

Part Number: MSP430G2744
Other Parts Discussed in Thread: MSP430F2272, MSP-FET

Tool/software: Code Composer Studio

Hi,

As test to build to create pal.hex to programmer into MSP430G2744 board,  I get MSP430Flasher programmer hex report issue Exit: 59 # ERROR: File type could not be identified. 

I tested other pal_good.hex file is OK.  why the CCS6.2.0 build the pal.hex can't burned into chip?Thanks!

I Inset the pal_good.hex and pal_bad.hex as zip.pal.zip

Below is the logs of MSP430Flasher:

D:\TI\MSPFlasher_1.3.17>MSP430Flasher.exe -n MSP430F2272_G2744 -w pal.hex -v -z [VCC]
* -----/|-------------------------------------------------------------------- *
* / |__ *
* /_ / MSP Flasher v1.3.16 *
* | / *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ COM19 <- Selected
* Initializing interface @ COM19...done
* Checking firmware compatibility:
* FET firmware is up to date.
* Reading FW version...
* Debugger does not support target voltages other than 3000 mV!
* Setting VCC to 3000 mV...done
* Accessing device...done
* Reading device information...done
* Loading file into device...
# Exit: 59
# ERROR: File type could not be identified
* Starting target code execution...done
* Disconnecting from device...done
*
* ----------------------------------------------------------------------------
* Driver : closed (No error)
* ----------------------------------------------------------------------------
*/

  • Hi Ray,

    could you please which Hardware interface you use to communicate with the MSP430G2744 target device? Is it the MSP-FET?
    Also, how did you generate the two different pal.hex files? Are you using TI tools and generate the file from CCS? What's the difference between those? Were both generated with the same CCS version and on the same PC?
    Can you confirm that both files follow the standard Intel Hex format?

    We'll try internally to reproduce the error and provide a solution. In the meantime please share the details I've asked for with my questions, this might help to troubleshoot what's wrong here.

    Thanks and best regards,
    Britta
  • I took a look at his hex files, and I believe "good" and "bad" are named backwards.  "Bad" appears to be a legitimate hex file, and it goes through my hex2txt.vbs utility with no problem.  However, "good" is completely corrupt.  The lines look like this:

    %4E646800008000D2B320001620F2404B001803C293D6031F203C405894B0123093D243D603B012
    %4E66D8000080206E81F2E080001D00B0129081B0128A920F3CC293D6030C24C29318030920C243
    %4E63C800008040D603F240190018033C406294B0123093E2B220001620F2404B001903C293D703
    %4E64D8000080601F203C406A94B0123093D243D703B0126E81F2E020001900B0129081B0122292
    %4E6638000080800F3CC293D7030C24C29319030920C243D703F240190019033C407494B0123093
    %4E67A8000080A0F2B080FF18001620F2404B001A03C293D8031F203C407C94B0123093D243D803

    instead of:

    :20800000....etc.

    So it's not in hex file format.  And that's why it didn't work.

  • Ray Liu,

    can you comment on what George indicated. George's answer is very well aligned with our internal feedback also.
    Could you please check and verify the given answer?

    Thanks and best regards,
    Britta
  • Maybe some configuration of CCS is wrong, the issue is fixed as use the before setting. thanks!