There is a less than 1 in 8 chance that your code is built in a way that will trigger the issue.
The issue was that an arbitrary value was being pulled from a null (address zero) pointer instead of a valid BYPASS instruction for the PS DAP.
There are 16 possible opcode values for the PS TAP and only 2 of the 16 can cause an issue.
To fix the issue apply the attached patch.
This issue is targeted to be fixed in the 2015.1 release.
|Name||File Size||File Type|