Mv0212 Supported Boot Modes - Intel Movidius MV0212 User Manual

This is parncularly relevant for the BOOT1, BOOT2 and BOOT3 pins. These pins have an alternate funcnon
on the COMMON_IO bus which is a set of pins shared with the AP/LCD and camera connectors. Their
funcnon is determined by the daughtercards they are connected to. As such this would normally create a
constraint for daughtercard designers. The MV0212 design removes this restricnon by using a muex on these
pins. This muex ensures that the GPIOs are connected to the boot confguranon only unnl the rising edge of
reset. Once reset is high the boot confguranon has already been latched and the muex then connects the
GPIO to its "Alternate Funcnonn. This simplifes daughtercard design.
OTE: During reset COM_IO_1, COM_IO_2,COM_IO_3 are foanng so daughtercard designs should
account for this.
3.1.2

MV0212 Supported Boot Modes

The MV0212 platorm supports selecnon of the GPIO confgured boot modes of the MA2450 SoC using DIP
Switches 8,7,6,5,4 and 3. As the MA2450 part on the MV0212 board does not have eFuses confgured the
WAKEUP DIP Switch should always be in the "OFF" state to select GPIO confgured boot mode.
Please see the Myriad2 Soc User Manual for full details on the supported boot modes.
The following table illustrates the subset of GPIO confgured boot modes which are supported by the
MV0212 board.
Boot Boot
Mode Mode
BOOT_CO TROL
umber Type
0ex2 USBD
0ex6 DEBUG_
2
HALT
0ex7 SPIME_
24bit
0exC SPIM_2
4bit
0exD SPIS
2 The DEBUG_HALT boot mode is mainly useful for troubleshoonng. It does not confgure the PLL, it just enables all
clocks and then goes into an infnite loop.
Intel Movidius Confdennal
DIP[2] DIP[3]
WAKEUP
OFF OFF
OFF OFF
OFF OFF
OFF OFF
OFF OFF
Table 4: MV0212 Boot tonfguraton Optons
16
DIP[4..8]
OFF,OFF,OFF,ON,OFF
OFF,OFF,ON,ON,OFF
OFF,OFF,ON,ON,ON
OFF,ON,ON,OFF,OFF
OFF,ON,ON,OFF,ON
User Manual (MV0212-UM-1.2)
otes
USB Device Boot
Doesn't boot from any
interface
Onboard fash memory
in fast boot mode
Onboard fash memory
in slower boot confg
Boot from eexternal AP
connected to the SPI
Slave interface using the
LCD/AP connector