The Analog Tests switch between two modes, Current (Amps) and Voltage. If a port is failing it is beneficial to know if it is only in one mode or if it is in both modes.

Once a test has switched to a Failed test result status it stays at that status until the board or Tests are reset. This is intentional to make sure we catch intermittent failures. To make it easier to tell if a test is intermittently passing, the test results will also show the results of the last test, Pass or Fail.

Unexpected Board Resets or Power Cycles on a controller are a bad thing. Prior to this change the 5226 could reset due to power or hardware issue without an obvious method of detection. Unless someone is present to see the heartbeat LED or the Web Page Test counter reset, it could easily get missed.

One the Web Page, in the More Information column of the SW Version row, the controller will display, in RED, "A Board Reset or Power Cycle has occurred!!!" after any reset. A new button labeled "Clear_Reset" has been added to clear this text at the beginning of a new board Test.

Clearing the text at the start of a new board test and checking for it at the end should allow us to detect boards that may have intermittent reset problems.

The intermittent resets are known to have been happening on the Hardware Test. The same bug has the capacity of causing resets on the Production software.

The K60 and K66 arm processors we use on 5226 boards both have a RAM segment boundry at address 0x20000000. If any memory operation spans that address, it can cause a processor Busfault, which ultimately ends up causing the processor to reset.

The K60 BSP library had protections enabled to prevent any software from using anything spanning that address. The K66 BSP did not.

The protection is to (Memory Leak) allocate memory at that address that is never used, which prevents any variable or data from spanning that address.