HOW TO DO A PROM MICROCODE INTEGRATIONAug 22, 1980Filed on: [Idun] HowToIntegrateProms.pressIntroductionYou can use this procedure to :- Blow some proms using the latest (i.e. most recent) PromMicrocode release. - Blow some proms using a specified PromMicrocode release. E.g. the Rev-K release. - Blow some proms using the current prerelease PromMicrocode . - Do a PromMicrocode Integration. Modify the current prerelease PromMicrocode, blowtest proms, and - after testing - save the modified microcode as the current version. Release versions of Prom files are stored in sub-directories designated by their revisionletter. As of Aug 22, 1980 : revision I is stored on [Idun]Proms>Rev-I> and revision K is stored on [Idun]Proms>Rev-K>Prerelease versions of Prom files are stored on [Idun].Libjects are used to provide librarian control of prerelease versions of the followingPromMicrocode files:Boot.mcD0CSProms.bcplEtherBoot.mcModel31Boot.mcPromDefs.mcSA4000Boot.mcCSLProm.cmTORProm.cmSDDProm.cmSPGProm.cmThis procedure is an interim hack until a better way to assign Processor IDs is created.1. Create a Prom DiskYou will need to create a Prom disk. The best thing to do is to start with a clean disk. Bootthe NetExec and type NewOs. Use the long installation dialog and erase the disk. To retrievethe files you will need to create a Prom disk,Always retrieve the following file: [Idun]Do.run If you want to use the latest released version , retrieve:bpX&%U` ZCq1 Upp REq Opqp qpq Kpq Hpqp q E!2`D*+ ?dpq4 = <\5 :1 7p q4 6KV 410 . - + * & %X # "P  J p q(5 BP . :$ pqpq  =XHow To Integrate Proms Aug 22, 19802 [Idun]Proms>Rev-latest>PromDisk.do If you want to use a specific release , retrieve: [Idun]Proms>Rev-I>PromDisk.do or [Idun]Proms>Rev-K>PromDisk.do If you want to use (or modify) the current prerelease version of the PromMicrocode,retrieve: [Idun]PromDisk.do Always Type: Do PromDiskThis procedure will prompt you for the name of a file server where it can get files(e.g., Iris, Isis).If you only want to blow proms (i.e. you don't want to modify prereeasePromMicrocode), go to step 7. 2. Check Out the Modules You Need to UpdateTo check out a module to edit, type a command of the form:Access "Reason"/r Module.mc/Owhere Reason is the reason for checking out the module and Module is the name of yourmodule. This command will retrieve the source.3. Edit Your Modules4. Assemble Your ModulesTo assemble all modules, type: @MicroAll5. Bind All ModulesTo bind all modules, type: @MicroDAllThis creates Boot.mb, which is input to the next step. fpqGp`q) ]npq Zf$XW^$ T3#pq RO L{ IP F$+/ D ?p'G >J 9w+ 6Kq:3  /M .q. )p $ !qt p vqK  7 =X2How To Integrate Proms Aug 22, 198036. Make MB File for PnewType:D0CSPromsThis program converts Boot.mb to a form acceptable to Pnew. The output file is namedProms.mb.7. Check Out the Processor IDThe processor ID is specified by the command line to Pnew. This is an interim hack to keeptrack of Processor IDs. Currently, Processor IDs are assigned as follows:CSL 0 - 4,999TOR 5,000 - 9,999SDD 10,000 - 19,999SDD 20,000 - 20,255 (first Dandelion Processor IDs)SPG 20,256 - ?You must check out the appropriate command file. Type one of the following:Access "ID"/r CSLProm.cm/OAccess "ID"/r TORProm.cm/OAccess "ID"/r SDDProm.cm/OAccess "ID"/r SPGProm.cm/OThis will check out the command file and retrieve it.8. Blow the C Prom. Use appropriate command file to run Pnew.The previous steps could have been done on any developement system. Step 8 and 9 mustbe done on a system with an attached Prom Blower. To blow the C Prom (the one thatcontains the Processor ID), type one of the following:@CSLProm@TORProm@SDDProm@SPGPromWhen the C Prom has been blown, you will end up in Bravo with this command file in thewindow. The Processor ID is specified by the number/W parameter. This is a decimalnumber. Increment this number by one and Put the file.It is very important that Processor IDs not be duplicated. Please keep the followingpoints in mind when blowing C Proms:Do not copy or duplicate the C Prom.Do not type "R" to Pnew to blow another Prom.It is OK to skip a few Processor ID numbers. If in doubt, skip one.Don't try to reuse Processor ID numbers when you blow a new revision level. Throwaway the old numbers and get new ones. fpqGp b ^q[ XT W REp Oq: MIJjHGbE)DZ A.K><:9w 6K5 1yp= .MqJ ,D +E6(&%# bO : Z6 /p4q $$T-)C '* ypq!` 2=]How To Integrate Proms Aug 22, 198049. Blow the G Prom. Use command file to run Pnew.To blow the G Prom, type:@GPromThe G Prom can be duplicated. Once you have one, it is easier to duplicate it than to runPnew each time.10. Checkin Your Processor IDYou must check in the command file that contains the Processor ID. This file is always leftwith the number of the next ID to be assigned. Type one of the following commands:Access CSLProm.cm/IAccess TORProm.cm/IAccess SDDProm.cm/IAccess SPGProm.cm/IIf you are just blowing some Proms, you are finished !If you are doing a Prom Integration, go on to steps 11 & 12.11. Checkin Your ModulesYou must check in each module that you have checked out to edit. For each module, type acommand of the form:Access Mumble.mc/Swhere Mumble is the name of your module. This copies the new source back to[Idun].12. Save Integration OutputIf you modified Prom microcode, save the output generated by this integration in[Idun] by typing:@Save fpqGp b1 ^q[ XR W REp Oq0+ M.$JjHGbE A p6 >< : 7q+- 6K3  /"4# .q )p &sq12< $! !|=F HELVETICA  HELVETICA 4m qj/ͩhowtointegrateproms.bravoFrandeenAugust 22, 1980 3:15 PM