| 11 | | The GBlade is pre-installed with Ubuntu Linux. To power the unit use an 802.3at PoE switch or inserter. The bottom 1GbE RJ45 is the PoE port by default. Contact factory for 10GbE PoE options. Typical power consumption is around 10-13W without any additional cards plugged into the NVME socket. |
| 12 | | |
| 13 | | |
| 14 | | === Serial Console Access |
| 15 | | |
| 16 | | Once the unit is powered, the GBlade serial console can be accessed through the type C USB port through a cable to a desktop/laptop PC. The serial console uses an industry standard FTDI FT2232HQ USB to Serial/JTAG converter IC and will show up as a /dev/ttyUSBx device in Linux and can be accessed through a terminal program with the baud rate of 115,200. For other operating systems, virtual COM port (VCP) drivers can be found here: [https://ftdichip.com/drivers/vcp-drivers/ Link]. |
| | 11 | The GBlade is pre-installed with Ubuntu Linux. You must access the serial console for initial configuration. The following steps are required when bringing up new units. |
| | 12 | |
| | 13 | 1. Power Gblade over active PoE |
| | 14 | Isolated 802.3at 1GbE active PoE is supported on the bottom 1GbE Ethernet port. The Gateworks GW10144 802.3at PoE power supply/inserter can be used to power individual units and/or during development. See link here for info on GW10144: |
| | 15 | [https://tsi.tyconsystems.com/doc/SpecSheets/TP-POE+10G__53V_30W_10GB_PoE_Inserter_Spec_Sheet.pdf Tycon Inserter]. Typical power consumption is around 10-13W without any additional cards plugged into the NVME socket. For rackmount applications a 802.3at PoE switch is recommended. To use the 10GbE port for PoE powering the device, please contact Gateworks Sales. |
| | 16 | |
| | 17 | 2. Status LED Indicator |
| | 18 | Once power is applied and the bootloader start loading the OS, the LED status indicator on the frontplate will turn on solid green. Once Linux is fully loaded this LED will flash (heartbeat) indicating that the OS has fully loaded. |
| | 19 | |
| | 20 | 3. Serial Console Access |
| | 21 | Once the unit is powered, the GBlade serial console can be accessed through the type C USB port through a cable to a desktop/laptop PC. The serial console uses an industry standard FTDI FT2232HQ USB to Serial/JTAG converter IC and will show up as a /dev/ttyUSBx device in Linux and can be accessed through a terminal program with the baud rate of 115,200. For other operating systems, such as Windows, virtual COM port (VCP) drivers can be found here: [https://ftdichip.com/drivers/vcp-drivers/ Link]. |
| 25 | | Once connected via the USB cable, SSH can be enabled (it is disabled by default) with instructions here: [wiki:ubuntu#SSHServer Enable SSH] |
| 26 | | |
| 27 | | Any server software (LAMP stack, etc) can then be installed with the package manager. |
| | 30 | 4. SSH Enabling |
| | 31 | The default Ubuntu BSP has SSH disabled. If access over the management port is desired the user must enable SSH using the serial console. See instructions here for enabling SSH: [wiki:ubuntu#SSHServer Enable SSH]. Note that the default Ubuntu BSP |
| | 32 | |
| | 33 | 5. Connecting Ethernet |
| | 34 | There are two Ethernet ports, 1GbE (management) and 10GbE (high speed data). |
| | 35 | * (eth1) 1GbE RGMII port is on the bottom (PoE by default) - Note this interface is not enabled in the default Linux installation and will need to be enabled if user wants to use this interface for both power and management. |
| | 36 | |
| | 37 | * (eth0) 10GbE XFI port is on the top - This port is brought up with DHCP enabled in the default Linux installation. |
| | 38 | |
| | 39 | [[Image(ethernet.JPG,300px)]] |
| | 40 | |
| | 41 | 6. Installing and Customizing Software |
| | 42 | Any server software (LAMP stack, etc) can then be installed using the Ubuntu package manager. |
| 33 | | |
| 34 | | |
| 35 | | === JTAG & Firmware/OS Update |
| 36 | | |
| 37 | | The GW3089 incorporates onboard a USB to JTAG FTDI chip to allow JTAG programming of the unit without the requirement for a separate JTAG dongle (GW16099) which is typically used on other Gateworks SBCs. |
| 38 | | |
| 39 | | The JTAG software is under development so for initial programming please see the following link on updating from a TFTP server. |
| 40 | | * [wiki:malibu/firmware#UpdateFirmwareviaSerialConsoleandEthernetfromBootloader] |
| 41 | | |
| 42 | | == Ethernet |
| 43 | | |
| 44 | | There are two Ethernet ports, 1GbE (management) and 10GbE (high speed data). |
| 45 | | |
| 46 | | * (eth1) 1GbE RGMII port is on the bottom (PoE by default) - Note this interface is not enabled in the default Linux installation. |
| 47 | | * (eth0) 10GbE XFI port is on the top - This port is brought up with DHCP in the default Linux installation. |
| 48 | | |
| 49 | | [[Image(ethernet.JPG,300px)]] |
| 50 | | |
| 51 | | === Powering Gblade with PoE |
| 52 | | |
| 53 | | Isolated 802.3at 1GbE active PoE is supported on the bottom 1GbE Ethernet port. The Gateworks GW10144 802.3at PoE power supply/inserter can be used to power individual units and/or during development. See link here for info on GW10144: |
| 54 | | [https://tsi.tyconsystems.com/doc/SpecSheets/TP-POE+10G__53V_30W_10GB_PoE_Inserter_Spec_Sheet.pdf Tycon Inserter] |
| 55 | | |
| 56 | | For rackmount applications a 802.3at PoE switch is recommended. |
| 57 | | |
| 58 | | To use the 10GbE port for PoE powering the device, please contact Gateworks Sales. |
| | 48 | === JTAG Programming & Firmware/OS Update |
| | 49 | |
| | 50 | The GW3089 incorporates onboard a USB to JTAG FTDI chip to allow JTAG programming of the unit without the requirement for a separate JTAG dongle (GW16099) which is typically used on other Gateworks SBCs. |
| | 51 | |
| | 52 | At this time, the GW3089 JTAG software is under development so for initial programming please see the following link on updating from a TFTP server: [wiki:malibu/firmware#UpdateFirmwareviaSerialConsoleandEthernetfromBootloader]. Check back for future JTAG software releases which will be posted here. Note that loading software over JTAG can take a significant amount of time so we recommend only using JTAG to load the bootloader and then using a TFTP server to load the Ubuntu image which can be quite large. |
| 62 | | The Type-C USB port is only for serial console access. This port will not work as a standard USB port. |
| 63 | | |
| 64 | | == NVME Drive |
| 65 | | |
| 66 | | The GBlade needs to be opened up to install a 2280 M-Key NVME flash storage drive. The Gblade supports PCIe Gen 3.0 x4 lanes. |
| 67 | | |
| 68 | | The NVME drive will show up as /dev/nvme0 and /dev/nvme0n1 respectively in Linux. |
| 69 | | |
| 70 | | Here are the basic steps to open the case and access the NVME socket. |
| | 56 | The Type-C USB port is only for serial console and JTAG access. This port will not work as a standard USB port. See serial console access above for more information. |
| | 57 | |
| | 58 | == NVME Socket |
| | 59 | |
| | 60 | The GBlade contains a M.2 2280 PCIe Gen 3 x4 lane socket that can be used to support NVME drives, accelerator cards and radio cards (ie. AI accelerators, SDR radios, etc..). For volume orders contact sales for pre-installed options. |
| | 61 | |
| | 62 | To load your own NVME drive you will need to be opened up the enclosure. Here are the steps to open the enclosure and access the NVME socket. |
| 74 | | 3. Slide out the side plate on the side the LED cable is mounted on. |
| 75 | | 4. The M.2 NVME socket should now be visible and a drive can be inserted. Secure the drive to the PEM towards the front of the unit and reinstall the frontplate. |
| 76 | | |
| 77 | | Some example NVME speed tests with a Samsung 980 drive: |
| | 66 | 3. Slide out the side plate on the backside of the board (this is the side that the LED cable is mounted on). |
| | 67 | 4. The M.2 NVME socket should now be visible and a drive can be inserted. Secure the drive to the PEM towards the front of the unit and reinstall the frontplate making sure the LED cable does not get pinched by any of the plates. |
| | 68 | 5. The NVME drive should now show up as /dev/nvme0 and /dev/nvme0n1 respectively in Linux. |
| | 69 | |
| | 70 | === Example NVME speed tests with a Samsung 980 drive |
| | 71 | Note for this example the hdparm utility is used which provides more direct access to the drive versus using a dd command which much go through the OS and has a lot of overhead. |
| 148 | | |
| 149 | | |
| 150 | | The GW8901 uses standard Linux cooling-maps, thermal-zones and the pwm-fan driver. |
| 151 | | |
| 152 | | There are several temperature sensors on the board, identified as 'thermal_zones'. |
| 153 | | These are shown in Linux under /sys/class/thermal: |
| | 134 | === Temperature Monitoring |
| | 135 | |
| | 136 | The CPU and 10GbE Phy have passive heatsinks to allow better cooling on these devices. When installing M.2 cards in the GW3089 make sure to take cooling into consideration. Most NVME and AI accelerators recommend some type of heatsink. |
| | 137 | |
| | 138 | The narrow width of the GW3089 enclosure will only allow an 8 to 9mm heatsink (depending on height of devices on the M.2 card). When installing heatsinks make sure to align the fins to maximize cooling with the air flowing from the front to rear of the enclosure. |
| | 139 | |
| | 140 | The GW8901 uses standard Linux cooling-maps, thermal-zones and the pwm-fan driver. There are several temperature sensors on the board, identified as 'thermal_zones'. These are shown in Linux under /sys/class/thermal: |
| 281 | | TPM2_PT_VENDOR_STRING_2: |
| 282 | | raw: 0x0 |
| 283 | | value: "" |
| 284 | | TPM2_PT_VENDOR_STRING_3: |
| 285 | | raw: 0x0 |
| 286 | | value: "" |
| 287 | | TPM2_PT_VENDOR_STRING_4: |
| 288 | | raw: 0x0 |
| 289 | | value: "" |
| 290 | | TPM2_PT_VENDOR_TPM_TYPE: |
| 291 | | raw: 0x0 |
| 292 | | TPM2_PT_FIRMWARE_VERSION_1: |
| 293 | | raw: 0x2005002 |
| 294 | | TPM2_PT_FIRMWARE_VERSION_2: |
| 295 | | raw: 0x0 |
| 296 | | TPM2_PT_INPUT_BUFFER: |
| 297 | | raw: 0x400 |
| 298 | | TPM2_PT_HR_TRANSIENT_MIN: |
| 299 | | raw: 0x3 |
| 300 | | TPM2_PT_HR_PERSISTENT_MIN: |
| 301 | | raw: 0x7 |
| 302 | | TPM2_PT_HR_LOADED_MIN: |
| 303 | | raw: 0x3 |
| 304 | | TPM2_PT_ACTIVE_SESSIONS_MAX: |
| 305 | | raw: 0x40 |
| 306 | | TPM2_PT_PCR_COUNT: |
| 307 | | raw: 0x18 |
| 308 | | TPM2_PT_PCR_SELECT_MIN: |
| 309 | | raw: 0x3 |
| 310 | | TPM2_PT_CONTEXT_GAP_MAX: |
| 311 | | raw: 0xFFFF |
| 312 | | TPM2_PT_NV_COUNTERS_MAX: |
| 313 | | raw: 0x0 |
| 314 | | TPM2_PT_NV_INDEX_MAX: |
| 315 | | raw: 0x640 |
| 316 | | TPM2_PT_MEMORY: |
| 317 | | raw: 0x6 |
| 318 | | TPM2_PT_CLOCK_UPDATE: |
| 319 | | raw: 0x400000 |
| 320 | | TPM2_PT_CONTEXT_HASH: |
| 321 | | raw: 0xB |
| 322 | | TPM2_PT_CONTEXT_SYM: |
| 323 | | raw: 0x6 |
| 324 | | TPM2_PT_CONTEXT_SYM_SIZE: |
| 325 | | raw: 0x100 |
| 326 | | TPM2_PT_ORDERLY_COUNT: |
| 327 | | raw: 0xFF |
| 328 | | TPM2_PT_MAX_COMMAND_SIZE: |
| 329 | | raw: 0x500 |
| 330 | | TPM2_PT_MAX_RESPONSE_SIZE: |
| 331 | | raw: 0x400 |
| 332 | | TPM2_PT_MAX_DIGEST: |
| 333 | | raw: 0x20 |
| 334 | | TPM2_PT_MAX_OBJECT_CONTEXT: |
| 335 | | raw: 0x320 |
| 336 | | TPM2_PT_MAX_SESSION_CONTEXT: |
| 337 | | raw: 0x320 |
| 338 | | TPM2_PT_PS_FAMILY_INDICATOR: |
| 339 | | raw: 0x0 |
| 340 | | TPM2_PT_PS_LEVEL: |
| 341 | | raw: 0x0 |
| 342 | | TPM2_PT_PS_REVISION: |
| 343 | | raw: 0x0 |
| 344 | | TPM2_PT_PS_DAY_OF_YEAR: |
| 345 | | raw: 0x0 |
| 346 | | TPM2_PT_PS_YEAR: |
| 347 | | raw: 0x0 |
| 348 | | TPM2_PT_SPLIT_MAX: |
| 349 | | raw: 0x80 |
| 350 | | TPM2_PT_TOTAL_COMMANDS: |
| 351 | | raw: 0x65 |
| 352 | | TPM2_PT_LIBRARY_COMMANDS: |
| 353 | | raw: 0x65 |
| 354 | | TPM2_PT_VENDOR_COMMANDS: |
| 355 | | raw: 0x0 |
| 356 | | TPM2_PT_NV_BUFFER_MAX: |
| 357 | | raw: 0x400 |
| 358 | | TPM2_PT_MODES: |
| 359 | | raw: 0x0 |
| 360 | | |
| 361 | | }}} |
| 362 | | |
| 363 | | |
| 364 | | |
| | 260 | etc..... |
| | 261 | |
| | 262 | }}} |
