FAST ROM TEST
Original Publication Date: 1999-Sep-01
Included in the Prior Art Database: 2002-Aug-30
Kerstin Harenberg: AUTHOR [+1]
Save time after restart of program by doing the ROM test not at every restart. This paper describes improvements in the field of ROM tests at powerup.
MOTOROLA Technical Developments
FAST ROM TEST
by Kerstin Harenberg and Michael Weyrich
Save time after restart of program by doing the ROM test not at every restart.
This paper describes improvements in the field of ROM tests at powerup.
PROBLEM(S) TO BE SOLVED
Normally a ROM test is done after every startup of the software. The ROM test at startup takes a long time depending on the range of memory. Often the user waits for a reaction of the software (e.g. startup tone or display action on powerup of a radio). Therefore the ROM test is often not done at all.
Doing the ROM test on each startup is not nec- essary because the probability of a ROM error is very low.
PROPOSED SOLUTION TO THE PROBLEM(S)
Solution 1: The ROM test is only done on first startup after programming the firmware. After com- pleting the test successfully, the result is saved at a defined byte of the EEPROM. On following startups this byte is checked and if the byte indicates that the test has been done, the ROM test will not be execut- ed again.
Solution 2: The ROM test is only done at a pre- defined number of startups. On the first startup after programming the fiiware, a byte in the EEPROM is set to $01.
This indicates that the test has been done suc- cessfully. On each startup of the program this byte is checked and compared to a predefined number of startups. If this number is reached the ROM-test will be executed and the value is set to $01 again, other- wise the va...