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.

TMS320F28004x OTP and DCSM care abouts

Other Parts Discussed in Thread: UNIFLASH

Hi experts

Now we are going to imbed OTP program into our CCS project, by adding file f28004x_dcsm_z1otp.asm and 28004x_dcsm_lnk.cmd into the project.

The only two OTP registers we want to change are b0_dcsm_otp_z1_gpreg and b0_dcsm_otp_z1_bootctrl , which are used to configure boot mode pin.

The question is:

when we generate the app hex/out file from this project, will the OTP part also be integrated into the hex file?

What we expected is:

1. when we program the MCU first time with bootloader and app hex file with Uniflash, the OTP registers can also be changed to what we want.

2. when the MCU bootloader later update appl hex file, OTP registers are neglected and others are not influenced by it.

Now I though the second part is okay, and we want to make sure the first part.

Thank

linna

  • Hi Linna,

    It's recommended to start a new thread for new query so that each post is tracked properly.

    1. when we program the MCU first time with bootloader and app hex file with Uniflash, the OTP registers can also be changed to what we want.

    Yes, if have these assembly files included in your project and linker cmd file has the section defined, these values will be included in .out/hex file and OTP location will get programmed accordingly.

    Are you not seeing these getting programmed?

    Regards,

    Vivek Singh

  • linna,

    Following up from the TI side, I had split the thread to its own topic; wanted to make sure if there was still an issue on your side and you needed TI help.

    Best,

    Matthew