Flashing the MCP750/74x0 Target System with the bootMonitor Image

See Chapter 5, Setting Up a Boot Server, for instructions on how to configure the boot server.

1. Copy the system image to the boot server.

   For example, on a Solaris host workstation:

   $ rcp bootMonitor.ROM boot_server:/tftpboot/

2. Check that you booted the target from the standard PPC-bug bank (B).

3. On the console output during the boot:

   Copyright Motorola Inc. 1988 - 1998, All Rights Reserved PPC1 Debugger/Diagnostics Release Version 4.2 - 11/03/99 HA RM03 COLD Start Local Memory Found =08000000 (&134217728) MPU Clock Speed =233Mhz BUS Clock Speed =67Mhz WARNING: Keyboard Not Connected Reset Vector Location : ROM Bank B ---> must be bank B !

4. Configure PPC-bug to download the correct system image:

   PPC1-Bug> niot Controller LUN =00?? Device LUN =00?? Node Control Memory Address =07F9E000? Client IP Address =129.xx.xx.xx? Server IP Address =129.xx.xx.xx? Subnet IP Address Mask =255.xx.xx.xx? Broadcast IP Address =129.xx.xx.xx? <- configure according to your network Gateway IP Address =0.0.0.0? Boot File Name ("NULL" for None) =chorus.mcpn750-pro1? bootMonitor.ROM Argument File Name ("NULL" for None) =? .

5. Download the bootMonitor image with PPC-bug:

   PPC1-Bug> nbh Network Booting from: DEC21140, Controller 0, Device 0 Device Name: /pci@80000000/pci1011,9@e,0:0,0 Loading: bootMonitor.ROM Client IP Address = 129.xx.xx.xx Server IP Address = 129.xx.xx.xx Gateway IP Address = 0.0.0.0 Subnet IP Address Mask = 255.255.255.0 Boot File Name = bootMonitor.ROM Argument File Name = Network Boot File load in progress... To abort hit <BREAK> Bytes Received =&1699840, Bytes Loaded =&1699840 Bytes/Second =&242834, Elapsed Time =7 Second(s) IP =00400000 MSR =00003040 CR =00000000 FPSCR =00000000 R0 =00000000 R1 =07F88000 R2 =00000000 R3 =00000000 R4 =00000000 R5 =49504C01 R6 =00007000 R7 =00400000 R8 =07FF9144 R9 =07FF8F44 R10 =07FF8F56 R11 =07FF9044 R12 =07FF9044 R13 =00000000 R14 =00000000 R15 =00000000 R16 =00000000 R17 =00000000 R18 =00000000 R19 =00000000 R20 =00000000 R21 =00000000 R22 =00000000 R23 =00000000 R24 =00000000 R25 =00000000 R26 =00000000 R27 =00000000 R28 =00000000 R29 =00000000 R30 =00000000 R31 =00000000 SPR0 =00000000 SPR1 =00000000 SPR8 =00000000 SPR9 =00000000 00400000 480004E8 B $004004E8

6. Program the flash memory with this system image:

   PPC1-Bug> pflash 00400000:&1699840 ff000000 ^ ^ ^ start addr of ROM BANK A | | size in bytes (decimal) of system image | addr where downloaded

   You should get something similar to:

   Source Starting/Ending Addresses =00400000/0059EFFF Destination Starting/Ending Addresses =FF000000/FF19EFFF Number of Effective Bytes =0019F000 (&1699840) Program FLASH Memory (Y/N)? y FLASH Memory Programming Complete

   ---

   Note -

   For MPCN765 targets, the ROM bank address is: f4000000

   ---

7. Power off the board, change the jumper setting to boot from ROM bank A, and then turn power in the board again.

   bootMonitor will start and download the system image from the server:

   ..... Booting Chorus ..... CORE: Floating Point unit enabled CORE: Vector unit (AltiVec) disabled ChorusOS r5.0.0 for PowerPC - Motorola MCP(N)750 (pvr 0x00088300) Copyright (c) 2001 Sun Microsystems, Inc. All rights reserved. Sun Proprietary/Confidential US Government Rights Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in the Chorus Software License Agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DRAS 252.227-7013(c)(ii) (OCT 1988), FAR 12.212(a)(1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. Sun Microsystems, Inc. Kernel modules : CORE SCHED_CLASS [ FIFO RR RT ] MEM_FLM KDB TICK ENV BLACKBOX LAPSAFE MUTEX PERF TIMEOUT LAPBIND DKI /cpu: sun:powerpc-(timebase,dec)-timer driver started /raven: sun:powerpc-(raven,hawk)-(bus,mngt,pci) driver started /raven: sun:pci-generic-pcimngr pseudo-driver started /raven/mpic: sun:(bus,powerpc)-openpic-(mngt,opic,timer,wdtimer) driver started /falcon: sun:powerpc-(falcon,hawk-smc)-(bus,mngt) driver started /raven/pci1106,3038@b,2: device node is created by sun:pci-enumerator- /raven/pci1106,3040@b,3: device node is created by sun:pci-enumerator- /raven/pci1011,9@e,0: device node is created by sun:pci-enumerator- /raven/pci1011,26@14,0: device node is created by sun:pci-enumerator- /raven/vt82c586-isa: sun:pci-vt82c586-(bus,isa) driver started /raven/vt82c586-isa/i8259: sun:bus-i8259-pic driver started /raven/vt82c586-isa/i8237: sun:bus-i8237-dma driver started /raven/vt82c586-isa/i8254: sun:bus-i8254-timer driver started /raven/vt82c586-isa/m48t559: sun:bus-m48txx-(nvram,rtc,wdtimer) driver started /raven/vt82c586-isa/m48t559: Hardware watchdog armed & started /raven/vt82c586-isa/ns16550/2: sun:bus-ns16550-uart driver started /raven/vt82c586-isa/z8536: sun:bus-z8536-gpio driver started /raven/vt82c586-isa/z85230/a: /raven/vt82c586-isa/z8536 GPIO device is connected /raven/vt82c586-isa/z85230/a: DTR signal is connected /raven/vt82c586-isa/z85230/a: DSR signal is connected /raven/vt82c586-isa/z85230/a: RI signal is connected /raven/vt82c586-isa/z85230/a: sun:bus-z85x30-uart device registered /raven/vt82c586-isa/z85230/b: /raven/vt82c586-isa/z8536 GPIO device is connected /raven/vt82c586-isa/z85230/b: DTR signal is connected /raven/vt82c586-isa/z85230/b: DSR signal is connected /raven/vt82c586-isa/z85230/b: RI signal is connected /raven/vt82c586-isa/z85230/b: sun:bus-z85x30-uart device registered /raven/vt82c586-ata/0,0: Model: SanDisk SDCFB-48 Serial: i121711030 Rev: Vdd 1.0. Unknown device type (config=0x844a) /raven/vt82c586-ata/0,0: Using Mode: PIO1. /raven/vt82c586-ata/0,0: sun:ata-atadisk-disk driver started /raven/vt82c586-ata: sun:pci-vt82c586-ata driver started /raven/pci1011,9@e,0: warning -- PHY is auto-detected at address 0x1 /raven/pci1011,9@e,0: 10BaseT (Twisted Pair) link auto-detected /raven/pci1011,9@e,0: Ethernet address 08:00:3e:2e:ff:51 /raven/pci1011,9@e,0: Rx buffers: 64*1520 Tx buffers: 64*1520 /raven/pci1011,9@e,0: sun:pci-dec21x4x-(ether,mngt) driver started /raven/pci1011,26@14,0: sun:pci-dec2115x-(bus,pci,mngt) driver started /raven/pci1011,26@14,0: sun:pci-generic-pcimngr pseudo-driver started /raven/pci1011,26@14,0/pci1011,46@c,0: device node is created by sun:pci-enumerator- /raven/pci1011,26@14,0/pci1011,46@d,0: device node is created by sun:pci-enumerator- /raven/mpic/timer@0: sun:(bus,powerpc)-openpic-(mngt,opic,timer,wdtimer) driver started /raven/mpic/timer@1: sun:(bus,powerpc)-openpic-(mngt,opic,timer,wdtimer) driver started /raven/mpic/timer@2: sun:(bus,powerpc)-openpic-(mngt,opic,timer,wdtimer) driver started /raven/mpic/timer@3: sun:(bus,powerpc)-openpic-(mngt,opic,timer,wdtimer) driver started /falcon/flashControl-1: sun:bus-(falcon,hawk-smc)-flash-ctl driver device started /falcon/flashControl-2: sun:bus-(falcon,hawk-smc)-flash-ctl driver device started /falcon/intel28F400: flash control is activated /falcon/intel28F400: sun:bus-intel28Fxxx-flash driver started /falcon/amd29F040: flash control is activated /falcon/amd29F040: sun:bus-amd29xxx-flash driver started TICK: using timer device /cpu, at 100 Hz Boot Monitor Loader v1.3 (env BOOTCONF) env BOOTCONF: 'RARP' *** booting using 'RARP' agent Unit: 0 device name: pci1011,9@e,0 Using unit 0 My IP 129.157.173.169, RARP Server IP 129.157.173.59 Loading file 819DADA9.ChorusOS.5.0 on server 129.157.173.59: loaded! Loading file chorus.RAM.bmon on server 129.157.173.59: loaded! Boot new system image ... ..... Booting Chorus .....

The ChorusOS system image is running on the target.

For information on what to do next, see About ChorusOS 5.0 Documentation, which will guide you to the appropriate information for your task.