Add Target to Farm

Note:Original Steps located in Workspace/Target Farm Sharepoint/Add Target to Farm

Due to the nature of our work, a general, one-size-fits-all Deos target installation procedure is impossible. That being said, a typical procedure is provided below.

Create a name for the target (TName). Naming convention is: Deos + <the name the manufacturer gave the hardware or customer's code name if customer hardware> + [if more than one "-n" where 'n' is a number]. For example, we have two NXP T1042D4 RDB boards: DeosT1042D4RDB-1 and DeosT1042D4RDB-2.

Once a name is choosen, perform the following:

1. Keep the Target Farm Sharepoint up to date.
   1. Take ESD precautions and ensure hardware is or has been photo'd and logged into the Target Farm Sharepoint (i.e., either DDC-I Hardware or Loaner Hardware, as appropriate). Take enough photos so that all items received can be identified and repackaged.
   2. If the hardware is loaned out or returned, update the Target Farm Sharepoint. If additional supplies are delivered (adapters, cables, power supplies), take pictures, add to Target Farm Sharepoint and make a note of the date and what changed.
   3. If another example of the same hardware is received, create a new entry for that hardware in the database, make it number 2, 3, etc.
2. Clearly Label the box(s) the hardware came in for storage or later return to owner. If multiple boxes label TName Box 1 of N, TName Box 2 of N, etc. Store the boxes noting location in the Target Farm Sharepoint.
3. Place Target on an ESD safe shelf in the farm affixing a TName label to the target and a magnetic sticker on the shelf below the target.
   1. Some targets may not need to be on an ESD mat, typically those are completely enclosed targets that have thier own grounding through a power cable, or seperate grounding strap.
   2. In either case, always wear ESD strap when handling any items in the farm.
4. Plug target into a NetBooter port and take note of the IP address and port number for later use.
   1. Some targets require multiple NetBooter ports (i.e. Target Power, Emulator Power, Relay Switch)
   2. If target power cannot be cycled via directly removing and applying power to its power supply, another solution, e.g. a "reset button relay" (hardware), or target's BIOS setting or jumper change may be needed.
5. Select and place a Host computer near the target for serial and emulator connections (i.e. TFHostXX).
   1. IT requests that all hosts have the NinjaRMMAgent installed, even on customer supplied hosts. Verify already installed, or with IT and install this (i.e. \\NX3000\utils\tools\NinjaRMM Agent\Win).
      1. When it is a customer supplied host, note any login information required on the Farm Wiki.
   2. Connect serial port to host machine, note which serial port if hard wired. If USB serial determine which COM port is assigned by the host.
      1. Sometimes USB Serial doesn't just-work. Opening device manager, right-clicking the machine and scanning for HW changes may be what's needed.
      2. Installing or updating the FTDI driver (for USB Serial) may also be required.
      3. If USB Serial still doesn't work, it may be that the host machine has had multiple USB Serial targets attached over time. A remedy to this may be to unplug all USB Serial connections, then:
         1. DeviceManager->View->Show Hidden Devices, delete all COMs above the physical COMs, (i.e. COM4 and up)
         2. Plug the USB cable back in, check device manager and do a scan for HW changes if not automatically detected.
6. Optional: If requested select and connect an emulator and cable to target and host machine.
   1. Move or Make magnetic label for the emulator and place on shelf in front of emulator.
7. Add target to X9 using the following information:
   1. Target Name TName
      1. Add comment to include the targets physical location on the Farm
         1. (i.e. Location:Rack2-2B) Racks are 1-3 starting at the door, -2 is for Shelf 2, A is the verticle near wall, B is near main walkway.
      2. Add comment describing the targets architecture and any other useful information. (i.e. Emulator, if attached, must be on).
      3. Add attribute Cable:<Cable Number>, otherwise set the Cable attribute to Cable:None
      4. Add attribute Emulator:<name of emulator>, otherwise set the Emulator attribute to Emulator:None
      5. Add attribute Host:<hostname> where serial port and emulator are connected>
      6. Add attribute IP:TBD
      7. Add attribute Serial denoting host's COM port and settings, e.g. serial:COM4_115200_8_N_1_N
      8. NetBooter IP noted above.
      9. NetBooter Port noted above
      10. Update Host information to denote the target TName the COM port and optional Emulator are connected to.
      11. If attached, update Emulator entry to reference the target TName the Emulator is now connected to, update its NetBooter IP and Port.
8. Add an entry for TName to the Target Farm Wiki Page.
   1. Generally, it should contain information not included in the target's BSP user guide, such as:
      1. tftp server paths used by uboot commands (boot and composite archive)
         1. boot and BIF paths should be unique per board, this is so symbolic links can point to same or different images.
      2. MAC address.
      3. Customer supplied host login information.
      4. DDC-I target farm specific rigging.
      5. Pictures of emulator connection, dip switch and jumper settings.
      6. Recovery information and or settings.
9. Add an entry to linux03.ddci.com:/tftpboot/tftp-update-targets.txt
   1. A copy of the file is kept at https://deos.ddci.com/scm/Deos/maintainer-tools/tftp-update/branches/mainline/code/tftp-update-targets.txt.
   2. It is suggested that you commit the change here (no pcr-required) and then scp the file to the TFTP server:

 scp -P 47734 ~/scm/Deos/maintainer-tools/tftp-update/branches/mainline/code/tftp-update-targets.txt linux03.ddci.com:/tftpboot/

The above steps enable Deos Board Support Package (BSP) software development for hardware with no existing Deos BSP. If a BSP does exist, follow these additional steps:

1. Determine the target's MAC address, perhaps by observing serial line output and or asking the engineer assigned to BSP development.
2. Obtain an available IP address from Target Farm IP Addresses or the IT team, and request that they rig the Intranet's DHCP server to map the target's MAC address to the obtained IP address.
3. Update Wiki with the Target Name and MAC addresse(s) assigned.
4. Update the X9 entry for the target, setting the IP attribute to the obtained IP address.
5. Read the BSP's User Guide to cross check the installation steps and determine how to rig the target for booting Deos.
   1. Should be able to ping the tftp server once everything (DHCP server MAC/IP assignment, uboot etc) are properly configured (i.e. ping 10.0.1.208)

Troubleshooting

1. Customer Host machines may be setup to provide a local tftp server to the target. While that may be used, our preference is to use our own tftp server. If instructed to connect the target, with or without an intermediate switch, to a second ethernet port on a host machine, that may not be necessary and that connection should be made to our network instead.
2. Some customer supplied equipment has its power controlled by the customer supplied host machine. Make notes of this in the appropriate X9 and Wiki entries.
   1. In this case X9 may only have one entry for the host machine (i.e. no separate target entry), put the target information in the comments section.
   2. In other cases, the customer supplied host simply needs to be added to X9 for reservation purposes.

Lastly, Notify the group (e.g., Deosgroup e-mail) that the target has been added.