Specifications

6
Board-level updates for the ATCA-45xx CPM and RTM
62
Customize the RTM FRU data during an update
IfyouneedtocustomizeRTMFRUdata,thecustomizationcanbeaccomplishedduringthe
FRUupdateprocessbyspecifyingthe
‐‐fulloptionfortheupdatefrucommand.
rmcpta‐h<ShelfIPAddress>
targetfwd<CarrierIPMBAddress><RTMIPMBLAddress>
updatefru<RTMFRUUpdateFile>backup.bin‐full
ThisisasampleoftheFRUupdateprompts,withtheselectedoptionsshowninbold:
ReadingintheFRUdataupdatefile...
DecodingthetemplateFRUdata...
RetrievingthecurrentdeviceFRU0data..................................
Backingupthedatatofilebackup.bin...
DecodingthecurrentFRUdata...
MergingtheFRUinformation...
Enterbyteforheaderformatversion(old=0x01,template=0x01)0x01
Enter0x01tochoosethedatafromthedevice.
Enter0x01tochoosethedatafromthesuppliedtemplatefile.
Note:Bothvaluescanbe0x01,dependingonthedeviceandfileheaderformatversion.
Inputdata:
000001.
Isthiscorrect?[yes/no]yes
Enteryesifthedataiscorrect.
Internaluseareadataondevice:
None
Internaluseareadataintemplate:
None
0Olddata,1Templatedata,2Enterdata
Selectdatatouse:
Enter0tochoosethedatafromthedevice.
Enter1tochoosethedatafromthesuppliedtemplatefile.
Enter
2toenteryourowncustomizedFRUdata.
Additionalsimilarpromptsfollow,butarenotshownhere.Followtheinstructionsinthe
promptsandenterthecustomizedFRUdata.
Note:ItisimportanttoenteranyrequireddataintheFRUmultirecordareasduringRTMFRU
customization.IncompleteFRUmultirecorddatacanproduceRTMinitializationpr oblems.
ThefollowingisanexampleofFRUmultirecords:
ProductExtra:
OEM(0xRadisysCorporation)Record
PICMGExtensionRecord
FRU_AMC_CURRENT
PICMGExtensionRecord
FRU_AMC_P2P
PICMGExtensionRecord
UnknownOEMExtensionRecordID:2d