Paul Gortmaker | bd42bbb | 2009-09-18 19:08:46 -0400 | [diff] [blame] | 1 | Intro: |
| 2 | ====== |
Joe Hamman | 9e3ed39 | 2007-12-13 06:45:14 -0600 | [diff] [blame] | 3 | |
Paul Gortmaker | bd42bbb | 2009-09-18 19:08:46 -0400 | [diff] [blame] | 4 | The SBC8548 is a stand alone single board computer with a 1GHz |
| 5 | MPC8548 CPU, 8MB boot flash, 64MB user flash and, 256MB DDR2 400MHz |
| 6 | memory. It also has 128MB SDRAM 100MHz LBC memory, with both a PCI-e, |
| 7 | and a PCI-X slot, dual mini-DB9 for UART, and dual RJ-45 for eTSEC |
| 8 | ethernet connections. |
Joe Hamman | 9e3ed39 | 2007-12-13 06:45:14 -0600 | [diff] [blame] | 9 | |
Paul Gortmaker | bd42bbb | 2009-09-18 19:08:46 -0400 | [diff] [blame] | 10 | U-boot Configuration: |
| 11 | ===================== |
Joe Hamman | 9e3ed39 | 2007-12-13 06:45:14 -0600 | [diff] [blame] | 12 | |
Paul Gortmaker | bd42bbb | 2009-09-18 19:08:46 -0400 | [diff] [blame] | 13 | The following possible u-boot configuration targets are available: |
Joe Hamman | 9e3ed39 | 2007-12-13 06:45:14 -0600 | [diff] [blame] | 14 | |
Paul Gortmaker | bd42bbb | 2009-09-18 19:08:46 -0400 | [diff] [blame] | 15 | 1) sbc8548_config |
| 16 | 2) sbc8548_PCI_33_config |
| 17 | 3) sbc8548_PCI_66_config |
| 18 | 4) sbc8548_PCI_33_PCIE_config |
| 19 | 5) sbc8548_PCI_66_PCIE_config |
| 20 | |
| 21 | Generally speaking, most people should choose to use #5. Details |
| 22 | of each choice are listed below. |
| 23 | |
| 24 | Choice #1 does not enable CONFIG_PCI, and assumes that the PCI slot |
| 25 | will be left empty (M66EN high), and so the board will operate with |
| 26 | a base clock of 66MHz. Note that you need both PCI enabled in u-boot |
| 27 | and linux in order to have functional PCI under linux. |
| 28 | |
| 29 | The second enables PCI support and builds for a 33MHz clock rate. Note |
| 30 | that if a 33MHz 32bit card is inserted in the slot, then the whole board |
| 31 | will clock down to a 33MHz base clock instead of the default 66MHz. This |
| 32 | will change the baud clocks and mess up your serial console output if you |
| 33 | were previously running at 66MHz. If you want to use a 33MHz PCI card, |
| 34 | then you should build a U-Boot with a _PCI_33_ config and store this |
| 35 | to flash prior to powering down the board and inserting the 33MHz PCI |
| 36 | card. [The above discussion assumes that the SW2[1-4] has not been changed |
| 37 | to reflect a different CCB:SYSCLK ratio] |
| 38 | |
| 39 | The third option builds PCI support in, and leaves the clocking at the |
| 40 | default 66MHz. Options four and five are just repeats of option two |
| 41 | and three, but with PCI-e support enabled as well. |
| 42 | |
| 43 | PCI output listing with an intel e1000 PCI-x and a Syskonnect SK-9Exx |
| 44 | is shown below for sbc8548_PCI_66_PCIE_config. (Note that PCI-e with |
| 45 | a 33MHz PCI configuration is currently untested.) |
| 46 | |
| 47 | => pci 0 |
| 48 | Scanning PCI devices on bus 0 |
| 49 | BusDevFun VendorId DeviceId Device Class Sub-Class |
| 50 | _____________________________________________________________ |
| 51 | 00.00.00 0x1057 0x0012 Processor 0x20 |
| 52 | 00.01.00 0x8086 0x1026 Network controller 0x00 |
| 53 | => pci 1 |
| 54 | Scanning PCI devices on bus 1 |
| 55 | BusDevFun VendorId DeviceId Device Class Sub-Class |
| 56 | _____________________________________________________________ |
| 57 | 01.00.00 0x1957 0x0012 Processor 0x20 |
| 58 | => pci 2 |
| 59 | Scanning PCI devices on bus 2 |
| 60 | BusDevFun VendorId DeviceId Device Class Sub-Class |
| 61 | _____________________________________________________________ |
| 62 | 02.00.00 0x1148 0x9e00 Network controller 0x00 |
| 63 | => |
Joe Hamman | 9e3ed39 | 2007-12-13 06:45:14 -0600 | [diff] [blame] | 64 | |
| 65 | |
Paul Gortmaker | dd9ca98 | 2009-09-25 11:14:11 -0400 | [diff] [blame] | 66 | Updating U-boot with U-boot: |
| 67 | ============================ |
| 68 | |
| 69 | Note that versions of u-boot up to and including 2009.08 had u-boot stored |
| 70 | at 0xfff8_0000 -> 0xffff_ffff (512k). Currently it is being stored from |
| 71 | 0xfffa_0000 -> 0xffff_ffff (384k). If you use an old macro/script to |
| 72 | update u-boot with u-boot and it uses the old address, you will render |
| 73 | your board inoperable, and you will require JTAG recovery. |
| 74 | |
| 75 | The following steps list how to update with the current address: |
| 76 | |
| 77 | tftp u-boot.bin |
| 78 | md 200000 10 |
| 79 | protect off all |
| 80 | erase fffa0000 ffffffff |
| 81 | cp.b 200000 fffa0000 60000 |
| 82 | md fffa0000 10 |
| 83 | protect on all |
| 84 | |
| 85 | The "md" steps in the above are just a precautionary step that allow |
| 86 | you to confirm the u-boot version that was downloaded, and then confirm |
| 87 | that it was copied to flash. |
| 88 | |
| 89 | |
Paul Gortmaker | bd42bbb | 2009-09-18 19:08:46 -0400 | [diff] [blame] | 90 | Hardware Reference: |
| 91 | =================== |
Joe Hamman | 9e3ed39 | 2007-12-13 06:45:14 -0600 | [diff] [blame] | 92 | |
Paul Gortmaker | bd42bbb | 2009-09-18 19:08:46 -0400 | [diff] [blame] | 93 | The following contains some summary information on hardware settings |
| 94 | that are relevant to u-boot, based on the board manual. For the |
| 95 | most up to date and complete details of the board, please request the |
| 96 | reference manual ERG-00327-001.pdf from www.windriver.com |
| 97 | |
| 98 | Boot flash: |
| 99 | intel V28F640Jx, 8192x8 (one device) at 0xff80_0000 |
| 100 | |
| 101 | Sodimm flash: |
| 102 | intel V28F128Jx, 16384x8 (4 devices) at 0xfb80_0000 |
Paul Gortmaker | 3fd673c | 2011-12-30 23:53:07 -0500 | [diff] [blame^] | 103 | Note that this address reflects the default setting for |
| 104 | the JTAG debugging tools, but since the alignment is |
| 105 | rather inconvenient, u-boot puts it at 0xec00_0000. |
Paul Gortmaker | bd42bbb | 2009-09-18 19:08:46 -0400 | [diff] [blame] | 106 | |
| 107 | |
| 108 | Jumpers: |
| 109 | |
| 110 | Jumper Name ON OFF |
| 111 | ---------------------------------------------------------------- |
| 112 | JP12 CS0/CS6 swap see note[*] see note[*] |
| 113 | |
| 114 | JP13 SODIMM flash write OK writes disabled |
| 115 | write prot. |
| 116 | |
| 117 | JP14 HRESET/TRST joined isolated |
| 118 | |
| 119 | JP15 PWR ON when AC pwr use S1 for on/off |
| 120 | |
| 121 | JP16 Demo LEDs lit not lit |
| 122 | |
| 123 | JP19 PCI mode PCI PCI-X |
| 124 | |
| 125 | |
| 126 | [*]JP12, when jumpered parallel to the SODIMM, puts the boot flash |
| 127 | onto /CS0 and the SODIMM flash on /CS6 (default). When JP12 |
| 128 | is jumpered parallel to the LBC-SDRAM, then /CS0 is for the |
| 129 | SODIMM flash and /CS6 is for the boot flash. Note that in this |
| 130 | alternate setting, you also need to switch SW2.8 to ON. Currently |
| 131 | u-boot doesn't support booting off the SODIMM in this alternate |
| 132 | setting without manually altering BR0/OR0 and BR6/OR6 in the |
| 133 | board config file appropriately. |
| 134 | |
| 135 | |
| 136 | Switches: |
| 137 | |
| 138 | The defaults are marked with a * |
| 139 | |
| 140 | Name Desc. ON OFF |
| 141 | ------------------------------------------------------------------ |
| 142 | S1 Pwr toggle n/a n/a |
| 143 | |
| 144 | SW2.1 CFG_SYS_PLL0 1 0* |
| 145 | SW2.2 CFG_SYS_PLL1 1* 0 |
| 146 | SW2.3 CFG_SYS_PLL2 1* 0 |
| 147 | SW2.4 CFG_SYS_PLL3 1 0* |
| 148 | SW2.5 CFG_CORE_PLL0 1* 0 |
| 149 | SW2.6 CFG_CORE_PLL1 1 0* |
| 150 | SW2.7 CFG_CORE_PLL2 1* 0 |
| 151 | SW2.8 CFG_ROM_LOC1 1 0* |
| 152 | |
| 153 | SW3.1 CFG_HOST_AGT0 1* 0 |
| 154 | SW3.2 CFG_HOST_AGT1 1* 0 |
| 155 | SW3.3 CFG_HOST_AGT2 1* 0 |
| 156 | SW3.4 CFG_IO_PORTS0 1* 0 |
| 157 | SW3.5 CFG_IO_PORTS0 1 0* |
| 158 | SW3.6 CFG_IO_PORTS0 1 0* |
| 159 | |
| 160 | SerDes CLK(MHz) SW5.1 SW5.2 |
| 161 | ---------------------------------------------- |
| 162 | 25 0 0 |
| 163 | 100* 1 0 |
| 164 | 125 0 1 |
| 165 | 200 1 1 |
| 166 | |
| 167 | SerDes CLK spread SW5.3 SW5.4 |
| 168 | ---------------------------------------------- |
| 169 | +/- 0.25% 0 0 |
| 170 | -0.50% 1 0 |
| 171 | -0.75% 0 1 |
| 172 | No Spread* 1 1 |
| 173 | |
| 174 | SW4 settings are readable from the EPLD and are currently not used for |
| 175 | any hardware settings (i.e. user configuration switches). |
| 176 | |
| 177 | LEDs: |
| 178 | |
| 179 | Name Desc. ON OFF |
| 180 | ------------------------------------------------------------------ |
| 181 | D13 PCI/PCI-X PCI-X PCI |
| 182 | D14 3.3V PWR 3.3V no power |
| 183 | D15 SYSCLK 66MHz 33MHz |
| 184 | |
| 185 | |
| 186 | Default Memory Map: |
| 187 | |
| 188 | start end CS<n> width Desc. |
| 189 | ---------------------------------------------------------------------- |
| 190 | 0000_0000 0fff_ffff MCS0,1 64 DDR2 (256MB) |
| 191 | f000_0000 f7ff_ffff CS3,4 32 LB SDRAM (128MB) |
| 192 | f800_0000 f8b0_1fff CS5 - EPLD |
Paul Gortmaker | 3fd673c | 2011-12-30 23:53:07 -0500 | [diff] [blame^] | 193 | fb80_0000 ff7f_ffff CS6 32 SODIMM flash (64MB) [*] |
Paul Gortmaker | bd42bbb | 2009-09-18 19:08:46 -0400 | [diff] [blame] | 194 | ff80_0000 ffff_ffff CS0 8 Boot flash (8MB) |
| 195 | |
Paul Gortmaker | 3fd673c | 2011-12-30 23:53:07 -0500 | [diff] [blame^] | 196 | [*] fb80 represents the default programmed by WR JTAG register files, |
| 197 | but u-boot places the flash at either ec00 or fc00 based on JP12. |
| 198 | |
Paul Gortmaker | bd42bbb | 2009-09-18 19:08:46 -0400 | [diff] [blame] | 199 | The EPLD on CS5 demuxes the following devices at the following offsets: |
| 200 | |
| 201 | offset size width device |
| 202 | -------------------------------------------------------- |
| 203 | 0 1fff 8 7 segment display LED |
| 204 | 10_0000 1fff 4 user switches |
| 205 | 30_0000 1fff 4 HW Rev. register |
| 206 | b0_0000 1fff 8 8kB EEPROM |