1 Matrix Vision mvBlueLYNX-M7 (mvBL-M7)
2 -------------------------------------
6 The mvBL-M7 is a 120x120mm single board computing platform
7 with strong focus on stereo image processing applications.
9 Power Supply is either VDC 12-48V or Pover over Ethernet (PoE)
10 on any port (requires add-on board).
15 Freescale MPC8343VRAGDB CPU running at 400MHz core and 266MHz csb.
16 512MByte DDR-II memory @ 133MHz.
17 8 MByte Nor Flash on local bus.
18 2 Vitesse VSC8601 RGMII ethernet Phys.
19 1 USB host controller over ULPI I/F.
20 2 serial ports. Console running on ttyS0 @ 115200 8N1.
21 1 SD-Card slot connected to SPI.
22 System configuration (HRCW) is taken from I2C EEPROM.
25 A miniPCI Type-III socket is present. PCI clock fixed at 66MHz.
28 Altera Cyclone-II EP2C20/35 with PCI DMA engines.
29 Connects to dual Matrix Vision specific CCD/CMOS sensor interfaces.
30 Utilizes another 256MB DDR-II memory and 32-128MB Nand Flash.
33 2x8 Outputs : Infineon High-Side Switches to Main Supply.
34 2x8 Inputs : Programmable input threshold + trigger capabilities
35 2 dedicated flash interfaces for illuminator boards.
36 Cross trigger for chaining several boards.
40 MAX5381 DAC @ 0x60 for 1st digital input threshold.
41 LM75 @ 0x90 for temperature monitoring.
42 EEPROM @ 0xA0 for system setup (HRCW etc.) + vendor specifics.
43 1st image sensor interface (slave adresses depend on sensor)
45 MAX5381 DAC @ 0x60 for 2nd digital input threshold.
46 2nd image sensor interface (slave adresses depend on sensor)
50 reset vector is 0xFFF00100, i.e. "HIGHBOOT".
53 FF802000 redundant environment
54 FF804000 u-boot script image
55 FF806000 redundant u-boot script image
56 FF808000 device tree blob
57 FF80A000 redundant device tree blob
63 FFF80000 FPGA raw bit file
65 mtd partitions are propagated to linux kernel via device tree blob.
69 On startup the bootscript @ FF804000 is executed. This script can be
70 exchanged easily. Default boot mode is "boot from flash", i.e. system
73 This behaviour depends on some environment variables :
75 "netboot" : yes ->try dhcp/bootp and boot from network.
76 A "dhcp_client_id" and "dhcp_vendor-class-identifier" can be used for
77 DHCP server configuration, e.g. to provide different images to
80 During netboot the system tries to get 3 image files:
81 1. Kernel - name + data is given during BOOTP.
82 2. Initrd - name is stored in "initrd_name"
83 3. device tree blob - name is stored in "dtb_name"
84 Fallback files are the flash versions.