Hi Kevin, thanks for the quick reply. Since test sequence is done at our customer's (contract manufacturer) place (they produce/test their customer's boards and I am part of the company that is providing the JTAG test equipment - GOEPEL electronic), I will involve the CM for more details. What I know is that the whole test sequence is part of a functional test system that includes a JTAG test and programming equipment. Somewhere in the middle of the sequence we do a Boundary Scan test and afterwards DSP programming. Many test cycles are resulting ok, just a minor part shows the problem and we need to find out what is causing the trouble since the boards are expensive and replacing the DSPs is not allowed for security reasons. So, we were hoping to get more information based on the values that are read from the CSMSCR register (0041H and 0047H). Yesterday I was browsing the forum for other and maybe similar cases but did not find much useful information. We understand that such behaviour most likely is caused by a interrupting situation during erase or programming of the devices. And we are aware of the two facts that you mentioned above... Also, afaik, there are no passwords programmed during that test sequence (will double check). What makes the situation a bit more strange is that both DSPs are mocated in the same scan chain, together with TI documentation (using TI-API functions) we found a way to handle this situation and program both devices after each other. Strange is that both devices seem to be locked (at least on one board DSP1 showed the 0041H value, the other DSP2 showed 0047H). Maybe that information can lead to the root cause? Best Regards Jan
↧