Hardware » Awaria

h1. Wiki

There are some issues that can only be tested via power resets.

* SPI has an issue that it needs retries
* Looks like configuration I2C EEPROM gets reset to defaults
* RTC-offline-test (Wie lange haelt die RTC Batterie)

The device has an CANBus in and an CANBus out. The testsoftware is on the DUT. The DUT sends the command to toggle power line to Awaria via CAN.
The switch-off time has to be an parameter. The RTC-Tests will be complex, the Awaria software shall be simple and generic.

An data multiplexer can be used along with a mosfet for power line.

Optionally controll it via USB from PC, not MCU. Optically isolated GPIOs.

h1. Parts

* MCU: The smallest thing
* Multiplexer:
** MC14551BDG bis zu 1K RON: 1050
** TS5A23166DCUR cool, 2 channels, up to 100mA, 1,8-6,5V
** Habe:
*** DG408LEDQ-T1-GE3; .#273; 1:8
*** DG409LEDQ-T1-GE3; .#321; 1:8
*** ADG736; .#315; 2x1:2
*** *RS2102XN ADG836YRMZ* Das ist er

* Big EEPROM, device can store test info from DUT

Spannungs/Strom zu umstaendlich.



h1. RTC-Tests

Can have a region in SPI-Flash.
If the Settings are not ok, just have an terminal.
The test can only be started from terminal.
rebootTest <startTime>

Start.
* Cut 2 Seconds. Time OK?
* Cut 4 Seconds. Time OK?
* Cut 8 Seconds. Time OK?

When it fails, "destroy" test-config in spi flash

h1. Connectors

* CANBus-In
* CANBus.Out
* Power in
* Power out
* USB PC to MCU
* USB PC to DUT