Scanlab RTC6 PCIe Board - Page 914

RTC6 boards
Doc. Rev. 1.0.21 en-US
16 Appendix A: The RTC6 Ethernet Board
914
innovators for industry
16.7.6 Automatic Booting – Process in
Detail
(1) After a Hardware Reset, the RTC6 Ethernet Board
tries to read data for automatic booting from the
NAND Memory.
(1)
During this time the yellow LED flashes dimmed
with approx. 1 Hz until the end of the
initialization.
– Case 1: There are no data present (after
store_program( Mode = 1 )) or
set_eth_boot_control( 0 ) has been carried
out.
The initialization is completed without these
data. Afterwards, the RTC6 Ethernet Board is in
“Normal PC Operation State”, page 908.
– Case 2: There are only data for
“Standalone Basic State“, see page 800 (after
store_program( Mode = 0 )). The RTC6 Ethernet
Board is initialized (as by load_program_file).
Afterwards, it is immediately ready for
PC operation = “Standalone Basic State“.
– Case 3: There are also data for
“Standalone Full State“, see page 800 (after
store_program( Mode = 2 )). Then step 2 is
executed.
(2) The RTC6 Ethernet Board
– switches on the BUSY Pin
– reads the “remaining” data for automatic
booting to “Standalone Full State“, see
page 800) from the NAND Memory.
(1)
– The subsequent boot steps 3...6 are two-phase.
(3) In Boot Phase 1 (duration: some seconds):
– The correction file(s) are read out
– Boot Phase 1-control commands are executed
(in the order in which they have been saved).
If such commands are stored more than once,
they are executed correspondingly often, with
newer data overwriting older data.
(4) After Boot Phase 1:
(1)
– Initialization ceases
– The BUSY Pin is switched off
– Do not switch the laser on yet!
– Switch on scan systems and other peripheral
devices
– Make sure peripheral devices are ready for
operation. Only then, trigger Boot Phase 2 by
an /START
– If your peripheral devices are always ready for
operation after a certain time, you can specify a
waiting time ( TimeOut) with the
Boot Phase 1-control command
eth_boot_timeout. After its expiry,
initialization continues automatically (=
without an explicit /START). With an /START
within the waiting time, Boot Phase 2 starts
immediately. Outside the waiting time, an
/START is ignored as long as Boot Phase 2 is still
running (see BUSY Pin!) The /START is
automatically enabled (similar to
set_control_mode( Bit #0 = 1)). Further
/STARTs after an /STOP must be enabled by
users themselves by
set_control_mode( Bit #3 = 1).
(1) Status == 1 of eth_get_standalone_status