Deos Target Farm

From DDCIDeos
Jump to navigationJump to search

Overview

The target farm hosts Deos-compatible targets accessible via the DDC-I corporate network; targets consist of reference boards (non-program specific) and custom boards (program specific). These targets are used to develop, debug, and test Deos applications. Targets includes a variety of platform and architecture types; e.g. Arm, PowerPC and Intel x86.

Deos does not at this time support multi-user development; therefore, only one person or test script may access a particular target at a time. To coordinate access to the targets, we use a web based utility known as X9 (developed by our very own BSP Goddess while interning at DDCI may moons ago). See X9 help.

In order to use the X9 Python command line client, use the Cygwin package installer and select x9-client from the Deos category.

Note: Reference boards should be Flash or TFTP programmed with "Jupiter" (Deos kernel 10.x and 10.x compatible BSPs).

Adding Targets to the Farm

https://deos.ddci.com/ddciWiki/Add_Target_to_Farm

Help

For assistance in having emulators moved, or any other target farm related requests:

Use Google Chat, Browse Spaces and post a message under Spaces->TargetFarm

You can Join and Leave spaces as needed if you don't want to see all notifications.

Target Farmers Schedule

All times are MST (Phoenix Arizona)

Target Farmers Schedule
Week Day Core Hours Farmer Scheduled
Monday 9:00am - 4:00pm John Dorman
Tuesday 9:00am - 4:00pm John Dorman
Wednesday 9:00am - 4:00pm on-call John Dorman
Thursday 9:00am - 4:00pm John Dorman
Friday 9:00am - 4:00pm John Dorman

Weekly Farm Maintenance

Once a week there are a couple activites that only take a few minutes, and has saved someones bacon more than once. At some point it would be nice if these were automated, but for now, a calendar reminder to do these tasks makes sure it gets done.

  1. Save the current state of the tftp server links following the README.
 README
  1. Save the current X9 target setup (page that includes the power switch IP and Plug numbers).
 README

Farm Hardware Database - was PTC

  • This database has historically been stored in Notes. A new Share Point list has been created to contain the textual portions of that data going forward.
  • Historical data is accessible here (Verify Latest Location with IT, 9/24/24 Export, paste to browser): file://nmigrator-w11vm/WebArchives/072565AD006E295F/index.html
  • The Asset Tag will be the Target Farm Name, or other uniuque name such as Oscilloscope-1 and will match the svn directory name where any pictures, manuals, packing list scans are stored.
  • You can certainly make up an SVN name to start with while captuing data, but once a Farm name has been choosen, the SVN directory, and Asset Tag name in the Share Point List should match.


Quick Start

Follow these steps.

  1. Reserve the target, and its emulator and host if applicable (Claim: Lock| Unlock) via X9.
  2. Power on targets and emulators by clicking "Power : On | Off | Boot" on X9.
  3. (If outside DDC-I firewall) Establish a Virtual Private Network (VPN) connection to DDC-I.
  4. Target names are listed on X9. Ping the target to ensure it is running and online (it may take a minute or so for the target to boot): 
    ping <target>.ddci.com
  5. Go write some code!
  6. Power off the target by clicking "Power : On | Off | Boot" on X9.
  7. Release the target and its emulator and host if applicable (Claim: Lock| Unlock) via X9.

Rebooting a Target

Any changes you make to the target's kernel file system will disappear on the next target reboot (i.e. power off, then on cycle). So, you can use X9 to reboot the target and get back to a known working configuration. Click on "Power : On | Off | Boot".

Rebooting X9

It is possible for anyone in the Engineering group to use sudo to restart the X9 server. Here is the procedure:

  • ssh to deos.ddci.com (or linux04.ddci.com) as yourself.
$ ssh mdiethelm@linux04.ddci.com -p 47734
  • Execute the following command. You may be prompted for your login password.
$ restart-x9
password for mdiethelm:

Powering On a Host with Wake-On-Lan

In the event that someone shuts a host system down as opposed to logging off, it is possible for anyone in the Engineering group to use sudo to power on a host capable of Wake-On-Lan (WoL). Here is the procedure:

  • ssh to deos.ddci.com (or linux04.ddci.com) as yourself.
$ ssh juser@linux04.ddci.com -p 47734
  • Execute the following command. You may be prompted for your login password.
$ sudo ether-wake <host name>
password for juser:

You may see the response "network is down". Ignore it.

NOTE: Only those host systems on X9 tagged "WoL Capable" will respond to this.

NOTE: New machines need their name and MAC address added to the /etc/ethers file on linux04.

Instructions to Enable Feature on a TFHost: https://www.windowscentral.com/how-enable-and-use-wake-lan-wol-windows-10

TFTP Server

The TFTP server is rigged on linux03.ddci.com (10.0.1.208).

It is advised to follow the instructions to save the current symbolic links on the TFTP server before changing them.

README

  • To push the image the boot loader will want to load, change to the TFTP server, perform the following, substituting the hyperstart image name, and your user name for the ones used in the example.

NOTE: The <deosBoot.bin> (located in the DDS "desk/platform/<target_folder>/boot") and <composite.darc> (located in the workspace "<workspace>/<platform_project>/output") both need to be moved to the desired location and symbolic linking should be added respectively. 

$ scp -P 47734 deosBoot.bin aroffelsen@linux03.ddci.com:/tftpboot/ls1043ardb/deosBoot1.0.0.bin 
$ ssh aroffelsen@linux03.ddci.com -p 47734
$ cd /tftpboot/ls1043ardb
$ chmod 664 deosBoot1.0.0.bin
$ exit
  • If creating a subdirectory to hold the image files, make sure the access rights are read-write-execute for the directory for both user and the 'eng' group.
$ cd /tftpboot
$ mkdir ep440c-1
$ chmod 775 ep440c-1
  • When naming the boot and hyperstart images put to the TFTP server, please think of a useful name, for example deosBoot1.0.0.bin would indicate it was built from the initial release sent to the customer. If your image is purely experimental, using your initials in the name may be appropriate. If a non-backward compatible kernel is used, the filename should contain hints to that regard, e.g. hypstart_k810.bin. Hypstart images that are being tested for delivery to the customer should contain 'rel' and an indication of which release. If this becomes complicated with many images on the TFTP server, please add a note describing the various images to the target farm wiki under your target's description. Please delete your old images as they become obsolete to avoid confusion.
  • Create a generic hypstart.bin and deosBoot.bin symbolic link which points to the image you are booting. This way, new images can be put to the TFTP server, and only the symbolic link pointing to the boot image needs to be changed. For example:
ln -sf deosBoot-rel1.bin deosBoot.bin

Look at the current symbolic links (using command ls -la) to determine their names before you delete the old one as some targets have unique names per target. For example, DeosLS1048A-GL1-1 and DeosLS1048A-GL2-1 must each have a symbolic link, so the symbolic links are named hypstartGL1.bin and hypstartGL2.bin. These details should be documented in the platform section of the target farm wiki.

Using ssh and scp without a password:
If you use scp and ssh as shown, you will have to enter your password for the remote machine every time. Doing so can certainly be a bother for common usage, but it's a show-stopper if you want to embed these commands in a script.

To allow password-free sessions, see SSH_configuration.

Once those instructions are correctly followed, the scp and ssh commands can be shortened to the following: 

$ scp deosBoot.bin linux03:/tftpboot/ls1043ardb/deosBoot1.0.0.bin 
$ ssh linux03

Switching Kernel Versions

Some boards can run multiple kernels, but both the boot and hypstart/composite must be changed simultaneously. For example, a board may run the 9999.1.21 kernel or the 9.0.0 kernel, but the two versions are not compatible with one another.

The following are the symbolic links for the kernel version 9999.1.21

  • deosBoot-1.bin -> deosBoot9999kernel.bin
  • hypstart-1.bin -> hypstart9999kernel.bin

The following are the symbolic links for the kernel version 9.0.0

  • deosBoot-1.bin -> deosBoot9kernel.bin
  • hypstart-1.bin -> hypstart9kernel.bin

To switch between versions:

  • ssh linux03
  • cd /tftpboot/<bsp name>
  • ls -la
  • Compare the symbolic links against the ones above for your desired kernel. If you need to switch to the other version than the one currently getting loaded, proceed.
  • rm hypstart-1.bin (delete the symbolic link to the hypstart)
  • rm deosBoot-1.bin (delete the symbolic link to deosBoot)
  • ln -s deosBoot9999kernel.bin deosBoot-1.bin (example creates a new symbolic link to deosBoot9999kernel.bin)
  • ln -s hypstart9999kernel.bin hypstart-1.bin (example creates a new symbolic link to the hypstart9999kernel.bin)

IP Address Assignments

Note: Each target's lwip.config must be rigged to use DHCP!

Deos target farm members get their IP addresses via DHCP. We've rigged the DDC-I DHCP server to ensure each target always receives the same IP address. Think of this degenerate DHCP behavior as identical to assigning each target a static IP address, except that the assignment is centralized at the server rather than spread amongst each target's lwip.config file.

To determine the IP address that was assigned, you can ping the target by name. Target names are listed on X9. Here's an example: 

$ ping DeosMiniPPC-2.ddci.com
PING DeosMiniPPC-2.ddci.com (10.0.1.98): 56 data bytes
64 bytes from 10.0.1.98: icmp_seq=0 ttl=254 time=1.800 ms
...

Remote Desktop Connection

It is often the case that remote Deos Board Support Package (BSP) developers would need to use an emulator or serial connection to a Deos target. Traditionally, this would be implemented by shipping the target to the BSP engineer so that they could connect the appropriate USB cable and or serial cable to their host. Rather than making Fed Ex rich this way, BSP engineers can use a target on the farm.

Warning: The first time you log into a Windows XP machine remotely, ensure you go to Control Panel, Power Settings, and choose the Always On option. If you forget to do this before logging out, the remote host will likely go to sleep. This will make it unavailable to others until someone can get back into the lab and physically wake it up.

Microsoft Remote Desktop

One can use a Microsoft Remote Desk client to attach to HPDesk. Follow these steps.

  1. Reserve the proper host machine (Claim: Lock| Unlock) via X9.
  2. (If outside DDC-I firewall) Establish a Virtual Private Network (VPN) connection to DDC-I.
  3. Connect to the host machine via Microsoft Remote Desktop.
  4. Log in using your DDC-I domain username and password
  5. When done, logoff (Clicking disconnect is insufficient).
  6. Don't forget to remove the X9 reservation.

Using Lauterbach Emulators

Older versions of Trace32 SW can be downloaded and installed from Old Trace32 Host SW

The emulator's power can be controlled via X9. Look for "lauterbach*".

The Lauterbach Trace32 client software can be accessed via the Windows Start menu. 

 Start, All Programs, Trace32, trace32 ICD <arch> USB

The first time in, you'll want to create an emulator batch file for yourself: 

 In TRACE32: File, Edit Batch
  1. Open T32.cmm
  2. Edit the DATA.LOAD.ELF command to point to your executable. Its best to put the executable name in double quotes, e.g., "//samba/home/libfoo.so"
  3. "Save As" to a copy for you, e.g., t32-alarson.cmm

If you want to do source level debugging, use the /STRIPPART option to remove directory components and use Symbol.SourcePATH.SetDir to point to a copy where you've copied your sources. 

 data.load.elf \\samba\home\libkernel.so.dbg /GNU /NOCODE /NOREG /strippart 3

You can either use windows shares to get your files to host machine plugged into the emulator. Make a directory for your stuff and copy the file to debug: 

 mkdir //hostname/home/$USER
 cp libkernel.so.dbg //hostname/home/$USER/

Or you can use rsync, but you must copy them to a UNIX host. You then reference the files from hostname as \\samba\home (which will refer to your personal home directory). E.g. from a build directory, 

 rsync -avC libkernel.so.dbg ../../../{code,common} linux03:

The result will show up on HPDesk as \\samba\home\code. To make your life easier you'll want to configure SSH.

When debugging virtual code use "onchip" breakpoints. Software breakpoints can get lost on TLB flushes. The typical message is: 

 Code at software breakpoint has changed at address C:....

To make the GUI breakpoint set onchip (rather than software) breakpoints: 

 break.select.program onchip

If a breakpoint is set on the first instruction executed on a page experiencing a TLB miss, you will see the breakpoint twice. The first time the emulator will display bogus instructions, the second time it will contain your code. If you can move your breakpoint to the following instruction, your life will be simpler.

Similarly, if will not be able to view data unless the page is in the data TLB.

If you have a dump window open when attempting to reboot, you may see the following message. The solution is to close or minimize your "dump" windows. 

 Emulation debug port fail

The UBoot target/emulator start up dance

On some platforms, after a cpu reset it is necessary to halt the cpu an continue or none of the cpu breakpoints that are set will halt the processor. If you need to halt on a breakpoint installed prior to the reset you can accomplish this by manually hitting "pause" during the target boot sequence when the U-boot message: 

  Hit any key to stop autoboot

is being displayed. To see the message, you'll need to attach a hyperterminal to the COM port listed on the X9 page or wiki entry for the target. Make sure to set the appropriate speed and communications parameters. Hyperterminal is at: 

 START menu, accessories, communications, hyperterminal

When you reboot the target, typically via:

  1. In trace32: CPU, system settings, Press the UP radio button
  2. When you see the U-boot message, press "PAUSE", then "PLAY"

Viewing Video Output

To get a more readable view of video memory, or to get something you can manipulate in a text editor, you can do the following: 

 # Substitute physical address of the board's video memory
 data.save.binary //samba/home/screen-dump.bin A:0x40018000--A:0x40018FFF  
 rsync linux03:screen-dump.bin .
 python -c 'import re; import sys; print(re.sub("(.{80})","\\1\n", open(sys.argv[1],"rb").read()[0:(25*80*2):2])),' screen-dump.bin

Alternative approach

Grab video output from memory; from Lauterbach command input B:: enter: 

Data.SAVE.Binary video.out a:0x00018000--a:0x00019000 /BSPLIT 2 0 1

Note: Change absolute address as appropriate for the BSP.

To display video output; from a DOS (cmd) shell enter once: 

mode CON: COLS=80 LINES=28

Then the following after each Lauterbach grab enter: 

cls && type C:\T32\video.out

Note: C:\T32 is the default Lauterbach output directory.

A helper batch file may exist at C:\T32\video.bat to simplify the above.

General target/emulator start up dance

In Emulator Software:

  • Choose CPU, System Settings...
    • For CPU, choose MPC8343
    • For Mode, choose Up
  • Choose CPU, In Target Reset
  • Choose CPU, Reset CPU Registers

You can now step, set breakpoints, etc. To see assembly, choose View, List Source.

T32Start Setting for Ethernet Connection

To connect to a Lauterbach Pod that is attached to the DDC-I network:

In T32Start, Add a configuration for the emulator and target. For example, Lauterbach07 as shown, the only thing changed was "Node Name/ IP address: Lauterbach07", and "Target: Intel x86 64"

WideView

JTAG Bus Scan Hint

When first connecting the Lauterbach to a new board, and the emulator cannot attach to the target, it may be helpful to issue the following command at the prompt in trace32:

DIAG 16001

This will cause the emulator to attempt to scan the JTAG bus.

Target Specific Emulator Hints

mpc567xx

  • When using trace32 to see cores other than core 0 you must issue the command 'core.ASSIGN 1 2' when the software is not attached to the target. Then once you attache the software you will be able to select core 0 or core 1 like you can with other multi-core targets.

mpc5777c

  • Even though the timers are configured to freeze when debug suspended they have been known to turn on while stepping.
  • The time stamp counter (TBL) is not single sourced across cores. The code synchronizes at boot, but halting/stepping with the emulator causes them to get out of sync.
  • See mpc57xx.

Intel DCI

  • There are 2 flavors of DCI debugger connection, Out of Band (OOB), and In-Band (DbC). OOB requires a Lauterbach Pod, CombiProbe, and USB Whisker Cable (C20 LA-4572). There is a script for each connection type in the c:\T32-Scripts folder, and in subversion here: IntelDCI.
  • The hardware must support DCI debugging, and the BIOS or SlimBoot must have the appropriate debugging method enabled. As of this update DbC is tested to work on DeosCOMe-cTL6-2, and both methods on DeosNAI68INT6-1.
  • TRACE32 In-Band (DbC) setup instructions: Media:Lauterbach-Trace32-setup-for-Intel-DCI-DbC-Debugging.pdf
    • If Lauterbach Gmbh? Doesn't show up in Device Manager USB Devices when board is powered, momentarily pull the Yellow USB cable and replace.
Needs at least TRACE32_R_2023_09_000165015.7z, and copy over the contents of trace32_n_2024_02_000166485_x86_x64_full_20240206092140.zip 
see [https://deos.ddci.com/scm/Deos/restricted/lauterbach-emulator/trace32_host_software/trace32_n_2024_02_000166485_x86_x64_full_20240206092140-README.txt]

Debugging with DCI.DbC has issues with reset: when the target resets, it takes the USB connection down, which disconnects the debugger. As this is not a simple direct connection like with DCI.OOB or JTAG, the connection must be re-negotiated from scratch. This can often be helped by directing the target to perform a warm reset instead of a cold one, and also assisted by turning on several onchip event triggers to halt the processor at startup:

; Prepare CPU to halt when reset, and use the warm (power-on) reset
; Some CPU need all, others may only need some
TrOnchip.Set RESet ON
TrOnchip.Set ColdRESet ON
TrOnchip.Set INIT ON
SYStem.Option.RESetMode WARM

; Prepare the debugger to reattach when a reset is detected
SYStem.Mode Attach
SYStem.Mode StandBy

; Perform the reset
SYStemSYStem.RESetTarget

Oscilloscope

There is a Tektronics oscilloscope available in the target farm. The following pictures show the oscilloscope as it was unpacked:

Stored: Cabinet 1-2

Here is the user's manual: media:OscilloscopeUserManual.pdf

Logic Analyzer

Stored: Cabinet 1-2 on top of Scope

DSLogic Series USB-based Logic Analyzer

DSLogic U3Pro32 (32 Channels, up to 1GHz sample rate)

More Product Info: https://www.dreamsourcelab.com/product/dslogic-series/

No license required for software available here: https://www.dreamsourcelab.com/download/

User Guide: https://www.dreamsourcelab.com/doc/DSView_User_Guide.pdf

The Manual and Software have been archived in the subversion repository.

Currently Connected to DeosS32V234-5 J52, J26

Connections
Channel Signal Name Board Connector
0 SPI-CS4 (Chip Select) J52-2
1 SPI-SCK J52-1
2 SPI-SOUT (Data Out of tgt) J52-5
3 SPI-SIN J52-3
NA Ground J52-6
NA 3.3V J26-5

Previously Connected to DeosZCU102-1 J55

Connections
Channel Signal Name
0 SPI-CS (Chip Select)
1 SPI-CLK
2 SPI-DO (Data Out of tgt)
3 SPI-DI

Previously Connected to DeosSpearMX8-3 SPI0 and SPI2

Connections
Channel Signal Name
0 SPI0-CS (Chip Select)
1 SPI0-CLK
2 SPI0-DO (Data Out of Mx8)
3 SPI0-DI
4 SPI2-CS
5 SPI2-CLK
6 SPI2-DO
7 SPI2-DI

USB Analyzer

There is a Total Phase Beagle USB480 Protocol Analyzer available in the target farm.

The Analyzer Manual and Software have been archived in the subversion repository.

USB Auto Switch

There is a Toggle by INOGENI available that allows a USB Thumb Drive (or any USB device up to 3) to auto-switch between say a TFHost and a Target. Manual, Website

  • This simple device automatically switches to the most recently or only powered USB connection. Since it's always powered by the TFHost it's connected to, that is where the device plugged into it will appear whenever the target is not powered allowing you to update, inspect, backup as needed.
  • Once the target is turned on, it will become the most recently powered port, and the memory device will auto-switch to appear to the targets bootloader, and dissappear from the TFHost.
  • Be sure to "eject" the device before powering the target to be sure all cached writes are complete.
  • Note this device was tested on the CTL6-1 board, and did not function properly, presumably because it didn't switch quickly enough for the bootloader to detect it. The autoswitch can be configured for relay control or RS-232 control if/when needed it could be made to work on this board.
  • At this time, we only have 2 of the auto switches, both are in-use, and should be able to search "USB Auto Switch Installed" to find them in this Wiki.

X86 Emulator

ASSET Technologies American Arium Emulator ECM-XDP3

Location:Cabinet 3-2 Box Marked x86 Emulator

Aug. 2021 used software from here and license from here.


CodeWarrior-1

Box Location: Cabinet 2-5

Device is USB Powered, therefore:

  • Power Down Target
  • Disconnect USB cable between Host and Emulator
  • Connect/Disconnect from Target
  • Reconnect USB cable between Host and Emulator

License

The License file is stored on TFHost15 in folder: C:\Freescale\CW4NET_v2019.01\Common\license.dat A copy is also stored in subversion in a sub-directory with the name of TFHost15's Disk Serial Number.


Paper work:

Media:CodeWarriorPackingList1.pdf

Media:CodeWarriorPackingList2.pdf

Media:CodeWarriorPackingSlip1.pdf

Media:CodeWarriorPackingSlip2.pdf

Media:CodeWarriorQuickStart1.pdf

Media:CWTAPUG-CodeWarriorTAP-UserGuide.pdf

Pictures:

CodeWarrior Connection - Click on image for higher resolution
CodeWarrior Picture 1 - Click on image for higher resolution
CodeWarrior Picture 2 - Click on image for higher resolution
CodeWarrior Picture 3 - Click on image for higher resolution
CodeWarrior Picture 4 - Click on image for higher resolution
CodeWarrior Picture 5 - Click on image for higher resolution
CodeWarrior Picture 6 - Click on image for higher resolution

Dediprog SF600Plus SPI Flash Programmer

SPI NOR Flash programmer supports ICP/ISP Programming, Socket Adaptor Programming, and Stand-Alone Programming.

https://www.dediprog.com/product/SF600Plus

Pictures:

SF600Plus-1
SF600Plus-2
SF600Plus-3
AdafruitSMT-TestSocket-SOIC-8
NOR-SPI-W25Q128JVSIQ

Targets

DeosAbaco-1

This target has been removed from the farm. Stored:??

Abaco Force2

MAC: 00808e045477

Farm Connection Pictures:

AbacoForce2

AiTech-C108

This target has been removed from the farm.

DeosAID

This target has been removed from the farm.

Network Name: deosaid.ddci.com

See #DeosAID2

DeosAID2

This target has been removed from the farm.

Network Name: deosaid2.ddci.com

These are AMCC PowerPC 405 boards.

A PDF file is available to assist with determining the proper Ethernet, RS-232, and Power Supply connections.

An image is provided to help with emulator attachement orientation.

AMCC405 JTAG Pin1 - Click on image for higher resolution










In lieu of an official User's Guide/ platform how-to, we've captured some Lauterbach scripts in subversion to facilitate re-flashing the Goodrich AID board.

I recommend you limit yourself to Flash loading the Deos hyperstart image (ref howtoflash.txt). Reloading the Boot is still a bit tricky so one misstep and the board is will not operate. Easy to recover, but stick to hyperstart loading unless a new boot is needed.

See the file "howtoflash.txt"

See X9 for host, network and serial port connections.

DeosAviage-ZynqUltra

Customer Board based on the Xilinx Zynq Ultrascale+ SOC.

MAC: 20B0F704A71A

Note: Requires Gigabit Switch, won't negotiate 100MBit.

Note: The attached 12V .5A power supply belongs to DDC-I.

Module View
Dip Switches

DeosCMM5675-1

Farm-Stored - Location:TBD

MAC: 00049f02c63f

This board uses the mpc5675k BSP.

See here for information about configuring trace32 to work with this target.

DeosCMM5675-2

Unavailable, Sent to Mocana.

MAC: 00049f02c640


DeosCOMe-cTL6-1

Program Durants3 Description Kontron COMe-cTL6 Intel Celeron on a COMe Ref. Carrier-i T6 TMI
Manufacturer Kontron Processor Celeron
Part Number [TBD] Serial Number [TBD]
MAC Addr i225 B:7 D:0 F:0 00:e0:4b:75:c3:6f Cable C21, See: Intel DCI
BSP (bootingNow)come-ctl6 and come-ctl6-x86_64 Captured Info [TBD]


Kontron COMe-cTL6 Intel Celeron on a COMe Ref. Carrier-i T6 TMI

NO Auto-Switch on this one, There are 2 USB Sticks Labeled cTL6-A and cTL6-B. One is always in the TFHost, the other in the Board.

  • Notify TargetFarm Space if/when you'd like them swapped.

UEFI Shell available via serial connection. Note, don't resize your PuTTY window, restarting PuTTY fixes it if you do.

If you "exit" from the UEFI shell, you'll be presented with the boards BIOS setting menus.

If you loose PuTTY functionality after changing settings, try powering down the board, restarting PuTTY, power up.

To enter BIOS setup use the ESC key during bootup.

Current MACs:

i210 B:6 D:0 F:0 00:e0:4b:73:86:3d

i225 B:7 D:0 F:0 00:e0:4b:75:c3:6f

Sent to CoreAVI MAC: i225 00e04b73a2c7

Current COMs:

  • uart0 - 0x819b7000
  • uart1 - 0x819b6000

Flashed new UEFI BIOS: [UEFI 2.7; PI 1.6], [CTL6E901.001 (x64)(Eval)]

Preliminary BSP setup instructions also completed, Booting UEFI, hyper threading off, network stack enabled for DHCP.

BIOS Files:

https://deos.ddci.com/svn/DDCI/administrivia/customer-specific/royal-oak/i210/

DediProg and NOR Flash Chip information is here: https://deos.ddci.com/ddciWiki/Deos_Target_Farm#Dediprog_SF600Plus_SPI_Flash_Programmer

Manuals:

https://www.kontron.com/download/download?filename=/downloads/manuals/come-compact/come-ctl6_user-guide_rev1.0.pdf&product=160493

https://www.kontron.com/download/download?filename=/downloads/manuals/c/come_it6_tim_rev-1.5_2020_09_30.pdf&product=145611

SERIAL: Note in the pictures, serial is plugged into SERIAL0, that is NOT the proper configuration as slimboot outputs on SERIAL1 (J29). Serial should be plugged into SERIAL1 (J29).

DeosCOMe-cTL6-2

Program Chino Description Kontron COMe-cTL6 E2 i7-1185GRE 16GB w/XDP and NVMe 1TB
Manufacturer Kontron, Carrier Processor Intel i7
Part Number COM:36031-1600-18-7, Carrier:38116-0000-00-5PRO Serial Number LOD380076, UPD0S0022
MAC Addr Kismet:i225: 00:E0:4B:81:38:40

Fourpeaks:i210: B4:96:91:26:25:62

Cable C21, See: Intel DCI
BSP come-ctl6-fp(bootingNow), come-ctl6 and come-ctl6-x86_64 Captured Info [TBD]

OOB Debugging enabled (2:Enabled DCI OOB), only works on USB0 (Blue, Lower Right). Run Script c:\T32-Scripts\OOB.cmm

There are two USBs associated with this board, "cTL6-2a" and "cTL6-2b" 2a - loads Kismet 2b - Boots fourpeaks, currently loaded for kernel RFS

USB Auto Switch Installed

DeosDGPU-LS1048-GL1

This target has been removed from the farm.

DeosDGPU-LS1048-GL2

This target has been removed from the farm.

DeosLS1043a-BL1

This target has been removed from the farm. 2023-02-13 Returned to Customer

DeosLS1043A-BL-CCA

This target has been removed from the farm. 2023-02-13 Returned to customer.

DeosDGPU-T1042-GL1

This target has been removed from the farm.

DeosDGPU-T1042-GL2

This target has been removed from the farm.

DeosDosa

This target has been removed from the farm. RETURNED TO CUSTOMER (22 May 2019 by S.H.H.)

DeosDPM2

MAC: <unknown>

Honeywell DPM2.0 hardware running a custom bootloader, the zcu102 boot, and a Honeywell hypstart image. More information is provided about the memory map is documented at DPM2-and-PIDU-memory-maps.txt

NOTE: This board requires the use of an additional power and JTAG control program as documented in [README.docx]. This document describes the steps to reflash the target with a new hyperstart image.

This board does not TFTP Boot. However, the file linux03:/tftpboot/durants-dpm2/ddci-dpm2.0-ddc-i-ultrascale.7z contains the work Stephen Smith did while onsite at DDC-I on 04/02/21. The programmed hypstart also contains additional files in the LFS providing context for the image.

Board Connections
Power Supply Setting
JTag Power Supply Setting

DeosDurants-pidu

MAC: 00049F05701B

Location: Rack 2-3 Box Location: None. Hand delivered in 2 anti static bags

Honeywell Durants PIDU hardware. This target is setup to TFTP Boot from the DDC-I TFTP Server using durants-pidu/deosboot.bin and durants-pidu/composite.darc.

In the TFTP folder is ddci-pidu-imx8-files.zip, which contains the work Stephen Smith did while onsite at DDC-I on 04/02/21 when delivering the PIDU target.

The power supply belongs to DDC-I. This power supply works via x9.

COM4-COM7 appear when powering on the target. I was not able to connect and see which is U-boot, but target is TFTP booting Deos. There is no output on the serial port while current image is executing.

Durants-PIDU
DDC-I provided Power Supply

DeosEP440C

Farm-Stored - Location:TBD

MAC: 0010ec010082

EP440C - Click on image for higher resolution

Network Name: deosep440c.ddci.com

This is a Yosemite AMCC EP440C. The Boot Loader will transmit on the serial connection.

Documentation is available in SCM. The entire Resource CD contents have been archived in \\nx3000\Deos\yosemite-amcc-ep440c.

This target tftp boots with images for the current fourpeaks distribution. To change this, log into the TFTP Server) and establish new symbolic links. Below is an example that would switch to files compatible with the elbert distribution. 

$ ssh linux03
cd /tftpboot/ep440c/
ln -s elbert/deosBoot.bin deosBoot.bin
ln -s elbert/hypstart.bin hypstart.bin
ln -s elbert/ubootFlashScript.img ubootFlashScript.img
ln -s elbert/ubootHypstartLoadFlashScript.img ubootHypstartLoadFlashScript.img
ln -s elbert/ubootHypstartLoadScript.img ubootHypstartLoadScript.img

DeosEP8280-1

This target has been removed from the farm.

Farm Stored Location: Cabinet 1-4


DeosEP8343M

These are all #Embedded Planet EP8343M boards. Documentation is available in SCM. The entire Resource CD contents have been archived in \\nx3000\Deos\ep8343m.

All these boards boot from U-Boot, with a DeosBoot programed at 0xF8000000. U-Boot loads a hyperstart image via tftp and places at 0x400000; where DeosBoots expects to find it. Therefore, all the boards use the below to define the bootcmd environment variable: 

setenv bootcmd 'run pingcmd;tftp 400000 /ep8343m/hypstart-[1|2|3].bin;go F8000000 400000'

DeosEP8343M-2 uses hypstart-2.bin and DeosEP8343M-3 uses hypstart-3.bin. hypstart-2.bin, and hypstart-3.bin are symbolic links on the tftp server, which by default point to hypstart_k8_1_0-5.bin (kernel version 8.1.0-5).

If you need to change the above for your specific testing purposes (e.g., need to use a Elbert hyperstart image hypstart-elbert.bin), please change it back when you are finished with the target. To change the symbolic link, log into the tftp server, and from /tftpboot/ep8343m remove the existing symbolic link and create a new one. Example follows for DeosEP8343M-2-1: 

$rm hypstart-2.bin
$ln -s  hypstart_k8_1_0-5.bin hypstart-2.bin

Note that this is different from the recommendation in the BSP User's Guide, but is nevertheless correct for our target farm environment.


DeosEP8343M-2-1

Farm-Stored - Location:TBD

MAC: 0010ec017b9e

ARINC 664 PCI mezzanine board attached to the ep8343m - Click on image for higher resolution

This target has an ARINC 664 PCI mezzanine board attached. The 664 board will NOT work with the older ep8343m boards, for example DeosEP8343M.

DeosEP8343M-2-2

MAC: 0010ec817b9e

DeosEP8343M-3

This target has been removed from the farm.

DeosEPT1042XS-2

TEMPORARILY REMOVED FROM FARM. Sent to Orxata customer.

Embedded Planet t4240xs - Click on image for higher resolution

Embedded Planet EP1043XS 11 eval/reference board.

MAC: 00:10:EC:01:B9:F1

See X9 for host, network and serial port connections.

DeosFit-pc*

Fit-PC2 front with power button illustrated - Click on image for higher resolution

These are Intel Atom based x86 targets. Each boots off of a USB stick inserted into a fee USB slot on the device. See /desk/help/fit-pc2-platform-howto.htm for how to program the USB stick.

All are rigged to power on and off via X9; however this feature needs to be enabled by powering them on once manually via the power switch.

If one ever stops responding to X9, try having someone power on via the power button (see figure). Once done, you can try cycling power via x9 again.

DeosFit-PC2-3

Box-Stored - Cabinet 3-2

MAC: 0001C0061A84 0001C0064326

Note that this is a fit-pc2, which has two Ethernet ports, and several USB ports.

The USB stick is currently booting kernel 8.1.0.

DeosHarrys

Customer Board based on S32V234 SOC.

MAC: 001BC3123423

Compatible Cable LA-3743X.

4/30/19 Programmed uBoot that supports eMMC.

See warnings about MAC Address in Harrys-2.

See flashing and debugging instructions in Harrys-2.

Harrys-1

DeosHarrys-2

This target has been removed from the farm. Returned to Customer 4/8/22

DeosHarrys-3

This target has been removed from the farm. Returned to Customer 4/8/22

DeosHosmer-1

A Hamilton Sundstrand EFAST Health Management Unit.

ChA found at 192.168.1.200 on RJ1 with adapter set to auto negotiate speed. ChB found at 192.168.2.201 on RJ3. Both channels connected to switch, then to USB Ethernet adapter on Host.

Host Ethernet Adapter Settings: Use the Following IP address: 192.168.2.5, mask 255.255.255.0 Advanced Button, click Add to add 192.168.1.5, mask 255.255.255.0 So, both addresses are in the IP addresses box. This allows access to both channels at the same time.


Current Images

Note Channel A Ethernet plugged into RJ1.

Hosmer Diagram - Click on image for higher resolution










Old Images

Hosmer Diagram - Click on image for higher resolution
Hosmer Diagram - Click on image for higher resolution
Hosmer Diagram - Click on image for higher resolution
Hosmer Pin-Out Diagram - Click on image for higher resolution

DeosHotdish-AID

This target has been removed from the farm, returned to customer 9/25/2024.

DeosIMX8QM

Rev B2 Hardware

MAC: 00049F05701A

Upon power-up, this target boots U-Boot via SD card. To attach the Lauterbach emulator while in U-Boot, see the directions in SCM.

Compatible Cable LA-7843.

The following are the symbolic links to be modified when TFTP booting this board:

  • imx8qm/deosBoot.bin
  • imx8qm/composite.darc

  • imx8qm/DeosIMX8QM/deosBoot.bin
  • imx8qm/DeosIMX8QM/composite.darc

To attach the Lauterbach emulator while in U-Boot, see the directions in SCM scripts are in C:\T32-scripts already.

https://deos.ddci.com/scm/Deos/products/bsp/imx8/references/lauterbach/scripts/

DeosIMX8QM-2

DDC-I Owned Rev C2 Hardware

MAC: 00049f060a5f

Note this board belongs to sales/marketing, but was on the Farm temporarily.

2019-10-03 Shipped to Gary G. for a Demo, see/use DeosIMX8QM.

To attach the Lauterbach emulator while in U-Boot, see the directions in SCM scripts are in C:\T32-scripts already.

https://deos.ddci.com/scm/Deos/products/bsp/imx8/references/lauterbach/scripts/

DeosIMX8QM-3

DDC-I Owned Rev C2 Hardware

MAC: 00049F074A03

The following are the symbolic links to be modified when TFTP booting this board:

  • imx8qm/deosBoot-3.bin
  • imx8qm/composite-3.darc

To attach the Lauterbach emulator while in U-Boot, see the directions in SCM scripts are in C:\T32-scripts already.

https://deos.ddci.com/scm/Deos/products/bsp/imx8/references/lauterbach/scripts/


Here is the quick start guide: media:IMX8QUADMAXQSG-Rev3.pdf

Here is uboot info as received: media:DeosIMX8QM-3-ubootAsRxd.txt

DeosJacinto7EVM-1

TI J721EXSOMXEVM Customer provided.

NOTE Serial is requiring an unplug/replug to resore functionality.


Current board is: J721EX-PM2-SOM rev A, previous board we still have is rev E8.
Current board MAC is: 24:76:25:a2:62:fd, previous was 24:76:25:93:5c:bc

Emulator Adapter
Power Supply
Emulator Connection
J43 J44
SD Boot
UART Boot
OSPI Boot

Currently Configured to boot from OSPI.

The following are the symbolic links to be modified when TFTP booting this board:

  • loewen/deosBoot.bin
  • loewen/composite.darc

Not Using Currently: Power Supply Tekpower settings (provided by Dan) seem to best at 13.3 V 0.77 A

Manual: https://www.ti.com/lit/ml/spruis8/spruis8.pdf

There is a BlackHawk USB560 v2 System Trace device by this board. Can't find info on it in PTC Database. If this is needed, it may be useful for this board. Info can be found here: https://www.blackhawk-dsp.com/products/jtag-emulators/usb560v2

R5 Loading Information

R5 Loading

Lauterbach Emulator Information

Compatible Cable C4, C13, C14, C15, C16, and C17 cables. Also needs LA-7748 TI adapter and cTI-20Pin from TI. Compatible Cable LA-3743X.

In CPU dropdown, pick TDA4VM, then attach.

Lauterbach provides some demo scripts for this board in C:\T32\demo\arm64\hardware\j721e\j721e-ca72. The ones that have dra829v in the name were modified by Adina per Lauterbach to replace the references to TDA4VM with DRA829V. For boards running the Loewen SBL, startup-both-cores.cmm should be run once, and load-images-to-RAM.cmm can be run at the boot entry to overwrite boot and the KFS in RAM. Lauterbach scripts are archived at Loewen Lauterbach Scripts

Adina's scripts do not restart the board. Use X9 to restart the board, and once SBL has printed "FL Core is running..." to serial, in Trace32 click File->Run Script...

Navigate to C:\T32-Scripts and double click C:\T32-scripts\load-images-to-RAM.cmm. This script assumes there is a branch to self at the start of DeosBoot. It will load the ./deosBoot.bin and ./hypstart.dkfs to their starting RAM addresses.

DeosJacinto7EVM-2

DDCI Owned TI J721EXSOMXEVM

The following are the symbolic links to be modified when TFTP booting this board:

  • loewen/deosBoot-2.bin
  • loewen/composite-2.darc

See DeosJacinto7EVM-1 for additional information.

BSP UG has lengthy method of creating boot media since included SD card doesn't do what is needed. Cloning the SD card from DeosJacinto7EVM-1, and then updating the uboot env vars ethaddr, ipaddr, worked, so this board currently booting the same image.

Lauterbach Emulator Information

Compatible Cable C4, C13, C14, C15, C16, and C17 cables. Also needs LA-7748 TI adapter and cTI-20Pin from TI. Compatible Cable LA-3743X.

Lauterbach provides some demo scripts for this board in C:\T32\demo\arm64\hardware\j721e\j721e-ca72. The ones that have dra829v in the name were modified by Adina per Lauterbach to replace the references to TDA4VM with DRA829V. The scripts Adina uses are C:\T32-scripts\startup-dra829.cmm and C:\T32-scripts\connect-second-core.cmm. Adina's scripts do not restart the board. Use X9 to restart the board, and once U-Boot is printing to serial in Trace32 click File->Run Script...

Navigate to C:\T32-Scripts and double click C:\T32-scripts\startup-dra829.cmm To connect to secondary cores after boot has started them, run connect-second-core.cmm


Basic startup-dra829.cmm: 

 SYStem.CPU DRA829V
 SYStem.CONFIG CORE 2. 1. ; assign the trace32 instance to core 2 chip 1
 CORE.ASSIGN 1.
 break.select.program onchip ; Set breakpoints to default to onchip
 SYStem.Up  ; Connect to Cortex-A72; Connect to Cortex-A72

connect-second-core.cmm: 

 SYStem.Down
 CORE.ASSIGN. 1. 2.
 SYStem.Up

DeosJacinto7EVM-3

Customer Provided Hardware, on the Farm, but not on the network yet, in BSP development.

Emulator Connection
UART Connection

DeosLS1043ARDB-1

NXP Semiconductors LS1043ARDB-PD

MAC: 00049F05ACA9

Compatible Cable LA-3743X.

The following are the symbolic links to be modified when TFTP booting this board:

  • ls1043ardb/deosBoot.bin
  • ls1043ardb/composite.darc

Deos Video Memory is at a:0x80018000

LS1043 Emulator Connection
LS1043 Chassis
LS1043 Probe-Cable

There are multiple jtag connectors on this board. The emulator plugs into the one labelled CPU JTAG.

LS1043 Switches
LS1043 JTAG
LS1043 JTAG Adapter
LS1043 FrontPanel

Instructions to configure the Lauterbach for a LS1043A on a host can be found at Readme


DeosLouie-1

Farm-Stored - Location:SRack-1-1

Media:POC_MPC5676R_UserGuide.pdf

DeosLouie-2

Farm-Stored - Location:SRack-1-1

Media:POC_MPC5676R_UserGuide.pdf

DeosLouie-3

Emulator CPU type MPC5676R seems to work.

Woodward Hardware, requires IP over serial setup.


DeosLouieV2-C

This target has been removed from the farm. Returned to customer.


DeosLS1048ARDB-1

This target has been removed from the farm. Returned to Customer


DeosLS1088ARDB-1

Boeing NXP Semiconductors LS1088ARDB

MAC: 00049f0624ba (Note Ethernet is plugged into port labeled DPMAC3)

Dip Switch 4-2 is "Undefined" in the manual, but this needs to be ON for X9 power to have control.

Dip Switch 3-1 is ON (1) so the board is configured as ls1088.

Compatible Cable LA-3743X.

Notes for using the Lauterbach emulator on this board are located here.

The following are the symbolic links to be modified when TFTP booting this board:

  • ls10x8ardb/deosBoot.bin
  • ls10x8ardb/composite.darc
Front Panel
JTag Connector
DipSw 1
DipSw 2
Getting Started

DeosLS1048A-GL1-1

This target has been removed from the farm. Returned to Customer

DeosLS1048A-GL2-1

This target has been removed from the farm. Returned to Customer


DeosMCP1048-1

Program Santan Description Boeing Santan Program Dual MCP LS1048a
Manufacturer Boeing Processor Layerscape LS1048a
Part Number 9100086-NH01-001 Serial Number A00117
MAC Addr MAC-a: 00049F0624A1
MAC-b: 00049F0624A3 		Cable LA-3743X
BSP 
de-ls1048, santan-ls1048a
B side Bare Metal w/custom lwip.config
Captured Info 
Info uboot
Note Side-a SATA is Flakey, works some, doesn't respond other times.
  • To connect with Trace32 run T32-Scripts\...\ls1088a_connect_sap_dap.cmm
  • There are 2 LS1048a Processors on same board so 2 COM ports and 2 Ethernets, all on same power supply.
  • UBoot saveenv is write-protected by a jumper. Jumpers currently installed on P6 and P7 (pins 1 & 2).
    • DeosMCP1048-1a is MCP1 on COM4, saveenv P7
    • DeosMCP1048-1b is MCP2 on COM5, saveenv P6
  • Processor 1 boots with u-boot using tftp download links
  • Processor 2 is bare-metal boot.

When set up for bare metal boot (on either processor side), be sure to modify lwip.config for your hypstart image to include the MAC address matching the one listed in the table above.

  • The following are the symbolic links to be modified when TFTP booting this board (Side A):
    • ls1048a/santan-ls1048a/deosBoot-mcp1.bin
    • ls1048a/santan-ls1048a/hypstart-mcp1.bin
  • Currently booting legacy images from DeosDGPU-LS1048-GLx as shown:
    • deosBoot-mcp1.bin -> deosBoot-unrel-1.0.0-4.bin
    • hypstart-mcp1.bin -> hypstart-unrel-1.0.0-4.dkfs
    • deosBoot-mcp2.bin -> deosBoot-unrel-1.0.0-4.bin
    • hypstart-mcp2.bin -> hypstart-unrel-1.0.0-4.dkfs
DeosMCP1048-Farmed
Uboot Write Protect

SPI Flash Programming

  • Aardvark SPI flash programmer is attached to P1 (Side-a), but USB cable is not plugged into TFHost.
    • Note Side-b would be P11, also note Pin 1 is marked on connector with white tape with "1" scribed. Only 3 of the 4 pins on the connector are used, pin 4 hangs free.
    • RCW Binary and programming instructions
      • Files currently on TFHost here: C:\SharedFolder\MCP1048-RCW-Programming
    • To Program, power off, connect the 2 1/2 connected jumpers 1-2, and 3-4, wires already there.
    • Plug Aardvark back into TFHost USB Port.
    • Follow above instructions using the desktop shortcut Aardvark Flash-Center-GUI
SPI Adapter
Attached to P1 (Side A)
P4 Jumper needed for SPI Programming

DeosMCP1048-1b

See DeosMCP1048-1 entry above. This board has two independent processors ("a" and "b") which share a single power supply.

Side "b" has a bare-metal boot process. It does not use the tftp server. It boots from deosBoot directly, using the version stored in flash memory, and it uses the hypstart image stored on the SATA drive on the board.

When using this target, it is recommended that you lock both DeosMCP1048-1 and DeosMCP1048-1b to prevent accidental power cycling by other users.

With a Lauterbach attached, to boot from u-boot rather than bare-metal, use the steps given in the image below.

To reset the CPU, select the Up mode, then Attach mode. Then Go/Play to start the CPU after that reset.

DeosMCP1048-2

Program Santan Description Boeing Dual MCP Blue Version CCA1.0
Manufacturer Boeing Processor NXP Layerscape LS1048a
Part Number 9100084-NH01-001 Serial Number A118183
MAC Addr MAC-a: 06fdc0663e1b
MAC-b: 06fdc0663e2b 		Cable LA-3743X
BSP 
de-ls1048, santan-ls1048a
B side Bare Metal w/custom lwip.config
Captured Info Info uboot
  • To connect with Trace32 run T32-Scripts\...\ls1088a_connect_sap_dap.cmm
  • There are 2 LS1048a Processors on same board so 2 COM ports and 2 Ethernets, all on same power supply.
  • UBoot saveenv is write-protected by a jumper. Jumpers currently installed on P6 and P7 (pins 1 & 2).
    • DeosMCP1048-2a is MCP1 on COM3, saveenv P7
    • DeosMCP1048-2b is MCP2 on COM4, saveenv P6


Processor 1 (side A) boots with u-boot using these tftp download links:

  • ls1048a/santan-ls1048a/deosBoot-mcp1-2.bin
  • ls1048a/santan-ls1048a/hypstart-mcp1-2.bin


Processor 2 (side B) is bare-metal boot. If bare metal boot fails, U-Boot is started and tftp download will be tried.

  • See the santan-ls1048a BSP User Guide for loading boot and hypstart images for bare metal use.
  • If bare metal boot fails, U-Boot will load from the following symbolic links:
    • ls1048a/santan-ls1048a/deosBoot-mcp2-2.bin
    • ls1048a/santan-ls1048a/hypstart-mcp2-2.bin


When set up for bare metal boot (on either processor side), be sure to modify lwip.config for your hypstart image to include the MAC address matching the one listed in the table above.

The Lauterbach is connected to side b processor. Side b is set up for bare metal boot by default. To switch to u-boot startup, use the Lauterbach to stop at 0x30000000, modify the value in the pc register to be 0x30400000, then let the board run.

  • The bare metal boot uses the deosBoot version stored in flash memory on the board, and the hypstart.dkfs stored in the (SSD) hard drive on the board. See the BSP UG to change these if needed.


DeosMCP1048-2b

See DeosMCP1048-2 entry above. This board has two independent processors ("a" and "b") which share a single power supply.

Side "b" has a bare-metal boot process. It does not use the tftp server. It boots from deosBoot directly, using the version stored in flash memory, and it uses the hypstart image stored on the SATA drive on the board.

See the notes in the DeosMCP1048-1b section above for using a Lauterbach to launch U-Boot and allow flashing of deosBoot and/or the hypstart image.

When using this target, it is recommended that you lock both DeosMCP1048-2 and DeosMCP1048-2b to prevent accidental power cycling by other users.

DeosMercuryXU8-1

Program Vivios Description Enclustra XU8 4CG ST1 Zynq UltraScale+ SoC
Manufacturer Enclustra Processor UltraScale+ Dual A53, Dual R5
Part Number EN105185 Serial Number SN254858
MAC Addr MAC-ethact: d22c4153b196
MAC-eth1act: d22c4153b197 		Cable LA-3743X with LA-3863 adapter
BSP Mercury XU8 Aarch64 (variation of zcu102) Captured Info MercuryXU8

Trace32 ICD Arm USB, then choose CPU ZYNQ-ULTRASCALE+-APU

The following are the symbolic links to be modified when TFTP booting this board:

  • zcu102/mercury-xu8/deosBoot-1.bin
  • zcu102/mercury-xu8/composite-1.darc
Emulator Connection
Power Jumpers

DeosMFCC-8558

This target has been removed from the farm. RETURNED TO CUSTOMER 25 Apr 2019 (SHH)

DeosModelo1

Farm-Stored - Location:TBD

MAC: 0019b80115a4

This is a Boundary Devices Nitrogen6s-SOM evaluation board (Arm iMx6) on loan from the Modelo_Program.

The Nitrogen6x-som boot, pal, config and network driver can be installed using the cygwin installer. The target will TFTP boot to an image loaded at linux03.ddci.com:/tftpboot/nitrogen6xsom/ Create the hypstart image using the good old "makeboot @../etc/basecon.hyp -bootDest=dir:."

Pictures of what was received and the I/O definitions received by the customer are in the Loaner Hardware Lotus Notes database.

To switch back to boot Linux stop boot at the uboot cmd prompt and change the bootcmd environment variable to "run bootlinux"

Hardware Configuration of the Lauterbach

The following describes how to get the Lauterbach working with the Modelo (Nitrogen6x_SOM) board.

Using JTAG on the Nitrogen6x_SOM board requires that the RN1 set of resistors NOT be populated, on both the SOM board and the carrier board. Also, the RN2 set MUST be populated, on both the SOM board and the carrier board. The following two pictures show the location of both RN1 and RN2 (they are right next to each other) on both the SOM board and the carrier board.

Modelo Carrier Board with RN1&RN2 Circled
Modelo SOM Board with RN1&RN2 Circled

Next, there is a daughter card that connects the Lauterbach cable to the Nitrogen6x_SOM carrier board. This daughter card has several jumpers. Please ensure that jumpers J3, J4, and J6 are populated, with the remaining jumpers left open. The following two pictures show not only the jumpers, but also how the daughter card must be aligned with the carrier board, and how the Lauterbach cable is to be plugged into the daughter card.

Modelo Carrier Board Daughter Card Front
Modelo Carrier Board Daughter Card Rear

Software Configuration of the Lauterbach

In TRACE32, the following configurations are required. First, the CPU type must be set to imxSoloLite (click on CPU -> System Settings then click the CPU button). Next, by default, there are way too many things that cause the emulator to stop the target. To turn these things off, click on Trace -> Configuration, then click the TrOnChip button, and finally uncheck everything that you don't want (a good place to start is uncheck everything except reset). Also note that you must 'attach' the emulator to the target (click on CPU -> System Settings, then click the attach radio button).

DeosMPC5676R

Farm-Stored - Location:TBD

Axiom MPC5676R reference board.

DeosMPC5777c-1

MPC5777c Target. Location: Rack 2-4B


DeosMPC5777c-2

Farm-Stored - Location:Cabinet 1-4

MAC: DE2017103006

See here for details.

DeosMPC8315E-1

This target has been removed from the farm.

DeosMPC8548

This target has been removed from the farm.


DeosNAI67G6-1

NAI 67G6 Prototype Board with Xilinx Zynq UltraScale+ SoC with dual A53 cores.

MAC: 7acd80c41a11

Compatible Cable LA-3743X.

Use TRACE32 ICD ARM64Bit USB already installed on hofmann.

The following are the symbolic links to be modified when TFTP booting this board:

  • nai67g6/deosBoot.bin
  • nai67g6/composite.darc
NAI67G6

DeosNAI67PPC2-FW

Program Savianos2 Description NAI 67PPC2 T2080E Development board w/FireWire
Manufacturer NAI Processor NXP QorIQ T2080 Quad Core e6500 Processor @ 1.8 GHZ
Part Number 67PPC2-B-B003 Serial Number N3878310011
MAC Addr 004521525600 Cable LA-3794
BSP nai68ppc2 Captured Info Info

PCIe FireWire Card SD-LP-TIFWB, SN 12080701622 https://www.syba.com/index.php?controller=Product&action=Info&Id=584

One Firewire cable was provided. Connected to 67PPC2's Cable marked #1 (of 6), and Hofmann Adapter Port #2. Hofmann adapter has 3 ports, only 2 and 3 have compatible connectors.

Can boot linux or uboot via remotely controlled jumper X9 - DeosNAI67PPC2-Jumper.

The following are the symbolic links to be modified when TFTP booting this board:

  • nai68ppc2/nai67-deosBoot.bin
  • nai68ppc2/nai67-composite.darc
  • nai68ppc2/68ppc2.dtb
NAI67PPC2 Emulator
NAI67PPC2
NAI67PPC2 Bank Select
NAI67PPC2 Jumper
Hofmann FW Adapter
NAI67PPC2 FW Cables

DeosNAI68ARM2-1

Program Wickford, and Others Description Xilinx Zynq UltraScale+ SoC, dual A53 cores
Manufacturer NAII Processor UltraScale+ A53
Part Number 68RTARM2-A-B003 Serial Number N4165130004
MAC Addr MAC-ethact: 3aec81838263
MAC-eth1act: ee57272a4919 		Cable LA-3743X
BSP nai-ultrascale Captured Info media:Manual68ARM2.pdf, zynq

Trace32 ICD Arm USB, then choose CPU ZYNQ-ULTRASCALE+-APU, then Attach

The onboard SATA device is write-protected, disable with uboot via: setenv sataenbl mw.l 0x83C10094 0

Remember the bootcmd "deosBoot" needs to then "run sataenbl" as part of its sequence.

U-Boot has backup to boot Petalinux.

The following are the symbolic links to be modified when TFTP booting this board:

  • nai68arm2-1/deosBoot.bin
  • nai68arm2-1/composite.darc
NAI68ARM2 Front
NAI68ARM2 Back

DeosNAI68ARM2-2

Program Wickford, and Others Description Xilinx Zynq UltraScale+ SoC, dual A53 cores
Manufacturer NAII Processor UltraScale+ A53
Part Number 68RTARM2-1 Serial Number 68ARM2-C-220XB003
MAC Addr MAC-ethact: 861697dac666
MAC-eth1act: fe4fe87c354d 		Cable LA-3743X
BSP nai-ultrascale Captured Info media:Manual68ARM2.pdf, zynq

Trace32 ICD Arm USB, then choose CPU ZYNQ-ULTRASCALE+-APU, then Attach

The onboard SATA device is write-protected, disable with uboot via: setenv sataenbl mw.l 0x83C10094 0

Remember the bootcmd "deosBoot" needs to then "run sataenbl" as part of its sequence.

U-Boot has backup to boot Petalinux.

The following are the symbolic links to be modified when TFTP booting this board:

  • nai68arm2-1/deosBoot.bin
  • nai68arm2-1/composite.darc

JTAG adapter wire disconnected from adapter, but is still attached to board. Board can be used for testing but cannot support a Lauterbach connection.

DeosNAI68INT6-1

Program Savianos2, and Others Description NAI68INT6 Intel Core i7-118xGRE
Manufacturer NAII Processor Intel i7 Tiger Lake
Part Number 68INT6-tbd Serial Number notVisible
MAC Addr 00A0C9082101 Cable C21a/b or C20/22
BSP come-ctl6 2.0.0 throws exception Captured Info media:Motherboard Manual-68INT6.pdf

TFHost c:\t32-scripts for OOB.cmm (TRACE32 ICD x86 64-bit USB) and int6-inband.cmm (TRACE32 Start) debugging methods.

DCI OOB Currently Configured, so use the OOB.cmm script to connect.

USB Auto Switch Installed

Two USB Sticks available, labeled:

68INT6-1a experimental for swapping

68INT6-1b experimental for swapping

Video memory at A:0x18000

  • Booting Linux
    • To get to Linux, in PuTTY stop the grub autoboot by pressing "c" no quotes within 5 seconds.
    • type "exit" at the grub prompt to enter BIOS and select Boot Manager, hit enter.
    • arrow down to "ubuntu ..." and hit enter.
    • Linux Login Username/Password: nai/nai

See Alternative Approach for video dump instructions.

Serial connection works for BIOS, EFI, and Grub, need to "exit" the first thing to get access to the others.

Farmed
BIOS Options

DeosNAI68PPC2

Program Celestial, and Others Description Power PC T2080 Platform
Manufacturer NAII Processor PPC QorIQ T2080 quad-core
Part Number 68PPC2-2-TE2Z000340WC100 D/C: 1929,
68R TPPC2-TE-A-B003 Rev A DC: 1920 		Serial Number N3871170003
MAC Addr 004532092503 Cable LA-3794
BSP nai68ppc2 Captured Info Info
  • The following are the symbolic links to be modified when TFTP booting this board:
    • nai68ppc2/deosBoot.bin
    • nai68ppc2/composite.darc
  • Note that uboot has an environment variable to boot a jupiter set of images called jupiter_bootcmd which does not use the above links.
  • Env Var bootcmd can be either of the following
    • cpld procreset 1;cpld tempalarm 0;run kismet_bootcmd (current)
    • cpld procreset 1;cpld tempalarm 0;run jupiter_bootcmd
      • As of this update, jupiter_bootcmd is:
jupiter_bootcmd=tftp 040000 nai68ppc2/68ppc2.dtb;fdt addr 040000;fdt boardsetup;fdt resize;run clockfreq;run busfreq;run timebasefreq;tftp 19000 nai68ppc2/deosBoot-jupiter-5.0.1.bin;tftp 0x0140000 nai68ppc2/composite-jupiter-5.0.1.darc;run sataenbl;go 19000 040000


Settings for the Relay Board: COM#, 9600, 8, N, 1

Part Serial Numbers
Emulator Connection Fragile!
NAI68PPC2 Chassis
NAI68PPC2 ENet Ports
NAI68PPC2 ENet PartNo
NAI68PPC2 Relay board
NAI68PPC2 Relay board instructions.

DeosNAI68PPC2-2

Program Celestial, and Others Description Power PC T2080 Platform
Manufacturer NAII Processor PPC QorIQ T2080 quad-core
Part Number 68PPC2-2-EM1CM50340KC370 Serial Number 549183
MAC Addr 004521525601 Cable LA-3794
BSP nai68ppc2 Captured Info Info

The following are the symbolic links to be modified when TFTP booting this board:

  • nai68ppc2/nai2-deosBoot.bin
  • nai68ppc2/nai2-composite.darc

Changes required in lwip.config file:

  • interface=dtsec:2,1,FMANV3,FORCEMAC DHCP 192.168.14.100 255.255.255.0
  • ethernet 00-45-21-52-56-01

The board can boot-bare-metal or U-Boot. If the U-Boot path is desired, all the bits in the Relay Board must be set to ON.

To enable writes to the SATA device, uboot needs to define and run this command: sataenbl=mw.l b1003f4c 0

Settings for the Relay Board (Pic on DeosNAI68PPC2): COM4, 9600, 8, N, 1

Sending Ctrl-@ sets all bits to zero, turning off all relays.

Sending Ctrl-O (Ohhhh, not zero) sets all bits to 1's, turning on all relays.

Part Serial Numbers
Emulator Connection Fragile!
NAI68PPC2 Chassis
NAI68PPC2 ENet Ports

DeosCelestial

This target has been removed from the farm, returned to customer.

DeosCelestial-2

Program Celestial Description NAI Power PC T2080 Platform
Manufacturer NAII Processor PPC QorIQ T2080
Part Number 68PPC2-2-EM1CM50340WH470-CM16 Serial Number 574236
MAC Addr 0016C60094BE Cable LA-3794
BSP celestial Captured Info Info

Open Arbor Testing requires DeosCelestial-2-JMPR to be OFF, and emulator if attached to be ON.

2022-11-02 Firmware updated to: MBCR 00004.00126, FPGA 00006.00001

WARNING! Hyperstart images are stored on media also used by CFFS Examples when Media MAL is used.

MAC(s): 4 Ethernet connections wired to Gigabit Switch

Celestial-2 Ports and MAC Addresses
Port lwip config driver name/minor number MAC address
EM1 Eth1 pro1000:0 0016C60094BE
EM1 Eth2 pro1000:1 0016C60094BF
PPC PORT1 (DTSEC3) dpaa:2,1,FMANV3 004521525800
PPC PORT2 (DTSEC4) dpaa:3,2,FMANV3 004521525801

Target boots uboot when DeosCelestial-2-JMPR is ON

To install emulator adapter cable, instructions from NAII:

Removal:

• First, we must remove the back cover of the NAI SIU36. Unscrew each 3/32” hex bolts. Note: they will stay as part of the cover using a spring retainer.

• After opening up the back-cover. Locate the 68PPC2 motherboard. It is the right-most card in the chassis, opposite the power supply.

• Loosen the 3/32” wedge-lock hex bolts. Do not remove completely, just until it’s loose.

• Use the card’s built-in extractor to push the card out of the chassis. The extractor is the black lever with our company’s info on it.

• Slide the card completely out.

Installation of JTAG connector:

• Refer pics for how the JTAG extender cable attaches to the 68PPC2 and Lauterbach.

Installation:

• Carefully insert the card back into the chassis in the same orientation. Be careful of the JTAG cable.

• Push card firmly back into the chassis.

• Tighten up the wedge lock hex bolts. Not too tight. I think the spec is 4Nm

• Leave cover off.

• Point a Fan at the chassis

DeosCelestial-2
Four Ethernets
Emulator Pre-Bent towards center, Fragile!
Emulator Pin1 to Square pad

DeosCelestial-3

This target has been removed from the farm. 2024-07-2x Returned to Customer

DeosCelestial-4

This target has been returned to its owner.

DeosP1010RDB

Farm-Stored - Location:TBD

MAC: 00049F02145D

NOT AVAILABLE - Sent to Chris Pow

P1010RDB - Click on image for higher resolution
P1010RDB - Click on image for higher resolution

Freescale development board for the QorIQ P1010 PPC CPU (e500 core). The documentation that came with the board is on \\Nx3000\Deos\Freescale\P1010RDB.

Warning: Currently booting kernel 8.3.1

To rig a P1010 on the farm, use a serial terminal (PuTTY) to enter the uboot terminal. Save off the environment variable for bootcmd as linuxboot (or whatever it would boot to). Create a new environment variable to boot to deos: 

setenv bootDeos 'tftp 1a000 /p1010/deosBoot.bin;tftp 400000 /p1010/active-hypstart.bin; go 1a000 400000'

Then replace the bootcmd with the one pointing to our bootDeos: 

setenv bootcmd 'run bootDeos'

Save these settings: 

saveenv

To determine the MAC address, issue the printenv instruction. Look for a line like: 

ethaddr=00:04:9F:02:FB:A5

DeosP1010RDB2

This target has been removed from the farm.

See DeosP1010RDB

DeosP2041RDB

Farm-Stored - Location:TBD

MAC: 00e00c00ea01

Freescale development board for the QorIQ P2041 PPC CPU (e500mc core). The documentation that came with the board is on \\Nx3000\Deos\Freescale\P2041RDB. Pictures of what was received are in the Loaner Hardware Lotus Notes database.

The network cable is currently plugged into DTSEC2. If moved, the registry must be changed as documented in the dtsec-release-notes.htm. The bootcmd in U-Boot is setup with DTSEC2 as the active interface. The default bootcmd (multicore) should be:

  • setenv ethact FM1@DTSEC2; tftp 21000 /p2041rdb/deosBoot.bin;tftp 400000 /p2041rdb/hypstart.bin;go 21000 400000

When updating the hypstart image on the TFTP server, please use a symbolic links (named hypstart.bin or deosBoot.bin) to point to your images. When done, please reset the symbolic link to point to a hypstart image with an 8.1.x kernel. The following example creates a symbolic link pointing to a single core hypstart image:

  • ln -s hypstart-sc.bin hypstart.bin

Since this board is very configurable, I feel it is necessary to point out some of the options to look out for.

Options:

  • U-boot version
  • Reset Configuration Word - controls clock speed and I/O interfaces
  • Hardware DIP Switch settings.

It is also important to note that the hardware manuals show a method of configuring the board as a 2040 (one processor) by changing DIP switches. This will not work with the current BSP.


The board in the DDC-I target farm has the following versions of these options: 

      U-Boot 2011.12-00025-gc6d9d50 (Oct 24 2012 - 04:48:58)

      Reset Configuration Word (RCW):
      00000000: 12600000 00000000 241c0000 00000000
      00000010: 648ea0c1 c3c02000 de800000 40000000
      00000020: 00000000 00000000 00000000 d0030f07
      00000030: 00000000 00000000 00000000 00000000

      DIP Switch Settings are not known by me at this time need to consult with PHX office to determine.

There is a newer board that is in Gary Gilliland's office in Dallas. The BSP has been verified to work on this board also it has an newer U-boot. 

      U-Boot 2013.01-00115-g831b30d (Jun 15 2013 - 05:53:49)

      Reset Configuration Word (RCW):
      00000000: 12600000 00000000 241c0000 00000000
      00000010: 648ea0c1 c3c02000 de800000 40000000
      00000020: 00000000 00000000 00000000 d0030f07
      00000030: 00000000 00000000 00000000 00000000

      The DIP switches on the board are set as follows:

      SW1 - 10110100
      SW2 - 00100100
      SW3 - 01010111

DeosPaschal

This target has been removed from the farm. The information below is being retained in case we get our own chassis and have to support FACE labs (or a customer with a VPX6-187)

DeosPMC5674B

This target has been removed from the farm.


DeosPMC5675A

This target has been removed from the farm.

DeosQuadi7

Farm-Stored - Location:TBD

MAC: A0F3C103739E

A Dell Optiplex 7010 with a quad-core Intel Core i7 3.4GHz processor.

DeosQuadi7 Bios - Click on image for higher resolution
DeosQuadi7 Memory - Click on image for higher resolution

This platform runs the intel-mc BSP. It boots from a USB stick.

The target currently has hyper threading disabled in the Bios.

This target currently has 8GB of DDR3 2133MHz RAM (4GB in DIMMs 1 and 2, with DIMMs 3 and 4 empty). The memory operates at 1600MHz. The memory is Patriot PVI38G213C1K 2133MHz (11-11-11-27).

See X9 for host, network, emulator, and serial port connections.

DeosSP0_3U_SBC-1-1

This target has been removed from the farm. Returned to customer (MDA).

MAC: 00807a807f90

DeosSP0_3U_SBC-1-2

This target has been removed from the farm. Returned to customer (MDA).

DeosS32_JMPR

A Relay board connected to a 5V phone power supply on one side, and 3-way female jumper connector on the other. Used to remotely control the selection of pins 1&2, or 2&3 on a 3-Way jumper.

Power OFF Jumpers 1&2, Power ON Jumpers 2&3. S32 boots from SD when in 1&2 (Off) position. Please leave in off condition when finished to preserve relay life, and so board will boot.

Green - Normally Closed - J37 Pin 1 - Selects SD Card Yellow - Common, Center - J37 Pin 2 Orange - Normally Open - J37 Pin 3 - Selects eMMC

Relay Jumper1
Relay Jumper2

DeosS32V234

MAC: 001BC3123422

Compatible Cable LA-3743X.

  • The emulator must be powered on in order for the target to boot.
  • Due to a longer than usual U-Boot boot delay, allow up to 15 seconds from power-on to "ping."
  • Although a multicore kernel is present, only a single processor core is supported.
  • Use a serial connection to inspect U-Boot's bootcmd environment variable for specific settings.

Reference: $DESKHOME/help/s32v234-bsp-user-guide.htm

The following are the symbolic links to be modified when TFTP booting this board:

  • s32v234/deosBoot.bin
  • s32v234/hypstart.bin

Emulator Tips

  • The serial connection is RS-232 to USB. This means one cannot connect putty or hyperterm until after the target has been powered on.
  • Use "Trace32 ICD ARM64 USB" Trace32 client.
  • Use S32V234 for the CPU setting.

After an "In target reset", the Lauterbach will generate an error and stop as if in a breakpoint in uboot code. This appears to be a mis-configuration of the lauterbach. The message is something like: 

 bla bla cti core base address 0 0x90010000 cti base address 0 0x90020000

A quick search of the lauterbach web indicates this implies the need for some commands, e.g., 

 system.config coredebug base 0x90010000
 system.config cti base 0x90020000

But that doesn't work, the emulator complains about a conflict with one of the other cores. I didn't investigate much. One can press go again and continue executing U-Boot, transition to Deos Boot, etc.

SD_eMMC_Selection
Emulator

DeosS32V234-2

This target has been removed from the farm.

DeosS32V234-3

Korry NXP S32V234 Evaluation Board

MAC: 6097dd022ac6 100 MBit Switch (Gigabit requires unreleased fec_andretti).

Compatible Cable LA-3743X.

Quick start page points user to: http://www.nxp.com/SBC-S32V234

The following are the symbolic links to be modified when TFTP booting this board:

  • s32v234/deosBoot-3.bin
  • s32v234/composite-3.darc

May be useful information above for the DeosS32V234 board

Has mini-pci Network card installed, uboot reports as:

BusDevFun VendorId DeviceId Device Class Sub-Class
01.00.00 0x8086 0x10d3 Network controller 0x00

Media:KoryS32ubootasreceived.txt

Farmed
BoardView

DeosS32V234-4

This target has been removed from the farm. RETURNED TO CUSTOMER (13 Feb 2023 by JMK)

DeosS32V234-5

Korry NXP S32V234-EVB2 Evaluation Board

This target has been removed from the farm. Stored: Storage Room Wall.

DeosShakaMX8-1

Program Shaka Description iMX8 based board with custom I/O attached
Manufacturer TQ Processor iMX8
Part Number SOM:TQMa8x, Carrier:MBa8x REV02XX Serial Number N/A, not visible
MAC Addr 00d093520705 Cable LA-7843
BSP imx8qm-aarch64, was imx8qm Captured Info Info

ETH0 Connected, ETH1 available

Make sure your lwip.config has this boards MAC address (see IP Address Table, or uncheck so it does not update).

Can boot linux with run mmcboot command in uboot.

This target has three different u-boot SD cards:

  • U-Boot for A53 cores i.e. imx8qm OR imx8qm-aarch64 ("no stripe" black 8GB card, supports PCI) <-- Use as default
  • U-Boot for 64-bit A72 cores i.e. imx8qm-a72-aarch64 ("red stripe" white 8GB card with RED stripe, no PCI support)
  • U-Boot for A53 cores ("white stripe" white 8GB card, supports PCI, no linux boot, may require u-boot variable changes to support pcie-scanner properly)

The SD cards must be manually swapped if changing the intended core for the target or features.

  • NOTE: This target has only 2 A72 cores (and 4 A53 cores).
    • When running imx8qm-a72-aarch64, you must have the deosBoot and composite tftp images loaded for that BSP linked or the board will not start. This is because the kernel in the non-a72 BSP flavors expects 4 cores and will not start with only 2 cores running.

General use default: "no stripe" SD card, aarch64 deosBoot.

The following are the symbolic links to be modified when TFTP booting this board:

  • imx8qm/deosBoot-shaka-1.bin
  • imx8qm/composite-shaka-1.darc

Black SD card can boot Linux, halt uboot and type "run mmcboot"

To attach the Lauterbach emulator while in U-Boot, see the directions in SCM scripts are in C:\T32-scripts already.

mini-pci card installed, it is a Network card (an Intel i210), uboot reports as: TBD

BusDevFun VendorId DeviceId Device Class Sub-Class
01.00.00 0x8086 0x10d3 Network controller 0x00

DeosShakaMX8-1 Farmed
Boot Mode Switches (SD Shown)
Emulator Not Keyed Check Pin 1

DeosShireZU6

This target has been removed from the farm. Returned to Customer.

DeosSpearMX8

This target has been removed from the farm. 2024-07-08 Returned to Customer


DeosSpearMX8-2

This target has been removed from the farm. 2024-07-08 Returned to Customer


DeosSpearMX8-3

Program TrickyFish, Blue Label Description Variscite Spear-MX8 Development Kit
Manufacturer Variscite Processor NXP ARM QuadMax Dual Cortex-A72 + Quad Cortex-A53
Part Number VCB-SP8-04A, V1.3-1221039 Serial Number F8DC7A7F09A0
MAC Addr F8DC7A7F09A0 Cable LA-7843
BSP imx8qm or trickyfish Captured Info Info

Make sure your lwip.config has this boards MAC address.

U-Boot SPL 2018.03-imx_v2018.03_4.14.98_2.0.0_ga_var01+g433901fa5a (Dec 21 2021 - 21:43:22 +0000)

The following are the symbolic links to be modified when TFTP booting this board:

  • trickyfish/deosBoot-spear-3.bin
  • trickyfish/composite-spear-3.dkfs

Currently booting the following images from the tftp server:

  • trickyfish/deosBoot-2.2.0.bin
  • trickyfish/rfs-images/ddciSWLFS0.dkfs

To attach the Lauterbach emulator while in U-Boot, see the directions in SCM scripts are in C:\T32-scripts already.

https://deos.ddci.com/scm/Deos/products/bsp/imx8/references/lauterbach/scripts/

Appears to save uboot environment to MMC, careful running filesystems with MMC MAL's

Boot Selection (BOOT): In SEL position boots from the SD card in the carrier, in BOOT position boots eMMC on the SOM.

Trickyfish DEOS I/O Hardware Setup and Wiring Instructions: media:DDCI-Wiring-Instructions.pdf

IO Device Spec Sheets

UBOOT Restore Command
setenv board_rev iMX8QM;setenv bootcmd "run bootdeossimple";setenv bootdelay 3;setenv bootdeossimple "tftp 0x82019000 trickyfish/deosBoot-spear-3.bin && tftp 0x8d660000 trickyfish/lfs-simple-spear-3.dkfs && dcache off && icache off && go 82019008 8d660000";setenv bootdeos "tftp 0x82019000 trickyfish/deosBoot-spear-3.bin && tftp 0x8d660000 trickyfish/stableImages/2.0.0/selectionArchive.darc && tftp 0x82060000 trickyfish/stableImages/2.0.0/ddciSWLFS0.dkfs && tftp 0x8d760000 trickyfish/stableImages/2.0.0/ddciSWLFS1.dkfs && tftp 0x86e62000 trickyfish/stableImages/2.0.0/dataLoaderMFS.dkfs && tftp 0x8a062000 trickyfish/stableImages/2.0.0/ofpMFS.dkfs && dcache off && icache off && go 82019008 8d660000";setenv fdt_file undefined;setenv fdtcontroladdr fce07560;setenv fileaddr 82019000;setenv filesize 41dc;setenv ipaddr 10.0.1.26;setenv netmask 255.255.252.0;setenv serverip 10.0.1.208;setenv soc_rev revb


Current UART Connections
TFHost COM J Connector Target UART
COM4 USB UART0
COM7 J23 2-Y, 4-Z, 6-B, 8-A UART1 via RS422
COM5 J26 17-tx, 19-rx UART2
COM6 J20 14-tx, 16-rx UART3
Current SPI Connections
SPI Bus J Connectors SPI Device
SPI 0 J20 1-clk, 3-sdo, 5-sdi, 7-cs0 w25q128fv
SPI 2 J20 13-clk, 15-sdo, 17-sdi, 19-cs0 w25q128fv
Current I2C Connections
I2C Bus J Connectors I2C Device
I2C 2 J26 12-scl, 14-sda 24LC32A
I2C 4 J26 16-scl, 18-sda 24LC32A

GPIOs 23, 24, 25 are currently connected to a relay module for remote control via TFHost01.

The USB Relay Manager application is on TFHost01 c:\RelayControl\GuiApp_English.exe
First click 'Find Device', then select the one and only found device from the drop-down (HW554), then click 'open device'.
The At-Rest, Default state is 'close' which means the GPIO is connected to Ground. Click open to put the GPIO into an open
state (no connection).

Best to leave relays in the 'Close All' state to preserve relay life. 

   Pin J29-12 (ADC_IN4, aka GPIO3_IO22)  No Connection
   Pin J29-14 (ADC_IN5, aka GPIO3_IO23)  Relay 1
   Pin J29-16 (ADC_IN6, aka GPIO3_IO24)  Relay 2
   Pin J29-18 (ADC_IN7, aka GPIO3_IO25)  Relay 3

See the BSP README file for instructions on how to build the Boot to use these GPIOs for image selection.

GPIO Loopback Connections
From Pin To Pin
J29-4 (ADC_IN0, aka GPIO3_IO18) J29-6 (ADC_IN1, aka GPIO3_IO19)
J29-8 (ADC_IN2, aka GPIO3_IO20) J29-10 (ADC_IN3, aka GPIO3_IO21)
J29-12 (ADC_IN4, aka GPIO3_IO22) J29-14 (ADC_IN5, aka GPIO3_IO23)
J29-16 (ADC_IN6, aka GPIO3_IO24) J29-18 (ADC_IN7, aka GPIO3_IO25)
J20-2 (GPIO0.IO08) J24-14 (GPIO2.IO08)

DeosSpearMX8-4

Program TrickyFish Description Variscite Spear-MX8 Development Kit
Manufacturer Variscite Processor NXP ARM QuadMax Dual Cortex-A72 + Quad Cortex-A53
Part Number VCB-SP8-04D, V1.3D-0223026 Serial Number F8DC7A7F0938
MAC Addr F8DC7A7F0938 fixed IP 10.0.1.67 Cable LA-7843
BSP imx8qm or trickyfish Captured Info Info

On Loan from Customer for debug; Gary, Ryan, Adina and Eliecer currently investigating

Red SD - No markings, presume good, boots linux and logging in as root does some flash programming automatically.

Blue SD - Marked "BAD EED51 CORRUPT IMAGE" boots linux, logging in as root just stops at prompt.

This Board Specific Info also stored here: \\tfhost14\SharedFolder\DeosSpearMX8-4

To attach the Lauterbach emulator while in U-Boot, see the directions in SCM scripts are in C:\T32-scripts already.

https://deos.ddci.com/scm/Deos/products/bsp/imx8/references/lauterbach/scripts/

Surcouf

The Surcouf target is located at the customer site, not actually on X9. TeamViewer has been installed on TFHost18 so that we can share access. The customer is currently using the target machine, but it will be dedicated for Deos engineers only starting June 6. Instructions to access the target through TeamViewer are at Readme.


Please consider that if you are running a release boot, the watchdog is enabled and it will reboot the board at 2 min. If you need the watchdog disabled while you flash the other boot, run this lauterbach script to disable the watchdog: 

SYStem.CPU MPC8548
SYStem.BdmClock 10.MHz
SYStem.attach
break
PER.Set.simple ANC:0x00:0xE800000c %Long %BE 0
go

DeosT1042D4RDB-1

An NXP T1042D4RDB Development System

MAC: 00049F05B78B

Switch: 10/100 Switch

The following are the symbolic links to be modified when TFTP booting this board:

  • t10xx/deost1042d4rdb-1/deosBoot.bin
  • t10xx/deost1042d4rdb-1/composite.darc

See DeosT1042D4RDB-2 for additional info.

T1042-1 MAC Addresses

DeosT1042D4RDB-2

An NXP T1042D4RDB Development System

MAC: 00049F05B795

Switch: Gigabit Switch, uboot was intermittent on the Gigabit Switch, added the following env var and called from bootcmd, bit 5? causes auto-negotiation to restart.

  • fixPhy=mii write 4 0 0x1160;sleep 1

The following are the symbolic links to be modified when TFTP booting this board:

  • t10xx/deost1042d4rdb-2/deosBoot.bin
  • t10xx/deost1042d4rdb-2/composite.darc

Compatible Cable LA-3794.

As delivered one would have to press the power button to turn the unit on. J39, an open 2-pin jumper can be shorted/jumped to bypass the power switch so X9 can control power, see photo.

Ethernet cable connected to port labeled ETH0, however the MAC address for DTSEC4 being broadcast is associated with the labeled ETH3: MAC.

T1042 Front
T1042 Power Jumper
T1042-2 MAC Addresses

DeosT2080RDB

An NXP T2080RDB Development System

MAC: 00049F04736E

Compatible Cable LA-3794.

T2080RDB Emulator
T2080RDB SATA Connector

The following are the symbolic links to be modified when TFTP booting this board:

  • t2080rdb/deosBoot.bin
  • t2080rdb/composite.darc

DeosT4240QDS-1

Farm-Stored - Location:TBD

MAC: 00049F0378A7

A Freescale QorlQ T4240 Development System

To use the emulator:

  1. Use cable C7
  2. Turn on the emulator via x9
  3. Turn on the target via x9
  4. Launch Trace32 via Trace32 ICD PPC64Bit USB shortcut. Note the PPC64Bit. The 32Bit variant will not work.
  5. In Trace32, Choose CPU, System Settings, and set CPU to T4240
  6. Select "Up" or "NoDebug". Note that the "Go" radio button in B::SYStem doesn't work, instead use the play button in the toolbar (also cleverly labled with tooltip "go")
T4240 Emulator

DeosTurbotQuadCore-1

Program All, DDCI-Owned Hardware Description Minnow Turbot Quad-Core, Intel Atom E3845
Manufacturer MinnowBoard.org Processor x86 Intel Atom E3845
Part Number 80500-0139-G01 R304 Serial Number 1145171114
MAC Addr 0008A20CF399 Cable None
BSP minnow-turbot Captured Info Info


BIOS Configuration

BIOS configuration requires a micro hdmi to regular hdmi cable, hdmi monitor, and USB keyboard. BIOS has boot configuration, default goes to its own boot loader shell prompt, its possible the BSP users guide and the version of the BIOS are out of sync, however there is a shell command to change the primary boot device to the SD card slot, assuming it is not already configured.

If the board stops booting, check out the BSP UG regarding Configuring the BIOS for Deos. Let board boot to the command shell prompt and type:

  • bcfg boot dump # lists all boot devices in boot order, figure out which one you want to boot from, note its <#>, probably the highest one.
  • bcfg boot mv <#> 0 # Replace <#> with above noted number. to set the SD/USB as the primary boot device. i.e. bcfg boot mv 4 0

This command moves the desired boot option to location "0", moving "0" down a notch to "1" etc. We believe that if you power the board without bootable media in the SD/USB card slot, the BIOS re-selects the shell as primary boot. This can be done within the BIOS also, pressing F2 or <ESC> during power up, and navigating the BIOS menus for boot order.

If a BIOS change causes you to loose access to the BIOS. i.e. pressing F2 etc does not get you to the BIOS. Place a jumper on J7 which is a lone 2-pin header between the SD card and fan, and press the delete key repeatedly during boot.

Pictures

TurbotQuadCore
TurbotQuadCorePN-SN

Setting up serial

To use serial, attach a FTDI adapter to uart3. To get output, attach the turbot quad tx pin (pin 5) to the pin labeled RXD on the adapter side. To get serial input, attach the turbot quad rx pin (pin 4) to the pin label TXD on the adpater side. Note: the picture only shows serial output as that was all that was needed at the time. Plug the adapter into a USB port. The driver should load automatically. When the device drivers have loaded, right click the device (from the devices and printers view), select properties, and then navigate to the Hardware tab to view what COM port the device is using. The COM port number can be used in a putty terminal to view the serial output. Note uart3 does not use the other signals (CTS and RTS).

TurbotQuad Uart3 Pinout
FDTI Adatper Serial to USB
Turbot Serial Schematic

Flashing The BIOS

If a new Minnow board is acquired that has a 64-Bit BIOS, it will need to be re-flashed with a 32-Bit Bios.

Binaries and instructions have been stored in subversion here:

https://deos.ddci.com/scm/Deos/products/bsp/minnow-turbot/branches/mainline/docs/BIOS-Flash-Files/

DeosTurbotQuadCore-2

Program All, DDCI-Owned Hardware Description Minnow Turbot Quad-Core, Intel Atom E3845
Manufacturer MinnowBoard.org Processor x86 Intel Atom E3845
Part Number 80500-0139-G01 R304 Serial Number 1110182246
MAC Addr 0008A20D903F Cable None
BSP minnow-turbot Captured Info Info

See DeosTurbotQuadCore-1

DeosVarsity

This target has been removed from the farm.


DeosVPX3-1708-1

This target has been removed from the farm, returned to customer 10/02/2024.

DeosXPedite5970-1

This target has been removed from the farm. Stored - Location:TBD

MAC: 00173C02C2E6

Extreem Engineering XPedite5970 with Freescale T2080 processor.

DeosXPedite5970-2

This target has been removed from the farm.

MAC: 00173C02C2E7

DeosZCU102-1

Program Durants, Shire, and Others Description Xilinx Ultrascale+ MPSoC Evaluation Board
Manufacturer Xilinx Processor Zynq UltraScale+ MPSoC ARM Cortex-A53, Cortex-R5F
Part Number HW-Z1-ZCU102 Rev D1 Serial Number 813415031624-54777
MAC Addr 000A3500890A Cable LA-3743X
BSP zus Captured Info Info

SD Card UBoot Current boot switch setting (up, dn, dn, dn: 1234)

Customer Provided UBoot on SD card: C:\svn\DDCI\administrivia\customer-specific\shire\customer-documents\ZCU102-uboot-20221213.bin

Uboot enables IP Block SPI Interface on J55 Connector, responds to: md A0000060 1

SPI flash Attached, See Logic Analyzer section for connection info (LA not currently connected, but flash chip is).

ZCU102 Boot Mode Switches - Click on image for higher resolution

The following are the symbolic links to be modified when TFTP booting this board:

  • zcu102/deosBoot-1.bin
  • zcu102/composite-1.darc

To use the emulator

  1. Turn on the emulator via x9
  2. Turn on the target via x9
  3. Use Trace32 client software on Host Machine
    1. CPU is zynq-ultrascale+APU.
    2. To start:
      1. B::System.attach
      2. Hit "pause"
      3. Hit go/play.
      4. If you are having trouble viewing memory try issuing the following 2 commands "translation.on", "translation.tablewalk.on"

Until all cores are released from reset there are various errors about processor in reset and config issues. After a while the pause is not needed anymore.

ZCU102 Emulator Connection - Click on image for higher resolution

Updating the SD Card Remotely

The easiest way to update the files on the SD card is to take the SD card out of the target and plug it into a PC. For those working remotely it is possible to update files on the SD card using U-Boot commands. Here are the steps:

  1. Place the files you wish to write to the SD card on the TFTP server in the zcu102 folder.
  2. Connect the to the targets U-Boot serial interface.
  3. Cycle power on the target and interrupt the boot sequence by pressing any key when prompted.
  4. Issue the following U-Boot commands, change <fileName> to the actual file name and <fileSize> to the size of the file in bytes in hexadecimal (without any formatting, i.e. 0x1b should be 1b). Note: the tftpboot command report the file size in hex.
setenv ipaddr 10.0.1.82
setenv gatewayip 10.0.1.1
setenv netmask 255.255.252.0
setenv serverip 10.0.1.208
setenv servpath zcu102/
setenv fileaddr 1b000
setenv filename <fileName>
tftpboot ${fileaddr} ${servpath}${filename}
fatwrite mmc $sdbootdev:$partid ${fileaddr} ${filename} <fileSize>

DeosZCU102-2

Program Durants, Shire, and Others Description Xilinx Ultrascale+ MPSoC Evaluation Board
Manufacturer Xilinx Processor Zynq UltraScale+ MPSoC ARM Cortex-A53, Cortex-R5F
Part Number HW-Z1-ZCU102 Rev 1.0 Serial Number 84730014801718-73787
MAC Addr 000A350377E7 Cable LA-3743X
BSP zus Captured Info Info
  • The following are the symbolic links to be modified when TFTP booting this board:
    • zcu102/deosBoot-2.bin
    • zcu102/composite-2.darc
  • NOTE currently booting SD card labeled ZCU-2 (see below).

SD Card Label Meanings:

  • ZCU-2 - is the Original SD card, TFTP boots
  • LPB - For Richards debug of Lake Pleasant Brewery MLD issue
  • MH - For Mike H. debug of GDB issue.
    • This Card loads from TFTP server (zcu102/) specially named files/links:
      • LCD-MH.bin
      • deosBoot-MH.bin
      • composite-MH.darc

DeosZCU102-3

MAC: 000a35002201

The following are the symbolic links to be modified when TFTP booting this board:

  • zcu102/deosBoot-3.bin
  • zcu102/composite-3.darc

The following are the current (2023-08-17) symbolic links.

  • deosBoot-3.bin -> deosBoot-rel-2023-05-01.bin
  • composite-3.darc -> composite-rel-2023-05-01.darc

DeosZCU102-4

MAC: 000a35002204

Board stored in Cabinet 2, see PTC Database

Booting DDS-gator-deos-jupiter-20230502 from SD card.

DeosZUBoard-1

Program Hermeus Description AVNET ZUBOARD 1CG Zynq UltraScale+ MPSoC
Manufacturer AVNET Processor Dual-core ARM Cortex-A53
Part Number AES-ZUB-1CG-DK-G Serial Number 4001003 1201 000502
MAC Addr d2:2c:41:53:b1:69 Cable FTDI USB Serial JTAG (TBD)
BSP zus Maybe Captured Info AVNET Xilinx

The following are the symbolic links to be modified when TFTP booting this board:

  • zuboard/deosBoot-1.bin
  • zuboard/composite-1.darc

This target requires a button push to turn it on, once X9 is on, have a farmer push the power button. Then you can connect to Putty/Serial. Then, if needed, have a farmer push the reset button. It's running uboot from the uSD card, tftps images, but crashes on GO. Suspect the version of uboot may not be compatible with Deos. i.e. uboot mentions 64-Bit and EL2, and is a 2023 build.

Application Processing Unit Dual-core ARM Cortex-A53 MPCore with CoreSight; NEON & Single/Double Precision Floating Point; 32KB/32KB L1 Cache, 1MB L2 Cache

  1. Real-Time Processing Unit Dual-core ARM Cortex-R5 with CoreSight; Single/Double Precision Floating Point; 32KB/32KB L1 Cache, and TCM
  2. Embedded and External Memory 256KB On-Chip Memory w/ECC; External DDR memory controller (LPDDR4 on ZUBoard 1CG)
  3. General Connectivity 214 PS I/O; UART; USB 2.0; I2C; SPI; 32b GPIO; Real Time Clock; WatchDog Timers; Triple Timer Counters

Getting Started
Hardware Guide

Power&Reset

ETXSDU-1

This target has been removed from the farm.

ETXSDU-2

This target has been removed from the farm.

DeosSP0_HBM_JMPR

A Relay board connected to a 5V phone power supply on one side, and a female jumper connector on the other. Used to remotely control a single circuit board jumper like a heartbeat jumper.

Power ON is Jumper ON, Power Off is Jumper Off. Please leave in off condition when finished to preserver relay life.

Relay Jumper1
Relay Jumper2

Deos68GP2

This target has been removed from the farm.



NetBooter

This section is only important if X9 is not working.

WTI Switch

Targets are plugged into a net boot device that allows you to cycle their power remotely via the network.

To reboot, you'll need to Telnet into the net booter and tell it which 120 VAC "plug" to turn off and or on.

  • Host Name: DeosPower1
  • IP Address: 10.0.1.142
  • password: admin

Note You will need to establish a VPN connection into DDC-I to access the net booter.

Here's an example of what you might see. 

$ telnet 10.0.1.142
Network Power Switch v2.03        Site: DeosPower1

Plug | Name             | Status  | Boot Delay | Password         | Default |
-----+------------------+---------+------------+------------------+---------+
 1   | CMU_28V_POWER    |   OFF   |   5  sec   | (none)           |   OFF   |
 2   | Emulator         |   ON    |   5  sec   | (none)           |   OFF   |
 3   | (none)           |   ON    |   5  sec   | (none)           |   ON    |
 4   | (none)           |   ON    |   5  sec   | (none)           |   ON    |
 5   | (none)           |   ON    |   5  sec   | (none)           |   ON    |
 6   | (none)           |   ON    |   5  sec   | (none)           |   ON    |
 7   | (none)           |   ON    |   5  sec   | (none)           |   ON    |
 8   | (none)           |   ON    |   5  sec   | (none)           |   ON    |
-----+------------------+---------+------------+------------------+---------+
"/H" for help.

Communication Settings:  9600,N,8,1
Modem Init. String:      ATE0M0Q1&C1&D2S0=1
Modem Disc. String:      (none)
MAC Address:             00-40-05-72-f6-5e
IP Address:              10.0.1.142            Disconnect Timeout:   30 Min
Subnet Mask:             255.255.255.0         Command Echo:         Off
Gateway Address:         10.0.1.1              Command Confirmation: On

NPS>

Synaccess_NP-08

  • Host Name: netbooter8.ddci.com
  • IP Address: 10.0.1.125
  • username: user
  • password: user

Note You will need to establish a VPN connection into DDC-I to access the net booter.

This has both HTTP (web) as well as Telnet interface.

The User Guide and Data Sheet is stored in Subversion.

Hosts

The list of workstations is kept in a Lotus Notes database. You must enter your notes username (e.g., gkindorf) and password before you can see the characterization of the hosts.

Laptops

Generally sucky performance.

lapdell9

Dec 2018, JMK, lapdell9 is off the farm, but information below is being retained for posterity.

The Apple USB network adapter is now in the cabinet, lapdell9 has retired.

An Apple USB network adapter has been installed for the purpose of monitoring ARINC 664 traffic on a local network. Neither Apple nor Microsoft provide an "official" Windows driver for this adapter, although Apple makes one available in their "boot camp" SDK. The driver that was installed has been archived in https://deos.ddci.com/svn/DDCI/maintainer-tools/windows/utils/, and was acquired from http://tnkgrl.wordpress.com/2008/02/10/windows-drivers-for-apple-usb-ethernet-adapter/.

In order for Wireshark to recognize the USB network adapter, the WinPCAP driver had to be reinstalled.

Workstations

DeosTower

Trace32 Software version date:

DESKTOP-6K0J3GI

This target has been removed from the farm. Returned to Customer

DESKTOP-SUHVDLM

This target has been removed from the farm. Returned to Customer

DTower2

Ubuntu 20.04 LTS, Dell Precision T3400, Intel Core2 Duo E8400 @ 3.0GHz 4GB Ram, 250 GB Hard drive

Hofmann

Windows 7 Pro 64-bit, Intel Core2 Duo E8400 @ 3.0GHz 4GB Ram

Inspiron3847

Not currently a TFHost, used for run-for-score and as a build machine for SCORE and TRAC.

Windows 7 Pro 64-bit, Intel i7-4790, 16GB Ram, 3.6Ghz

opt360dell

Trace32 Software version date:

TFHost01

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 256 GB HDD, Windows 10 Enterprise.

TFHost02

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 256 GB HDD, Windows 10 Enterprise.

TFHost03

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 465 GB SSD, Windows 10 Enterprise.

TFHost04

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 256 GB HDD, Windows 10 Enterprise.

TFHost05

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 256 GB HDD, Windows 10 Enterprise.

TFHost06

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 256 GB HDD, Windows 10 Enterprise.

TFHost07

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 256 GB HDD, Windows 10 Enterprise.

TFHost08

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 256 GB HDD, Windows 10 Enterprise.

TFHost09

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 465 GB SSD, Windows 10 Enterprise.

TFHost10

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 465 GB SSD, Windows 10 Enterprise.

TFHost11

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 256 GB HDD, Windows 10 Enterprise.

TFHost12

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 256 GB HDD, Windows 10 Enterprise.

TFHost13

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 500 GB HDD, Windows 10 Enterprise.

TFHost14

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 465 GB SSD, Windows 10 Enterprise.

TFHost15

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 300 GB HDD, Windows 10 Enterprise.

TFHost16

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 300 GB HDD, Windows 10 Enterprise.

TFHost17

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 300 GB HDD, Windows 10 Enterprise.

TFHost18

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 256 GB HDD, Windows 10 Enterprise.

TFHost19

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 300 GB HDD, Windows 10 Enterprise.

TFHost20

Dell Optiplex 9020 Core i7-4770 3.9 Ghz, 32GB RAM, 1TB SSD, Windows 10 Enterprise.

TFHost21

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 320 GB HDD, Windows 10 Enterprise.

TFHost22

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 320 GB HDD, Windows 10 Enterprise.

TFHost23

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 465 GB SSD, Windows 10 Enterprise.

TFHost24

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 320 GB HDD, Windows 10 Enterprise.

TFHost25

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 320 GB HDD, Windows 10 Enterprise.

TFHost27

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 320 GB HDD, Windows 10 Enterprise.

TFHost28

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 320 GB HDD, Windows 10 Enterprise.

TFHost29

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 320 GB HDD, Windows 10 Enterprise.

TFHost30

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 320 GB HDD, Windows 10 Enterprise.

TFHost31

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 320 GB HDD, Windows 10 Enterprise.

TFHost32

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 320 GB HDD, Windows 10 Enterprise.

TFHost33

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 320 GB HDD, Windows 10 Enterprise.

TFHost34

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 320 GB HDD, Windows 10 Enterprise.

TFHost35

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 320 GB HDD, Windows 10 Enterprise.

TFHost36

Dell Optiplex 7010 Core-i5, 2.90 GHz, 8 GB RAM, 320 GB HDD, Windows 10 Enterprise.

TFHost37

Dell OptiPlex 7040 SFF, Windows 10 Enterprise 64-Bit, WoL Cabable. Intel i7-6700 3.4GHz, 16GB RAM, 476GB SSD

TFHost38

Dell OptiPlex 7040 SFF, Windows 10 Enterprise 64-Bit, WoL Cabable. Intel i7-6700 3.4GHz, 16GB RAM, 476GB SSD, PSW Data Loader Installed

TFHost39

Dell OptiPlex 7040 SFF, Windows 10 Pro 64-Bit, WOL Capable, Intel i7-6700 3.40GHz, 16GB RAM, 476GB SSD

  • Has Camtasia Screencast Recording Software Installed Camtasia
TFHost40

Dell OptiPlex 7040 SFF, Windows 10 Pro 64-Bit, WOL Capable, Intel i7-6700 3.40GHz, 16GB RAM, 476GB SSD

TFHost41

Dell OptiPlex 7040 SFF, Windows 10 Pro 64-Bit, WOL Capable, Intel i7-6700 3.40GHz, 16GB RAM, 476GB SSD

TFHost42

Dell OptiPlex 7040 SFF, Windows 10 Enterprise 64-Bit, WoL Cabable. Intel i7-6700 3.4GHz, 16GB RAM, 476GB SSD

WarHorse
ARINC 664 board - Click on image for higher resolution

Hosts the target data loader software and ARINC 664 board, both from Avionics Interface Technologies. The target data loader software is available via the Avionics Interface Technologies program group, and the SDK for the ARINC 664 board is available via the AIM-USA program group. The target data loader software can communicate over Ethernet or the 664 board.

Trace32 Software version date:

Wireshark Usage

Debugging network issues is sometimes necessary, and using the Wireshark utility is a popular method.

It is recommended to install WinPcap, which works better than the included npcap, prior to Wireshark, both located here:\\nx3000\utils\tools\WireShark During the Wireshark install, be sure to uncheck the "Install npcap" checkbox that is selected by default.

In the past a network Hub has been connected so that one computer can see the traffic to/from the target. A recent attempt to use this method failed with the target getting timeouts, sometimes booting, and sometimes failing, and with a TFHost connected would always timeout.

DUALCOMM ETAP-2003 Network TAP

https://www.dualcomm.com/products/usb-powered-10-100-1000base-t-network-tap

Simple device that has 3 RJ45 jacks, pass through for the switch to target, and a snoop port wired to a TFHost Ethernet Dongle. Powered by USB to any 5V source. Important points for network settings are Fixed IP address (May need to talk to IT to select one), Proper Mask (255.255.252.0 probably), and NO Gateway, NO DNS.

ETAP-2003 - Click on image for higher resolution
Network Settings Example - Click on image for higher resolution

Bridge Method

Recommend TAP method above.

Limited Success with this method, seems traffic intended for the TFHost is also presented to the target:

  • Add a USB Network dongle to the TFHost
  • Connect the targets network connection to the dongle (instead of the main switch)
  • In Control Panel, Network Connections select the USB adapter, right-click properties, configure, Advanced Tab, Speed & Duplex, 100 Mbps Full Duplex.
  • Get and save the ipv4 settings of the main adapter, save to a file for future reference (ip, mac, dns, etc).
  • The following caused the TFHost to go offline and be un-accessable. We had to connect keyboard, monitor, mouse to configure this locally. Perhaps there is a better/another way?
  • Ctrl-Select the 2 adapters, right-click and select Bridge Connections, this will create a new icon for the bridge.
  • Now the ipv4 settings of the bridge can be made to match what was captured earlier.
  • Done, TFHost should have access to the web/internet, remote users can see it again, and the target will work through the bridge without knowing about the bridge.
  • If not done yet install WinPcap, and wireshark, select the proper interface which will be the name provided for the dongle, and all target and TFHost traffic can be captured. If the network bridge is the only interface available, npcap is in use. Uninstall npcap and Wireshark then re-install Wireshark making sure npcap does NOT get installed with it.

Administration

This section contains information related to the administration of this wiki page and X9.

As a general rule, the wiki contains information about possible configuration information (what is possible, what's worked in the past, etc.) and x9 contains what is current.

Adding a Target

Use the following guidance:

  • If new hardware, document its unboxing via photos. Save the boxes for possible future return or inter-company shipment.
  • If DDC-I purchased hardware, update the relevant Lotus Notes' PTC Computer Operations database, "DDC-I Hardware." Attach the unboxing photos.
  • If Customer hardware, do the same as above, but make the entries in the "Loaner Hardware" section. The Current Loaner Hardware view contains all of the customer hardware DDC-I currently possesses. In the toolbar is a button," New Loaner Hardware" which should be used to log a new piece of equipment when it arrives.
  • Determine a target name, and create a section for it on this wiki page.
  • Copy provided documentation into SCM, ideally in a BSP_name/branches/mainline/docs project directory. Coordinate the BSP_name choice with the assigned BSP developer.

Locate a Compatible Host

Ideally, one would like to find a host that is not already attached to a target, and has an available serial (COM) or USB-Serial connection. If the target is to have an emulator attached, an additional constraint is that the chosen host have compatible emulator client software installed, and an additional USB connection for the emulator. A less desirable option is to use a host already connected to one or more targets, and the least desirable option is to use more than one host, i.e. one for the host-to-target serial connection, and a second for the host-to-emulator connection.

If a Lauterbach emulator will be needed, use the following guidance:

  • Locate the appropriate emulator cable that is compatible with the target.
  • Determine the appropriate Trace32 client software that is compatible with the emulator cable selected above, and locate a host with that version installed, or install it on the host.
  • Note the chosen host name for subsequent X9 update.

Connect Target and Host

If an emulator is needed:

  • Connect the emulator cable to an available Lauterbach pod, and connect the pod's USB cable to the chosen host. Update the #Lauterbach_Cables table.
  • Connect the emulator pod's power to an available netbooter plug. Note the netbooter IP address and plug number for X9 update.
  • Connect the emulator cable to the target. Consider taking a photo of the connection to document proper connector placement. Store this photo alongside the target's information on this wiki page.

Regardless:

  • Connect the target's serial line to the chosen host. Note for later the host COM port used.
  • Locate an available netbooter connection, and rig the target to it. Note the netbooter's IP address and plug number for later.
  • Connect an Ethernet cable from the target to an available switch port.

Once the connection is usable, add an entry with the targetname, emulator, cable, and date to the "Host" (Rationale: if in the near future a target needs to get the emulator re-attached, this documents a good starting point for that re-attachment). For example:

Test the Set Up

  • Update X9 to note the new target and its attributes using the information noted in the previous guidance.
    • Serial:HostComPort_baudrate_bits_parity_stopbits. If there is more than one serial port, use Serial0:..., Serial1:...
    • Serialhost: name of host where serial port is connected.
  • If an emulator is attached, change the X9 Lauterbach: attribute of the old and new #Hosts, and change the X9 Lauterbach: attribute of the new target, and, if the emulator was moved, the old target.
  • Use www.lauterbach.com to look up the compatible emulator cable, and note that on this Wiki.
  • Test that x9 can cycle the target and emulator (if present) on and off.
  • Ensure that the host can receive and transmit serial data to the target.
  • If an emulator is present, verify that the emulator's installed client software can communicate with the target.
  • If TCP/IP networking is available, e.g. the target boots using U-Boot, record the target's MAC and IP address to #Target IP Addresses. Note that you will need to coordinate with DDC-I IT for an appropriate IP address, as we prefer the target get its IP address via DHCP.
  • Make a note of the targets MAC address on this Wiki.
  • Make a note of the targets location (rack-shelf#) on this Wiki.

Serial Port Issues

If the serial/putty connection to the target is not working, there are several possibilities.

  • Fastest thing to check is by bringing up Task Manager, click on the Users Tab/Icon, right-click any other users and Sign-Off. Most likely they did not close Putty and sign-off of the machine locking up the COM port.
  • If it is COM1, that is a physical port on the TFHost so should always be available. If the above wasn't the problem, try rebooting the TFHost, or get a Farmer Involved to check connections.
  • COM Ports greater than 1, typically COM4 and up are USB simulated COM ports.
    • On some targets, they must be powered on before windows makes that COM port active. You can observe this in Device Manager under Ports (COM & LPT).
    • Other targets power the USB/COM interface from the TFHost USB power and are always available.
    • Sometimes Windows will re-order, or create new COM ports for the same connection, i.e. your COM4 becomes COM8 or any other number. To Resolve this...
      • Power down the board.
      • In Device Manager click View->Show Hidden Devices. From there, under Ports for each COM port starting at the highest, working your way down to COM4, right-click->Uninstall Device, keeping any device drivers if asked.
      • Power up the board, right-click TFHost name at the top of device manager and select Scan for Hardware Changes.
      • It make take a minute for the newly discoverd ports to install. See if your COM port works now, if not, try the other COM ports that appeared.
    • Have a farmer unplug the USB for a few seconds, and plug back in while observing Device Manager for Port changes.
  • Reboot the TFHost
  • Contact a Farmer

Removing a Target

Use the following guidance:

  • If there is any chance we'll reconnect this hardware some day, don't remove from Wiki, add Wiki note explaining its status (on loan, stored (where), returned to customer, etc.).
    • Better to keep useful information on the Wiki than let it go into history.
  • Box it using original packaging. See PTC Loaner or DDCI database for pictures, Wiki for possible box storage location, etc.
  • If DDC_I owned, or being stored locally; put in cabinet or shelf, note location on Wiki.
  • If customer owned, contact and ship back to them.
  • Update X9, Remove or add note stating on-loan if we expect it back in a reasonable amount of time.
  • Do the same for emulator if attached, and return emulator and cable to storage or its owner if applicable.
  • Update X9 to free up the host computer. Note which host was used for this target on the target Wiki in case it comes back.
  • If appropriate have IT remove MAC/IP assignment from the DHCP server and Wiki Table.
  • Return any DDCI owned accessories to storage cabinet(s) (emulator, network cables, usb cables, extensions, etc.)
  • Do one last search for the target, host, emulator names on X9 and the Wiki to make sure nothing was missed.
    • Update this Wiki section if something was missed that should be listed here.

Adding a Lauterbach Cable/License

When we get a new cable or license (the ability to use a cable on a new piece of hardware), you should:

  1. Update #Lauterbach_Cables.
  2. Put the license information in subversion in a sub-directory with a name of the cable's serial number.

Lauterbach contact for questions or quotes is Bob Kupyn, Dennis Griffith

Lauterbach Emulators

Configuration

The Lauterbach emulators use host side tooling known as Trace32, typically installed on Windows hosts at c:\T32.

Lauterbach's licensing scheme is such that the license is programmed into the Emulator cable, and its expiration is tied to a particular Trace32 version date. For example, if the Emulator cable license indicates that it is "Valid until software version 2013.08", this means one needs to use a Trace32 version *older* than August of 2013.

All Trace32 software has been compressed into individual zip files and stored in the subversion repository.

On a Farm Host machine, one can paste the subversion link above into a browser, log in with your credentials, and download the appropriate Trace32 version.

To determine the Trace32 version to use for a particular cable, use the Lauterbach website:

  1. Go to Lauterbach.com.
  2. On the left-hand side, expand the "support" listing.
  3. Click on "TRACE32 Maintenance check".
  4. In the "License Serial Number" box, enter the Emulator cable serial number, e.g. C07060094097, and press "Maintenance check". You should then see something like "C07060094097: Valid until software version 2013.08".
  5. Retrieve the appropriate Trace32 version from SCM, and install it.

Note: If the necessary Trace32 version is so old it no longer runs on the host, you will need to ask the boss to pay Lauterbach for an Emulator cable license renewal.

The emulator client software and emulator cable license scripts have been archived in the subversion repository. Note that the software continues to work after the license expiration date.

Lauterbach Contacts

Sales Contact: Bob Kupyn
Support Contact: Dennis Griffith

Lauterbach Pods

Lauterbach Pods
Name Model Serial # Owned By MAC Address Remarks
Lauterbach01 LA-3500 Debug-USB3 C13080177051 DDC-I, Inc. None
Lauterbach02 LA-7708 Debug-USB2 C09120126018 DDC-I, Inc. None
Lauterbach03 LA-7705 Debug-ETH/USB2 E07060013226 DDC-I, Inc. 00:C0:8A:81:32:26
Lauterbach04 LA-3500 Debug-USB3 C13080177070 DDC-I, Inc. None
Lauterbach05 LA-3505 Debug-ETH/USB3 E18030032984 DDC-I, Inc. 00:C0:8A:83:29:84
Lauterbach06 LA-3505 Debug-ETH/USB3 E19010034949 DDC-I, Inc. 00:C0:8A:83:49:49
Lauterbach07 LA-3505 Debug-ETH/USB3 E19050035654 DDC-I, Inc. 00:C0:8A:83:56:54
Lauterbach08 LA-3505 Debug-ETH/USB3 E20010037275 DDC-I, Inc. 00:C0:8A:83:72:75
Lauterbach09 LA-3505 Debug-ETH/USB3 E21060040260 DDC-I, Inc. 00:C0:8A:84:02:60
Lauterbach10 LA-3505 Debug-ETH/USB3 E22040043157 DDC-I, Inc. 00:C0:8A:84:31:57
Lauterbach11 LA-3505 Debug-ETH/USB3 E22040043158 DDC-I, Inc. 00:C0:8A:84:31:58

Lauterbach Adapters

Lauterbach Adapters
Name Model Info Remarks
LA-3881-1 LA-3881 IDC20A to XILINX-14 Used On DeosShireZU6
LA-7748-1, -2, -3 LA-7748 IDC20A to TI-14, ARM-TI Used On DeosJacinto7EVM
LA-3770-1 LA-3770 IDC20A to MIPI-10/20/34 Used On many ARM Boards.
ARM-10-1 From Amazon IDC20A to mini arm-10 Used On many ARM Boards.
LA-4572-1 CombiProbe 2 MIPI60-Cv2 Incl. LA-4572 (CombiProbe), LA-4571 (XDP), LA-1228 (XDP Flex), LA-4515 (USB) x86 XDP or USB DCI OOB
LA-3863-1 LA-3863 IDC20A to ALTERA-10/RISCV-10 Used on DeosMercuryXU8

Lauterbach Cables

Lauterbach Cables
Cable Model Serial # Expires Key Owned By Connected To Remarks
C1 LA-7721 Debug-PPC603 MPC60x+MPC75x

LA-7734 MPC51xx+MPC52xx

LA-3794X QorIQ PPC 64-Bit (JTAG Debugger Ext.)		 C10060131983 2024-05 0b18d46da9966fbd DDCI Ref X9 or In Cabinet
C2 LA-7752 Debug-PPC44X C12010155247 2014-07 86aa12ac0fb79995 TBD Ref X9 or In Cabinet
C4 LA-7843 JTAG-CORTEX-A/R ARMv7 32-Bit
LA-3743X Cortex-A/R (ARMv8 32/64-bit)		 C13100179785 2022-09 0f3efa6cc73f94ff DDC-I Ref X9 or In Cabinet License files are here.
C5 LA-3736 JTAG Debugger for MPC5xxx Automotive C15050206625 2016-08 TBD DDC-I Ref X9 or In Cabinet NOTE! Pin 1 is opposite the red wire as annotated on the small circuit board.
C6 LA-3735 Debug-MPC8641

LA-7764X MPC85xx (JTAG debugger Ext.)
LA-7960X Multicore-LIZENZ (License for Multicore Debugging)

LA-7729X Ext for MPC8260/MPC8240/MPC83xx		 C07060094097 2013-08 3691e096aa62ebe4 TBD Ref X9 or In Cabinet
C7 LA-3796 MPC85XX/QorIQ e500 (ICD)
LA-3794X QorIQ PPC 64-Bit (JTAG Debugger Ext.)		 C12080164031 2022-09 7a012c04cdb6241e TBD On X9 or In Cabinet
C8 LA-3795 Debug-QORIQ32 C13040173397 2024-05 11fc89f1b717fa63 TBD On X9 or In Cabinet PPC QorIQ 32-Bit (ICD)supports QorIQ 32-bit with e500mc cores
C9 LA-7752 Debug-PPC44X
LA-7723X Ext for PPC400(ICD)		 C09090122538 2014-07 2dad3e69ccca6099 TBD Ref X9 or In Cabinet
C10 LA-3736 JTAG Debugger for MPC5xxx Automotive
LA-7960X Multicore-LIZENZ (License for Multicore Debugging)		 C17030231727 2018-06 TBD DDC-I Ref X9 or In Cabinet NOTE! Pin 1 is opposite the red wire as annotated on the small circuit board.
C12 LA-3736 JTAG Debugger for MPC5xxx Automotive C17090238886 2018-12 TBD DDC-I Ref X9 or In Cabinet NOTE! Pin 1 is opposite the red wire as annotated on the small circuit board.
C13 LA-7843 JTAG-CORTEX-A/R ARMv7 32-Bit
LA-3743X JTAG Ext. Cortex-A/R (ARMv8) 32/64-bit		 C18020245444 2024-05 33a7440fdaa3ba49 DDC-I Ref X9 or In Cabinet
C14 LA-7843 JTAG-CORTEX-A/R ARMv7 32-Bit
LA-3743X JTAG Ext. Cortex-A/R (ARMv8) 32/64-bit		 C19010261631 2024-05 5c829604d9f19667 DDC-I Ref X9 or In Cabinet
C15 LA-7843 JTAG-CORTEX-A/R ARMv7 32-Bit
LA-3743X JTAG Ext. Cortex-A/R (ARMv8) 32/64-bit		 C19040265268 2024-05 dea6e2448a651b7a DDC-I Ref X9 or In Cabinet
C16 LA-7843 JTAG-CORTEX-A/R ARMv7 32-Bit
LA-3743X JTAG Ext. Cortex-A/R (ARMv8) 32/64-bit		 C19040266961 2024-05 5882905c0355ed40 DDC-I Ref X9 or In Cabinet
C17 LA-7843 JTAG-CORTEX-A/R ARMv7 32-Bit
LA-3743X JTAG Ext. Cortex-A/R (ARMv8) 32/64-bit		 C19040266962 2024-05 3bdec5b4905c0d10 DDC-I Ref X9 or In Cabinet
C18 LA-3794 JTAG Debugger for QorIQ PowerPC 64-Bit (ICD)
 C20010280816 2021-04 See Remarks DDC-I Ref X9 or In Cabinet
C19 LA-3794 JTAG Debugger for QorIQ PowerPC 64-Bit (ICD)
 C21070307435 2024-05 3ba4b0fad5d0de1e DDC-I Ref X9 or In Cabinet
C20 LA-4572 CombiProbe for x86 XDP or USB
 C22080341311 2025-02 4524e2d308fffb98 DDC-I Ref X9 or In Cabinet
C21a, C21b DCI-DbC Intel SVT DCI DbC2/3 Debug Cable 1 Meter
 NA NA NA DDC-I Ref X9 or In Cabinet USB 3.0 Gen 1 AtoA Cable, Isolated VBUS. License served by RLM Server hosted on DDCI-Utils server (http://ddci-utils:5054/).
C22 LA-3087 CombiProbe for x86 DCI OOB USB
 C24030390439 2025-06 NA DDC-I Ref X9 or In Cabinet

Managed Switch FS.com

  • A Managed Switch (10.0.1.9) has been installed on Rack 3 in the Farm, all DeosCelestial targets have been plugged into it and a note in the Comment Section describes which Port on the Switch is connected to that interface. Nomenclature is MPN:<portNum> standing for Managed Port Number. Ports that are not connected to a target are noted here:
    • MPN:01 - TFHost37
    • MPN:06 - TFHost31
    • MPN:09 - Was: TFHost38 - Ethernet 3, ASIX AX88179 USB 3 Adapter, Static IP: 10.0.0.61, Port Monitoring: 7
    • MPN:14 - Wall/DDCI Network
    • MPN:16 - TFHost15
    • Open Port(s) 09, 17, 18, 19, 20, 21, 22, 23, 24
  • Switch GUI Manual: media:s3900-series-switches-web-management-user-manual.pdf
  • Switch Configuration Manual: media:S3900-Series-Switches-Configuration-Guide.pdf
  • Switch Quick Start Manual: media:s3900-series-switches-quick-start-guide.pdf
The configuration setting found that appears to make the
Aruba Switches block the FS Switch.

The Aruba switches have Spanning Tree enabled.

White Spanning Tree is enabled on those switches, the FS
switch must either have Spanning Tree turned off OR enabled
and STP set as the TYPE. There was a new problem with this turned
on, so leave it off. tftp/ping was ARP timing out on targets.

If the TYPE is set to either RSTP or MSTP, the Aruba’s will
block the physical port, i.e. all downstream devices, middle-men,
etc. will not have a connection.

Settings changed after resetting to factory default:
Admin password was set
Guest user was removed

Under IP configuration, added static entry
10.0.1.9/255.255.252.0, this adds the VLAN1 Static Route to
10.0.0.0/255.255.252.0

Spanning Tree Protocol left enabled but changed type to STP

Storm Control checked all interfaces except the SFPs

Updated System Description
  System Name FS S3900
  System Location Farm
  System Contact Jerry Kelley
  Time Setting set to NTP
  Added servers 10.0.3.200 and 10.0.3.201
  Set time zone to -700-AZ

Target IP Addresses

  • Important that at least one entry for a target has a DNS name that matches the X9 name.
    • This is needed for OA testing as well as informing the community which IP Deos is responding to.
  • If your board doesn't Ping and it used to and it's not "your" fault... It could be something on the DHCP/DNS server. Send Kevin Lew or Richard Frost a message with the targets information from the table below.
Target IP Addresses
Client IP Unique ID Description Comment
10.0.1.25 00DE055777C0 DeosMPC5777c-1
10.0.1.26 F8DC7A7F09A0 DeosSpearMX8-3
10.0.1.27 001BAC043634 DeosVPX3-1708-1
10.0.1.28 F8DC7A7F0938 DeosSpearMX8-4 MPN:02 Set to 100MBit Limit
10.0.1.40 984fee142d77 DeosXeon
10.0.1.49 00e04b75c36f DeosCOMe-cTL6-1 i225
10.0.1.53 7acd80c41a11 DeosNAI67G6-1
10.0.1.54 000a35002201 DeosZCU102-3
10.0.1.55 00E04B813840 DeosCOMe-cTL6-2 i225
10.0.1.56 00A0C9082101 DeosNAI68INT6-1 MPN:03
10.0.1.57 TBD DeosJacinto7EVM-3
10.0.1.58 00049F05B78B DeosT1042D4RDB-1
10.0.1.59 00049F05B795 DeosT1042D4RDB-2
10.0.1.60 00d093520705 DeosShakaMX8-1 MPN:11
10.0.1.61 6097DD022AC0 DeosS32V234-2
10.0.1.62 247625a262fd DeosJacinto7EVM-1
10.0.1.63 00049f0624ba DeosLS1088ARDB-1
10.0.1.64 0008A20CF399 DeosTurbotQuadCore-1
10.0.1.65 000A350377E7 DeosZCU102-2
10.0.1.66 00049F05701A DeosIMX8QM
10.0.1.67 00c08a813226 Lauterbach03
10.0.1.68 20B0F704A71A DeosAviage-ZynqUltra
10.0.1.69 00e04b73863d DeosCOMe-cTL6-1-i210
10.0.1.70 6097dd022ac6 DeosS32V234-3
10.0.1.71 004521525600 DeosNAI67PPC2-FW
10.0.1.72 0008A20D903F DeosTurbotQuadCore-2
10.0.1.73 <unassigned>
10.0.1.74 00049F05ACA9 DeosLS1043ARDB-1 FM1@DTSEC3
10.0.1.75 3408e159086f DeosJacinto7EVM-2
10.0.1.76 00049F0624A1 DeosMCP1048-1, DeosMCP1048-1a MCP1
10.0.1.77 00049F0624A3 DeosMCP1048-1b MCP2
10.0.1.78 06fdc0663e1b DeosMCP1048-2, DeosMCP1048-2a MCP1
10.0.1.79 06fdc0663e2b DeosMCP1048-2b MCP2
10.0.1.80 001BC3123422 DeosS32V234
10.0.1.81 B49691262562 DeosCOMe-cTL6-2-i210
10.0.1.82 000A3500890A DeosZCU102-1 Rev.1
10.0.1.83 00049F074A03 DeosIMX8QM-3 Rev C2
10.0.1.84 0001C0064326 DeosFIT-PC2-3
10.0.1.85 001BC3123423 DeosHarrys
10.0.1.86 00C08A835654 Lauterbach07
10.0.1.87 00049F04736E DeosT2080RDB
10.0.1.88 d22c4153b169 DeosZUBoard-1
10.0.1.89 004521525601 DeosNAI68PPC2-2
10.0.1.90 004532092503 DeosNAI68PPC2 MPN:05
10.0.1.91 004521525605 DeosNAI68PPC2-2-DTSEC4 uboot FM1@DTSEC4 Board Labeled PHY3
10.0.1.92 B86B23961AD1 FarmFlashAir-01 8GB SD Card with WiFi Update Access
10.0.1.93 <unassigned>
10.0.1.94 ee57272a4919 DeosNAI68ARM2-1 MPN:12, ethernet@ff0c0000?
10.0.1.95 0010EC010066 DeosHotdish-AID MPN:07
10.0.1.96 d22c4153b196 DeosMercuryXU8-1
10.0.1.97 d22c4153b197 DeosMercuryXU8-1-eth2
10.0.1.98 oem-virtual-mac <unavailable>
10.0.1.99 aabbccddeeff DeosNAI75Arm1
10.0.1.100 000a35002202 Deos68GP2
10.0.1.101 3aec81838263 DeosNAI68ARM2-1-eth1 MPN:13, eth0 ethernet@ff0b0000?
10.0.1.102 004521525800 DeosCelestial-2-dtsec3 MPN:15, FM1@DTSEC3 - dtsec:2,1,FMANV3
10.0.1.103 <unknown> deosdurants-pidu Reserved for Durants i.mx8 target
10.0.1.104 <unknown> DeosDPM2
10.0.1.105 004521525801 DeosCelestial-2-dtsec4 MPN:10, FM1@DTSEC4 - dtsec:3,2,FMANV3
10.0.1.106 0016C60094BE DeosCelestial-2, DeosCelestial-2-EM1-Eth1 MPN:08, EM1 Eth1 - pro1000:0
10.0.1.107 0016C60094BF DeosCelestial-2-EM1-Eth2 MPN:04, EM1 Eth2 - pro1000:1
10.0.1.108 861697dac666 DeosNAI68ARM2-2-eth0 MPN:12, eth0 ethernet@ff0b0000
10.0.1.109 fe4fe87c354d DeosNAI68ARM2-2-eth1 MPN:13, eth0 ethernet@ff0c0000
10.0.1.110 <unassigned>
10.0.1.111 <unassigned>
10.0.1.116 <unassigned>
10.0.1.117 N/A DeosJacinto7EVM-1 and DeosJacinto7EVM-2 DHCP failure fallback static address
Retrieved from "https://ddci.zapto.org/ddciWiki/index.php?title=Deos_Target_Farm&oldid=68986"