2 SPEAr (Structured Processor Enhanced Architecture).
4 SPEAr600 is also known as SPEArPlus and SPEAr300 is also known as SPEArBasic
6 The SPEAr SoC family embeds a customizable logic that can be programmed
7 one-time by a customer at silicon mask level (i.e. not at runtime!).
9 We are now adding the support in u-boot for two SoC: SPEAr600 and SPEAr3xx.
11 All 4 SoCs share common peripherals.
13 1. ARM926ejs core based (sp600 has two cores, the 2nd handled only in Linux)
14 2. FastEthernet (sp600 has Gbit version, but same controller - GMAC)
17 5. NAND controller (FSMC)
24 Everything is supported in Linux.
25 u-boot is not currently supporting all peripeharls (just a few as listed below).
27 2. NAND controller (FSMC)
28 3. Serial Memory Interface
29 4. EMI (Parallel NOR interface)
40 make ENV=NAND (supported by all 4 SoCs)
41 - This option generates a uboot image that saves environment inn NAND
43 make CONSOLE=USB (supported by all 4 SoCs)
44 - This option generates a uboot image for using usbdevice as a tty i/f
46 make FLASH=PNOR (supported by SPEAr310 and SPEAr320)
47 - This option generates a uboot image that supports emi controller for
48 CFI compliant parallel NOR flash
50 Mac id storage and retrieval in spear platforms
52 Please read doc/README.enetaddr for the implementation guidelines for mac id
53 usage. Basically, environment has precedence over board specific storage. The
54 ethaddr beeing used for the network interface is always taken only from
55 environment variables. Although, we can check the mac id programmed in i2c
56 memory by using chip_config command