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.

TMS320F280025: Can OTP configuration work with Uniflash Standalone Command Line?

Part Number: TMS320F280025
Other Parts Discussed in Thread: UNIFLASH

Dear Champs,

I am asking this for our customer.

The user reports that he can use the Uniflash (V6.3.0.3193) built-in GUI configuration for OTP setting like zero-pin boot.

However, he could not use the Standalone Command Line for OTP setting by calling one_time_setup.bat once and then dslite.bat for later programming.

Because this is related to OTP and one chip can be used to test once, it's not convenient for us field to test on our side.

Would you confirm if OTP configurations work with Standalone Command Line?

Wayne Huang

  • Wayne,

    I am assigning this to our CLI expert to help you.

    Thanks and regards,

    Vamsi

  • Wayne,

    OTP programming should work using CLI. Can you provide more details on what the customer is trying to do, what command they are running, and what error they are getting?

    Thanks,

    Ricky

  • Dear Ricky Lau,

    I sent the user's testing steps to you offline.

    Please help check if there is anything wrong.

    Wayne

  • Wayne,

    If you want to program Z1 GPREG and OTPBOOTCTRL before loading the program, you will need to add the following to the command (-b Z1GPREGProgram - b Z1OTPBOOTCTRLProgram).

    You can do this by opening the generated dslite.bat in a text editor and updating the "set GENERATED_COMMAND=" section and adding the "-b Z1GPREGProgram -b Z1OTPBOOTCTRLProgram" part.

    Or you can run dslite.bat with the full command:

    > dslite.bat -c <pathToCcxmlFile> -l <pathToSettingsFile> -b Z1GPREGProgram -b Z1OTPBOOTCTRLProgram -e -f -v <pathToImageFile>

    Let me know if you have any questions on this.

    Thanks,

    Ricky

  • An additional bug was found after additional debugging, where the values of setting files via the -l command is being overwritten. A bug has been filed for tracking this issue, and it is currently targeted for the next UniFlash release in October.

    In the mean time, users can use the -s command to set the setting values instead.

    For example:

    > dslite.bat -c <pathToCcxmlFile> -s Z1B0OTPGPREG1="12345678" -s Z1B0OTPGPREG3="AABBCCDD" -b Z1GPREGProgram -b Z1OTPBOOTCTRLProgram -e -f -v <pathToImageFile>

    Additionally, we are also looking at enhancing the CLI generation feature to be able to select operations you want to do before and after a program load, so that users don't have to manually add the -b and -a commands after generating the package. No planned date is available for this feature at this time.

    Thanks,

    Ricky