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/TMS320F28377S: F28377S can be programmed using uniFlash but not CCS6.2

Part Number: TMS320F28377S
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

Dear TI Tech support,

Could you help me on this issue: Why I failed to program F28377S flash under CCS6.2

I created a F28377S binary (.out) code under CCS6.2.

1) under CCS6.2,  using BH-USB560 v2 System Trace emulator, when I tried to program the DSP, I got the following error message (see below).

2) under CCS6.2,  using XDS100v2 emulator, when I tried to program the DSP, I got the same error message (see below).

3) under uniFlash, using XDS100v2 emulator,  the flash can be programmed successfully (see below).

Boot Selection pins on my control board were configured as wait mode: GPIO84 = 0 (pull_down 5k) ; GPIO72 = 1 (pull_up 10k) .

In CCS, the Target Configuration File was set accordingly when BH-USB560 v2 System Trace or XDS100v2 was used.

I also tried other emulators like BH-USB2000 and BH-USB510L, the issue remains same.

Thank you.

Keith

 

Under CCS6.2

C28xx_CPU1: GEL Output: 
Memory Map Initialization Complete
C28xx_CPU1: Error during Flash programming (Flash algorithm returned error code). Operation cancelled.
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: C:\workspace\xwpro_porting_debug\PfrmB_XWP_6848-120_240-60\Base\Software\Code\SolarWave\Bin\ReleaseNoLoader\XWP.out: Load failed.
C28xx_CPU1: Error during Flash programming (Flash algorithm returned error code). Operation cancelled.
C28xx_CPU1: Please make sure the memory location you are programming have not already been programmed.
C28xx_CPU1: Error during Flash programming (Flash algorithm returned error code). Operation cancelled.
C28xx_CPU1: Please make sure the memory location you are programming have not already been programmed.

Under uniFlash

[5/18/2018, 9:32:50 AM] [INFO] C28xx_CPU1: GEL Output: Memory Map Initialization Complete

[5/18/2018, 9:35:28 AM] [SUCCESS] Program Load completed successfully.

[5/18/2018, 9:38:45 AM] [INFO] C28xx_CPU1: GEL Output: Memory Map Initialization Complete

[5/18/2018, 9:38:46 AM] [INFO] C28xx_CPU1: Erasing Flash memory...

[5/18/2018, 9:38:53 AM] [SUCCESS] C28xx_CPU1: Operation completed successfully.

[5/18/2018, 9:42:00 AM] [INFO] C28xx_CPU1: GEL Output: Memory Map Initialization Complete

[5/18/2018, 9:44:39 AM] [SUCCESS] Program Load completed successfully.

  • Keith,

    Can you try CCSv8?  On-chip Flash Plugin is updated for new features and bug fixes.  

    UniFlash has the latest updates in it - which worked for you.

    Thanks and regards,
    Vamsi

  • Hi Vamsi,

    Thank you for your email.

    Our projects (with multiple dependency projects) were built under CCS6x.
    I can try CCSv8. However my question is: Can CCSv8 open my projects (built by CCSv6x) with no conflicts?

    Thank you.
  • Keith,

    I asked CCS team to help you on this.

    Thanks and regards,
    Vamsi
  • Keith,

    I would expect that CCSv8 will be able to import and open the projects without any issues - I recommend to de-risk this migration attempt by working with a copy of the projects. In the unlikely event that you do come across some migration problems we would be happy to help you.

    Martin
  • Hello Martin,

    Thank you for your support.

    I installed CCSv8 and I can open and compile/build my projects created under CCS6.2 now. 

    This is good.

    Now I have one more question: since I have configured the Boot Selection pins on my control board to wait mode: GPIO84 = 0 (pull_down 5k) ; GPIO72 = 1 (pull_up 10k), have do I boot the code into flash at power up ?

    Thank you.

    Keith

  • Keith,

    Please check Table 3-3. Device Default Boot Modes in Chapter 3 (ROM Code and Peripheral Booting) of the TRM.

    Thanks and regards,

    Vamsi  

  • Hi Vamsi,

    I set the Boot Config pins to the GetMode (IO84/72 = 1/1).

    Now the DSP can boot to Flash with the emulator disconnected. I am happpy with this.

    However, whenever I modify the firmware and try to program the flash again, I have to set the boot config pins back to the WaitMode (IO84/72 = 0/1).

    My questions:

    1) Is there a solution that will not require change the boot pins back and forth to support both the flash programming and power up to flash?

    2) I used F28377D for long time. Why F28377D deos'nt needed the WaitMode to program the flash?

    TI cliamed that D and S are compitable. That is why we changed the D to S to save the cost. Do you have any advices that will deal with the F28377S flash programing (our app requires upgrade firmware in field) ?

    Thank you.

    Keith

  • Keith

    You should be seeing this same requirement for F28377D. It is possible that your F28377D was getting an ITRAP and getting stuck in an ITRAP loop which would result in the same behavior as being in wait boot.

    Best regards
    Chris
  • Keith

    Regarding your question #1, if you plan on using JTAG, when you startup the device with JTAG connected and no emulation key is programmed, the device will go to wait boot.

    Best regards

    Chris

  • Hi Chris,

    What do mean by "when you startup the device with JTAG connected" ?

    You mean "turn on the power" or "start the CCS" ?

    Thank you.

    Keith 

  • Keith

    I mean when you connect a JTAG debugger to your device and reset the device via CCS, it will go to wait boot since the behavior changes to that described in the emulation boot flow.

    Best regards
    Chris
  • Hi Chris and TI tech supporters,

    I think my platform (F28377S + CCSv8) is working OK now. 

    Thank you very much for the help.

    Keith