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.

TMS320F280025C-Q1: Download Problem (CCS, Uniflash)

Part Number: TMS320F280025C-Q1
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hello,

I am encountering an issue related to saving a voltage offset in a flash area that is locked with DCSM.
I have included DCSM_claimZoneSemaphore(DCSM_FLSEM_ZONE1); in the main function before initializing the flash API.
However, I am experiencing inconsistencies in how the voltage offset is retained across different programming and power cycles.

Specifically, I have observed the following behavior:

  1. When downloading the code via CCS using the debug button and executing it once with the run button, the voltage offset is correctly saved in the flash area.
  2. If I download the code through CCS, but do not execute it before turning off the power and turning it back on, the voltage offset does not persist indefinitely.
  3. When programming through Uniflash, the voltage offset does not persist indefinitely.

I would appreciate any insights into what might be causing this discrepancy and how I can ensure the voltage offset is reliably stored under all scenarios.

Thank you for your time and assistance.

Best regards,
Min Oh

  • Any comment would be appreciated.

  • Hello,

    Apologies for the delayed response. Note that after a device reset, the DCSM will become locked. If you have connected to the device via JTAG and you've specified DCSM passwords in the On-Chip flash tool or Uniflash in order to reprogram the device. The DCSM will be unlocked until the next device reset occurs. This may explain why you are unable to read the variable you have stored in flash under different conditions.

    Thank you,

    Luke

  • I need to determine the proper procedure for preserving the voltage offset in the DCSM area after downloading firmware via Uniflash.
    Our product is approaching its start of production, and it is critical that this issue be resolved promptly to ensure system integrity and performance.
    Could you please advise on the best practices or configuration steps required to retain the voltage offset data during the programming process?

    Thank you for your prompt assistance.
    I look forward to your expert recommendations.

  • Hi Seongmin,

    I believe the voltage offset value is being preserved in the DCSM area, the DCSM is simply being locked after a device reset. A reset can occur anytime you attempt to connect to the device or program the device if you have enabled reset before flash programming operations.

    When is it necessary to read the offset value? Is it your code that has to read this value or do you need to read it over JTAG? To read the value successfully, the DCSM needs to be unlocked, or the code performing the read of the value needs to be executing from a secured memory location.

    What resources have you already referred to to understand DCSM? I will look into how our collateral can be improved so that future users are less likely to encounter this issue.

    Thank you,

    Luke

  • Hi Luke,

    I have solved this issue by using different Flash Library.
    I have been using ROM version of Flash Library and have switched to Normal version of Flash Library.

    Thank you.
    Sincerely,
    Min Oh