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.

How to see what commands CCS runs to flash firmware?

Other Parts Discussed in Thread: UNIFLASH, MSP430F5310

I'm using CCS to develop for MSP430.  I believe CCS uses UniFlash to load firmware.  I would like to see the exact commands that are run when flashing, and to be able to duplicate these from the commandline.

Environment: CCS 6.0, Ubuntu 14.04LTS, MSP430F5310

  • Hello Gautam, Thank you for the pointers. This does explain a bit how to use uniflash, but doesn't tell me how CCS calls uniflash. I've tried to use uniflash from the commandline, and it works in some cases (not always), but it doesn't seem to be the same as when CCS flashes firmware. I thought finding out how CCS calls it is the easier approach to getting it to work, because that definitely works 100%
  • Alex Izvorski said:
     I believe CCS uses UniFlash to load firmware.  I would like to see the exact commands that are run when flashing, and to be able to duplicate these from the commandline.

    My understanding is that CCS and UniFlash are separate installations, and that CCS loads firmware without calling UniFlash.

    I believe CCS calls shared libraries in the ccs_base/DebugServer/bin directory to load firmware, rather than calling UniFlash from the command line. Therefore, it is not possible to automatically extract a UniFlash command line from when CCS loads firmware.

    What problem are you getting with UniFlash?

  • CCS and UniFlash are separate installations. However they both use the same debug engine underneath and the same flash programmer. I believe UniFlash 3.4.1 uses the same debug engine as CCSv6.1.2. The calls used to program flash should be the same between CCS and UniFlash. What is likely different is the emulation drives or device support packages between the two installations.

    Note that things with change with UniFlash 4 where the same debug engine as CCS will not be used. This will help reduce the installation size of UniFlash to make it more lightweight.

    Thanks
    ki