Tool/software:
Document source:https://www.ti.com/lit/an/spraca7a/spraca7a.pdf?ts=1731498442520&ref_url=https%253A%252F%252Fwww.bing.com%252F

result:


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.
Tool/software:
Document source:https://www.ti.com/lit/an/spraca7a/spraca7a.pdf?ts=1731498442520&ref_url=https%253A%252F%252Fwww.bing.com%252F

result:


After some internal discussion, there is a known issue with running HWBIST with reduced clock rate. Currently we are evaluating if we can support reduced clock rate for power savings or this needs to be removed as option.
For background, do you have power consumption concerns at full clock rate that don't allow to run HWBIST at full clock, or can you revert the code back to the original clock settings for HWBIST to run?
Best,
Matthew
I have restored HWBIST to the original clock settings, and it runs the HWBIST test normally. I still have some questions and would appreciate your feedback:
Currently we do not have conclusion if HWBIST can run at reduced clock rate on F280039 or any other C2000 device.
For #3, I think you are asking based on some of my earlier comments. I was not yet aware of this issue in general of reduced clock + HWBIST when I made that statement. This is not the root cause of this issue, so that is no longer valid problem.
I was speculating that if the watchdog was active, and HWBIST clock was slower, then perhaps accommodations had not been made to increase the WD timeout window. But again, this is not the reason HWBIST does not work with reduced clock rate.
Best,
Matthew
Part Number: TMS320F280039C
Tool/software:
In the previous post, I asked about clock division in HWBIST. I’d like to know if there are any new updates on this.