Other Parts Discussed in Thread: C2000WARE
When check the TRM of TMS320F28P650DK, see that the changes compared with F28386D, I want to know does this MPOST have the new application notes or performance data document ?

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.
When check the TRM of TMS320F28P650DK, see that the changes compared with F28386D, I want to know does this MPOST have the new application notes or performance data document ?

WZ,
We are aware that the MPOST application note needs to be updated for the newer devices for cycle counts and pass/fail info.
Since the algos are all memory size dependent, you should be able to scale the numbers accordingly from the ones in the app note https://www.ti.com/lit/spraci7
The MPOST signatures are in the BROM source here:
C:\ti\c2000\C2000Ware_5_01_00_00\libraries\boot_rom\f28P65x\rev0\rom_sources\cpu1\F28P65x_ROM\bootROM\include\cpu1brom_pbist.h
Relevant info for pass/fail codes from this file
// // ERROR CODES - Used as return values // #define PBIST_ALWAYSFAIL_TIMEOUT_ERROR 0xFF00FF00U // Expected fail test did not complete #define PBIST_ALWAYSFAIL_INCORRECT_OPERATION 0xFF11FF01U #define PBIST_DOUBLEINT_TIMEOUT_ERROR 0xFF22FF02U #define PBIST_MEMORYTEST_TIMEOUT_ERROR 0xFF33FF03U #define PBIST_MEMORY_TEST_FAIL_ERROR 0xFF44FF04U #define PBIST_MEMORY_TEST_IN_PROGRESS 0xFAAB1234UL // Return status while memory testing is in progress #define PBIST_MEMORY_TEST_PASS 0xFAABDEEDUL // Marker for successful completion of mem test
Best,
Matthew
WZ,
Let me check on the first question, if this is still supported in the current MPOST on this device vs F28004x device which the app note was written.
I'll try out the MPOST on the controlCARD here to see if I can duplicate. I've confirmed that address 0x8 should be correct to store the result, but will verify on HW.
Best,
Matthew
WZ, I have a controlCARD, but debugging the MPOST flow as well. Can you confirm the below:
1)MPOST will only run after a power on reset, not after normal XRSn based reset. Please confirm that you are looking at register 0x8 after Power On
2)This address region of M0 is reserved for BROM, but I am trying to verify if the MPOST status gets over-written if boot ROM continues past the MPOST into the normal boot flow. Can you comment on the boot mode you are using (boot pins state) for your system? would it be possible to change to wait boot to debug this issue?
Best,
Matthew
For the first question.
Yes, I checked the result after a power on reset.
When config
For the second question. You have a controlCARD, it is easy to reproduce. I also use the controlCARD to verify the MPOST.
Sorry, I did not get the inconvenient point from your side.
Due to I am not familar with boot mode, if need I to do this verification, i need to understand this know how of how to change the boot mode from boot pins to wait boot
WZ
Don't worry about the boot mode for now, I have confirmed that doesn't matter.
I'm also seeing 0x00000000, but I think MPOST is not running at all vs change in pass signature or different address. I'm debugging this with some others and hope to have an update in the next few days.
For F28P65x there looks to be additional register Z1_DIAG that also must have value in order to run MPOST; but I'm checking on this as well.
Best,
Matthew
WZ, Sorry for the delay here, I am waiting on a reply from our internal test team to clarify the correct procedure here for running MPOST. From the above it appears that the procedure is slightly different than outlined in the app note/TRM.
In addition to setting the Z1GPREG2, there is need to set the Z1DIAG register MPOST_EN field to "1". This has not been detailed thoroughly in our support documentation today.
However, I have done this locally on my controlCARD and I am not seeing MPOST run after power up as it should. There is some more debug needed on my side to get the MPOST to run, and then document those details. I will try and give another update by Thursday of this week.
Best,
Matthew
WZ, can you look at memory address 0x725E8 and let me know the value you see at this address? If possible can you also take a picture of the top of the device an post it to your reply? If you can't upload an image, you can just tell me the characters you see.
Best,
Matthew
WZ,
Thanks for doing this, this is the expected value.
When connected to the device, open the flash tools, and scroll down until you see Z1-DIAG. You want to program a value of 0x00000010 to this location. This, along with what you have already programmed to Z1GPREG2 will allow MPOST to run at power up.
Please try this and let me know if you see the MPOST status update corrected at address 0x0008 after power up.
Best,
Matthew
WZ thanks for doing this, I'm not sure why that did not work. The TRM is incorrect on the location of this Z1-DIAG it is actually part of the link table. so this can be modified many times, by incrementing the link pointer in the OTP.
Let me try again on my side to see if I can replicate.
Best,
Matthew
WZ,
When you open the flash tool, can you capture what it is reading back from the Z1GPREGx registers as well as the Z1-DIAG? Just want to make sure that is a known value here.
Best,
Matthew
WZ,
I've reproduced your issue on TMS silicon, i.e. MPOST is not running even with correct GPREG2/DIAG configs in OTP. I'm still investigating with our design team on the exact issue but for now I don't have a way to run MPOST on your device. Will keep you updated on the resolution here and path forward.
Best,
Matthew