Products
Knowledge
This webpage doesn't work with Internet Explorer. Please use the latest version of Google Chrome, Microsoft Edge, Mozilla Firefox or Safari.
require 3 characters or more.
The information presented in this cross reference is based on TOSHIBA's selection criteria and should be treated as a suggestion only. Please carefully review the latest versions of all relevant information on the TOSHIBA products, including without limitation data sheets and validate all operating parameters of the TOSHIBA products to ensure that the suggested TOSHIBA products are truly compatible with your design and application.
Please note that this cross reference is based on TOSHIBA's estimate of compatibility with other manufacturers' products, based on other manufacturers' published data, at the time the data was collected.
TOSHIBA is not responsible for any incorrect or incomplete information. Information is subject to change at any time without notice.
require 3 characters or more.
Answer
The answer to this question varies depending on your system configuration.
One way of finding out the cause of a malfunction is by using test tools.
The following shows an example of the procedure for malfunction analysis.
1) Set a breakpoint at the point where the malfunction occurred.
2) Execute the program to verify whether the execution results (trace data) match the expected values.
3) Verify whether the input/output values up to the breakpoint match the expected values.
4) If no problem is found in the above steps 2) and 3), the malfunction may have been caused by hardware. In this case, use test tools to directly control SFRs, etc. and verify hardware operation.
It is also possible to analyze a malfunction by preparing a simplified version of the program and verifying program operation.
(NO.ED9901101 2011/10/21)