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.

TMS320F28P659DK-Q1: setting MPOST in TMS320F28P659DK

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

Tool/software:

I want to enable MPOST in my application.

I've set : 

with uniflash.

The diagnosis is working and all is ok.

Now I would like to create a .s19 file that includes the settings above.

I've added in .cmd file:

  OTP_Z1_GPREG2 : origin = 0x7800A, length = 0x00002
  DCSM_Z1_DIAG :    origin = 0x5F03E, length = 0x00002

  z1otp_gpreg2 : > OTP_Z1_GPREG2
  z1dcsm_diag : > DCSM_Z1_DIAG

and included an additional file with:

.sect "z1otp_gpreg2"
.retain
.long 0x5AFFFFBF ;Z1OTP_GPREG2

.sect "z1dcsm_diag"
.retain
.long 0x00000010 ;Z1_DIAG

the .s19 file seems correct, as i've the lines:

S20805F03E00100000B4
S20807800AFFBF5AFF4F

But when I try to load this file using uniflash I've the following:

 [WARNING] C28xx_CPU1: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map

Can you tell me what i'm doing wrong?

Many thanks

  • Thanks for reaching out to us on the E2E, if you build the project in CCS, and use it to load the corresponding .out file do you see this work or get the same error?

    Can you clarify the .s19 file extension, I'm assuming this is a format from the hex utility, but I'm not familiar with it.  I know the Uniflash tool accepts both .out and .hex; but I've not used the .s19.

    Best,

    Matthew

  • The .s19 file is a motorola hex file generated using Oput Format Options:

    in CCS.

    Even loading file with CCS it doesn't work

  • Barbara,

    I've looked into this some more, and both the flash tools in CCS and Uniflash will not attempt to program the security locations from the .out.  This was done out of abundance of caution so that our customers wouldn't accidentally enable CSM settings since they are in One Time Programmable regions of the flash memory.

    There are 2 options with our tools to program these locations:

    1)Utilize the GUI options to manually load these settings then "write" them with the associated button click in either flash tools(CCS) or in the Uniflash GUI itself

    2)Embed the flash API and these settings into a small program(or into your main application), and write them by invoking the Flash API during run time of the application.

    Best regards,

    Matthew