blob: e3fcb4eb1bc6319e83fb13cd7d045b21169d2859 [file] [log] [blame]
Andre Schwarz5e0de0e2008-07-09 18:30:44 +02001Matrix Vision mvBlueCOUGAR-P (mvBC-P)
2-------------------------------------
3
41. Board Description
5
6 The mvBC-P is a 70x40x40mm multi board gigabit ethernet network camera
7 with main focus on GigEVision protocol in combination with local image
8 preprocessing.
9
10 Power Supply is either VDC 48V or Pover over Ethernet (PoE).
11
122 System Components
13
Wolfgang Denk699f0512008-07-15 22:22:44 +0200142.1 CPU
Andre Schwarz5e0de0e2008-07-09 18:30:44 +020015 Freescale MPC5200B CPU running at 400MHz core and 133MHz XLB/IPB.
16 64MB SDRAM @ 133MHz.
17 8 MByte Nor Flash on local bus.
18 1 serial ports. Console running on ttyS0 @ 115200 8N1.
19
202.2 PCI
21 PCI clock fixed at 66MHz. Arbitration inside FPGA.
22 Intel GD82541ER network MAC/PHY and FPGA connected.
Wolfgang Denk699f0512008-07-15 22:22:44 +020023
Andre Schwarz5e0de0e2008-07-09 18:30:44 +0200242.3 FPGA
25 Altera Cyclone-II EP2C8 with PCI DMA engine.
26 Connects to Matrix Vision specific CCD/CMOS sensor interface.
27 Utilizes 64MB Nand Flash.
28
292.3.1 I/O @ FPGA
30 2 Outputs : photo coupler
31 2 Inputs : photo coupler
32
332.4 I2C
34 LM75 @ 0x90 for temperature monitoring.
35 EEPROM @ 0xA0 for vendor specifics.
36 image sensor interface (slave adresses depend on sensor)
37
383 Flash layout.
39
40 reset vector is 0x00000100, i.e. "LOWBOOT".
41
42 FF800000 u-boot
43 FF840000 u-boot script image
44 FF850000 redundant u-boot script image
45 FF860000 FPGA raw bit file
46 FF8A0000 tbd.
47 FF900000 root FS
48 FFC00000 kernel
49 FFFC0000 device tree blob
50 FFFD0000 redundant device tree blob
51 FFFE0000 environment
52 FFFF0000 redundant environment
53
54 mtd partitions are propagated to linux kernel via device tree blob.
55
564 Booting
57
58 On startup the bootscript @ FF840000 is executed. This script can be
59 exchanged easily. Default boot mode is "boot from flash", i.e. system
60 works stand-alone.
61
62 This behaviour depends on some environment variables :
63
64 "netboot" : yes ->try dhcp/bootp and boot from network.
65 A "dhcp_client_id" and "dhcp_vendor-class-identifier" can be used for
66 DHCP server configuration, e.g. to provide different images to
67 different devices.
68
69 During netboot the system tries to get 3 image files:
70 1. Kernel - name + data is given during BOOTP.
71 2. Initrd - name is stored in "initrd_name"
72 3. device tree blob - name is stored in "dtb_name"
73 Fallback files are the flash versions.