Posted on August 31, 2004 at 11:59Hi Kuni,
Normaly the dvp3 hardware test is stable but according to your application configurations changes (mcu option, mapping...) it may fails, I explain :
1) The hardware test of the dvp3 is made to be OK with the default debugger & target configuration : default mapping, default mcu options (watchdog soft, frequency set to 16Mhz for the mdt20 for instance ...). So if, according to your workspace settings, you have, for instance, turn an area from RAM to NEM and if this space is used by the hardware test, it may fails. If, as a secon example, you use an external frequency in your workspace and that you launch the hardware test AND if your external frequency is too high (out of spec for instance..) it may fails, in the other hand, with it basic 16Mhz if must successed.
2) The hardware test must be run only without any connections to the application.
In summary, to be stable, the hardware test must :
1) be always run with the same mcu & mapping configurations, and to be OK it must be launched with the default mcu & mapping configuration, the best way to do that is to launch debugger without loading any workspace.
2) be always run without any connections to application.
If, even with this way to do, it does not return same result in same conditions
: it is totally abnormel and please keep me informed
regards.
--Richard
