• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 83 subscribers
  • Views 196 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.

TMS320F28388D: TMS320F28388S

Swati Gangopadhyay
Prodigy 60 points
Part Number: TMS320F28388D
Other Parts Discussed in Thread: UNIFLASH, C2000WARE

Tool/software:

During FW upgrade of binary generated from hex sci command in Linux from c2000 serial utility(customized as per our need), it is giving VERIFY ERROR. Although it is giving successful message in Flash Erase and after the load Program also. When checked in UniFlash Memory View the memory address 0x80000 (which is starting address) shows value as FF. 

Earlier the binary was getting generated from CCS 12.0.0.00009 and c2000 toolchain version was 4_02_00. Now the CCS version is upgraded to 12.5.0 and c2000 toolchain is upgraded to 4_05_00 and binary is generated in Linux environment. The size of the binary has increased from 187KB to 191KB.

What can be the issue as memory map looks ok?

  • 0
    TI__Genius 15040 points

    Hi Swati,

    If the memory value at 0x80000 is seen as 0xFF, did other parts of the program download to Flash appropriately or are they also showing 0xFF? 0x80000 is usually where you see the codestart address for the application as default.

    What alignment is being used to generate the Flash Application in the linker command file, ALIGN(4) or ALIGN(8)?

    Thanks and regards,

    Charles

  • 0
    Prodigy 60 points

    Hi Charles, sorry for the delay in response. For other parts of the program also it is showing 0XFF and the alignment is set ALIGN(8) in the linker file. Also, the upgraded ccs version is 12.7(not 12.5) and c2000 ware version is 5.00(not 4.05)

  • 0 in reply to Swati Gangopadhyay
    TI__Genius 15040 points

    Hi Swati,

    Swati Gangopadhyay said:
    binary is generated in Linux environment. The size of the binary has increased from 187KB to 191KB.

    When performing the firmware update, are you sending a .txt file to the device? Are you able to generate a binary on Windows and compare the success of transmission?

    What do the Build->C2000 Hex Utility properties look like for the project? Are you able to set the Post-Build steps mentioned in Serial Flash Programming of C2000 Microcontrollers application note?

    Thanks and regards,

    Charles

  • 0 in reply to Charles Roberson
    Prodigy 60 points

    Hi Charles. No we are sending .bin file generated from the post-build step in .cproject file of the project: 

    postbuildStep=""${CG_TOOL_HEX}" "${BuildArtifactFileName}" -boot -sci8 -a -o "${BuildArtifactFileBaseName}.bin""
    The binary is generated in WSL environment. 
  • 0 in reply to Swati Gangopadhyay
    TI__Genius 15040 points

    Hi Swati,

    The Serial Flash Programmer accepts files in the .txt format. 

    Thanks and regards,

    Charles

  • 0 in reply to Charles Roberson
    Prodigy 60 points

    Hi Charles as mentioned earlier we have taken reference from the serial programmer and customized it for our use for embedded device.

  • 0 in reply to Swati Gangopadhyay
    TI__Expert 6545 points

    Hi Swati,

    Are you using your own custom bootloader to receive and program the data received over SCI? Or are you using a project from C2000Ware? Either way, please verify that the data being sent by the host matches what is being received by the target. It sounds like the device is receiving some data but there could be some error in the formatting of the image being sent/received. I recommend using xxd or something similar to compare the contents on your bin file and a .txt file generated using the default post-build steps highlighted in the serial flash programming app note. 

    Kind regards,

    Skyler