MAS Hardware

From DDCIDeos
Jump to navigationJump to search

Most of the important information on the hardware is stored on the X9 Wiki. This wiki page contains supplemental information.

For information on rebooting the X9 wiki page: Rebooting X9

Farm Room

  • Entry Code for Farm Room: 5315

Processor Cores

To determine the number of cores, follow these steps:

  • Navigate to the appropriate platform/etc directory in /desk. Example: /desk/platform/celestial/etc
  • Open the basecon.hyp file into your favorite editor
  • Search for -maxCoreIndex which will provide the index to the final processor core. Max Core = maxCoreIndex + 1

General Hardware Information

General Steps in Using Hardware

  • You need VPN running
  • Lock the target you need. If there is a connected Lauterbach, then lock it as well.
  • If a hardware target has a Lauterbach connected, ALWAYS power on the Lauterbach first. When powering down, power down the Lauterbach last.
  • Power on the target hardware
  • Ping the hardware to confirm it is running. Please note that some targets can take dozens of seconds to run and respond to the ping command.

Examples: 

ping 10.0.1.26
ping DeosSpearMX8-3
  • Set DESK_IP_ADDR to the hardware target:

Examples: 

export DESK_IP_ADDR=10.0.1.26
export DESK_IP_ADDR=DeosSpearMX8-3

tftp-update

If stable links exist for a board AND the current links are something other than stable, then the tftp-update script (located in the desk) can be used to quickly fix the links.

Use the following steps (this example assumes we are fixing the links for deost2080rdb board):

  • Confirm the current links:
/desk/bin/tftp-update.sh DeosT2080RDB -l
  • Power down the board
  • Reset the links to the “stable” links:
/desk/bin/tftp-update.sh DeosT2080RDB -s
  • Power up the board and confirm that the board works

If the stable links do NOT exist for the board, then use the following steps:

  • In Open Arbor:
    • Select the target project name in the DDC-I Project Window
    • Select Properties
    • Select the Deos tab
    • Select the Boot Image tab
    • Select (checkbox) the “Generate a boot image file” option
    • Select Apply and Close

From your Linux window, do the following (where “DeosSpearMX8-3” is the name of the target from the X-9 page):

  • Display the current deosBoot and composite link:
/desk/bin/tftp-update.sh DeosSpearMX8-3 -l
  • Copy the above deosBoot and composite links for later use
  • Use the tftp-update script to update the links:
/desk/bin/tftp-update.sh DeosSpearMX8-3 -b imx8qm -p ~/OpenArbor/workspace-kismet/imx8qm/output/
  • Power down and power up the board
  • Use the board
  • When you are done, then return the board to its original state using the following command:
/desk/bin/tftp-update.sh DeosSpearMX8-3 -e <deosBoot link goes here> <composite link goes here>


Hardware Candidates

NOTE: The following is a subset of the boards available. It is provided as a quick reference (copy/paste) for boards that have been used for verification.

AARCH64

DeosIMX8QM-3 

export DESK_IP_ADDR_imx8qm_aarch64=DeosIMX8QM-3
common/test-utils/regress -q -j8 vfile so imx8qm-aarch64 run release

ARM

DeosZCU102-2 

export DESK_IP_ADDR_zcu102=10.0.1.65
common/test-utils/regress -q deos653p1 so zcu102 build run release

Harrys 

export DESK_IP_ADDR_harrys=10.0.1.85
common/test-utils/regress -q deos653p1 so harrys build local run release instrumented instrumented_optimized

Jacinto 

export DESK_IP_ADDR_jacinto7evm=10.0.1.75
common/test-utils/regress -q deos653p1 so jacinto7evm build run release

DeosIMX8QM-3 

export DESK_IP_ADDR_imx8qm=10.0.1.66
common/test-utils/regress -q -j8 vfile so imx8qm run release

s32v234 

export DESK_IP_ADDR_s32v234=10.0.1.70
common/test-utils/regress -q deos653p1 so s32v234 build local run release

TrickyFish NOTE: see additional information below to prep the board for execution 

export DESK_IP_ADDR_trickyfish=DeosSpearMX8-2
common/test-utils/regress -q dvms so trickyfish build run release

PPC

DeosCelestial 

export DESK_IP_ADDR_celestial=10.0.1.106
common/test-utils/regress -q deos653p1 so celestial build run release

DeosT1042D4 (e5500 processor) 

export DESK_IP_ADDR_t10xx=10.0.1.59
common/test-utils/regress -q deos653p1 so t10xx build run release

DeosNai67ppc2 (e6500 processor) 

export DESK_IP_ADDR_nai68ppc2=DeosNAI67PPC2-FW
common/test-utils/regress -q deos653p1 so nai68ppc2 build run release

DeosNai68ppc2-2 (e6500 processor) 

export DESK_IP_ADDR_nai68ppc2=DeosNAI68PPC2
common/test-utils/regress -q deos653p1 so nai68ppc2 build run release

DeosT2080RDB (e6500 processor) 

export DESK_IP_ADDR_t2080rdb=DeosT2080RDB
common/test-utils/regress -q deos653p1 so t2080rdb build run release

X86_64

DeosCOMe-cTL6-s NOTE: see additional information below to prep the board for execution 

export DESK_IP_ADDR_come_ctl6_x86_64=DeosCOMe-cTL6-1
common/test-utils/regress -q deos653p1 so come-ctl6-x86_64 build run release

DeosNAI68INT6-1 

export DESK_IP_ADDR=10.0.1.56
common/test-utils/regress -q deos653p1 so nai68int6-x86_64 build run release

Additional Information on Boards

Processor platform type

To determine the processor's platform type (aarch64, arm, ppc, x86_64), use the following command: 

cdproc-query  <bsp> targetArch

Where <bsp> is the name of the bsp component (example imx8qm, qemu-arm)

NOTE: On older systems (prior to cdproc), the following command can be used: 

grep target /desk/platform/<bsp>/etc/basecon.hyp

DeosCOMe-cTL6-n

15 Dec 2025: The COMe-cTL boards need additional steps to make the boards functional (updating the interrupt number and building the correct container.bin file)

See the COMe-cTL6-X86_64 User Guide (section "Build Deos Bootable Image(s)") for additional information.

Update the interrupt number:

  • REGRESS
    • Create a /test-utils/platform/tiger-lake/etc path of folders (e.g. /tiger-lake/etc)
    • Copy the igc.pia.xml file from desk (e.g. /desk/platform/tiger-lake/etc) into the local folder above
    • Update the interrupt number in the local igc.pia.xml file to the value indicated on the X-9 page (e.g. 36)
  • OpenArbor
    • Expand the come-ctl6-x86_64 Project Window
    • Complete Integration -> IT Pia Files
    • Select igc.pia.xml and select "Copy for Editing"
    • Modify the platformIntteruptNumber to the value indicated on the X-9 page
    • Save the file, and rebuild the target

Power down the target.

Create/copy the container.bin file:

  • If the target was built above in OA, then follow these steps:
    • Navigate to the OpenArbor platform output folder associated with the current workspace (e.g. X:\OpenArbor\workspace-kismet-development\come-ctl6-x86_64\output)
    • Copy the container.bin file
  • Use the Remote Desktop app to log onto the TF Host machine associated with the target board
  • Paste the container.bin file onto the USB drive the is connected to the TF Host
  • Use the "eject" command to stop the USB drive so it can be safely moved (see next step)
  • Ask someone at DDCI to swap the USB drives between the TF Host and the hardware target
  • Once the USB has been swapped, then you can power up the target and use the board

TrickyFish

  • Launch OpenArbor, create a new Deos Platform Project for trickyfish.
  • Within the "bootimage.hyp" file, comment out the following line: -registryKFSPhysicalAddress=0x8a062000
  • Select "trickyfish" project. Select Properties: Deos (tab) : Boot Image (tab). Select "Generate a boot image" check box. Select Apply and Close.
  • Confirm that "composite.darc" appears in the output folder after the OA auto build is completed
  • For formal test, use this image for the formal build on the target board
  • Power off the target board
  • From BASH window:
$ scp -P 47734 /cygdrive/c/Openarbor/workspace-xxxxx/trickyfish/output/composite.darc linux03.ddci.com:/tftpboot/imx8qm/composite-spear2-dvms-rfs.darc

$ ssh linux03.ddci.com -p 47734
-bash-4.2$ cd /tftpboot/imx8qm
-bash-4.2$ chmod 664 composite-spear2-dvms-rfs.darc
-bash-4.2$ rm composite-spear-2.darc
-bash-4.2$ ln -s composite-spear2-dvms-rfs.darc composite-spear-2.darc
-bash-4.2$ exit
  • Power on the target board
  • Build and run the tests
  • Return the board to its starting state:
$ ssh linux03.ddci.com -p 47734
-bash-4.2$ cd /tftpboot/imx8qm/
-bash-4.2$ rm composite-spear-2.darc
-bash-4.2$ ln -s composite-rel-2022-5-30-spear2.darc composite-spear-2.darc
-bash-4.2$ exit
Retrieved from "https://ddci.zapto.org/ddciWiki/index.php?title=MAS_Hardware&oldid=76509"