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.

UNIFLASH: Uniflash does not generate scripts correctly

Part Number: UNIFLASH

I have a uniflash project from whom I want to generate a standalone package. Since it is programming an otp section I do not want to verify because this is not possible due to a known UNIFLASH issue. So i deselct the "Verify flash after programming" Checkbox and select Erase and Program.

However the batch script that is created does select the -v switch which stands for "verify". IMHO this is a bug in the generator.

Please take a look at this TI

BR Andreas

  • Hi Andreas,

    Your option for deselecting "Verify flash after programming" should be preserved in the generated.ufsettings file, and the settings would be loaded before executing your command. This should turn off the flash based verification during program load.

    As you noted, the -v command is added to the command line package right now, and this command will perform a simple memory comparison between the program you loaded and the memory on device. If this is causing an issue in OTP, you will need to manually remove the option in the generated script for now. Alternately, you can also override the entire command when calling dslite if needed.

    We are looking into adding more customization for the generated CLI package in future UniFlash releases, which should hopefully improve this use case.

    Thanks,

    Ricky

  • OK thanks for the reply. At least we can work around. But as you mentioned UNIFLASH definitly needs a sharp look and a refactoring regarding the CLI generator.
    BR Andreas