Differences

This shows you the differences between two versions of the page.

--- gecko-platforms:gecko3_tester [2017/03/06 12:17] – external edit 127.0.0.1
+++ gecko-platforms:gecko3_tester [2021/12/20 10:49] (current) – external edit 127.0.0.1
@@ Line 13: / Line 13: @@
 We provide two different test configurations:
-  * {{:huce:microlab:projects:internal:gecko:gecko3_systems:gecko3tester:full-hw-test.bit.tar.bz2|}} tests all components and does full memory testing.\\ Use this for production test or if expect bad memory blocks. Runtime: ~ 15 minutes.
+  * {{:gecko-systems:gecko3_tester:full-hw-test.bit.tar.bz2|}} tests all components and does full memory testing.\\ Use this for production test or if expect bad memory blocks. Runtime: ~ 15 minutes.
   * FIXME - coming later <del>quick-hw-test.bit</del> tests all components with a short go/no-go test pattern.\\
 Runtime: 30 seconds.
@@ Line 23: / Line 24: @@
 ===== Test setup =====
-{{ :huce:microlab:projects:internal:gecko:gecko3main_tester.jpg?300|}}
+{{ gecko-systems:gecko3_tester:gecko3main_tester.jpg?300|}}
 ==== Required material ====
   * GECKO3 tester
@@ Line 210: / Line 212: @@
 **Note:**\\
-The GPIO pin numbering used by the test software is different than the normal system bus names. Refer to the [[:platforms:gecko3tester:start]] schematic to know which hardware pin has problems.
+The GPIO pin numbering used by the test software is different than the normal system bus names. Refer to the [[gecko-platforms:gecko3_tester]] schematic to know which hardware pin has problems.
 If a error on the system bus or on a memory chip is detected, most of the time you will get a bunch of errors after that. Always look for the first detected error and try to fix that. Afterwards do another test run.