From 26e0a16ae02935a60dbba51850f0f6c18072516a Mon Sep 17 00:00:00 2001 From: Josefine Hansson Date: Mon, 27 May 2024 12:16:52 +0200 Subject: [PATCH] fixing spelling issues --- .../01.guides/07.node-red/nodered-intro.md | 2 +- .../tutorials/yun-first-config/content.md | 2 +- .../boards/portenta-x8/datasheet/datasheet.md | 1138 +++---- .../tutorials/01.user-manual/content.md | 2868 ++++++++--------- .../tutorials/user-manual/content.md | 2 +- .../tutorials/user-manual/content.md | 2 +- .../tutorials/user-manual/content.md | 2 +- .../connecting-to-iot-cloud/content.md | 2 +- .../secrets-of-arduino-pwm.md | 4 +- scripts/resources/spell-check-ignore-list.txt | 4 +- 10 files changed, 2014 insertions(+), 2012 deletions(-) diff --git a/content/arduino-cloud/01.guides/07.node-red/nodered-intro.md b/content/arduino-cloud/01.guides/07.node-red/nodered-intro.md index d5f769fba4..f2b433be31 100644 --- a/content/arduino-cloud/01.guides/07.node-red/nodered-intro.md +++ b/content/arduino-cloud/01.guides/07.node-red/nodered-intro.md @@ -100,7 +100,7 @@ You can run the simple flow shown below using Node-RED's default nodes: - drag the **"debug"** node into the workspace - connect the two nodes by dragging a wire from the message node to the debug node - click on the debug menu from the sidebar on the right -- press **Depoly** from the header on the top +- press **Deploy** from the header on the top - finally, press on the checkbox of the message node ![Creating a simple flow](assets/nodered-02.gif) diff --git a/content/hardware/02.hero/boards/yun-rev2/tutorials/yun-first-config/content.md b/content/hardware/02.hero/boards/yun-rev2/tutorials/yun-first-config/content.md index 6fe8744df0..f748f1b5e2 100644 --- a/content/hardware/02.hero/boards/yun-rev2/tutorials/yun-first-config/content.md +++ b/content/hardware/02.hero/boards/yun-rev2/tutorials/yun-first-config/content.md @@ -559,7 +559,7 @@ void wifiConfig(String yunName, String yunPsw, String wifissid, String wifipsw, p.runShellCommand("uci set network.lan.proto='dhcp'"); - p.runShellCommand("echo -e \"" + yunPsw + "\n" + yunPsw + "\" | passwd root"); //change the passwors + p.runShellCommand("echo -e \"" + yunPsw + "\n" + yunPsw + "\" | passwd root"); //change the password p.runShellCommand("uci commit"); //save the mods done via UCI diff --git a/content/hardware/04.pro/boards/portenta-x8/datasheet/datasheet.md b/content/hardware/04.pro/boards/portenta-x8/datasheet/datasheet.md index a998bbf04a..8a7aa56d15 100644 --- a/content/hardware/04.pro/boards/portenta-x8/datasheet/datasheet.md +++ b/content/hardware/04.pro/boards/portenta-x8/datasheet/datasheet.md @@ -1,569 +1,569 @@ ---- -identifier: ABX00049 -title: Arduino® Portenta X8 -type: pro -author: Ali Jahangiri ---- - -![](assets/featured.png) - -# Description - -The Arduino® Portenta X8 is a high-performance system on module designed to power the upcoming generation of the Industrial Internet of Things. This board combines the NXP® i.MX 8M Mini (4+1-cores) hosting an embedded Linux OS with the STM32H7 (2-cores) for real-time applications in the Arduino environment. Shield and carrier boards are available to extend the functionality of the Portenta X8 or alternatively can be used as reference designs to develop your own custom solutions. - -# Target Areas - -Edge computing, industrial internet of things, system on module, artificial intelligence - -# Features - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ComponentDetails
NXP® i.MX 8M Mini Processor4x Arm® Cortex®-A53 core platforms up to 1.8 GHz per core -

32KB L1-I Cache

-

32 kB L1-D Cache

-

512 kB L2 Cache

-
Arm® Cortex®-M4 core up to 400 MHz -

16 kB L1-I Cache

-

16 kB L2-D Cache

-
3D GPU (1x shader, OpenGL® ES 2.0)
2D GPU
1x MIPI DSI (4-lane) with PHY
1080p60 VP9 Profile 0, 2 (10-bit) decoder, HEVC/H.265 decoder, AVC/H.264 Baseline, Main, High decoder, VP8 decoder
1080p60 AVC/H.264 encoder, VP8 encoder
5x SAI (12Tx + 16Rx external I2S lanes), 8ch PDM input
1x MIPI CSI (4-lane) with PHY
2x USB 2.0 OTG controllers with integrated PHY
1x PCIe 2.0 (1-lane) with L1 low power substates
1x Gigabit Ethernet (MAC) with AVB and IEEE 1588, Energy Efficient Ethernet (EEE) for low power
4x UART (5mbps)
4x I2C
3x SPI
4x PWM
STM32H747XI MicrocontrollerArm® Cortex®-M7 core at up to 480 MHz with double-precision FPU16K data + 16K instruction L1 cache
1x Arm® 32-bit Cortex®-M4 core at up to 240 MHz with FPU, Adaptive real-time accelerator (ART Accelerator™)
Memory -

2 MB of Flash Memory with read-while-write support

-

1 MB of RAM

-
Onboard memoryNT6AN512T32AV2GB Low Power DDR4 DRAM
FEMDRW016G16GB Foresee® eMMC Flash module
USB-C®High Speed USB
DisplayPort output
Host and Device operation
Power Delivery support
-

High Density connectors

- 		1 lane PCI express
1x 10/100/1000 Ethernet interface with PHY
2x USB HS
4x UART (2 with flow control)
3x I2C
1x SDCard interface
2x SPI (1 shared with UART)
1x I2S
1x PDM input
4 lane MIPI DSI output
4 lane MIPI CSI input
4x PWM outputs
7x GPIO
8x ADC inputs with separate VREF
Murata® 1DX Wi-Fi®/Bluetooth® ModuleWi-Fi® 802.11b/g/n 65 Mbps
Bluetooth® 5.1 BR/EDR/LE
NXP® SE050C2 CryptoCommon Criteria EAL 6+ certified up to OS level
RSA & ECC functionalities, high key length and future proof curves, such as brainpool, Edwards, and Montgomery
AES & 3DES encryption and decryption
HMAC, CMAC, SHA-1, SHA-224/256/384/512 operations
HKDF, MIFARE® KDF, PRF (TLS-PSK)
Support of main TPM functionalities
Secured flash user memory up to 50kB
I2C slave (High-speed mode, 3.4 Mbit/s), I2C master (Fast-mode, 400 kbit/s)
SCP03 (bus encryption and encrypted credential injection on applet and platform level)
ROHM BD71847AMWV Programmable PMICDynamic voltage scaling
3.3V/2A voltage output to carrier board
Temperature range -40°C to +85°C It is user’s sole responsibility to test board's operation in full temperature - range. To improve the board performance in critical conditions, it is possible to attach external heatsinks on the processor and on the memory chip.
Safety informationClass A
- -# Contents - -## The Board - -### Application Examples - -The Arduino® Portenta X8 has been designed for high-performance embedded computing applications in mind, based on the quad-core NXP® i.MX 8M Mini Processor. The Portenta form factor enables the use of a wide range of shields to expand upon its functionality. - -- **Embedded Linux:** Kickstart the deployment of Industry 4.0 with Linux Board Support Packages running on the feature packed and energy efficient Arduino® Portenta X8. Make use of the GNU toolchain to develop your solutions free from a technological lock-in. -- **High performance networking:** The Arduino® Portenta X8 includes Wi-Fi® and Bluetooth® connectivity to interact with a wide range of external devices and networks providing high flexibility. Additionally, the Gigabit Ethernet interface provides high speed and low latency for the most demanding of applications. -- **High speed modular embedded development:** The Arduino® Portenta X8 is a great unit for developing a wide range of custom solutions. The high-density connector provides access to many functions, including PCIe connectivity, CAN, SAI and MIPI. Alternatively, use the Arduino ecosystem of professionally designed boards as a reference for your own designs. Low-code software containers allow for rapid deployment. - -### Accessories (Not Included) - -- USB-C® Hub -- USB-C® to HDMI Adapter -- Heatsink (if required) - -### Related Products - -- Arduino® Portenta Breakout Board (ASX00031) -- Arduino® Portenta Max Carrier (ABX00043) -- Arduino® Portenta Hat Carrier (ASX00049) - -## Rating - -### Recommended Operating Conditions - -| Symbol | Description | Min | Typ | Max | Unit | -|:-------------------|:----------------------------------------------------|:----:|:---:|:----:|:----:| -| VIN | Input voltage from VIN pad | 4.5 | 5 | 5.5 | V | -| VUSB | Input voltage from USB connector | 4.5 | 5 | 5.5 | V | -| V3V3 | 3.3 V output to user application | | 3.1 | | V | -| I3V3 | 3.3 V output current available for user application | - | - | 1000 | mA | -| VIH | Input high-level voltage | 2.31 | - | 3.3 | V | -| VIL | Input low-level voltage | 0 | - | 0.99 | V | -| IOH Max | Current at VDD-0.4 V, output set high | | | 8 | mA | -| IOL Max | Current at VSS+0.4 V, output set low | | | 8 | mA | -| VOH | Output high voltage, 8 mA | 2.7 | - | 3.3 | V | -| VOL | Output low voltage, 8 mA | 0 | - | 0.4 | V | - -### Power Consumption - -| Symbol | Description | Min | Typ | Max | Unit | -|-----------------|:------------------------------------|:---:|:----:|:---:|:----:| -| PBL | Power consumption with busy loop | | 2350 | | mW | -| PLP | Power consumption in low power mode | | 200 | | mW | -| PMAX | Maximum Power Consumption | | 4000 | | mW | - -The use of a USB 3.0 compatible port will ensure that the current requirements for the Portenta X8 are met. Dynamic scaling of the Portenta X8 compute units can change the current consumption, leading to current surges during bootup. Average power consumption is provided in the above table for several reference scenarios. - -## Functional Overview - -### Block Diagram - -![Block Diagram of Portenta X8](assets/x8BlockDiagram.svg) - -## Board Topology - -### Front View - -![Front view of Portenta X8 Topology](assets/x8TopologyFront.svg) - -| **Ref.** | **Description** | **Ref.** | **Description** | -|----------|------------------------------------------------|-----------------|--------------------------------------------------------------| -| U1 | BD71847AMWV i.MX 8M Mini PMIC | U2 | MIMX8MM6CVTKZAA i.MX 8M Mini Quad IC | -| U4 | NCP383LMUAJAATXG Current-Limiting Power Switch | U6 | ANX7625 MIPI-DSI/DPI to USB Type-C® Bridge IC | -| U7 | MP28210 Step Down IC | U9 | LBEE5KL1DX-883 WLAN+Bluetooth® Combo IC | -| U12 | PCMF2USB3B/CZ Bidirectional EMI Protection IC | U16,U21,U22,U23 | FXL4TD245UMX 4-Bit Bidirectional Voltage-level Translator IC | -| U17 | DSC6151HI2B 25MHz MEMS Oscillator | U18 | DSC6151HI2B 27MHz MEMS Oscillator | -| U19 | NT6AN512T32AV 2GB LP-DDR4 DRAM | IC1,IC2,IC3,IC4 | SN74LVC1G125DCKR 3-state 1.65-V to 5.5-V buffer IC | -| PB1 | PTS820J25KSMTRLFS Reset Push Button | Dl1 | KPHHS-1005SURCK Power On SMD LED | -| DL2 | SMLP34RGB2W3 RGB Common Anode SMD LED | Y1 | CX3225GB24000P0HPQCC 24MHz crystal | -| Y3 | DSC2311KI2-R0012 Dual-Output MEMS Oscillator | J3 | CX90B1-24P USB Type-C® connector | -| J4 | U.FL-R-SMT-1(60) UFL Connector | - -### Back View - -![Back view of Portenta X8 Topology](assets/x8TopologyBack.svg) - -| **Ref.** | **Description** | **Ref.** | **Description** | -|----------|-------------------------------------------------------|--------------|------------------------------------------------------| -| U3 | LM66100DCKR Ideal Diode | U5 | FEMDRW016G 16GB eMMC Flash IC | -| U8 | KSZ9031RNXIA Gigabit Ethernet Transceiver IC | U10 | FXMA2102L8X Dual Supply, 2-Bit Voltage Translator IC | -| U11 | SE050C2HQ1/Z01SDZ IoT Secure Element | U12, U13,U14 | PCMF2USB3B/CZ Bidirectional EMI Protection IC | -| U15 | NX18P3001UKZ Bidirectional power switch IC | U20 | STM32H747AII6 Dual Arm® Cortex® M7/M4 IC | -| Y2 | SIT1532AI-J4-DCC-32.768E 32.768KHz MEMS Oscillator IC | J1, J2 | High density connectors | -| Q1 | 2N7002T-7-F N-Channel 60V 115mA MOSFET | - -
- -## Processor - -The Arduino Portenta X8 makes use of two Arm®-based physical processing units. - -### NXP® i.MX 8M Mini Quad Core Microprocessor - -The MIMX8MM6CVTKZAA iMX8M (U2) features a quad-core Arm® Cortex® A53 running at up to 1.8 GHz for high-performance applications alongside an Arm® Cortex® M4 running at up to 400 MHz. The Arm® Cortex® A53 is capable of running a fully-fledged Linux or Android operating system through a Board Support Packages (BSP) in a multithreaded fashion. This can be expanded via the use of specialized software containers via OTA updates. The Arm® Cortex® M4 has lower power consumption allowing for effective sleep management as well as optimal performance in real-time applications and is reserved for future use. Both processors can share all peripherals and resources available on the i.MX 8M Mini, including PCIe, on-chip memory, GPIO, GPU and Audio. - -### STM32 Dual Core Microprocessor - -The X8 includes an embedded H7 in the form of a STM32H747AII6 IC (U20) with a dual-core Arm® Cortex® M7 and Arm® Cortex® M4. This IC is used as an I/O expander for the NXP® i.MX 8M Mini (U2). Peripherals are automatically controlled via the M7 core. Additionally, the M4 core is available for real-time control of motors and other time-critical machinery at a barebones level. The M7 core acts as a mediator between the peripherals and the i.MX 8M Mini. It achieves this by running a custom firmware [https://github.com/arduino/portentax8-stm32h7-fw](https://github.com/arduino/portentax8-stm32h7-fw) normally invisible to the User, which maps all its peripherals as Linux devices. Advanced users can customize the M7 firmware to fit their needs but this could break the seamless Linux integration. Users are instead encouraged to write custom Arduino programs (sketches) running on the M4, which can access all the peripherals supported by the M7. The STM32H7 is not exposed to networking and should be programmed via the i.MX 8M Mini (U2). - -## Wi-Fi®/Bluetooth® Connectivity - -The Murata® LBEE5KL1DX-883 wireless module (U9) simultaneously provides Wi-Fi® and Bluetooth® connectivity in an ultra-small package based on the Cypress CYW4343W. The IEEE 802.11b/g/n Wi-Fi® interface can be operated as an access point (AP), station (STA) or as dual-mode simultaneous AP/STA and supports a maximum transfer rate of 65 Mbps. Bluetooth® interface supports Bluetooth® Classic and Bluetooth® Low Energy. An integrated antenna circuitry switch allows a single external antenna (J4 or ANT1) to be shared between Wi-Fi® and Bluetooth®. Module U9 interfaces with i.MX 8M Mini (U2) via a 4bit SDIO and UART interface. Based on the software stack of the wireless module in the embedded Linux OS, Bluetooth® 5.1 is supported together with Wi-Fi® conforming to the IEEE802.11b/g/n standard. - -## Onboard Memories - -The Arduino® Portenta X8 includes two onboard memory modules. A NT6AN512T32AV 2GB LP-DDR4 DRAM (U19) and 16GB Forsee eMMC Flash module (FEMDRW016G) (U5) are accessible to the i.MX 8M Mini (U2). - -## Crypto Capabilities - -The Arduino® Portenta X8 enables IC-level edge-to-cloud security capability through the NXP® SE050C2 Crypto chip (U11). This provides Common Criteria EAL 6+ security certification up to OS level, as well as RSA/ECC cryptographic algorithm support and credential storage. It interacts with the NXP® i.MX 8M Mini via I2C. - -## Gigabit Ethernet - -The NXP® i.MX 8M Mini Quad includes a 10/100/1000 Ethernet controller with support for Energy Efficient Ethernet (EEE), Ethernet AVB, and IEEE 1588. An external physical connector is required to complete the interface. This can be accessed via a high-density connector with an external component such as the Arduino® Portenta Breakout board. - -
- -## USB-C® Connector - -![USB-C® Pinout](assets/usbCPinout.png) -The USB-C® connector provides multiple connectivity options over a single physical interface: - -- Provide board power supply in both DFP and DRP mode -- Source power to external peripherals when the board is powered through VIN -- Expose High Speed (480 Mbps) or Full Speed (12 Mbps) USB Host/Device interface -- Expose Displayport output interface -The Displayport interface is usable in conjunction with USB and can be either used with a simple cable adapter when the board is powered via VIN or with dongles able to provide power to the board while simultaneously outputting Displayport and USB. Such dongles usually provide an ethernet over USB port, a 2-port USB hub and a USB-C® port that can be used to provide power to the system. - -## Real-Time Clock - -The Real-Time clock allows for keeping the time of day with very low power consumption. - -## Power Tree - -![](assets/x8PowerTree.svg) -Power management is mainly performed by the BD71847AMWV IC (U1). - -## Board Operation - -### Getting Started - IDE - -If you want to program your Arduino® Portenta X8 while offline you need to install the Arduino® Desktop IDE **[1]** To connect the Arduino® Edge control to your computer, you’ll need a USB Type-C cable. This also provides power to the board, as indicated by the LED. - -### Getting Started - Arduino Web Editor - -All Arduino® boards, including this one, work out-of-the-box on the Arduino® Web Editor **[2]**, by just installing a simple plugin. - -The Arduino® Web Editor is hosted online, therefore it will always be up-to-date with the latest features and support for all boards. Follow **[3]** to start coding on the browser and upload your sketches onto your board. - -### Getting Started - Arduino Cloud - -All Arduino® IoT enabled products are supported on Arduino® IoT Cloud which allows you to Log, graph and analyze sensor data, trigger events, and automate your home or business. - -### Sample Sketches - -Sample sketches for the Arduino® Portenta X8 can be found either in the “Examples” menu in the Arduino® IDE or in the “Documentation” section of the Arduino Pro website **[4]** - -### Online Resources - -Now that you have gone through the basics of what you can do with the board you can explore the endless possibilities it provides by checking exciting projects on ProjectHub **[5]**, the Arduino® Library Reference **[6]** and the online store **[7]** where you will be able to complement your board with sensors, actuators and more. - -### Board Recovery - -All Arduino boards have a built-in bootloader which allows flashing the board via USB. In case a sketch locks up the processor and the board is not reachable anymore via USB it is possible to enter bootloader mode by configuring DIP switches. - -**Note: A compatible carrier board with DIP switches (e.g. Portenta Max Carrier, Portenta Hat Carrier, or Portenta Breakout) is required to enable bootloader mode. It cannot be enabled with the Portenta X8 alone.** - -## Mechanical Information - -### Pinout - -![](assets/x8HDCPinout.png) - -### Mounting Holes and Board Outline - -The Portenta X8 is a double-sided 66.04 mm x 25.40 mm board with a USB-C® port overhanging the top edge and two High-Density connectors on the bottom side of the board. The onboard wireless antenna connector is located on the bottom edge of the board. The board has four 2.25 mm drilled mounting holes to provide for mechanical fixing. - -![](assets/x8Dimensions.png) - -## Certifications - -| Certification | Details | -|:--------------|:--------------------------------------------------------------------------| -| CE (EU) | EN 301489-1
EN 301489-1
EN 300328
EN 62368-1
EN 62311 | -| WEEE (EU) | Yes | -| RoHS (EU) | 2011/65/(EU)
2015/863/(EU) | -| REACH (EU) | Yes | -| UKCA (UK) | Yes | -| RCM (RCM) | Yes | -| FCC (US) | ID.
Radio: Part 15.247
MPE: Part 2.1091 | -| RCM (AU) | Yes | - -### Declaration of Conformity CE DoC (EU) - -We declare under our sole responsibility that the products above are in conformity with the essential requirements of the following EU Directives and therefore qualify for free movement within markets comprising the European Union (EU) and European Economic Area (EEA). - -### Declaration of Conformity to EU RoHS & REACH 211 01/19/2021 - -Arduino boards are in compliance with RoHS 2 Directive 2011/65/EU of the European Parliament and RoHS 3 Directive 2015/863/EU of the Council of 4 June 2015 on the restriction of the use of certain hazardous substances in electrical and electronic equipment. - -| **Substance** | **Maximum Limit (ppm)** | -|----------------------------------------|-------------------------| -| Lead (Pb) | 1000 | -| Cadmium (Cd) | 100 | -| Mercury (Hg) | 1000 | -| Hexavalent Chromium (Cr6+) | 1000 | -| Poly Brominated Biphenyls (PBB) | 1000 | -| Poly Brominated Diphenyl ethers (PBDE) | 1000 | -| Bis(2-Ethylhexyl} phthalate (DEHP) | 1000 | -| Benzyl butyl phthalate (BBP) | 1000 | -| Dibutyl phthalate (DBP) | 1000 | -| Diisobutyl phthalate (DIBP) | 1000 | - -Exemptions: No exemptions are claimed. - -Arduino Boards are fully compliant with the related requirements of European Union Regulation (EC) 1907 /2006 concerning the Registration, Evaluation, Authorization and Restriction of Chemicals (REACH). We declare none of the SVHCs (), the Candidate List of Substances of Very High Concern for authorization currently released by ECHA, is present in all products (and also package) in quantities totaling in a concentration equal or above 0.1%. To the best of our knowledge, we also declare that our products do not contain any of the substances listed on the "Authorization List" (Annex XIV of the REACH regulations) and Substances of Very High Concern (SVHC) in any significant amounts as specified by the Annex XVII of Candidate list published by ECHA (European Chemical Agency) 1907 /2006/EC. - -### Conflict Minerals Declaration - -As a global supplier of electronic and electrical components, Arduino is aware of our obligations with regards to laws and regulations regarding Conflict Minerals, specifically the Dodd-Frank Wall Street Reform and Consumer Protection Act, Section 1502. Arduino does not directly source or process conflict minerals such as Tin, Tantalum, Tungsten, or Gold. Conflict minerals are contained in our products in the form of solder, or as a component in metal alloys. As part of our reasonable due diligence, Arduino has contacted component suppliers within our supply chain to verify their continued compliance with the regulations. Based on the information received thus far we declare that our products contain Conflict Minerals sourced from conflict-free areas. - -## FCC Caution - -Any Changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment. - -This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: - -(1) This device may not cause harmful interference - -(2) this device must accept any interference received, including interference that may cause undesired operation. - -**FCC RF Radiation Exposure Statement:** - -1. This Transmitter must not be co-located or operating in conjunction with any other antenna or transmitter. - -2. This equipment complies with RF radiation exposure limits set forth for an uncontrolled environment. - -3. This equipment should be installed and operated with a minimum distance of 20cm between the radiator & your body. - -English: -User manuals for license-exempt radio apparatus shall contain the following or equivalent notice in a conspicuous location in the user manual or alternatively on the device or both. This device complies with Industry Canada license-exempt RSS standard(s). Operation is subject to the following two conditions: - -(1) this device may not cause interference - -(2) this device must accept any interference, including interference that may cause undesired operation of the device. - -French: -Le présent appareil est conforme aux CNR d’Industrie Canada applicables aux appareils radio exempts de licence. L’exploitation est autorisée aux deux conditions suivantes : - -(1) l’ appareil nedoit pas produire de brouillage - -(2) l’utilisateur de l’appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d’en compromettre le fonctionnement. - -**IC SAR Warning:** - -English -This equipment should be installed and operated with a minimum distance of 20cm between the radiator and your body. - -French: -Lors de l’ installation et de l’ exploitation de ce dispositif, la distance entre le radiateur et le corps est d ’au moins 20 cm. - -**Important:** The operating temperature of the EUT can’t exceed 85℃ and shouldn’t be lower than -40℃. - -Hereby, Arduino S.r.l. declares that this product is in compliance with essential requirements and other relevant provisions of Directive 201453/EU. This product is allowed to be used in all EU member states. - -| Frequency bands | Maximum output power (ERP) | -|----------------------|----------------------------| -| 2.4 GHz, 40 channels | +6dBm | - -## Company Information - -| Company name | Arduino SRL | -|-----------------|-----------------------------------------------| -| Company Address | Via Andrea Appiani 25, 20900, MONZA MB, Italy | - -## Reference Documentation - -| Ref | Link | -|---------------------------|-----------------------------------------------------------------------------------------------------| -| Arduino IDE (Desktop) | | -| Arduino IDE (Cloud) | | -| Cloud IDE Getting Started | | -| Arduino Pro Website | | -| Project Hub | | -| Library Reference | | -| Online Store | | - -## Change Log - -| **Date** | **Revision** | **Changes** | -|------------|--------------|----------------------------------------| -| 11/12/2023 | 5 | Add Portenta Hat Carrier compatibility | -| 07/11/2023 | 4 | Add missing board dimensions | -| 26/01/2023 | 3 | Clarify open-source nature of M7 core | -| 12/09/2022 | 2 | Make cores clear, minor fixes | -| 24/03/2022 | 1 | Release | +--- +identifier: ABX00049 +title: Arduino® Portenta X8 +type: pro +author: Ali Jahangiri +--- + +![](assets/featured.png) + +# Description + +The Arduino® Portenta X8 is a high-performance system on module designed to power the upcoming generation of the Industrial Internet of Things. This board combines the NXP® i.MX 8M Mini (4+1-cores) hosting an embedded Linux OS with the STM32H7 (2-cores) for real-time applications in the Arduino environment. Shield and carrier boards are available to extend the functionality of the Portenta X8 or alternatively can be used as reference designs to develop your own custom solutions. + +# Target Areas + +Edge computing, industrial internet of things, system on module, artificial intelligence + +# Features + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ComponentDetails
NXP® i.MX 8M Mini Processor4x Arm® Cortex®-A53 core platforms up to 1.8 GHz per core +

32KB L1-I Cache

+

32 kB L1-D Cache

+

512 kB L2 Cache

+
Arm® Cortex®-M4 core up to 400 MHz +

16 kB L1-I Cache

+

16 kB L2-D Cache

+
3D GPU (1x shader, OpenGL® ES 2.0)
2D GPU
1x MIPI DSI (4-lane) with PHY
1080p60 VP9 Profile 0, 2 (10-bit) decoder, HEVC/H.265 decoder, AVC/H.264 Baseline, Main, High decoder, VP8 decoder
1080p60 AVC/H.264 encoder, VP8 encoder
5x SAI (12Tx + 16Rx external I2S lanes), 8ch PDM input
1x MIPI CSI (4-lane) with PHY
2x USB 2.0 OTG controllers with integrated PHY
1x PCIe 2.0 (1-lane) with L1 low power substates
1x Gigabit Ethernet (MAC) with AVB and IEEE 1588, Energy Efficient Ethernet (EEE) for low power
4x UART (5mbps)
4x I2C
3x SPI
4x PWM
STM32H747XI MicrocontrollerArm® Cortex®-M7 core at up to 480 MHz with double-precision FPU16K data + 16K instruction L1 cache
1x Arm® 32-bit Cortex®-M4 core at up to 240 MHz with FPU, Adaptive real-time accelerator (ART Accelerator™)
Memory +

2 MB of Flash Memory with read-while-write support

+

1 MB of RAM

+
Onboard memoryNT6AN512T32AV2GB Low Power DDR4 DRAM
FEMDRW016G16GB Foresee® eMMC Flash module
USB-C®High Speed USB
DisplayPort output
Host and Device operation
Power Delivery support
+

High Density connectors

+ 		1 lane PCI express
1x 10/100/1000 Ethernet interface with PHY
2x USB HS
4x UART (2 with flow control)
3x I2C
1x SDCard interface
2x SPI (1 shared with UART)
1x I2S
1x PDM input
4 lane MIPI DSI output
4 lane MIPI CSI input
4x PWM outputs
7x GPIO
8x ADC inputs with separate VREF
Murata® 1DX Wi-Fi®/Bluetooth® ModuleWi-Fi® 802.11b/g/n 65 Mbps
Bluetooth® 5.1 BR/EDR/LE
NXP® SE050C2 CryptoCommon Criteria EAL 6+ certified up to OS level
RSA & ECC functionalities, high key length and future proof curves, such as brainpool, Edwards, and Montgomery
AES & 3DES encryption and decryption
HMAC, CMAC, SHA-1, SHA-224/256/384/512 operations
HKDF, MIFARE® KDF, PRF (TLS-PSK)
Support of main TPM functionalities
Secured flash user memory up to 50kB
I2C slave (High-speed mode, 3.4 Mbit/s), I2C master (Fast-mode, 400 kbit/s)
SCP03 (bus encryption and encrypted credential injection on applet and platform level)
ROHM BD71847AMWV Programmable PMICDynamic voltage scaling
3.3V/2A voltage output to carrier board
Temperature range -40°C to +85°C It is user’s sole responsibility to test board's operation in full temperature + range. To improve the board performance in critical conditions, it is possible to attach external heatsinks on the processor and on the memory chip.
Safety informationClass A
+ +# Contents + +## The Board + +### Application Examples + +The Arduino® Portenta X8 has been designed for high-performance embedded computing applications in mind, based on the quad-core NXP® i.MX 8M Mini Processor. The Portenta form factor enables the use of a wide range of shields to expand upon its functionality. + +- **Embedded Linux:** Kickstart the deployment of Industry 4.0 with Linux Board Support Packages running on the feature packed and energy efficient Arduino® Portenta X8. Make use of the GNU toolchain to develop your solutions free from a technological lock-in. +- **High performance networking:** The Arduino® Portenta X8 includes Wi-Fi® and Bluetooth® connectivity to interact with a wide range of external devices and networks providing high flexibility. Additionally, the Gigabit Ethernet interface provides high speed and low latency for the most demanding of applications. +- **High speed modular embedded development:** The Arduino® Portenta X8 is a great unit for developing a wide range of custom solutions. The high-density connector provides access to many functions, including PCIe connectivity, CAN, SAI and MIPI. Alternatively, use the Arduino ecosystem of professionally designed boards as a reference for your own designs. Low-code software containers allow for rapid deployment. + +### Accessories (Not Included) + +- USB-C® Hub +- USB-C® to HDMI Adapter +- Heatsink (if required) + +### Related Products + +- Arduino® Portenta Breakout Board (ASX00031) +- Arduino® Portenta Max Carrier (ABX00043) +- Arduino® Portenta Hat Carrier (ASX00049) + +## Rating + +### Recommended Operating Conditions + +| Symbol | Description | Min | Typ | Max | Unit | +|:-------------------|:----------------------------------------------------|:----:|:---:|:----:|:----:| +| VIN | Input voltage from VIN pad | 4.5 | 5 | 5.5 | V | +| VUSB | Input voltage from USB connector | 4.5 | 5 | 5.5 | V | +| V3V3 | 3.3 V output to user application | | 3.1 | | V | +| I3V3 | 3.3 V output current available for user application | - | - | 1000 | mA | +| VIH | Input high-level voltage | 2.31 | - | 3.3 | V | +| VIL | Input low-level voltage | 0 | - | 0.99 | V | +| IOH Max | Current at VDD-0.4 V, output set high | | | 8 | mA | +| IOL Max | Current at VSS+0.4 V, output set low | | | 8 | mA | +| VOH | Output high voltage, 8 mA | 2.7 | - | 3.3 | V | +| VOL | Output low voltage, 8 mA | 0 | - | 0.4 | V | + +### Power Consumption + +| Symbol | Description | Min | Typ | Max | Unit | +|-----------------|:------------------------------------|:---:|:----:|:---:|:----:| +| PBL | Power consumption with busy loop | | 2350 | | mW | +| PLP | Power consumption in low power mode | | 200 | | mW | +| PMAX | Maximum Power Consumption | | 4000 | | mW | + +The use of a USB 3.0 compatible port will ensure that the current requirements for the Portenta X8 are met. Dynamic scaling of the Portenta X8 compute units can change the current consumption, leading to current surges during boot-up. Average power consumption is provided in the above table for several reference scenarios. + +## Functional Overview + +### Block Diagram + +![Block Diagram of Portenta X8](assets/x8BlockDiagram.svg) + +## Board Topology + +### Front View + +![Front view of Portenta X8 Topology](assets/x8TopologyFront.svg) + +| **Ref.** | **Description** | **Ref.** | **Description** | +|----------|------------------------------------------------|-----------------|--------------------------------------------------------------| +| U1 | BD71847AMWV i.MX 8M Mini PMIC | U2 | MIMX8MM6CVTKZAA i.MX 8M Mini Quad IC | +| U4 | NCP383LMUAJAATXG Current-Limiting Power Switch | U6 | ANX7625 MIPI-DSI/DPI to USB Type-C® Bridge IC | +| U7 | MP28210 Step Down IC | U9 | LBEE5KL1DX-883 WLAN+Bluetooth® Combo IC | +| U12 | PCMF2USB3B/CZ Bidirectional EMI Protection IC | U16,U21,U22,U23 | FXL4TD245UMX 4-Bit Bidirectional Voltage-level Translator IC | +| U17 | DSC6151HI2B 25MHz MEMS Oscillator | U18 | DSC6151HI2B 27MHz MEMS Oscillator | +| U19 | NT6AN512T32AV 2GB LP-DDR4 DRAM | IC1,IC2,IC3,IC4 | SN74LVC1G125DCKR 3-state 1.65-V to 5.5-V buffer IC | +| PB1 | PTS820J25KSMTRLFS Reset Push Button | Dl1 | KPHHS-1005SURCK Power On SMD LED | +| DL2 | SMLP34RGB2W3 RGB Common Anode SMD LED | Y1 | CX3225GB24000P0HPQCC 24MHz crystal | +| Y3 | DSC2311KI2-R0012 Dual-Output MEMS Oscillator | J3 | CX90B1-24P USB Type-C® connector | +| J4 | U.FL-R-SMT-1(60) UFL Connector | + +### Back View + +![Back view of Portenta X8 Topology](assets/x8TopologyBack.svg) + +| **Ref.** | **Description** | **Ref.** | **Description** | +|----------|-------------------------------------------------------|--------------|------------------------------------------------------| +| U3 | LM66100DCKR Ideal Diode | U5 | FEMDRW016G 16GB eMMC Flash IC | +| U8 | KSZ9031RNXIA Gigabit Ethernet Transceiver IC | U10 | FXMA2102L8X Dual Supply, 2-Bit Voltage Translator IC | +| U11 | SE050C2HQ1/Z01SDZ IoT Secure Element | U12, U13,U14 | PCMF2USB3B/CZ Bidirectional EMI Protection IC | +| U15 | NX18P3001UKZ Bidirectional power switch IC | U20 | STM32H747AII6 Dual Arm® Cortex® M7/M4 IC | +| Y2 | SIT1532AI-J4-DCC-32.768E 32.768KHz MEMS Oscillator IC | J1, J2 | High density connectors | +| Q1 | 2N7002T-7-F N-Channel 60V 115mA MOSFET | + +
+ +## Processor + +The Arduino Portenta X8 makes use of two Arm®-based physical processing units. + +### NXP® i.MX 8M Mini Quad Core Microprocessor + +The MIMX8MM6CVTKZAA iMX8M (U2) features a quad-core Arm® Cortex® A53 running at up to 1.8 GHz for high-performance applications alongside an Arm® Cortex® M4 running at up to 400 MHz. The Arm® Cortex® A53 is capable of running a fully-fledged Linux or Android operating system through a Board Support Packages (BSP) in a multithreaded fashion. This can be expanded via the use of specialized software containers via OTA updates. The Arm® Cortex® M4 has lower power consumption allowing for effective sleep management as well as optimal performance in real-time applications and is reserved for future use. Both processors can share all peripherals and resources available on the i.MX 8M Mini, including PCIe, on-chip memory, GPIO, GPU and Audio. + +### STM32 Dual Core Microprocessor + +The X8 includes an embedded H7 in the form of a STM32H747AII6 IC (U20) with a dual-core Arm® Cortex® M7 and Arm® Cortex® M4. This IC is used as an I/O expander for the NXP® i.MX 8M Mini (U2). Peripherals are automatically controlled via the M7 core. Additionally, the M4 core is available for real-time control of motors and other time-critical machinery at a barebones level. The M7 core acts as a mediator between the peripherals and the i.MX 8M Mini. It achieves this by running a custom firmware [https://github.com/arduino/portentax8-stm32h7-fw](https://github.com/arduino/portentax8-stm32h7-fw) normally invisible to the User, which maps all its peripherals as Linux devices. Advanced users can customize the M7 firmware to fit their needs but this could break the seamless Linux integration. Users are instead encouraged to write custom Arduino programs (sketches) running on the M4, which can access all the peripherals supported by the M7. The STM32H7 is not exposed to networking and should be programmed via the i.MX 8M Mini (U2). + +## Wi-Fi®/Bluetooth® Connectivity + +The Murata® LBEE5KL1DX-883 wireless module (U9) simultaneously provides Wi-Fi® and Bluetooth® connectivity in an ultra-small package based on the Cypress CYW4343W. The IEEE 802.11b/g/n Wi-Fi® interface can be operated as an access point (AP), station (STA) or as dual-mode simultaneous AP/STA and supports a maximum transfer rate of 65 Mbps. Bluetooth® interface supports Bluetooth® Classic and Bluetooth® Low Energy. An integrated antenna circuitry switch allows a single external antenna (J4 or ANT1) to be shared between Wi-Fi® and Bluetooth®. Module U9 interfaces with i.MX 8M Mini (U2) via a 4bit SDIO and UART interface. Based on the software stack of the wireless module in the embedded Linux OS, Bluetooth® 5.1 is supported together with Wi-Fi® conforming to the IEEE802.11b/g/n standard. + +## Onboard Memories + +The Arduino® Portenta X8 includes two onboard memory modules. A NT6AN512T32AV 2GB LP-DDR4 DRAM (U19) and 16GB Forsee eMMC Flash module (FEMDRW016G) (U5) are accessible to the i.MX 8M Mini (U2). + +## Crypto Capabilities + +The Arduino® Portenta X8 enables IC-level edge-to-cloud security capability through the NXP® SE050C2 Crypto chip (U11). This provides Common Criteria EAL 6+ security certification up to OS level, as well as RSA/ECC cryptographic algorithm support and credential storage. It interacts with the NXP® i.MX 8M Mini via I2C. + +## Gigabit Ethernet + +The NXP® i.MX 8M Mini Quad includes a 10/100/1000 Ethernet controller with support for Energy Efficient Ethernet (EEE), Ethernet AVB, and IEEE 1588. An external physical connector is required to complete the interface. This can be accessed via a high-density connector with an external component such as the Arduino® Portenta Breakout board. + +
+ +## USB-C® Connector + +![USB-C® Pinout](assets/usbCPinout.png) +The USB-C® connector provides multiple connectivity options over a single physical interface: + +- Provide board power supply in both DFP and DRP mode +- Source power to external peripherals when the board is powered through VIN +- Expose High Speed (480 Mbps) or Full Speed (12 Mbps) USB Host/Device interface +- Expose Displayport output interface +The Displayport interface is usable in conjunction with USB and can be either used with a simple cable adapter when the board is powered via VIN or with dongles able to provide power to the board while simultaneously outputting Displayport and USB. Such dongles usually provide an ethernet over USB port, a 2-port USB hub and a USB-C® port that can be used to provide power to the system. + +## Real-Time Clock + +The Real-Time clock allows for keeping the time of day with very low power consumption. + +## Power Tree + +![](assets/x8PowerTree.svg) +Power management is mainly performed by the BD71847AMWV IC (U1). + +## Board Operation + +### Getting Started - IDE + +If you want to program your Arduino® Portenta X8 while offline you need to install the Arduino® Desktop IDE **[1]** To connect the Arduino® Edge control to your computer, you’ll need a USB Type-C cable. This also provides power to the board, as indicated by the LED. + +### Getting Started - Arduino Web Editor + +All Arduino® boards, including this one, work out-of-the-box on the Arduino® Web Editor **[2]**, by just installing a simple plugin. + +The Arduino® Web Editor is hosted online, therefore it will always be up-to-date with the latest features and support for all boards. Follow **[3]** to start coding on the browser and upload your sketches onto your board. + +### Getting Started - Arduino Cloud + +All Arduino® IoT enabled products are supported on Arduino® IoT Cloud which allows you to Log, graph and analyze sensor data, trigger events, and automate your home or business. + +### Sample Sketches + +Sample sketches for the Arduino® Portenta X8 can be found either in the “Examples” menu in the Arduino® IDE or in the “Documentation” section of the Arduino Pro website **[4]** + +### Online Resources + +Now that you have gone through the basics of what you can do with the board you can explore the endless possibilities it provides by checking exciting projects on ProjectHub **[5]**, the Arduino® Library Reference **[6]** and the online store **[7]** where you will be able to complement your board with sensors, actuators and more. + +### Board Recovery + +All Arduino boards have a built-in bootloader which allows flashing the board via USB. In case a sketch locks up the processor and the board is not reachable anymore via USB it is possible to enter bootloader mode by configuring DIP switches. + +**Note: A compatible carrier board with DIP switches (e.g. Portenta Max Carrier, Portenta Hat Carrier, or Portenta Breakout) is required to enable bootloader mode. It cannot be enabled with the Portenta X8 alone.** + +## Mechanical Information + +### Pinout + +![](assets/x8HDCPinout.png) + +### Mounting Holes and Board Outline + +The Portenta X8 is a double-sided 66.04 mm x 25.40 mm board with a USB-C® port overhanging the top edge and two High-Density connectors on the bottom side of the board. The onboard wireless antenna connector is located on the bottom edge of the board. The board has four 2.25 mm drilled mounting holes to provide for mechanical fixing. + +![](assets/x8Dimensions.png) + +## Certifications + +| Certification | Details | +|:--------------|:--------------------------------------------------------------------------| +| CE (EU) | EN 301489-1
EN 301489-1
EN 300328
EN 62368-1
EN 62311 | +| WEEE (EU) | Yes | +| RoHS (EU) | 2011/65/(EU)
2015/863/(EU) | +| REACH (EU) | Yes | +| UKCA (UK) | Yes | +| RCM (RCM) | Yes | +| FCC (US) | ID.
Radio: Part 15.247
MPE: Part 2.1091 | +| RCM (AU) | Yes | + +### Declaration of Conformity CE DoC (EU) + +We declare under our sole responsibility that the products above are in conformity with the essential requirements of the following EU Directives and therefore qualify for free movement within markets comprising the European Union (EU) and European Economic Area (EEA). + +### Declaration of Conformity to EU RoHS & REACH 211 01/19/2021 + +Arduino boards are in compliance with RoHS 2 Directive 2011/65/EU of the European Parliament and RoHS 3 Directive 2015/863/EU of the Council of 4 June 2015 on the restriction of the use of certain hazardous substances in electrical and electronic equipment. + +| **Substance** | **Maximum Limit (ppm)** | +|----------------------------------------|-------------------------| +| Lead (Pb) | 1000 | +| Cadmium (Cd) | 100 | +| Mercury (Hg) | 1000 | +| Hexavalent Chromium (Cr6+) | 1000 | +| Poly Brominated Biphenyls (PBB) | 1000 | +| Poly Brominated Diphenyl ethers (PBDE) | 1000 | +| Bis(2-Ethylhexyl} phthalate (DEHP) | 1000 | +| Benzyl butyl phthalate (BBP) | 1000 | +| Dibutyl phthalate (DBP) | 1000 | +| Diisobutyl phthalate (DIBP) | 1000 | + +Exemptions: No exemptions are claimed. + +Arduino Boards are fully compliant with the related requirements of European Union Regulation (EC) 1907 /2006 concerning the Registration, Evaluation, Authorization and Restriction of Chemicals (REACH). We declare none of the SVHCs (), the Candidate List of Substances of Very High Concern for authorization currently released by ECHA, is present in all products (and also package) in quantities totaling in a concentration equal or above 0.1%. To the best of our knowledge, we also declare that our products do not contain any of the substances listed on the "Authorization List" (Annex XIV of the REACH regulations) and Substances of Very High Concern (SVHC) in any significant amounts as specified by the Annex XVII of Candidate list published by ECHA (European Chemical Agency) 1907 /2006/EC. + +### Conflict Minerals Declaration + +As a global supplier of electronic and electrical components, Arduino is aware of our obligations with regards to laws and regulations regarding Conflict Minerals, specifically the Dodd-Frank Wall Street Reform and Consumer Protection Act, Section 1502. Arduino does not directly source or process conflict minerals such as Tin, Tantalum, Tungsten, or Gold. Conflict minerals are contained in our products in the form of solder, or as a component in metal alloys. As part of our reasonable due diligence, Arduino has contacted component suppliers within our supply chain to verify their continued compliance with the regulations. Based on the information received thus far we declare that our products contain Conflict Minerals sourced from conflict-free areas. + +## FCC Caution + +Any Changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment. + +This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: + +(1) This device may not cause harmful interference + +(2) this device must accept any interference received, including interference that may cause undesired operation. + +**FCC RF Radiation Exposure Statement:** + +1. This Transmitter must not be co-located or operating in conjunction with any other antenna or transmitter. + +2. This equipment complies with RF radiation exposure limits set forth for an uncontrolled environment. + +3. This equipment should be installed and operated with a minimum distance of 20cm between the radiator & your body. + +English: +User manuals for license-exempt radio apparatus shall contain the following or equivalent notice in a conspicuous location in the user manual or alternatively on the device or both. This device complies with Industry Canada license-exempt RSS standard(s). Operation is subject to the following two conditions: + +(1) this device may not cause interference + +(2) this device must accept any interference, including interference that may cause undesired operation of the device. + +French: +Le présent appareil est conforme aux CNR d’Industrie Canada applicables aux appareils radio exempts de licence. L’exploitation est autorisée aux deux conditions suivantes : + +(1) l’ appareil nedoit pas produire de brouillage + +(2) l’utilisateur de l’appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d’en compromettre le fonctionnement. + +**IC SAR Warning:** + +English +This equipment should be installed and operated with a minimum distance of 20cm between the radiator and your body. + +French: +Lors de l’ installation et de l’ exploitation de ce dispositif, la distance entre le radiateur et le corps est d ’au moins 20 cm. + +**Important:** The operating temperature of the EUT can’t exceed 85℃ and shouldn’t be lower than -40℃. + +Hereby, Arduino S.r.l. declares that this product is in compliance with essential requirements and other relevant provisions of Directive 201453/EU. This product is allowed to be used in all EU member states. + +| Frequency bands | Maximum output power (ERP) | +|----------------------|----------------------------| +| 2.4 GHz, 40 channels | +6dBm | + +## Company Information + +| Company name | Arduino SRL | +|-----------------|-----------------------------------------------| +| Company Address | Via Andrea Appiani 25, 20900, MONZA MB, Italy | + +## Reference Documentation + +| Ref | Link | +|---------------------------|-----------------------------------------------------------------------------------------------------| +| Arduino IDE (Desktop) | | +| Arduino IDE (Cloud) | | +| Cloud IDE Getting Started | | +| Arduino Pro Website | | +| Project Hub | | +| Library Reference | | +| Online Store | | + +## Change Log + +| **Date** | **Revision** | **Changes** | +|------------|--------------|----------------------------------------| +| 11/12/2023 | 5 | Add Portenta Hat Carrier compatibility | +| 07/11/2023 | 4 | Add missing board dimensions | +| 26/01/2023 | 3 | Clarify open-source nature of M7 core | +| 12/09/2022 | 2 | Make cores clear, minor fixes | +| 24/03/2022 | 1 | Release | diff --git a/content/hardware/04.pro/boards/portenta-x8/tutorials/01.user-manual/content.md b/content/hardware/04.pro/boards/portenta-x8/tutorials/01.user-manual/content.md index eb3995b7ae..ab046ec7a7 100644 --- a/content/hardware/04.pro/boards/portenta-x8/tutorials/01.user-manual/content.md +++ b/content/hardware/04.pro/boards/portenta-x8/tutorials/01.user-manual/content.md @@ -1,1434 +1,1434 @@ ---- -beta: true -title: '01. Portenta X8 User Manual' -description: 'Get a general overview of Portenta X8 and its features.' -difficulty: intermediate -tags: - - Embedded Linux - - Containers - - Firmware - - Pins - - Connections -author: 'Marta Barbero' -hardware: - - hardware/04.pro/boards/portenta-x8 -software: - - ide-v1 - - ide-v2 - - iot-cloud ---- - - -## Introduction - -Portenta X8 is a powerful, industrial-grade System on Module with Linux OS preloaded onboard, capable of running device-independent software thanks to its modular container architecture. In this user manual, we will go through the foundations of the Portenta X8 to help you understand how the board works and how you can benefit from its advanced features. - -## Required Hardware - -* 1x [Portenta X8](https://store.arduino.cc/products/portenta-x8) board -* 1x USB-C® cable (either USB-C® to USB-A or USB-C® to USB-C®) -* 1x Wi-Fi® Access Point or Ethernet with Internet access - -## Required Software - -* [Arduino IDE 1.8.10+](https://www.arduino.cc/en/software), [Arduino IDE 2](https://www.arduino.cc/en/software), or [Arduino Web Editor](https://create.arduino.cc/editor) -* Latest "Arduino Mbed OS Portenta Boards" Core > 3.0.1 -* Latest Linux image available, check [this section](#portenta-x8-os-image-update) to verify if your Portenta X8 is already updated. - -## Product Overview - -Portenta X8 offers the best of two approaches: flexibility of usage of Linux combined with real-time applications through the Arduino environment. Developers can now execute real-time tasks, while simultaneously performing high-performance processing on Linux cores. -So, let's have a look at its technical specification. - -### Architecture Overview - -Portenta X8 is a powerful, industrial-grade System on Module combining a Yocto Linux distribution with the well-known Arduino environment. - -![Portenta X8 Tech Specs](assets/portenta_x8_call_outs.png "Portenta X8 Tech Specs") - -As you can see, Portenta X8 features two powerful computing units: - -* **NXP® i.MX 8M Mini** Cortex®-A53 quad-core up to 1.8GHz per core + 1x Cortex®-M4 up to 400 MHz. This microprocessor is the one where the Yocto Linux distribution is running together with Docker containers (check [this section](#linux-environment) of this user manual to learn more). - -* **STMicroelectronics STM32H747XI** dual-core Cortex®-M7 up to 480 MHz + M4 32 bit Arm® MCU up to 240 MHz. This microcontroller is the one where the "Arduino Mbed OS Portenta Boards" Core is running. M4 core is accessible and programmable by the user, while M7 is dedicated to establishing and guaranteeing the communication between i.MX 8M Mini and M4 as well as to manage peripherals through RPC. Check [this section](#arduino-environment) of this user manual to learn more. - -The two computing units are responsible for different tasks, which are summarized in the table below. - - | NXP® i.MX 8M Mini | STMicroelectronics STM32H747XI (M4) | - | ------------------------------------------------------- | -------------------------------------------------------------- | - | Running Yocto Linux distribution with Docker containers | Running Arduino sketches with the Mbed OS Portenta Boards Core | - | Dedicated to high level tasks | Dedicated to real-time tasks | - | Manage network connectivity | No direct connection to any network stack | - | Manage network-based buses (e.g. Modbus TCP, etc.) | Manage field buses (e.g. Modbus RTU, CANbus, etc.) | - | Access to peripherals without concurrent access control | Access to peripherals without concurrent access control | - -In addition to the above features, Portenta X8 guarantees security over time. A crypto element (i.e. [NXP® SE050C2](https://www.nxp.com/docs/en/data-sheet/SE050-DATASHEET.pdf)) ensures a secure connection at the hardware level and allows the board to be PSA certified from ARM® (click [here](https://www.psacertified.org/products/portenta-x8/) to learn more). - -Moreover, Portenta X8 can be further customized to get a continuously maintained Linux kernel distribution and to keep security at first by Over-The-Air (OTA) device updates and fleet management. In order to activate these features, you need to create an Arduino Cloud for business account including the so-called **Portenta X8 Board Manager**. Portenta X8 Board Manager has been developed together with [Foundries.io](https://foundries.io/) and allows a user to: - -* Securely maintain Linux distribution inside a FoundriesFactory, i.e. a dedicated workspace where all your Portenta X8 are provisioned and maintained. -* Deploy and update applications packaged into containers, including both containers provided by Arduino or custom containers. -* Get individual provisioning keys for each device. -* Perform secure Over-the-air (OTA) updates to target Portenta X8 devices/fleets. - -***Click [here](https://cloud.arduino.cc/plans#business) to learn more about Arduino Cloud for business and the Portenta X8 Board Manager add-on. Otherwise, check the [dedicated section](#working-with-portenta-x8-board-manager) of this user manual to start working with Portenta X8 Manager.*** - -### Pinout - -The full pinout is available and downloadable as PDF from the link below: -* [Portenta X8 Pinout](https://docs.arduino.cc/static/019dd9ac3b08f48192dcb1291d37aab9/ABX00049-full-pinout.pdf) - -### Datasheet - -The full datasheet is available and downloadable as PDF from the link below: -* [Portenta X8 Datasheet](https://docs.arduino.cc/resources/datasheets/ABX00049-datasheet.pdf) - -### Schematics - -The full schematics are available and downloadable as PDF from the link below: -* [Portenta X8 Schematics](https://docs.arduino.cc/resources/schematics/ABX00049-schematics.pdf) - -### STEP Files - -The full _STEP_ files are available and downloadable from the link below: -* [Portenta X8 STEP files](../../downloads/ABX00049-step.zip) - -### Linux Environment - -As you already know, Portenta X8 is based on a Yocto Linux distribution. - -Before going into the details of Yocto distribution, it is important to understand how embedded Linux works. - -The term **Embedded Linux** is used to define embedded systems based on the Linux Kernel and other open-source components. Over the years, Linux has established itself as the best operating system to be installed on embedded devices. This achievement is due to the fact that Linux is an open-source and completely free operating system. - -An **Embedded Linux** system is composed of the following items: - -* **Bootloader:** The first program executed right after powering the board. It has the task of initializing the hardware and loading the operating system loading the **device tree** and its configuration file into the RAM. The **device tree** is basically a database containing information on the hardware components of the board and it is used to forward information from the bootloader to the Kernel at the hardware level. -* **Linux Kernel:** The core of the operating system. It deals with resource management, scheduling, hardware access and all the low-level operations which the user does not want to worry about. In particular, the Linux Kernel manages all the hardware resources, like CPU, memory and I/Os, and it provides a set of APIs that abstracts those resources allowing the user applications and libraries to be easily deployed. -* **Root Filesystem:** It contains all system programs and utilities, configurations and user data (roughly speaking, the equivalent of the `C:\` drive on Windows). The Root Filesystem can be mounted from a USB stick, SD card or flash memory, being the case of the Portenta X8. - -![Embedded Linux Start-Up](assets/Embedded_Linux_Start.png "Embedded Linux Start-Up") - -#### Linux Yocto Distribution - -In order to install a Linux operating system on a board, you need to decide which packages, applications and libraries you want to use, so basically you need to decide which Linux distribution better suits your needs. As a matter of fact, a Linux distribution is an operating system consisting of the Linux Kernel, GNU tools, additional software and a package manager. It may also include a display server and a desktop environment for using it as a regular desktop operating system. There are more than 300 Linux distributions available in the market, like Ubuntu, Debian, Fedora, Red Hat, etc. - -Portenta X8 is running a [Yocto Linux distribution](https://www.yoctoproject.org/). Yocto is built on the basis of [OpenEmbedded (OE)](http://www.openembedded.org/wiki/Main_Page), which uses [BitBake](https://docs.yoctoproject.org/bitbake/) build to generate a full Linux image. BitBake and OE are combined together to form the Yocto reference project, historically called [Poky](https://www.yoctoproject.org/software-item/poky/). - -In addition, a full selection of metadata is defined to select which tasks to be performed. The following metadata is used in a Yocto project: - -* **Recipes:** They deliver information regarding each package (i.e. author, homepage, license, etc.), recipe version, existing dependencies, source code location and how to retrieve it, configuration settings and target path where the created package will be saved. Files with the `.bb` extension are recipe files. -* **Configuration file:** They contain metadata that define how to perform the build process. These files (with `.conf` file extension) determine the configuration options for the machine, the compiler, the distribution and general and user configurations. They allow you to set the target where you want to create the image and where you want to save the downloaded sources and other particular configurations. -* **Classes:** Class files, which have the extension `.bbclass`, contain common functionalities that can be shared between various recipes within the distribution. When a recipe inherits a class, it also inherits its settings and functions. -* **File append:** With the extension `.bbappend`, File append extends or overwrites information for an existing recipe. - -OpenEmbedded Core contains a recipe layer, classes and a set of associated files, common to all OE-based systems, including Yocto. This set of metadata is in fact maintained by both the Yocto project and the OpenEmbedded project. - -The development environment of the Yocto distribution is made up of various functional areas, as shown in the figure below. - -![Yocto Distribution Architecture](assets/Yocto_Architecture.png "Yocto Distribution Architecture") - -* **Layer:** The layers allow you to separate metadata by differentiating them according to: software, hardware information, metadata concerning distribution and adopted policies. Within each layer, there are the `conf` (with layer-specific configuration files) and `recipes-` directories. To illustrate how to use layers to maintain modularity, consider the example of recipes to support a specific target, which usually resides in a BSP layer. In this scenario, those recipes should be isolated from other recipes and supporting metadata, like a new Graphical User Interface (GUI). You would then have a couple of layers: one for the configurations of the machine and one for the GUI environment. This would allow a specific machine to present special GUI features within the BSP layer, without affecting the recipes inside the GUI layer itself. All of this is possible via an append file. -* **Source file:** To cross-compile any software module, being it a distribution or an application, we must have access to various source files. The latter can be sourced from three different upstream areas: Upstream Project Releases (archived at a specific location), Local Projects (available at a certain local path) and Source Control Managers (like GitHub). -* **Package feeds:** This area contains packages generated by the build system and they will be used later to generate operating system images or Software Development Kits (SDKs). -* **Build System:** The Build System macroblock is the heart of the Yocto distribution. It contains various processes controlled by BitBake, a tool written in Python language. The Build System is responsible for parsing the metadata, from which it extracts the list of tasks to be performed. BitBake checks the software build process by using the recipes and, for each successfully completed task, it writes a *stamp* file in the Build Directory. -* **Images:** They are compressed forms of the Root Filesystem, ready to be installed on the target. BitBake releases multiple lists of images saved into the Build Directory, including *kernel-image*, *root-filesystem-image* and *bootloaders*. -* **SDK:** From the SDK generation process you can get a standard SDK or an extensible SDK. In both cases, the output is an installation script of the SDK, which installs: a cross-development toolchain, a set of libraries and headers files; generating an environment setup script. The toolchain can be considered as part of the build system, while libraries and headers as target parts, since they are generated for the target hardware. - -***If you want to learn more about how to work with Yocto Distribution on your Portenta X8, please check the [dedicated section](#working-with-linux) of this user manual.*** - -#### Docker Containers - -With Portenta X8 it is possible to deploy device-independent software thanks to its modular container architecture. - -To explain how containers work, imagine the classic containers that transport goods around the world by ship. These containers "blocks" can be moved in multiple ways and to multiple locations: from a ship to a truck or from a truck to a warehouse. The same thing happens in computer science: you can consider an application, package it with everything needed to make it work and take it out of the environment in which it runs. This is a container! - -![Virtual Machine vs Containers](assets/Virtual_Machine_Containers.png "Virtual Machine vs Containers") - -On one side, classic virtualization is able to virtualize an entire machine; on the other side, containers are able to virtualize even just a small subset of resources of the same machine. - -Traditional virtual machines share hardware resources, but the operating system and applications are on the host. This translates into long start-up times (it takes minutes) and considerable use of resources (several Gigabytes). Containers, on the other hand, share the operating system as well as the infrastructure with the host. This means that start-up times are short (a few seconds) and dimensions are significantly reduced (even a few KB). - -Being able to "pack" applications and distribute them in any environment leads to a series of advantages in terms of: performance, time, costs and integration. As a matter of fact, containers can be an interesting way to simplify infrastructure complexity, provide maximum performance and optimize costs by eliminating virtual machine licenses. - -But let's see in detail some of the advantages of this technology: - -* **Simple development, test and deployment:** The decoupling between applications and the environments in which they run allows you to deploy a container everywhere: on a public Cloud, in a private data center or on a PC. Whatever the chosen environment, the container will always remain the same. This means that even applications updates can be released easily without involving the operating system hosting the container, or all the other containers in use. In a nutshell, if you have to update an application, it will not be necessary to restart the whole machine. -* **Control version:** In the case that the deployment of an update was not successful, thanks to the containers architecture it is easier to roll back and to have the previous version working again in few time. -* **Isolation and security:** In containers, applications and resources are isolated. This means that if an application has to be deleted, it will be sufficient to remove its container and the operation will delete everything that concerns it, such as temporary or configuration files. At the same time, since containers are isolated, each of them "sees" only their own processes, while the others will remain unknown. Security first! -* **Granularity:** It is possible to containerize not only an entire application, but also a single component. In this way, resources can be reduced into micro-services, guaranteeing greater control and improved performance. - -At this point, it is worth mentioning that Portenta X8 containers are based on [Docker](https://www.docker.com/). Docker is an open-source software platform, developed by the company with the same name, which allows you to create, test and distribute containerized applications. The goal of Docker is therefore to facilitate the creation and management of containers, in order to distribute the resources required for an application in any environment, always keeping the executed code under control. Docker containers can run everywhere, in on-premises data centers or in public and private Clouds. Thanks to the virtualization at the operating system level, typical of this technology, Docker allows you to natively create containers in Linux environments. - -To understand the purpose of a platform like Docker, it is sufficient to focus on the differences between Docker containers and the more generic Linux containers. Docker mainly serves to simplify the construction and management of containers compared to the standard approach. Although it is based on the same technology, i.e. the **LXC (Linux Container)**, Docker guarantees a much more advanced experience than the standard implementation. LXC basically permits a light virtualization, independent from the underlying hardware, but basically cumbersome to implement. In other words, basic LXC presents critical issues in terms of user experience. - -Docker specifically facilitates the interface between the container and the end user, for example through a series of automated procedures that guide the user step-by-step during container development, with correct versioning of all the generated images. Docker also simplifies the management of the applications to be run on the different containers, to make the overall orchestration more practical and faster, especially when dealing with applications made of a very large number of components. - -The reasons for using Docker are therefore closely connected to the usefulness of the containers themselves, now indispensable tools for developing software based on a microservices architecture. In particular, this applies to the DevOps methodologies used for the development of native Cloud applications, which provide for continuous integration / continuous deployment cycles, to guarantee the end user always and only the most up-to-date version. - -The technology behind containers, and therefore of Docker itself, can be extremely summarized in three key terms: - -* **Builder:** tools used to create containers. In the case of Docker, this tool corresponds to the **Dockerfile**. -* **Engine:** it is the engine that allows you to run containers, as in the case of **Docker command** and **Docker Daemon**. -* **Orchestration:** technology used to manage containers, with full visibility of their execution status (tasks, servers / VMs, etc.), as in the case of **Docker Swarm** or the famous **Kubernetes**. - -The fundamental advantage of a container is that it makes both the application and the execution environment configuration available. This allows you to manage the various images as instances, without having to install the application each time, as happens in the case of traditional procedures. - -As already mentioned, containers running with Docker are absolutely isolated and independent from each other and it is therefore possible to have complete control over their visibility and management, without any constraints whatsoever. The advantages in terms of IT security are obvious: if a container is corrupted, for example by exploiting a vulnerability of the application it is running, this event does not affect the functioning of the other running containers. Isolation prevents, or at least makes it more difficult, the propagation of the threat within the host system, allowing Docker to terminate the corrupted instance and restart it in completely safe conditions, as well as having traces of what happened in the system logs. - -Thus, Docker is able to ensure application security without sacrificing anything in terms of portability, guaranteeing full operation both on-premise and in the Cloud, using open and closed APIs to respond optimally to any business need. - -As shown in the image below, Docker needs to be installed in the host operating system and it is composed of three main items: - -* ***docker-daemon:*** It is a service that runs on the host operating system and leverages Linux Kernel features to work. It allows the user to create a container and run it, starting from an image developed by the user or downloaded from a registry. -* ***docker-cli:*** It is a command-line tool that allows the user to properly communicate with the *docker-daemon*. As a matter of fact, any operation on images or containers always starts via *docker-cli*. When Docker is installed, both the *docker-daemon* and the *docker-cli* are installed together and any operation always takes place via *docker-cli*, even if managed via *docker-daemon*. -* ***docker-hub:*** It is a [Docker image repository](https://hub.docker.com/) from which it is possible to download all the images of interest and run them to create containers. Alternatively, a user can create the needed images through a *dockerfile*, using the repository only to download the required base images (like Linux-alpine). - -![Docker host](assets/Docker_host.png "Docker host vs client") - -Now it is time to highlight better which is the difference between an image and a container. In programming languages, an image can be assimilated to a class, while a container to an object. It is possible to create a container starting from an image and then run it, stop it or pause it. When it is no longer needed, it can be deleted without removing the corresponding image. - -As already mentioned, images can be downloaded from a registry like Docker or they can be defined through a *dockerfile*. A *dockerfile* is a text file that contains all the commands (*FROM, COPY, CMD, ENTRYPOINT, etc.*) that a user can call from the command line to build various image layers. The *dockerfile* represents a definition of the image but not the final image, which can be built through `docker build` command. - -A Docker image is made up of many layers and includes everything needed to configure a container. In particular, all the layers an image contains are read-only and, consequently, the image itself is also read-only. In this way, it is possible to launch the image several times always creating the same container. When the container is created, a thin writable layer will be placed on top of the existing image layers and will be prepared to execute the main process command. This last writable layer will contain any changes made when the container is running, but will not affect the original underlying image. When the container is deleted, this thin writable layer is removed. - -An important thing to keep in mind is that, even if Docker shares the Linux Kernel with the underlying host, it is always necessary to add a full operating system or a Linux distribution as the first layer. - -![Images and containers](assets/images_containers.png "Images vs containers") - -On the other hand, a container represents a process, which runs starting from an image. The important thing to understand is that a container has a lifecycle and, for this reason, it can reach different states depending on whether it is running or not. The lifecycle of a Container consists of the following states: - -* **Created:** This is the first state of the container lifecycle and it occurs after an image has been created with the command `docker create`. A writable thin layer is created on the specified image and prepared to execute the main process commands. Consider that in this state the container is created but not started. -* **Running:** This is the state in which the container is actually running. A container created through `docker create` or interrupted can be restarted through the command `docker start`. -* **Paused:** A running container can be paused through the command `docker pause`. As a consequence, all the processes of the specified container are suspended or blocked. When a container is paused, both the file system and the RAM are not affected. -* **Stopped:** A stopped container does not have any running process. When a container is stopped through the command `docker stop`, the file system is not affected, but the RAM gets deleted. This is the main difference between stopped and paused states. -* **Deleted:** A container can be removed through the command `docker rm`. This implies the complete cancellation of all the data associated with the container, including file system, volume and network mapping. - -Let's now have a look at the main Docker commands. The full list can be found [here](https://docs.docker.com/engine/reference/commandline/docker/). -Through the command `docker image ls` it is possible to check all the images installed on your Portenta. These images may have been downloaded from a repository using the command `docker pull XXX` or created from scratch with the command `docker build XXX` starting from a *dockerfile*. - -Through the command `docker run XXX`, it is possible to run the image downloaded from the repository. But, if a user tries to launch a container through the command `docker run XXX` for a container whose image has not been downloaded yet, first the image will be downloaded and then the container will start running. - -To verify whether a container is running as expected, it is possible to launch the command `docker ps`. - -So, to summarize, Docker is a very powerful technology that allows a user to avoid installing an infinite number of servers and services on a machine. Furthermore, since it runs in an isolated environment makes it possible to move the container or rather the image to another machine or to a production server without friction. - -***If you want to learn more about how to work with Docker containers on your Portenta X8, please check the [dedicated section](#working-with-linux) of this user manual.*** - -### Arduino Environment - -In addition to what has been addressed before, the user has the possibility to upload sketches on **M4 core** of **STM32H7** through the **Arduino IDE 1.8.10 or above**. - -In order to do that, it is sufficient to open the Arduino IDE, make sure you have selected the Portenta X8 in the board selector and start writing your sketch. - -***Have a look at [this section](#portenta-x8-with-arduino-ide) of this user manual if you would like to start uploading your sketch on Portenta X8.*** - -From a user perspective, the process may appear to be the same as for other Arduino boards, but there are major differences in what happens behind the scenes: the Portenta X8 includes a service that waits for a sketch to be uploaded to a folder. This service is called `monitor-m4-elf-file.service`: it monitors the directory `/tmp/arduino/` looking for an updated version of the `m4-user-sketch.elf` and, each time it detects a new file, it proceeds to flash the M4 with the new sketch using `openOCD` (check [openOCD website](https://openocd.org/doc/html/About.html) if you want to learn more). - -### Communication Between Linux And Arduino - -The two processors inside Portenta X8 need a communication mechanism to exchange data with one another. The communication mechanism that is used is called **RPC (Remote Procedure Call)**. - -The expression RPC refers to the activation of a "procedure" or "function" by a program on a computer other than the one on which the program itself is executed. In other words, RPC allows a program to execute procedures "remotely" on "remote" computers (but accessible through a network). - -Essential to the concept of RPC is also the idea of transparency: the remote procedure call must in fact be performed in a way similar to that of the traditional "local" procedure call; the details of the network communication must therefore be "hidden" (i.e. made transparent) for the user. - -The RPC paradigm is particularly suitable for distributed computing based on the client-server model: the "call procedure" corresponds to the "request" sent by the "client" and the "return value" of the procedure corresponds to the "response" sent by the "server". In fact, distributed computing uses the resources of several computers connected to each other in a network (usually via the Internet) to solve large-scale computational problems. - -Although the ultimate goal of the RPC paradigm is to provide a remote procedure call mechanism whose semantics is essentially equivalent to that of the local procedure call (hence the aforementioned transparency of the mechanism), this equivalence is never fully achieved, due to difficulties that can arise in network communication (always subjected to failure). - -Since there is no single obviously "right" way to handle these complications, RPC mechanisms can differ subtly in the exact semantics of the remote call. Some mechanisms, for example, have "at most once" semantics: in other words, a remote procedure call can fail (i.e. not be executed) but it is guaranteed not to result in multiple activations. The opposite approach is represented by the "at least once" semantics, which guarantees that the procedure is called at least once (it could therefore happen that it is activated several times). - -As a consequence, there are multiple types of RPC implementations. In the case of Portenta X8, **MessagePack-RPC** is used (check the [library repository](https://github.com/msgpack-rpc/msgpack-rpc) to get more details). It is an RPC implementation that uses MessagePack as a serialization protocol, i.e. data exchange is encoded in MsgPack format. - -It is transported over different protocols: - -* OpenAMP via Shared Memory -* SPI -* Linux Char Device -* TCP/IP - -![Linux Arduino RPC](assets/linux_arduino_RPC.png "Linux Arduino RPC") - -As you can see in the image above, the **M7 core** of **STM32H7** is used to facilitate the communication between the Linux and the Arduino environments. If an Arduino sketch is running on the **M4 core**, the **M7 core** will hand over any data/request between the M4 core and the Linux side. Due to this hardware design, traditional dual-core processing is not supported in the Portenta X8. - -At the same time, on the Linux side, there is a service that takes care of sending data between the two worlds, `m4-proxy`. - -So, the communication between Arduino and Linux side will proceed as follow (check the image below): - -* A program registers as the RPC server on port X for a list of procedures that the M4 may call -* `m4-proxy` will forward the calls from the M4 to the registered program/port - -![RPC M4 proxy](assets/m4-proxy.png "RPC M4 proxy") - -***If you want to learn more about how to work with RPC on your Portenta X8, please check the [dedicated section](#working-with-arduino) of this user manual.*** - -## Portenta X8 OS Image Update - -It is recommended to check every now and then if your Portenta X8 image version is up to date, in order to have the latest security updates. - -In the next sections, four major ways to update your Portenta X8 are described: - -* Update for OS release V.399 -* Update through Out-of-the-box experience (available for OS release XXXX or newer) -* Update through Portenta X8 Manager in your Arduino Cloud for Business account (available for all OS releases) -* Update using `uuu` tool (compatible with custom images) - -### Check Portenta X8 OS Release - -In order to verify which OS release is flashed on your Portenta X8, you need to connect to your board through **ADB**, as explained in [this section](#working-with-linux) of this user manual. - -At this point, you can type `cat /etc/os-release` in your command line window to get the OS release currently running on your device. - -![Get OS release](assets/adb-shell-os-release.png "Get OS Release") - -As shown in the image above, the OS release of this Portenta X8 corresponds to `IMAGE_VERSION=569`. - -### Update For OS Release V.399 - -If your Portenta X8 is flashed with the OS release V.399 and you have a carrier compatible with Portenta X8 (like Portenta Breakout), we recommend you to update it to the latest image release by following [this tutorial](https://docs.arduino.cc/tutorials/portenta-x8/image-flashing#flashing-mode-with-carrier). - -Otherwise, you can also open a new Command Line window and connect to your Portenta X8 as explained [here](#working-with-linux). At this point, verify that your Portenta X8 is connected to the Internet and type the following commands: - -```arduino -wget https://downloads.arduino.cc/portentax8image/399-install-update -``` - -```arduino -chmod +x 399-install-update -``` - -```arduino -sudo ./399-install-update -``` - -Remember that the default password for admin access is `fio`. - -Now you need to reboot the board by pressing its pushbutton for around 10 seconds. After that, connect again to your Portenta X8 through the Command Line and type the following commands: - -```arduino -wget https://downloads.arduino.cc/portentax8image/399-finalize-update -``` - -```arduino -chmod +x 399-finalize-update -``` - -```arduino -sudo ./399-finalize-update -``` - -These commands will make your V.399 compatible with [aklite-offline](https://docs.foundries.io/latest/user-guide/offline-update/offline-update.html) tool and will allow you to update your Portenta X8 to the latest image version Arduino released at that point in time. Arduino provides this tool for free for any Portenta X8 user to enable offline secure updates to all devices, even if those devices are not connected to any FoundriesFactory. - -After the update process is finalized, your Portenta X8 will immediately start running the latest OS release. - -### Update Through Out-Of-The-Box Experience - -Leverage the integrated Out-of-the-box experience to update your Portenta X8 to the latest release. - -***Warning: The Out-of-the-box update feature is not a complete Over-The-Air (OTA) update, it allows the user to update only Portenta X8 default image and containers. It will overwrite any custom container application. Thus, it is recommended to make a local copy of your containers before updating your Portenta X8.*** - -Open your Out-of-the-box as explained in [this section](#first-use-of-your-portenta-x8). - -![Out-of-the-box homepage](assets/OOTB_homepage.png "Out-of-the-box homepage") - -Click on **CHECK FOR UPDATES** in the lower right corner. - -At this point, you have to select whether you would like to proceed with the update. If yes, click on **UPDATE**. - -![Proceed with update](assets/OOTB_update_select.png "Proceed with update") - -During the update, do not turn off your Portenta X8 or disconnect it from the network. This process may take few minutes. - -![Successful update](assets/OOTB-succesful-OS-update.png "Successful update") - -Once the update is finished, your Portenta X8 will automatically restart with the new Linux image in place. - -At this point, if you would to continue to use your Out-of-the-box, you can open a new command line window and launch again the command `adb forward tcp:8080 tcp:80`. Now open your browser, go to [http://localhost:8080](http://localhost:8080) and the same Out-of-the-box dashboard will appear. - -#### Troubleshooting - -If something gets wrong during the update, you still have the possibility to manually flash your Portenta X8 with the latest Linux image provided at [this link](https://github.com/arduino/lmp-manifest/releases). You can follow [this section](#update-using-uuu-tool) to learn to use `uuu` tool and update your device manually with the latest OS Image version. Follow [this dedicated tutorial](https://docs.arduino.cc/tutorials/portenta-x8/image-flashing) to learn how to flash your device manually. - -### Update With Portenta X8 Board Manager - -If you have an *Arduino Cloud for business* account with the Portenta X8 Manager, check if the target installed on your Portenta X8 is the latest one available in your FoundriesFactory. - -![FoundriesFactory device overview](assets/web_board_manager_factory_device-overview.png "FoundriesFactory device overview") - -If this is not the case, you can update your device using FoundriesFactory **Waves** functionality. Check [this tutorial](https://docs.arduino.cc/tutorials/portenta-x8/waves-fleet-managment) to read the complete instructions. More information about Waves can be found in the official Foundries documentation at [this link](https://docs.foundries.io/latest/reference-manual/factory/fioctl/fioctl_waves.html?highlight=wave). - -### Update Using `uuu` Tool - -An alternative method to updating the Portenta X8 with the latest OS image is to use the `uuu` command (`uuu_mac` command in case you are using MAC OS). This flash method is helpful if you have built a custom image or desire a more manual approach. Nonetheless, you will need to prepare the OS image files and the board must be set into programming mode for this flashing process. - -***To learn more about creating a custom image for Portenta X8, please check out [How To Build a Custom Image for Your Portenta X8](https://docs.arduino.cc/tutorials/portenta-x8/image-building) tutorial.*** - -You will need to download the latest OS image file via [Arduino Download repository](https://downloads.arduino.cc/portentax8image/image-latest.tar.gz) and extract the files in a desired directory. The structure should be similar as follows after also extracting `mfgtool-files-portenta-x8.tar.gz` and `lmp-partner-arduino-image-portenta-x8.wic.gz` that came within the original compressed file: - -``` -Unzipped folder -├── mfgtool-files-portenta-x8/ -├── imx-boot-portenta-x8 -├── lmp-partner-arduino-image-portenta-x8.wic -├── lmp-partner-arduino-image-portenta-x8.wic.gz **(Compressed)** -├── mfgtool-files-portenta-x8.tar.gz **(Compressed)** -├── sit-portenta-x8.bin -└── u-boot-portenta-x8.itb -``` - -#### Set Flashing Mode with Carrier - -The Portenta X8 can be set into programming mode by using a carrier platform, such as Max Carrier, Breakout, or Hat Carrier, which provides DIP switches for convenient access; or using a few more lines of command with barebone Portenta X8 via ADB. - -If you plan to use a carrier, please check the carrier's configuration to be paired with Portenta X8. - -For the **Portenta Max Carrier**, set the `BOOT SEL` and `BOOT` DIP switches to ON position as depicted in the figure: - -![Portenta Max Carrier DIP switches](assets/max-carrier-dip-switches.png) - -Upon executing the `uuu` tool and ensuring the DIP switches are correctly configured, the Portenta Max Carrier will automatically start the flashing operation for the Portenta X8. - -For the **Portenta Breakout**, the `BT_SEL` and `BOOT` DIP switches should be set to the ON position, as illustrated in the figure: - -![Portenta Breakout DIP switches](assets/breakout-dip-switches.png) - -After running the `uuu` tool, perform a long press on the `ON` button of the Portenta Breakout to begin the flashing process. This action enables the tool to identify and connect with the device, continuing with the flashing operation. - -For the **Portenta Hat Carrier**, the `BTSEL` DIP switch must be set to the ON position, as depicted in the figure below: - -![Portenta Hat Carrier DIP switches](assets/hatCarrier-dip-switches.png) - -The `ETH CENTER TAP` DIP switch position does not affect the flashing mode state for the Portenta Hat Carrier. - -Like with the Portenta Max Carrier, once the `uuu` tool is run and starts searching for the device, the flashing process will commence. - -#### Set Flashing Mode without Carrier - -If you decide to flash Portenta X8 without using the carrier, use the following command sequence inside the Portenta X8's terminal via ADB while you are in the root environment with root permission to reset Portenta X8's bootloader sector: - -```arduino -echo 0 > /sys/block/mmcblk2boot0/force_ro -``` - -```arduino -dd if=/dev/zero of=/dev/mmcblk2boot0 bs=1024 count=4096 && sync -``` - -```arduino -echo 0 > /sys/block/mmcblk2boot1/force_ro -``` - -```arduino -dd if=/dev/zero of=/dev/mmcblk2boot1 bs=1024 count=4096 && sync -``` - -#### Flashing the Portenta X8 Using `uuu` Command - -Now that we have the Portenta X8 in programming mode, we need to flash the OS image. Within the previously described OS image file structure, you need to navigate to `mfgtool-files-portenta-x8` directory. Inside the directory, you will find the `uuu` executable and its components. Here, you will open a terminal and run the following command: - -``` -uuu full_image.uuu -``` - -If Portenta X8 is to be flashed without a carrier, you will want to execute the command **first** to let it search for the board. Subsequently, you will recycle the power source for Portenta X8 by unplugging and reconnecting the USB-C® cable. It will let the board begin its boot sequence, allowing it to enter programming mode as set with the defaulted internal bootloader. When the active `uuu` instance detects board has entered programming mode, it will continue with its flashing process. - -Once the flashing operation finishes, you will be greeted with a similar message in the terminal as the following figure: - -![Successful uuu flashing operation](assets/uuu-flashing-success.png) - -This applies to both flashing scenarios. If you have the carrier attached and decide to continue using docked with the platform, you must reset the DIP switch positions for either `BOOT SEL`, `BTSEL`, or `BT_SEL` and `BOOT` to OFF state. Reconnect the board and wait approximately 10 seconds until the Blue LED blinks, confirming the boot was successful. - -In case the Portenta X8 was flashed barebone, you will just need to recycle the power and should be ready with the latest OS image. - -***For more in-depth tutorial for flashing Portenta X8, please check out [How To Flash Your Portenta X8](https://docs.arduino.cc/tutorials/portenta-x8/image-flashing) tutorial.*** - -## First Use Of Your Portenta X8 - -You can now start interacting with your Portenta X8. Portenta X8 comes with an embedded Out-of-the-box experience that will guide you step-by-step in the configuration of your board. - -### Power The Board - -Connect the Portenta X8 to your PC via a USB-C® cable (either USB-C® to USB-A or USB-C® to USB-C®). - -Once connected, you will see the Portenta X8 LEDs start blinking. Portenta X8 features two LEDs, a Power LED and a Status LED, which can blink in parallel. - -![Portenta X8 LEDs](assets/portenta_x8_leds.png "Portenta X8 LEDs") - -The table below describes LEDs meaning and functionalities. - - | LED Type | Colour | Meaning | - | ------------ | ------------ | ------------------------------------------------| - | Power LED | Red | Power ON | - | Status LED | White | OS booting in progress | - | Status LED | Blue | Linux Kernel running | - | Status LED | Green | Board connected to the Internet | - | Status LED | Red | STM32H7 LED, blinking when triggered in the IDE | - -### Out-Of-The-Box Experience - -***It is recommended to have your Portenta X8 with the latest OS version. Check [this section](#portenta-x8-os-image-update) to learn how to have your Portenta X8 up-to-date.*** - -Once the Portenta X8 is correctly powered up, you can start interacting with it. - -In order to do that, you have the possibility to connect to your Portenta X8 through [**ADB**](https://developer.android.com/studio/command-line/adb). Android Debug Bridge (ADB) is a tool included in the SDK software (Software Development Kit) and used, inter alia, to make an Android device and a computer to communicate with each other. - -In the case of the Portenta X8, ADB allows to establish a reliable communication between Portenta X8 and a command-line interface of a computer. In order to check if you have already installed ADB on your computer, you have to verify you installed the latest **Mbed OS Portenta Core** from the IDE. Portenta core contains ADB in it. - -***If you need to install ADB, you can also download the right tool for your Operating System directly from the [official Android website](https://developer.android.com/studio/releases/platform-tools).*** - -At this point, you can open your terminal window and look for ADB inside the directory **Arduino15/packages/arduino/tools/adb/32.0.0**. - -***The Arduino15 folder may have a different location depending on the Operating System you are using. Check [this article](https://support.arduino.cc/hc/en-us/articles/360018448279-Open-the-Arduino15-folder) to learn where your Arduino15 folder is located.*** - -To check if ADB is working correctly, you can type `adb devices`. Your Portenta X8 will be listed there. - -![Connection with ADB](assets/adb-connection.png "Connection with ADB") - -To start the Out-of-the-box experience, you can continue typing in your terminal `adb forward tcp:8080 tcp:80`. With this command, ADB allows to forward the requests of the `8080 TCP-IP port` of your computer to the `80 TCP-IP port` of your device, that for this case it is the device with the name _Portenta X8_. - -![ADB forward command](assets/adb-tcp-port.png "ADB forward command") - -Now you can open your browser, go to [http://localhost:8080](http://localhost:8080) and the same Out-of-the-box dashboard will appear to allow you to configure your Portenta X8. - -![Out-of-the-box Homepage](assets/OOTB_homepage.png "Out-of-the-box Homepage") - -#### Portenta X8 Out-Of-The-Box Homepage - -This web page is hosted on the Portenta X8 and allows a user to: - -- Get board details -- [Configure Portenta X8 Wi-Fi®](#wi-fi-configuration) -- [Interact with the board through the embedded Python® Alpine Shell](#portenta-x8-with-python-alpine-shell) -- [Provision your device to Arduino Cloud](#portenta-x8-with-arduino-cloud) -- Manage the Linux distribution with the dedicated [Portenta X8 Board Manager](#portenta-x8-board-manager) - -#### Wi-Fi® Configuration - -Click **Wi-Fi® Settings** to start configuring your network connectivity. Otherwise, you can also connect your Portenta X8 to the Internet through an Ethernet cable, using a USB-C® hub with an RJ45 port or a Portenta Carrier. In this tutorial, Wi-Fi® connectivity will be used. - -![Out-of-the-box Wi-Fi® Settings](assets/OOTB_homepage_Wifi.png "Out-of-the-box Wi-Fi® Settings") - -Select your Wi-Fi® SSID. You can either select a network from the available list or insert your SSID manually. - -![Out-of-the-box Wi-Fi® SSID set-up](assets/OOTB_wifi_selection.png "Out-of-the-box Wi-Fi® SSID set-up") - -Type your Wi-Fi® password. - -![Out-of-the-box Wi-Fi® password set-up](assets/OOTB_wifi_SSID.png "Out-of-the-box Wi-Fi® password set-up") - -Once it is connected, you will get a notification confirming your Portenta X8 is now connected to the selected network. - -Moreover, you can check the network you are connected to in the bottom left section of this dashboard. - -![Out-of-the-box Wi-Fi® connection successful](assets/OOTB_wifi_connected.png "Out-of-the-box Wi-Fi® connection successful") - -Now you can click **OK** and you will be redirected to the Out-of-the-box homepage shown below. - -![Out-of-the-box Homepage](assets/OOTB_homepage.png "Out-of-the-box Homepage") - -***You can change your network by clicking on the Wi-Fi® Settings button and repeat the steps from above.*** - -#### Portenta X8 with Python Alpine Shell - -Click the **Shell** button to start using your Portenta X8 with Python-Alpine. - -![Out-of-the-box Shell button](assets/OOTB_homepage_shell.png "Out-of-the-box Shell button") - -This shell is running in a Python-Alpine container embedded in Portenta X8. In this shell, you will find multiple examples under the directory `/root/examples`. Additionally, you can either add your own package through the command `apk add ` or start exploring the packages available online at [this link]( https://pkgs.alpinelinux.org/packages). - -![Out-of-the-box Python-Alpine Shell](assets/OOTB_alpine_shell.png "Out-of-the-box Python-Alpine Shell") - -#### Portenta X8 with Arduino Cloud - -***Note: this is an optional step. The Portenta X8 can be also used with a local IDE without the need for any internet connection.*** - -Making Portenta X8 compatible with Arduino Cloud means opening a wide range of new applications. This compatibility is guaranteed by a brand-new Python container, which includes a dedicated [Arduino IoT Cloud Python library](https://github.com/arduino/arduino-iot-cloud-py). Through Arduino Cloud APIs, the Python container ensures full interaction and simple porting of any Python developed application in the Arduino Cloud. - -***Check all the available Arduino Cloud plans [here](https://cloud.arduino.cc/plans#business) and create your Arduino Cloud account in a couple of steps (see the dedicated documentation at [this link](https://docs.arduino.cc/arduino-cloud/)).*** - -With the Out-of-the-box experience, your Portenta X8 can be securely self-provisioned in Arduino Cloud, you just need to create API keys and the Python container running on X8 will do the rest. When provisioned, you can start directly interacting with an example Thing and Dashboard that will be automatically generated for you to guide you step-by-step in this new journey. - -Click the **Arduino Cloud** button to start provisioning your Portenta X8 in Arduino Cloud. - -![Out-of-the-box Arduino Cloud](assets/OOTB_homepage_cloud.png "Out-of-the-box Arduino Cloud") - -Start setting up the device name for your Portenta X8 (in this case *portenta-x8-test*) and click on **CONTINUE**. The same device name will be used and visualized into your Arduino Cloud space, but you can freely change it in the future. - -![Out-of-the-box Arduino Cloud Device Name](assets/OOTB_cloud_device_name.png "Out-of-the-box Arduino Cloud Device Name") - -At this point, you will be asked to insert your API Key credentials and Organization ID. Organization ID is optional and should be filled in only in case you are using a Shared Space in Arduino Cloud for Business. - -![Out-of-the-box Arduino Cloud API Keys](assets/OOTB_cloud_generate_API.png "Out-of-the-box Arduino Cloud API Keys") - -In order to get API keys, you need to log into your Arduino Cloud account and select the Space you would like your X8 to be provisioned into. - -Thus, click on **GENERATE API KEY** in your Out-of-the-box dashboard. A new window will open in your web browser to allow you to login to your Arduino Cloud space. - -***If you want to learn more about what API keys are and how they work, please take a look at the dedicated documentation available at [this link](https://docs.arduino.cc/arduino-cloud/getting-started/arduino-iot-api).*** - -![Arduino Cloud Login](assets/web_Cloud_login.png "Arduino Cloud Login") - -Click on **SIGN IN**. If you do not have an Arduino Cloud account yet, create a new one from the same webpage. - -Sign in to your Arduino Cloud account by adding your credentials, i.e. Username/email and Password. - -![Arduino Cloud Sign in](assets/web_cloud_signin.png "Arduino Cloud Sign in") - -You are now logged into your Arduino Cloud space. Go on by clicking on **API keys** found within the account banner located at the top right corner. - -![Arduino Cloud Homepage](assets/web_cloud_homepage.png "Arduino Cloud Homepage") - -It is time to generate your API keys. Click on **CREATE API KEY** in the upper right-hand corner. - -![Arduino Cloud New API Key](assets/web_cloud_new_api.png "Arduino Cloud New API Key") - -Define a name for your API key, in this case *portenta-x8-test-API*, and click on **CREATE**. These API Keys are personal and visible just from your account. - -![Arduino Cloud API Key name](assets/web_cloud_API_name.png "Arduino Cloud API Key name") - -At this point, your API key has been created. Save the correspondent credentials in a safe storage space by clicking on **download the PDF**. - -Keep this file safely stored, your API credentials cannot be recovered otherwise. If you lose it, you will have to generate new API keys by repeating the above procedure. - -![Arduino Cloud API Key](assets/web_cloud_API_key.png "Arduino Cloud API Key") - -The PDF file will look like the image below and it will include the credentials you need to copy and paste into the Out-of-the-box page. - -![Arduino Cloud API Key PDF](assets/web_cloud_API_key_PDF.png "Arduino Cloud API Key PDF") - -Thus, copy the **Client ID** and the **Client Secret** credentials and paste them into your Out-of-the-box dashboard as shown below. - -![Out-of-the-box with API Keys](assets/OOTB_cloud_API_copy.png "Out-of-the-box with API Keys") - -If you are using an Arduino Cloud for Business account with Shared Spaces, you need to add also the Organization ID you would like your Portenta X8 to be provisioned into by clicking on **ADD ORGANIZATION**. - -![Out-of-the-box successful Cloud provisioning](assets/OOTB_cloud_success.png "Out-of-the-box successful Cloud provisioning") - -In order to recover the Organization ID, known as Space ID, of your Shared Space on Arduino Cloud for Business, open your Arduino Cloud homepage and navigate to **Space Settings > General** in the sidebar on the left. - -![Space ID on Cloud Settings](assets/shared-space-settings.png "Space ID on Cloud Settings") - -At this point, you can copy the **Space ID** of your Shared Space and paste it into your Out-of-the-box dashboard together with your API keys. - -![API keys and Organization ID](assets/OOTB_cloud_organization_ID.png "API keys and Organization ID") - -Click on **SETUP DEVICE** and you are ready to go, your Portenta X8 is now provisioned into your Arduino Cloud space. - -![Out-of-the-box successful Cloud provisioning](assets/OOTB_cloud_success.png "Out-of-the-box successful Cloud provisioning") - -Once provisioned, the Portenta X8 will be automatically linked to an example [Thing](https://create.arduino.cc/iot/things) and [Dashboard](https://create.arduino.cc/iot/dashboards). You can freely check them by clicking on the corresponding links embedded in the Out-of-the-box. - -![Portenta X8 example Thing](assets/cloud_thing_created.png "Portenta X8 example Thing") - -As already said, Arduino provides you with an example dashboard that will automatically set up and be visible live after your Portenta X8 has been provisioned. In order to make this dashboard to automatically update its data, you need to go back to your Out-of-the-box and launch the example. - -To do so, it is sufficient to copy the shown code `python3 examples/arduino_iot_cloud_example.py` and click on **Launch Example**. An Alpine-Python shell will open and you will have to paste the previous code here to launch the example. - -![Launching dashboard example](assets/OOTB_example_dashboard_launch.png "Launching dashboard example") - -Now you can navigate to your dashboard [here](https://create.arduino.cc/iot/dashboards) to see your Portenta X8 LED blinking as well as the live temperature inside the microprocessor. - -![Portenta X8 dashboard working](assets/cloud_dashboard_working.png "Portenta X8 dashboard working") - -***If you face any issues during the provisioning of your Portenta X8, feel free to repeat the procedure above.*** -***If you would like to customize your Portenta X8 Things/Dashboards with your own data, check [this section](#working-with-arduino-cloud) of the user manual.*** - -#### Portenta X8 Board Manager - -***Note: this is an optional step. Although the Portenta X8 Board manager opens a wide range of possibilities that are important for business applications, the Portenta X8 can be used for free without the need of any additional paid license*** - -Now you can start connecting your Portenta X8 to the Portenta X8 Board Manager. To enjoy this feature, you need an Arduino Cloud for business account. - -Check the Arduino Cloud for business plan with Portenta X8 Manager [here](https://cloud.arduino.cc/plans#business) and create your Arduino Cloud account in a couple of steps (see the dedicated documentation at [this link](https://docs.arduino.cc/arduino-cloud/)). - -When your Arduino Cloud for business account is correctly set up, log into it [here](https://cloud.arduino.cc/home/) and click on **Portenta X8 Board Manager**. The feature is located within the **Integrations** section of the Cloud. - -![Arduino Cloud homepage with Portenta X8 Manager](assets/web_board_manager_cloud_integration.png "Arduino Cloud homepage with Portenta X8 Manager") - -At this point, you will be asked to create a new account on [Foundries.io](https://foundries.io/) platform. It is recommended to register with the same email address you are currently using in your Arduino Cloud for business account. - -![Foundries.io login](assets/web_board_manager_foundries_login.png "Foundries.io login") - -Add all your credentials and click on **Sign up**. - -![Foundries.io sign up](assets/web_board_manager_signup.png "Foundries.io sign up") - -So, let's create your brand new FoundriesFactory. Select **Arduino Portenta X8**, define a **Factory name** for your Factory and then click on **Create Factory**. - -![FoundriesFactory name](assets/web_board_manager_factory_name.png "FoundriesFactory name") - -Your FoundriesFactory is correctly set-up. As you can see, the Factory does not have any device connected to it. - -![FoundriesFactory homepage with no devices](assets/web_board_manager_factory_overview.png "FoundriesFactory homepage with no devices") - -To provision your Portenta X8, you need to go back to your Out-of-the-box webpage and click on **Portenta X8 Manager** button. - -![Out-of-the-box Portenta X8 Manager](assets/OOTB_homepage_portenta_x8_manager.png "Out-of-the-box Portenta X8 Manager") - -Enter the Factory name you have just registered, in this case *user-test*, and assign a Board Name to your Portenta X8. This Board Name will be used to correctly identify your Portenta X8 into your FoundriesFactory. You can now click on **REGISTER**. - -![Out-of-the-box Factory and device registration](assets/OOTB_board_manager_factory_registration.png "Out-of-the-box Factory and device registration") - -To complete the registration of the Board with the FoundriesFactory, copy the code that appeared in your Out-of-the-box. - -![Out-of-the-box Factory code challenge](assets/OOTB_board_manager_factory_challenge.png "Out-of-the-box Factory code challenge") - -Click on **COMPLETE REGISTRATION** to be re-directed to the Foundries.io activation page. - -Paste your token in the text box and press **Next**. - -***The token code is valid for 15 minutes; if you do not paste it in this time span, you have to repeat all the above registration steps in your Out-of-the-box to generate a new code.*** - -![FoundriesFactory pasted token](assets/web_board_manager_factory_challenge.png "FoundriesFactory pasted token") - -Confirm the addition of your Portenta X8 by pressing **Connect**. - -![FoundriesFactory device confirmation](assets/web_board_manager_factory_challange_connect.png "FoundriesFactory device confirmation") - -Go to your FoundriesFactory by clicking on **Factories Page**. - -![FoundriesFactory device registration completed](assets/web_board_manager_factory_challenge_approved.png "FoundriesFactory device registration completed") - -Now you will see the number of devices associated with your FoundriesFactory to be equal to 1. - -![FoundriesFactory with 1 device](assets/web_board_manager_factory_device.png "FoundriesFactory with 1 device") - -Your Portenta X8 is correctly provisioned into your FoundriesFactory. - -To verify your device status, click on your FoundriesFactory, go to **Devices** section and check its target update and the installed containers Apps. - -![FoundriesFactory device overview](assets/web_board_manager_factory_device-overview.png "FoundriesFactory device overview") - -***If you want to learn more about Portenta X8 Manager features, check the dedicated section of this user manual called [Working with Portenta X8 Board Manager](#working-with-portenta-x8-board-manager).*** - -## Portenta X8 with Arduino IDE - -In this section you will learn how to upload a sketch to the M4 core on the STM32H747XI MCU. - -Open the Arduino IDE and make sure you downloaded the latest Arduino Mbed OS Portenta Boards Core. Learn how to do it by following [this tutorial](https://docs.arduino.cc/software/ide-v1/tutorials/getting-started/cores/arduino-mbed_portenta). - -Select Portenta X8 in the board selector. - -![IDE Board Selector](assets/x8-IDE.png "IDE Board Selector") - -Create a custom sketch or open one of the example sketches e.g. the blink sketch: - -```arduino -void setup(){ - pinMode(LED_BUILTIN ,OUTPUT); -} - -void loop(){ - digitalWrite(LED_BUILTIN , HIGH); - delay(1000); - digitalWrite(LED_BUILTIN , LOW); - delay(1000); -} -``` - -At this point, select the port of your device in the port selector menu and then press the Compile and Upload button. - -Behind the curtains, the sketch gets compiled into a binary. That binary file is then uploaded to the Linux side of the Portenta X8. The flashing is done on the board itself by the RPC service running on Linux (see [Communication between Linux and Arduino section](#communication-between-linux-and-arduino) of this user manual to learn more). - -When the sketch has been uploaded successfully, the onboard LED of your Portenta X8 will start blinking at an interval of one second. - -You can also upload the firmware manually if you like. To do so, you first need to compile the sketch: select **Export compiled binary** from the Sketch menu in the Arduino IDE. It will compile the sketch and save the binary file in the sketch folder. Alternatively, you can use the [Arduino CLI](https://arduino.github.io/arduino-cli/0.29/) to create an `elf` file. - -To upload the firmware you can use the ADB tool that has been installed as part of the Portenta X8 core. It can be found at `Arduino15\packages\arduino\tools\adb\32.0.0`. - -From that directory, you can use the `adb` tool. To upload your compiled sketch, you just need to type the following command into your terminal window: - -``` -adb push /tmp/arduino/m4-user-sketch.elf -``` - -![ADB upload with a terminal](assets/x8-terminal-ADB-push.png) - -## Working with Linux - -Now it is time to start interacting with the Linux OS embedded in your Portenta X8. To do that, you need to open your terminal window and look for ADB inside the directory **Arduino15/packages/arduino/tools/adb/32.0.0**. - -To check if ADB is working correctly, you can type `adb devices`. Your Portenta X8 will be listed there. - -![Connection with ADB](assets/adb-connection.png "Connection with ADB") - -At this point, you can type `adb shell` to start communicating with your Portenta X8. - -![ADB shell command](assets/adb-shell-command.png "ADB shell command") - -As it is a Linux device, you can do tasks like creating files, changing directories, etc. - -To gain admin (root) access, type `sudo su -` and the password, which by default is `fio`. After that, the terminal prefix should turn red. - -![ADB shell with admin access](assets/adb-sudo-su.png "ADB shell with admin access") - -You can now freely program your Portenta X8 Linux OS. In the sections below you can check some basic commands to get started. - -### Change Default User Password - -Your Portenta X8 comes with the default user fio with password fio. - -For security reasons, we strongly suggest changing the default password. To do so, when logged in to your Portenta X8, launch this command to change the password of the fio account: - -```arduino -passwd fio -``` - -### Manage Your Network Via CLI - -In order to connect to a Wi-Fi® Access Point via CLI, you can use the network manager tool **nmcli**. These are some of the most used commands: - -* `nmcli device wifi connect password ` to connect to a specific SSID -* `nmcli de` to check the connection status -* `nmcli connection show` to visualize the active network interfaces (and their types) on your Portenta X8 - -### Accessing Over SSH Session - -Establishing communication with the Portenta X8 via an SSH session is possible. To do so, a network connection is needed, either over Wi-Fi® or Ethernet. For Ethernet connections, using a device with DHCP server capabilities, such as a network router, is recommended. After setting up the network connection and DHCP, the Portenta X8 will be ready for SSH communication. - -For Windows users, it is necessary to install a service tool to ease the following procedures. While Bonjour, Apple's implementation of zero-configuration networking, comes built into macOS, it is not natively included in Windows and must be installed separately. - -***Before proceeding on __Windows__, please install [Bonjour Print Services for Windows](https://support.apple.com/kb/DL999?locale=en_US) before continuing the following steps.*** - -For macOS and Linux users, _Bonjour_ is pre-installed on macOS, and _Avahi-Browse_ is typically available on Linux by default. Thus, additional installation steps may be unnecessary for these operating systems. - -In the subsequent sections, we will first guide you through the process on Windows, followed by details and instructions for Linux and macOS. - -#### Using the Terminal -

- -![SSH Services Availability Discovery](assets/ssh-x8-dns-sd-service.png "SSH Services Availability Discovery") - -The command below is used to browse for SSH services on the local network that are advertised over a multicast Domain Name System (mDNS). This protocol resolves hostnames to IP addresses within small networks without a local name server. - -```bash -dns-sd -B _sftp-ssh._tcp local -``` - -By executing this command, you can discover devices offering _SFTP services_ (file transfer over SSH) without prior knowledge of their IP addresses or hostnames. - -The command lists these services, indicating where an SSH connection can be established for secure file transfers or shell access, helping to ease the identification and utilization of networked devices that support this protocol. - -![Network Query for IPv4 and IPv6](assets/ssh-x8-dns-sd-v4v6.png "Network Query for IPv4 and IPv6") - -```bash -dns-sd -G v4v6 portenta-x8-.local -``` - -The command above queries the network for the _IPv4_ and _IPv6_ addresses associated with the hostname `portenta-x8-.local`. The _UUID_ can be found within the instance name listed previously or if you have accessed the Portenta X8 via an ADB shell. An example command would look as follows: - -```bash -dns-sd -G v4v6 portenta-x8-1822aa09dab6fad9.local -``` - -This command is handy for finding the IP addresses of devices such as the Portenta X8 that a DHCP server may assign dynamic IP addresses. It simplifies connecting to such devices over the network by providing their current IP addresses. - -![Device Ping Test](assets/ssh-x8-dns-sd-ping.png "Device Ping Test") - -The following command sends echo requests to the device with the hostname `portenta-x8-.local` to check its network availability and measure round-trip time. - -```bash -ping portenta-x8-.local -``` - -This command helps verify that the Portenta X8 is online and reachable over the network and for diagnosing connectivity issues. The UUID can be ascertained by referring to the findings from an earlier SSH services scan with network query or the ADB shell. - -![Portenta X8 Communication over SSH Session](assets/ssh-x8-session.png "Portenta X8 Communication over SSH Session") - -After verifying that the Portenta X8 is accessible using a simple ping test, it is now possible to start an SSH session using the following command: - -```bash -ssh fio@portenta-x8-1822aa09dab6fad9.local -``` - -The example command above starts an SSH (Secure Shell) connection to the Portenta X8 with the hostname `portenta-x8-1822aa09dab6fad9.local` using the username `fio`. The command format should be as follows: - -```bash -ssh fio@portenta-x8-.local -``` - -When executing the command, substitute the `` placeholder with the actual UUID of the Portenta X8 you are attempting to connect to. You can confirm this UUID by checking the results of a prior SSH services scan with a network query or ADB shell. - -If the device is configured correctly to accept SSH connections and the _fio_ account exists with SSH access, this command will prompt for the password associated with the _fio_ user. - -Upon successful authentication, it will open a secure shell session to the device, allowing for command-line interface access and the execution of commands remotely on the Portenta X8. - -The password and the rest of the configuration for using the Portenta X8 inside the shell remain the same. - -The process is similar for _GNU/Linux_ and _macOS_, with minor differences in the initial steps when browsing for SSH services on the local network. - -- __For GNU/Linux__: - -Use _Avahi-Browse_ to search for SSH services on the local network: - -```bash -avahi-browse -d local _sftp-ssh._tcp --resolve -t -``` - -- __macOS__: - -On macOS, you can use the similar command: - -```bash -dns-sd -B _sftp-ssh._tcp local -``` - -Alternatively, you can use a software called "_Discovery_", which is available [here](https://apps.apple.com/it/app/discovery-dns-sd-browser/id1381004916?l=en&mt=12). - -#### Using Software With GUI -

- -The SSH session can be initialized using third-party software with a Graphical User Interface (GUI) for easy access. An example is a software called "_Bonjour Browser_", which can be downloaded [here](https://hobbyistsoftware.com/bonjourbrowser). - -![SSH Services Availability Discovery with GUI](assets/ssh-x8-bonjour.png "SSH Services Availability Discovery with GUI") - -This software simplifies browsing SSH services on the local network advertised over mDNS using a GUI. The image above, for example, shows all available services on the network, including those for the Portenta X8. By simply clicking on a service item, you can retrieve the IP address information. - -Once the information is verified, you can use that data with software such as [_PuTTY_](https://www.putty.org/). _PuTTY_ is a free and open-source terminal emulator, serial console, and network file transfer application. It supports several network protocols, including _SSH (Secure Shell)_ and _SFTP (SSH File Transfer Protocol)_. - -![Portenta X8 SSH Session with PuTTY - Setup](assets/ssh-x8-putty.png "Portenta X8 SSH Session with PuTTY - Setup") - -In the PuTTY Configuration window, keeping the default values, you must specify the _Host Name (or IP address)_ field with `portenta-x8-`. For instance, you would use: - -``` -portenta-x8-1822aa09dab6fad9 -``` - -Click on `Open`, and it will prompt a security alert. It displays information about the connection, including fingerprint details. Depending on your connection profile preference, you can choose to `Accept` or `Connect Once`. - -![Portenta X8 SSH Session with PuTTY - Authentication](assets/ssh-x8-putty-auth.png "Portenta X8 SSH Session with PuTTY - Authentication") - -After verifying the security alert and proceeding, you have an SSH session that has begun communicating with the Portenta X8. - -![Portenta X8 SSH Session with PuTTY](assets/ssh-x8-putty-session.png "Portenta X8 SSH Session with PuTTY") - -### Inspect Real-Time Tasks And Logs Via CLI - -Run `journalctl -f` to check the status of active services and possibly their errors, but also various system event logs. - -![ADB shell journalctl package](assets/adb-shell-real-time-tasks.png "ADB shell journalctl package") - -By calling `journalctl` it is possible to take a look at the log of all the running activities, by specifying also the type of log you are looking for. Some logs may be a warning which can be ignored or some may be critical errors. Type `journalctl -p 0` to view emergency system messages, otherwise change the number 0 with the error code you want to investigate according to the following error code numbers: - -| Error code | Meaning | -|------------|-----------| -| 0 | Emergency | -| 1 | Alerts | -| 2 | Critical | -| 3 | Errors | -| 4 | Warning | -| 5 | Notice | -| 6 | Info | -| 7 | Debug | - -When you specify the error code, it shows all messages from that code and above. For example, if you specify error code 2, then it shows all messages with priority 2, 1 and 0. - -Additionally, you can also view logs for a specific time and date duration. You can use the `-- since` switch with a combination of `"yesterday"`, `"now"`, or a specific date and time `"YYYY-MM-DD HH:MM:SS"`. - -An example of how to use the command: - -```arduino -journalctl --since "2022-12-22 12:20:00" --until yesterday -``` - -### Create And Upload Docker Containers To Portenta X8 - -We created dedicated tutorials covering this topic. Go check them out: - -* [Managing Containers with Docker on Portenta X8](https://docs.arduino.cc/tutorials/portenta-x8/docker-container) -* [Deploy a Custom Container with Portenta X8 Manager](https://docs.arduino.cc/tutorials/portenta-x8/custom-container) -* [Running Wordpress & Database Containers on Portenta X8](https://docs.arduino.cc/tutorials/portenta-x8/wordpress-webserver) - -### Output Video Content On A Screen - -The USB-C® port on your Portenta X8 supports video output. As a consequence, you can freely connect a USB-C® monitor or a USB-C® to HDMI hub to your Portenta X8 to start visualizing video or other visual renders. - -Here you can find a list of validated compatible USB-C® to HDMI hubs: - -* [TPX00145](https://store.arduino.cc/products/usb-c-to-hdmi-multiport-adapter-with-ethernet-and-usb-hub) -* [TPX00146](https://store.arduino.cc/products/usb-c-to-hdmi-multiport-adapter-4k-usb-hub-pd-pass-through) - -***Learn more on how to output WebGL content on a screen with Portenta X8 by checking the [dedicated tutorial](https://docs.arduino.cc/tutorials/portenta-x8/display-output-webgl).*** - -### Build A Custom Image For Portenta X8 - -You may want to build a custom image for the Portenta X8 with the source code provided in the public [GitHub repository of lmp-manifest](https://github.com/arduino/lmp-manifest). Building an image locally can help debug certain aspects of the system, such as the bootloader or kernel support. - -***Have a look at [this dedicated tutorial](https://docs.arduino.cc/tutorials/portenta-x8/image-building) to understand how to build your own custom image.*** - -### Additional Tutorials - -If you want to continue working with your Portenta X8, you can find tons of additional tutorials in the **Tutorials** section of our [Arduino Docs](https://docs.arduino.cc/hardware/portenta-x8). Go check them out! - -## Working With Arduino - -You have learned how to use your Portenta X8 with the Arduino IDE in the section [Portenta X8 with Arduino IDE](#portenta-x8-with-arduino-ide), but you can do much more with the Arduino environment, in particular leveraging the RPC communication between the Arduino layer and the Linux layer. - -You can have a look at this [GitHub repository](https://github.com/arduino/ArduinoCore-mbed/tree/master/libraries/RPC/examples) to have access to multiple IDE examples showing how to use RPC communication with Portenta X8. - -***Check [Communication between Linux and Arduino](#communication-between-linux-and-arduino) section of this user manual to learn more about RPC.*** - -You can build an Arduino sketch to manage all the tasks requiring real-time, including sensors communication, Fieldbus management, etc., and then send those data to a Cloud or remote server via multiple connectivity options, by leveraging the high-performance network management capabilities of Linux OS. - -For instance, try [Data Exchange Between Python® on Linux and an Arduino Sketch](https://docs.arduino.cc/tutorials/portenta-x8/python-arduino-data-exchange) tutorial to learn how to exchange sensor data between the Python® container embedded on Portenta X8 and an Arduino sketch. - -Additionally, if you are a more advanced user, you can check [Multi-Protocol Gateway With Portenta X8 & Max Carrier](https://docs.arduino.cc/tutorials/portenta-x8/multi-protocol-gateway) tutorial to develop your own multi-protocol gateway: receive data from a sensor with the Arduino layer via MQTT protocol, take advantage of RPC to establish communication between Arduino and Linux, and then send the acquired data to The Things Network via LoRaWAN® managed by the Linux layer. - -## Working With Arduino Cloud - -To start using your Portenta X8 with Arduino Cloud, provision your device as described in [this section](#portenta-x8-with-arduino-cloud). - -Once ready, you will have the chance to customize Portenta X8 example Thing and Dashboard. This can be done by writing your own Python script leveraging the [Arduino IoT Cloud Python library](https://github.com/arduino/arduino-iot-cloud-py). Check the documentation and the examples inside the library to learn more about how to create your own Python application. - -When your Python script is ready, you have to create a dedicated Dockerfile integrating your new script. The Dockefile needs the Out-of-the-box Python container (i.e. `arduino-ootb-python-devel`) to be able to correctly interact with your Arduino Cloud account. - -So, open a terminal window and create a Dockerfile integrating the following code together with your Python script: - -```arduino -FROM arduino/arduino-ootb-python-devel:latest -``` - -```arduino -# Copy custom python cloud scripts -COPY ./custom-examples /root/custom-examples -``` - -```arduino -RUN chmod -R 755 /root/custom-examples -``` - -### Build Your Container - -You can create your own custom container and build them inside the Portenta X8. Since Portenta X8 is based on an arm64 architecture, you can use the command `build` only if you are actually building the container directly on an arm64 architecture (e.g. Macbook based on M1/M2 processor or Portenta X8). Open a terminal window and type: - -```arduino -docker build . -t x8-custom-devel -``` - -Otherwise, if you are using a different architecture or building machine, use `buildx` command to specify which architecture your build should compile for: - -```arduino -docker buildx build --platform linux/arm64 -t x8-custom-devel --load . -``` - -In this way, your Docker image will be built and tagged with the name `x8-custom-devel`. - -Now it is time for you to deploy the newly created Docker image. To do so, you need to save it somewhere and then deploy it on your Portenta X8. - -### Deploy Your Container With Docker Hub - -If you have a [Docker Hub account](https://hub.docker.com/), you can freely upload your Docker image to your registry (e.g. `yourhubusername`): - -```arduino -docker push yourhubusername/x8-custom-devel -``` - -Your image is now available in your Docker Hub registry `yourhubusername`. - -At this point, you can directly pull the image to your Portenta X8. To do so, connect to your Portenta X8 through ADB. It can be found at `Arduino15\packages\arduino\tools\adb\32.0.0`. - -From that directory, you can pull the image to the location you prefer. - -```arduino -adb shell -``` - -With the Portenta X8's terminal, following command is used. - -```arduino -docker pull x8-custom-devel -``` - -Now your image is correctly deployed on your Portenta X8. - -### Deploy Your Container Without Docker Hub - -If you do not have a Docker Hub account, you can also save the Docker container locally as a .tar archive, and then you can easily load that to an image. - -To save a Docker image after you have built it, you can use the `docker save` command. For example, let's save a local copy of the `x8-custom-devel` docker image you made: - -```arduino -docker save x8-custom-devel:latest | gzip > x8-custom-devel_latest.tar.gz -``` - -At this point, you can directly pull the image to your Portenta X8. To do so, connect to your Portenta X8 through ADB. It can be found at `Arduino15\packages\arduino\tools\adb\32.0.0`. - -```arduino -docker import /home/fio/x8-custom-devel_latest.tar.gz x8-custom-devel:latest -``` - -Now your image is correctly deployed on your Portenta X8. - -### Launch Your Container - -In order to launch your brand new image, you need to create a new `docker-compose.yml`. To do so, first you must stop the current `docker-compose.yml`. - -```arduino -cd /var/sota/compose-apps/arduino-ootb && docker compose stop -``` - -You can now create the path for the new `docker-compose.yml`: - -```arduino -mkdir /var/sota/compose-apps/custom-devel && cd /var/sota/compose-apps/custom-devel && touch docker-compose.yml -``` - -Before uploading, open the `docker-compose.yml` and edit it as follow to make it use the Docker image you have just created: - -```arduino -services: - custom: - container_name: custom-devel - hostname: "portenta-x8" - image: x8-custom-devel:latest - - restart: unless-stopped - tty: true - read_only: false - user: "0" - volumes: - #- '/dev:/dev' - - '/run/arduino_hw_info.env:/run/arduino_hw_info.env:ro' - - '/sys/devices:/sys/devices' - - '/sys/class/pwm:/sys/class/pwm' - - '/sys/bus/iio:/sys/bus/iio' - - '/var/sota:/var/sota' - - './keys:/tmp/keys:ro' - devices: - - '/dev/gpiochip5' - - '/dev/tee0' -``` - -It is now time to upload the new `docker-compose.yml` to your Portenta X8: - -```arduino -docker-compose up --detach -``` - -And you are ready to go! Your Portenta X8 Dashboards and Things can be customized multiple times with the same process. - -***If you are using the Portenta X8 Manager, go to [this documentation](https://docs.foundries.io/latest/tutorials/getting-started-with-docker/getting-started-with-docker.html) to learn how to upload the newly created container in your FoundriesFactory.*** - -## Working With Portenta X8 Board Manager - -As already mentioned, Portenta X8 Board Manager allows you to easily keep your Portenta X8 Linux image and corresponding containers up to date, even from remote through Over-The-Air (OTA) updates (via wireless connectivity). - -Subscribe to an *Arduino Cloud for business* plan with Portenta X8 Board Manager to have access to all these features. Take a look at [this section](#portenta-x8-board-manager) of the user manual to learn more. - -### Device And Fleet Management With Portenta X8 Board Manager - -Verify that your Portenta X8 is correctly added to your FoundriesFactory by checking if it is listed among the available devices under the **Devices** section. - -![FoundriesFactory device overview](assets/web_board_manager_factory_device-overview.png "FoundriesFactory device overview") - -If you want to check if your Portenta X8 is updated according to the latest available Target (i.e. update), you can check the color of the bulb under the status column. There are three main color options: - -| Bulb color | Meaning | -|-------------|--------------------------------| -| Green | Device online and updated | -| Yellow | Device online and not updated | -| Red | Device offline and not updated | - -In this case, the Portenta X8 is connected to the network (and so to the FoundriesFactory), but it is not updated. - -You can see the Target uploaded on your device under the Target column, i.e. *portenta-x8-lmp-569*, and get additional information about what is included in this specific Target by clicking on it. - -![FoundriesFactory device target specs](assets/web_board_manager_factory_device_specs.png "FoundriesFactory device target specs") - -The above window also shows you all the container apps you have installed on your device and you can start using. - -If you scroll down in the same window, you can also have a look at the update history of that specific device. - -![FoundriesFactory device update history](assets/web_board_manager_factory_update_history.png "FoundriesFactory update history") - -At this point, you can compare the Target uploaded on your Portenta X8 with the Target available in the **Targets** section and decide whether to update your device or not. - -![FoundriesFactory target overview](assets/web_board_manager_factory_target.png "FoundriesFactory target overview") - -***Learn how to update your Portenta X8 with your FoundriesFactory by checking the [dedicated section](#portenta-x8-os-image-update) of this user manual.*** - -This **Target** page contains the Linux images built each time something is committed in the repositories available under the **Source** section. In this section, you can find the four repositories that are used to customize the images: - -* **ci-scripts.git:** Scripts that define the platform and container build jobs on the FoundriesFactory system. -* **containers.git:** This is where containers and docker-compose apps are defined. It allows you to define which containers to build/deploy and how to orchestrate them on the platform. -* **lmp-manifest.git:** The repo manifest for the platform build. It defines which layer versions are included in the platform image. This includes **meta-partner-arduino**, the layer containing Arduino-specific customizations (machine definition, device drivers, etc.). -* **meta-subscriber-overrides.git:** *OE* layer that defines what is included in your FoundriesFactory image. You can add board-specific customizations and overrides or add and remove packages provided in the default Linux microPlatform. - -Committing to **lmp-manifest.git** or **meta-subscriber-overrides.git** repositories will create a platform Target, i.e. base Linux platform image. On the other hand, committing to **containers.git** will create a container Target including all the containers and docker-compose apps you would like to upload on your Portenta X8. Both these Targets will generate the artifacts specified in the **ci-scripts.git**, which includes all the required files to program the Target in case of platform build. - -### RBAC With Portenta X8 Board Manager - -You do not have to be the only one in your organization with permission to update your Portenta X8 devices. The FoundriesFactory integrates a Role-Based-Access-Control functionality (RBAC) to allow users to add multiple teams with multiple members each. - -You can start defining a new team by clicking on **Teams** section. - -![FoundriesFactory Teams](assets/web_board_manager_team.png "FoundriesFactory Teams") - -The level of access and specific permissions are defined by the team’s role in the FoundriesFactory. As you can notice from the image below, multiple roles and permissions are available. - -![FoundriesFactory Team roles and permissions](assets/web_board_manager_factory_team_roles.png "FoundriesFactory Team roles and permissions") - -Once you created the team, you can go to the **Members** section of your FoundriesFactory to invite new members to the team. - -![FoundriesFactory new member](assets/web_board_manager_factory_member.png "FoundriesFactory new member") - -You can type the email addresses of your teammates and they will receive an automatic email with the invitation to join the corresponding team in your FoundriesFactory. - -### FoundriesFactory FIOCTL - -The FoundriesFactory includes a command line tool called [FIOCTL](https://docs.foundries.io/latest/getting-started/install-fioctl/index.html) which allows you to manage your Portenta X8 through your CLI. - -With this tool, you can easily upload containers to a board that is linked to your FoundriesFactory just by stating the FoundriesFactory name, the board name and the app you would like to upload. - -***Learn how to use this tool by checking the dedicated tutorial at [this link](https://docs.arduino.cc/tutorials/portenta-x8/custom-container) or the corresponding [Foundries documentation](https://docs.foundries.io/latest/getting-started/install-fioctl/index.html).*** - -## Pins - -In order to learn how to properly call GPIOs or other peripherals both in the Arduino environment or in Linux, with or without a carrier, you can check the following pinout diagrams: - -* [Portenta X8 pinout](https://docs.arduino.cc/static/019dd9ac3b08f48192dcb1291d37aab9/ABX00049-full-pinout.pdf) -* [Portenta Breakout pinout](https://docs.arduino.cc/static/8d54d1a01d6174ed60fc9698e881ad4c/ASX00031-full-pinout.pdf) -* [Portenta Max Carrier pinout](https://docs.arduino.cc/static/d0bd73b17e97af0fe376b7d518b18660/ABX00043-full-pinout.pdf) -* [Portenta Hat Carrier pinout](https://docs.arduino.cc/resources/pinouts/ASX00049-full-pinout.pdf) - -## Communication - -In this section you will learn how to make your Portenta X8 to communicate with multiple types of sensors or other external devices, leveraging the vast variety of supported interfaces: - -* [SPI](#spi) -* [I2C](#i2c) -* [UART](#uart) -* [Bluetooth®](#bluetooth) - -### SPI - -In this case, a Portenta X8 with Portenta Breakout board is used to connect an external SPI device. - -#### SPI With Linux - -You need to enable SPI support before using SPI devices. - -Open Portenta X8 Shell as explained [here](#working-with-linux). - -```arduino -sudo modprobe spi-dev -``` - -Insert the user password `fio`. - -An upcoming image release for the X8 will load the `spi-dev` modules automatically at boot. In the current version, please create a `/etc/modules-load.d/spi-dev.conf` file with the following content: - -```arduino -spi-dev -``` - -and restart the board. - -```arduino -echo "spi-dev" | sudo tee > /etc/modules-load.d/spi-dev.conf -``` - -```arduino -sudo systemctl reboot -``` - -Add the device you want to communicate within a container in a `docker-compose.yml` file: - -```arduino -services: - my_spi_service: - devices: - - /dev/spi-1 - - /dev/spi-2 - - /dev/spi-3 -``` - -If the Linux user on which the container is running is not `root`, you need to set up the permissions for the user to access the SPI devices. You might add the required comments to an `entrypoint.sh` shell file (to be added to the `Dockerfile` or the `docker-compose.yml` file). - -```arduino -#!/usr/bin/env sh - -# entrypoint.sh example - -chgrp users /dev/spi-* -chmod g+rw /dev/spi-* -usermod -aG users - -# Possible command to execute your application as a non-privileged user with gosu -# Check https://github.com/tianon/gosu for more information -gosu /usr/bin/python my_spi_service.py -``` - -#### SPI Port Mapping - -| Linux | Arduino Portenta Breakout | -|-------|---------------------------| -| 134 | **`SPI1 CK`** | -| 135 | **`SPI1 COPI`** | -| 136 | **`SPI1 CIPO`** | -| 137 | **`SPI1 CS`** | - -#### SPI With Arduino - -The `SPI` object is [mapped](https://github.com/arduino/ArduinoCore-mbed/blob/23e4a5ff8e9c16bece4f0e810acc9760d3dd4462/variants/PORTENTA_X8/pins_arduino.h#L85) as follows on the Portenta Breakout Board and can be deployed as usual: - -| SPI Pin | Arduino Portenta Breakout | -|---------|---------------------------| -| CIPO | Pin 0 (Header GPIO0) | -| COPI | Pin A6 (Header Analog) | -| SCK | Pin A5 (Header Analog) | -| CS | Pin 1 (Header GPIO0) | - -### I2C - -In this case, a Portenta X8 with Portenta Breakout board is used to connect an external I2C device. - -#### I2C With Linux - -You need to enable I2C support before using I2C devices. - -Open Portenta X8 Shell as explained [here](#working-with-linux). - -Thus, execute the following command: - -```arduino -sudo modprobe i2c-dev -``` - -Insert the user password `fio`. - -An upcoming image release for the X8 will load the `i2c-dev` modules automatically at boot. In the current version, please create a `/etc/modules-load.d/i2c-dev.conf` file with the following content: - -```arduino -i2c-dev -``` - -and restart the board. - -```arduino -echo "i2c-dev" | sudo tee > /etc/modules-load.d/i2c-dev.conf -``` - -```arduino -sudo systemctl reboot -``` - -Add the device you want to communicate within a container in a `docker-compose.yml` file: - -```arduino -services: - my_i2c_service: - devices: - - /dev/i2c-1 - - /dev/i2c-2 - - /dev/i2c-3 -``` - -If the Linux user on which the container is running is not `root`, you need to set up the permissions for the user to access the I2C devices. You might add the required comments to an `entrypoint.sh` shell file (to be added to the `Dockerfile` or the `docker-compose.yml` file). - -```arduino -#!/usr/bin/env sh - -# entrypoint.sh example - -chgrp users /dev/i2c-* -chmod g+rw /dev/i2c-* -usermod -aG users - -# Possible command to execute your application as a non-privileged user with gosu -# Check https://github.com/tianon/gosu for more information -gosu /usr/bin/python my_i2c_service.py -``` - -#### I2C Port Mappings - -| Linux | Arduino Portenta Breakout | Notes | -|------------|---------------------------|---------------| -|`/dev/i2c-1`| **`I2C1`** | | -|`/dev/i2c-2`| **`I2C0`** | Recommended | -|`/dev/i2c-3`| **`I2C1`** | | - -#### Examples - -Examples of using SMBus-compatible [libraries](https://github.com/kplindegaard/smbus2): - -```arduino -from smbus2 import SMBus - -# Connect to /dev/i2c-2 -bus = SMBus(2) -b = bus.read_byte_data(80, 0) -print(b) -``` - -Example of using [python-periphery](https://python-periphery.readthedocs.io/en/latest/index.html): - -```arduino -from periphery import I2C - -# Open i2c-0 controller -i2c = I2C("/dev/i2c-2") - -# Read byte at address 0x100 of EEPROM at 0x50 -msgs = [I2C.Message([0x01, 0x00]), I2C.Message([0x00], read=True)] -i2c.transfer(0x50, msgs) -print("0x100: 0x{:02x}".format(msgs[1].data[0])) - -i2c.close() -``` - -#### I2C With Arduino - -The `Wire` object is [mapped](https://github.com/arduino/ArduinoCore-mbed/blob/23e4a5ff8e9c16bece4f0e810acc9760d3dd4462/variants/PORTENTA_X8/pins_arduino.h#L113) to pins `PWM6` (I2C `SCL`) and `PWM8` (I2C `SDA`) on the Portenta Breakout Board and can be deployed as usual. - -Since one of the `I2C` pins is GPIO-multiplexed, you need to detach it from the other GPIO. Just add the following line in the `setup()` definition to have it fully functional for `I2C` operations. - - ```arduino - void setup() { - pinMode(PA_12, INPUT); - } - ``` - -### UART - -In this case, a Portenta X8 with Portenta Breakout board is used to explore UART communication. - -#### UART With Linux - -A standard UART is available as `/dev/ttymxc1` in Linux and is mapped to the **`UART1`** port on the Portenta Breakout. - -### Bluetooth® - -Portenta X8 supports Bluetooth® connectivity just on the Linux side. - -In order to communicate with Bluetooth® devices via the Portenta X8 Shell, you can use the Bluetooth® utility **bluetoothctl**. These are some of the most used commands: - -* `bluetoothctl devices` to list all the available Bluetooth® devices -* `bluetoothctl pair [mac_address]` to pair with a specific device through its MAC address -* `bluetoothctl connect [mac_address]` to connect to a paired device -* `bluetoothctl disconnect [mac_address]` to disconnect from a paired device - -***Do you want to send data from your Nicla to Portenta X8 via BLE? Check [this link](https://github.com/Zalmotek/arduino-environmental-monitoring-with-arduino-pro) to get started.*** - -## Support - -If you encounter any issues or have questions while working with the Portenta X8, we provide various support resources to help you find answers and solutions. - -### Help Center - -Explore our [Help Center](https://support.arduino.cc/hc/en-us), which offers a comprehensive collection of articles and guides for the Portenta X8. The Arduino Help Center is designed to provide in-depth technical assistance and help you make the most of your device. - -- [Portenta Family help center page](https://support.arduino.cc/hc/en-us/sections/360004767859-Portenta-Family) - -### Forum - -Join our community forum to connect with other Portenta X8 users, share your experiences, and ask questions. The forum is an excellent place to learn from others, discuss issues, and discover new ideas and projects related to the Portenta X8. - -- [Portenta X8 category in the Arduino Forum](https://forum.arduino.cc/c/hardware/portenta/portenta-x8/172) - -### Contact Us - -Please get in touch with our support team if you need personalized assistance or have questions not covered by the help and support resources described before. We're happy to help you with any issues or inquiries about the Portenta X8. - -- [Contact us page](https://www.arduino.cc/en/contact-us/) +--- +beta: true +title: '01. Portenta X8 User Manual' +description: 'Get a general overview of Portenta X8 and its features.' +difficulty: intermediate +tags: + - Embedded Linux + - Containers + - Firmware + - Pins + - Connections +author: 'Marta Barbero' +hardware: + - hardware/04.pro/boards/portenta-x8 +software: + - ide-v1 + - ide-v2 + - iot-cloud +--- + + +## Introduction + +Portenta X8 is a powerful, industrial-grade System on Module with Linux OS preloaded onboard, capable of running device-independent software thanks to its modular container architecture. In this user manual, we will go through the foundations of the Portenta X8 to help you understand how the board works and how you can benefit from its advanced features. + +## Required Hardware + +* 1x [Portenta X8](https://store.arduino.cc/products/portenta-x8) board +* 1x USB-C® cable (either USB-C® to USB-A or USB-C® to USB-C®) +* 1x Wi-Fi® Access Point or Ethernet with Internet access + +## Required Software + +* [Arduino IDE 1.8.10+](https://www.arduino.cc/en/software), [Arduino IDE 2](https://www.arduino.cc/en/software), or [Arduino Web Editor](https://create.arduino.cc/editor) +* Latest "Arduino Mbed OS Portenta Boards" Core > 3.0.1 +* Latest Linux image available, check [this section](#portenta-x8-os-image-update) to verify if your Portenta X8 is already updated. + +## Product Overview + +Portenta X8 offers the best of two approaches: flexibility of usage of Linux combined with real-time applications through the Arduino environment. Developers can now execute real-time tasks, while simultaneously performing high-performance processing on Linux cores. +So, let's have a look at its technical specification. + +### Architecture Overview + +Portenta X8 is a powerful, industrial-grade System on Module combining a Yocto Linux distribution with the well-known Arduino environment. + +![Portenta X8 Tech Specs](assets/portenta_x8_call_outs.png "Portenta X8 Tech Specs") + +As you can see, Portenta X8 features two powerful computing units: + +* **NXP® i.MX 8M Mini** Cortex®-A53 quad-core up to 1.8GHz per core + 1x Cortex®-M4 up to 400 MHz. This microprocessor is the one where the Yocto Linux distribution is running together with Docker containers (check [this section](#linux-environment) of this user manual to learn more). + +* **STMicroelectronics STM32H747XI** dual-core Cortex®-M7 up to 480 MHz + M4 32 bit Arm® MCU up to 240 MHz. This microcontroller is the one where the "Arduino Mbed OS Portenta Boards" Core is running. M4 core is accessible and programmable by the user, while M7 is dedicated to establishing and guaranteeing the communication between i.MX 8M Mini and M4 as well as to manage peripherals through RPC. Check [this section](#arduino-environment) of this user manual to learn more. + +The two computing units are responsible for different tasks, which are summarized in the table below. + + | NXP® i.MX 8M Mini | STMicroelectronics STM32H747XI (M4) | + | ------------------------------------------------------- | -------------------------------------------------------------- | + | Running Yocto Linux distribution with Docker containers | Running Arduino sketches with the Mbed OS Portenta Boards Core | + | Dedicated to high level tasks | Dedicated to real-time tasks | + | Manage network connectivity | No direct connection to any network stack | + | Manage network-based buses (e.g. Modbus TCP, etc.) | Manage field buses (e.g. Modbus RTU, CANbus, etc.) | + | Access to peripherals without concurrent access control | Access to peripherals without concurrent access control | + +In addition to the above features, Portenta X8 guarantees security over time. A crypto element (i.e. [NXP® SE050C2](https://www.nxp.com/docs/en/data-sheet/SE050-DATASHEET.pdf)) ensures a secure connection at the hardware level and allows the board to be PSA certified from ARM® (click [here](https://www.psacertified.org/products/portenta-x8/) to learn more). + +Moreover, Portenta X8 can be further customized to get a continuously maintained Linux kernel distribution and to keep security at first by Over-The-Air (OTA) device updates and fleet management. In order to activate these features, you need to create an Arduino Cloud for business account including the so-called **Portenta X8 Board Manager**. Portenta X8 Board Manager has been developed together with [Foundries.io](https://foundries.io/) and allows a user to: + +* Securely maintain Linux distribution inside a FoundriesFactory, i.e. a dedicated workspace where all your Portenta X8 are provisioned and maintained. +* Deploy and update applications packaged into containers, including both containers provided by Arduino or custom containers. +* Get individual provisioning keys for each device. +* Perform secure Over-the-air (OTA) updates to target Portenta X8 devices/fleets. + +***Click [here](https://cloud.arduino.cc/plans#business) to learn more about Arduino Cloud for business and the Portenta X8 Board Manager add-on. Otherwise, check the [dedicated section](#working-with-portenta-x8-board-manager) of this user manual to start working with Portenta X8 Manager.*** + +### Pinout + +The full pinout is available and downloadable as PDF from the link below: +* [Portenta X8 Pinout](https://docs.arduino.cc/static/019dd9ac3b08f48192dcb1291d37aab9/ABX00049-full-pinout.pdf) + +### Datasheet + +The full datasheet is available and downloadable as PDF from the link below: +* [Portenta X8 Datasheet](https://docs.arduino.cc/resources/datasheets/ABX00049-datasheet.pdf) + +### Schematics + +The full schematics are available and downloadable as PDF from the link below: +* [Portenta X8 Schematics](https://docs.arduino.cc/resources/schematics/ABX00049-schematics.pdf) + +### STEP Files + +The full _STEP_ files are available and downloadable from the link below: +* [Portenta X8 STEP files](../../downloads/ABX00049-step.zip) + +### Linux Environment + +As you already know, Portenta X8 is based on a Yocto Linux distribution. + +Before going into the details of Yocto distribution, it is important to understand how embedded Linux works. + +The term **Embedded Linux** is used to define embedded systems based on the Linux Kernel and other open-source components. Over the years, Linux has established itself as the best operating system to be installed on embedded devices. This achievement is due to the fact that Linux is an open-source and completely free operating system. + +An **Embedded Linux** system is composed of the following items: + +* **Bootloader:** The first program executed right after powering the board. It has the task of initializing the hardware and loading the operating system loading the **device tree** and its configuration file into the RAM. The **device tree** is basically a database containing information on the hardware components of the board and it is used to forward information from the bootloader to the Kernel at the hardware level. +* **Linux Kernel:** The core of the operating system. It deals with resource management, scheduling, hardware access and all the low-level operations which the user does not want to worry about. In particular, the Linux Kernel manages all the hardware resources, like CPU, memory and I/Os, and it provides a set of APIs that abstracts those resources allowing the user applications and libraries to be easily deployed. +* **Root Filesystem:** It contains all system programs and utilities, configurations and user data (roughly speaking, the equivalent of the `C:\` drive on Windows). The Root Filesystem can be mounted from a USB stick, SD card or flash memory, being the case of the Portenta X8. + +![Embedded Linux Start-Up](assets/Embedded_Linux_Start.png "Embedded Linux Start-Up") + +#### Linux Yocto Distribution + +In order to install a Linux operating system on a board, you need to decide which packages, applications and libraries you want to use, so basically you need to decide which Linux distribution better suits your needs. As a matter of fact, a Linux distribution is an operating system consisting of the Linux Kernel, GNU tools, additional software and a package manager. It may also include a display server and a desktop environment for using it as a regular desktop operating system. There are more than 300 Linux distributions available in the market, like Ubuntu, Debian, Fedora, Red Hat, etc. + +Portenta X8 is running a [Yocto Linux distribution](https://www.yoctoproject.org/). Yocto is built on the basis of [OpenEmbedded (OE)](http://www.openembedded.org/wiki/Main_Page), which uses [BitBake](https://docs.yoctoproject.org/bitbake/) build to generate a full Linux image. BitBake and OE are combined together to form the Yocto reference project, historically called [Poky](https://www.yoctoproject.org/software-item/poky/). + +In addition, a full selection of metadata is defined to select which tasks to be performed. The following metadata is used in a Yocto project: + +* **Recipes:** They deliver information regarding each package (i.e. author, homepage, license, etc.), recipe version, existing dependencies, source code location and how to retrieve it, configuration settings and target path where the created package will be saved. Files with the `.bb` extension are recipe files. +* **Configuration file:** They contain metadata that define how to perform the build process. These files (with `.conf` file extension) determine the configuration options for the machine, the compiler, the distribution and general and user configurations. They allow you to set the target where you want to create the image and where you want to save the downloaded sources and other particular configurations. +* **Classes:** Class files, which have the extension `.bbclass`, contain common functionalities that can be shared between various recipes within the distribution. When a recipe inherits a class, it also inherits its settings and functions. +* **File append:** With the extension `.bbappend`, File append extends or overwrites information for an existing recipe. + +OpenEmbedded Core contains a recipe layer, classes and a set of associated files, common to all OE-based systems, including Yocto. This set of metadata is in fact maintained by both the Yocto project and the OpenEmbedded project. + +The development environment of the Yocto distribution is made up of various functional areas, as shown in the figure below. + +![Yocto Distribution Architecture](assets/Yocto_Architecture.png "Yocto Distribution Architecture") + +* **Layer:** The layers allow you to separate metadata by differentiating them according to: software, hardware information, metadata concerning distribution and adopted policies. Within each layer, there are the `conf` (with layer-specific configuration files) and `recipes-` directories. To illustrate how to use layers to maintain modularity, consider the example of recipes to support a specific target, which usually resides in a BSP layer. In this scenario, those recipes should be isolated from other recipes and supporting metadata, like a new Graphical User Interface (GUI). You would then have a couple of layers: one for the configurations of the machine and one for the GUI environment. This would allow a specific machine to present special GUI features within the BSP layer, without affecting the recipes inside the GUI layer itself. All of this is possible via an append file. +* **Source file:** To cross-compile any software module, being it a distribution or an application, we must have access to various source files. The latter can be sourced from three different upstream areas: Upstream Project Releases (archived at a specific location), Local Projects (available at a certain local path) and Source Control Managers (like GitHub). +* **Package feeds:** This area contains packages generated by the build system and they will be used later to generate operating system images or Software Development Kits (SDKs). +* **Build System:** The Build System macroblock is the heart of the Yocto distribution. It contains various processes controlled by BitBake, a tool written in Python language. The Build System is responsible for parsing the metadata, from which it extracts the list of tasks to be performed. BitBake checks the software build process by using the recipes and, for each successfully completed task, it writes a *stamp* file in the Build Directory. +* **Images:** They are compressed forms of the Root Filesystem, ready to be installed on the target. BitBake releases multiple lists of images saved into the Build Directory, including *kernel-image*, *root-filesystem-image* and *bootloaders*. +* **SDK:** From the SDK generation process you can get a standard SDK or an extensible SDK. In both cases, the output is an installation script of the SDK, which installs: a cross-development toolchain, a set of libraries and headers files; generating an environment setup script. The toolchain can be considered as part of the build system, while libraries and headers as target parts, since they are generated for the target hardware. + +***If you want to learn more about how to work with Yocto Distribution on your Portenta X8, please check the [dedicated section](#working-with-linux) of this user manual.*** + +#### Docker Containers + +With Portenta X8 it is possible to deploy device-independent software thanks to its modular container architecture. + +To explain how containers work, imagine the classic containers that transport goods around the world by ship. These containers "blocks" can be moved in multiple ways and to multiple locations: from a ship to a truck or from a truck to a warehouse. The same thing happens in computer science: you can consider an application, package it with everything needed to make it work and take it out of the environment in which it runs. This is a container! + +![Virtual Machine vs Containers](assets/Virtual_Machine_Containers.png "Virtual Machine vs Containers") + +On one side, classic virtualization is able to virtualize an entire machine; on the other side, containers are able to virtualize even just a small subset of resources of the same machine. + +Traditional virtual machines share hardware resources, but the operating system and applications are on the host. This translates into long start-up times (it takes minutes) and considerable use of resources (several Gigabytes). Containers, on the other hand, share the operating system as well as the infrastructure with the host. This means that start-up times are short (a few seconds) and dimensions are significantly reduced (even a few KB). + +Being able to "pack" applications and distribute them in any environment leads to a series of advantages in terms of: performance, time, costs and integration. As a matter of fact, containers can be an interesting way to simplify infrastructure complexity, provide maximum performance and optimize costs by eliminating virtual machine licenses. + +But let's see in detail some of the advantages of this technology: + +* **Simple development, test and deployment:** The decoupling between applications and the environments in which they run allows you to deploy a container everywhere: on a public Cloud, in a private data center or on a PC. Whatever the chosen environment, the container will always remain the same. This means that even applications updates can be released easily without involving the operating system hosting the container, or all the other containers in use. In a nutshell, if you have to update an application, it will not be necessary to restart the whole machine. +* **Control version:** In the case that the deployment of an update was not successful, thanks to the containers architecture it is easier to roll back and to have the previous version working again in few time. +* **Isolation and security:** In containers, applications and resources are isolated. This means that if an application has to be deleted, it will be sufficient to remove its container and the operation will delete everything that concerns it, such as temporary or configuration files. At the same time, since containers are isolated, each of them "sees" only their own processes, while the others will remain unknown. Security first! +* **Granularity:** It is possible to containerize not only an entire application, but also a single component. In this way, resources can be reduced into micro-services, guaranteeing greater control and improved performance. + +At this point, it is worth mentioning that Portenta X8 containers are based on [Docker](https://www.docker.com/). Docker is an open-source software platform, developed by the company with the same name, which allows you to create, test and distribute containerized applications. The goal of Docker is therefore to facilitate the creation and management of containers, in order to distribute the resources required for an application in any environment, always keeping the executed code under control. Docker containers can run everywhere, in on-premises data centers or in public and private Clouds. Thanks to the virtualization at the operating system level, typical of this technology, Docker allows you to natively create containers in Linux environments. + +To understand the purpose of a platform like Docker, it is sufficient to focus on the differences between Docker containers and the more generic Linux containers. Docker mainly serves to simplify the construction and management of containers compared to the standard approach. Although it is based on the same technology, i.e. the **LXC (Linux Container)**, Docker guarantees a much more advanced experience than the standard implementation. LXC basically permits a light virtualization, independent from the underlying hardware, but basically cumbersome to implement. In other words, basic LXC presents critical issues in terms of user experience. + +Docker specifically facilitates the interface between the container and the end user, for example through a series of automated procedures that guide the user step-by-step during container development, with correct versioning of all the generated images. Docker also simplifies the management of the applications to be run on the different containers, to make the overall orchestration more practical and faster, especially when dealing with applications made of a very large number of components. + +The reasons for using Docker are therefore closely connected to the usefulness of the containers themselves, now indispensable tools for developing software based on a microservices architecture. In particular, this applies to the DevOps methodologies used for the development of native Cloud applications, which provide for continuous integration / continuous deployment cycles, to guarantee the end user always and only the most up-to-date version. + +The technology behind containers, and therefore of Docker itself, can be extremely summarized in three key terms: + +* **Builder:** tools used to create containers. In the case of Docker, this tool corresponds to the **Dockerfile**. +* **Engine:** it is the engine that allows you to run containers, as in the case of **Docker command** and **Docker Daemon**. +* **Orchestration:** technology used to manage containers, with full visibility of their execution status (tasks, servers / VMs, etc.), as in the case of **Docker Swarm** or the famous **Kubernetes**. + +The fundamental advantage of a container is that it makes both the application and the execution environment configuration available. This allows you to manage the various images as instances, without having to install the application each time, as happens in the case of traditional procedures. + +As already mentioned, containers running with Docker are absolutely isolated and independent from each other and it is therefore possible to have complete control over their visibility and management, without any constraints whatsoever. The advantages in terms of IT security are obvious: if a container is corrupted, for example by exploiting a vulnerability of the application it is running, this event does not affect the functioning of the other running containers. Isolation prevents, or at least makes it more difficult, the propagation of the threat within the host system, allowing Docker to terminate the corrupted instance and restart it in completely safe conditions, as well as having traces of what happened in the system logs. + +Thus, Docker is able to ensure application security without sacrificing anything in terms of portability, guaranteeing full operation both on-premise and in the Cloud, using open and closed APIs to respond optimally to any business need. + +As shown in the image below, Docker needs to be installed in the host operating system and it is composed of three main items: + +* ***docker-daemon:*** It is a service that runs on the host operating system and leverages Linux Kernel features to work. It allows the user to create a container and run it, starting from an image developed by the user or downloaded from a registry. +* ***docker-cli:*** It is a command-line tool that allows the user to properly communicate with the *docker-daemon*. As a matter of fact, any operation on images or containers always starts via *docker-cli*. When Docker is installed, both the *docker-daemon* and the *docker-cli* are installed together and any operation always takes place via *docker-cli*, even if managed via *docker-daemon*. +* ***docker-hub:*** It is a [Docker image repository](https://hub.docker.com/) from which it is possible to download all the images of interest and run them to create containers. Alternatively, a user can create the needed images through a *dockerfile*, using the repository only to download the required base images (like Linux-alpine). + +![Docker host](assets/Docker_host.png "Docker host vs client") + +Now it is time to highlight better which is the difference between an image and a container. In programming languages, an image can be assimilated to a class, while a container to an object. It is possible to create a container starting from an image and then run it, stop it or pause it. When it is no longer needed, it can be deleted without removing the corresponding image. + +As already mentioned, images can be downloaded from a registry like Docker or they can be defined through a *dockerfile*. A *dockerfile* is a text file that contains all the commands (*FROM, COPY, CMD, ENTRYPOINT, etc.*) that a user can call from the command line to build various image layers. The *dockerfile* represents a definition of the image but not the final image, which can be built through `docker build` command. + +A Docker image is made up of many layers and includes everything needed to configure a container. In particular, all the layers an image contains are read-only and, consequently, the image itself is also read-only. In this way, it is possible to launch the image several times always creating the same container. When the container is created, a thin writable layer will be placed on top of the existing image layers and will be prepared to execute the main process command. This last writable layer will contain any changes made when the container is running, but will not affect the original underlying image. When the container is deleted, this thin writable layer is removed. + +An important thing to keep in mind is that, even if Docker shares the Linux Kernel with the underlying host, it is always necessary to add a full operating system or a Linux distribution as the first layer. + +![Images and containers](assets/images_containers.png "Images vs containers") + +On the other hand, a container represents a process, which runs starting from an image. The important thing to understand is that a container has a lifecycle and, for this reason, it can reach different states depending on whether it is running or not. The lifecycle of a Container consists of the following states: + +* **Created:** This is the first state of the container lifecycle and it occurs after an image has been created with the command `docker create`. A writable thin layer is created on the specified image and prepared to execute the main process commands. Consider that in this state the container is created but not started. +* **Running:** This is the state in which the container is actually running. A container created through `docker create` or interrupted can be restarted through the command `docker start`. +* **Paused:** A running container can be paused through the command `docker pause`. As a consequence, all the processes of the specified container are suspended or blocked. When a container is paused, both the file system and the RAM are not affected. +* **Stopped:** A stopped container does not have any running process. When a container is stopped through the command `docker stop`, the file system is not affected, but the RAM gets deleted. This is the main difference between stopped and paused states. +* **Deleted:** A container can be removed through the command `docker rm`. This implies the complete cancellation of all the data associated with the container, including file system, volume and network mapping. + +Let's now have a look at the main Docker commands. The full list can be found [here](https://docs.docker.com/engine/reference/commandline/docker/). +Through the command `docker image ls` it is possible to check all the images installed on your Portenta. These images may have been downloaded from a repository using the command `docker pull XXX` or created from scratch with the command `docker build XXX` starting from a *dockerfile*. + +Through the command `docker run XXX`, it is possible to run the image downloaded from the repository. But, if a user tries to launch a container through the command `docker run XXX` for a container whose image has not been downloaded yet, first the image will be downloaded and then the container will start running. + +To verify whether a container is running as expected, it is possible to launch the command `docker ps`. + +So, to summarize, Docker is a very powerful technology that allows a user to avoid installing an infinite number of servers and services on a machine. Furthermore, since it runs in an isolated environment makes it possible to move the container or rather the image to another machine or to a production server without friction. + +***If you want to learn more about how to work with Docker containers on your Portenta X8, please check the [dedicated section](#working-with-linux) of this user manual.*** + +### Arduino Environment + +In addition to what has been addressed before, the user has the possibility to upload sketches on **M4 core** of **STM32H7** through the **Arduino IDE 1.8.10 or above**. + +In order to do that, it is sufficient to open the Arduino IDE, make sure you have selected the Portenta X8 in the board selector and start writing your sketch. + +***Have a look at [this section](#portenta-x8-with-arduino-ide) of this user manual if you would like to start uploading your sketch on Portenta X8.*** + +From a user perspective, the process may appear to be the same as for other Arduino boards, but there are major differences in what happens behind the scenes: the Portenta X8 includes a service that waits for a sketch to be uploaded to a folder. This service is called `monitor-m4-elf-file.service`: it monitors the directory `/tmp/arduino/` looking for an updated version of the `m4-user-sketch.elf` and, each time it detects a new file, it proceeds to flash the M4 with the new sketch using `openOCD` (check [openOCD website](https://openocd.org/doc/html/About.html) if you want to learn more). + +### Communication Between Linux And Arduino + +The two processors inside Portenta X8 need a communication mechanism to exchange data with one another. The communication mechanism that is used is called **RPC (Remote Procedure Call)**. + +The expression RPC refers to the activation of a "procedure" or "function" by a program on a computer other than the one on which the program itself is executed. In other words, RPC allows a program to execute procedures "remotely" on "remote" computers (but accessible through a network). + +Essential to the concept of RPC is also the idea of transparency: the remote procedure call must in fact be performed in a way similar to that of the traditional "local" procedure call; the details of the network communication must therefore be "hidden" (i.e. made transparent) for the user. + +The RPC paradigm is particularly suitable for distributed computing based on the client-server model: the "call procedure" corresponds to the "request" sent by the "client" and the "return value" of the procedure corresponds to the "response" sent by the "server". In fact, distributed computing uses the resources of several computers connected to each other in a network (usually via the Internet) to solve large-scale computational problems. + +Although the ultimate goal of the RPC paradigm is to provide a remote procedure call mechanism whose semantics is essentially equivalent to that of the local procedure call (hence the aforementioned transparency of the mechanism), this equivalence is never fully achieved, due to difficulties that can arise in network communication (always subjected to failure). + +Since there is no single obviously "right" way to handle these complications, RPC mechanisms can differ subtly in the exact semantics of the remote call. Some mechanisms, for example, have "at most once" semantics: in other words, a remote procedure call can fail (i.e. not be executed) but it is guaranteed not to result in multiple activations. The opposite approach is represented by the "at least once" semantics, which guarantees that the procedure is called at least once (it could therefore happen that it is activated several times). + +As a consequence, there are multiple types of RPC implementations. In the case of Portenta X8, **MessagePack-RPC** is used (check the [library repository](https://github.com/msgpack-rpc/msgpack-rpc) to get more details). It is an RPC implementation that uses MessagePack as a serialization protocol, i.e. data exchange is encoded in MsgPack format. + +It is transported over different protocols: + +* OpenAMP via Shared Memory +* SPI +* Linux Char Device +* TCP/IP + +![Linux Arduino RPC](assets/linux_arduino_RPC.png "Linux Arduino RPC") + +As you can see in the image above, the **M7 core** of **STM32H7** is used to facilitate the communication between the Linux and the Arduino environments. If an Arduino sketch is running on the **M4 core**, the **M7 core** will hand over any data/request between the M4 core and the Linux side. Due to this hardware design, traditional dual-core processing is not supported in the Portenta X8. + +At the same time, on the Linux side, there is a service that takes care of sending data between the two worlds, `m4-proxy`. + +So, the communication between Arduino and Linux side will proceed as follow (check the image below): + +* A program registers as the RPC server on port X for a list of procedures that the M4 may call +* `m4-proxy` will forward the calls from the M4 to the registered program/port + +![RPC M4 proxy](assets/m4-proxy.png "RPC M4 proxy") + +***If you want to learn more about how to work with RPC on your Portenta X8, please check the [dedicated section](#working-with-arduino) of this user manual.*** + +## Portenta X8 OS Image Update + +It is recommended to check every now and then if your Portenta X8 image version is up to date, in order to have the latest security updates. + +In the next sections, four major ways to update your Portenta X8 are described: + +* Update for OS release V.399 +* Update through Out-of-the-box experience (available for OS release XXXX or newer) +* Update through Portenta X8 Manager in your Arduino Cloud for Business account (available for all OS releases) +* Update using `uuu` tool (compatible with custom images) + +### Check Portenta X8 OS Release + +In order to verify which OS release is flashed on your Portenta X8, you need to connect to your board through **ADB**, as explained in [this section](#working-with-linux) of this user manual. + +At this point, you can type `cat /etc/os-release` in your command line window to get the OS release currently running on your device. + +![Get OS release](assets/adb-shell-os-release.png "Get OS Release") + +As shown in the image above, the OS release of this Portenta X8 corresponds to `IMAGE_VERSION=569`. + +### Update For OS Release V.399 + +If your Portenta X8 is flashed with the OS release V.399 and you have a carrier compatible with Portenta X8 (like Portenta Breakout), we recommend you to update it to the latest image release by following [this tutorial](https://docs.arduino.cc/tutorials/portenta-x8/image-flashing#flashing-mode-with-carrier). + +Otherwise, you can also open a new Command Line window and connect to your Portenta X8 as explained [here](#working-with-linux). At this point, verify that your Portenta X8 is connected to the Internet and type the following commands: + +```arduino +wget https://downloads.arduino.cc/portentax8image/399-install-update +``` + +```arduino +chmod +x 399-install-update +``` + +```arduino +sudo ./399-install-update +``` + +Remember that the default password for admin access is `fio`. + +Now you need to reboot the board by pressing its pushbutton for around 10 seconds. After that, connect again to your Portenta X8 through the Command Line and type the following commands: + +```arduino +wget https://downloads.arduino.cc/portentax8image/399-finalize-update +``` + +```arduino +chmod +x 399-finalize-update +``` + +```arduino +sudo ./399-finalize-update +``` + +These commands will make your V.399 compatible with [aklite-offline](https://docs.foundries.io/latest/user-guide/offline-update/offline-update.html) tool and will allow you to update your Portenta X8 to the latest image version Arduino released at that point in time. Arduino provides this tool for free for any Portenta X8 user to enable offline secure updates to all devices, even if those devices are not connected to any FoundriesFactory. + +After the update process is finalized, your Portenta X8 will immediately start running the latest OS release. + +### Update Through Out-Of-The-Box Experience + +Leverage the integrated Out-of-the-box experience to update your Portenta X8 to the latest release. + +***Warning: The Out-of-the-box update feature is not a complete Over-The-Air (OTA) update, it allows the user to update only Portenta X8 default image and containers. It will overwrite any custom container application. Thus, it is recommended to make a local copy of your containers before updating your Portenta X8.*** + +Open your Out-of-the-box as explained in [this section](#first-use-of-your-portenta-x8). + +![Out-of-the-box homepage](assets/OOTB_homepage.png "Out-of-the-box homepage") + +Click on **CHECK FOR UPDATES** in the lower right corner. + +At this point, you have to select whether you would like to proceed with the update. If yes, click on **UPDATE**. + +![Proceed with update](assets/OOTB_update_select.png "Proceed with update") + +During the update, do not turn off your Portenta X8 or disconnect it from the network. This process may take few minutes. + +![Successful update](assets/OOTB-succesful-OS-update.png "Successful update") + +Once the update is finished, your Portenta X8 will automatically restart with the new Linux image in place. + +At this point, if you would to continue to use your Out-of-the-box, you can open a new command line window and launch again the command `adb forward tcp:8080 tcp:80`. Now open your browser, go to [http://localhost:8080](http://localhost:8080) and the same Out-of-the-box dashboard will appear. + +#### Troubleshooting + +If something gets wrong during the update, you still have the possibility to manually flash your Portenta X8 with the latest Linux image provided at [this link](https://github.com/arduino/lmp-manifest/releases). You can follow [this section](#update-using-uuu-tool) to learn to use `uuu` tool and update your device manually with the latest OS Image version. Follow [this dedicated tutorial](https://docs.arduino.cc/tutorials/portenta-x8/image-flashing) to learn how to flash your device manually. + +### Update With Portenta X8 Board Manager + +If you have an *Arduino Cloud for business* account with the Portenta X8 Manager, check if the target installed on your Portenta X8 is the latest one available in your FoundriesFactory. + +![FoundriesFactory device overview](assets/web_board_manager_factory_device-overview.png "FoundriesFactory device overview") + +If this is not the case, you can update your device using FoundriesFactory **Waves** functionality. Check [this tutorial](https://docs.arduino.cc/tutorials/portenta-x8/waves-fleet-managment) to read the complete instructions. More information about Waves can be found in the official Foundries documentation at [this link](https://docs.foundries.io/latest/reference-manual/factory/fioctl/fioctl_waves.html?highlight=wave). + +### Update Using `uuu` Tool + +An alternative method to updating the Portenta X8 with the latest OS image is to use the `uuu` command (`uuu_mac` command in case you are using MAC OS). This flash method is helpful if you have built a custom image or desire a more manual approach. Nonetheless, you will need to prepare the OS image files and the board must be set into programming mode for this flashing process. + +***To learn more about creating a custom image for Portenta X8, please check out [How To Build a Custom Image for Your Portenta X8](https://docs.arduino.cc/tutorials/portenta-x8/image-building) tutorial.*** + +You will need to download the latest OS image file via [Arduino Download repository](https://downloads.arduino.cc/portentax8image/image-latest.tar.gz) and extract the files in a desired directory. The structure should be similar as follows after also extracting `mfgtool-files-portenta-x8.tar.gz` and `lmp-partner-arduino-image-portenta-x8.wic.gz` that came within the original compressed file: + +``` +Unzipped folder +├── mfgtool-files-portenta-x8/ +├── imx-boot-portenta-x8 +├── lmp-partner-arduino-image-portenta-x8.wic +├── lmp-partner-arduino-image-portenta-x8.wic.gz **(Compressed)** +├── mfgtool-files-portenta-x8.tar.gz **(Compressed)** +├── sit-portenta-x8.bin +└── u-boot-portenta-x8.itb +``` + +#### Set Flashing Mode with Carrier + +The Portenta X8 can be set into programming mode by using a carrier platform, such as Max Carrier, Breakout, or Hat Carrier, which provides DIP switches for convenient access; or using a few more lines of command with barebone Portenta X8 via ADB. + +If you plan to use a carrier, please check the carrier's configuration to be paired with Portenta X8. + +For the **Portenta Max Carrier**, set the `BOOT SEL` and `BOOT` DIP switches to ON position as depicted in the figure: + +![Portenta Max Carrier DIP switches](assets/max-carrier-dip-switches.png) + +Upon executing the `uuu` tool and ensuring the DIP switches are correctly configured, the Portenta Max Carrier will automatically start the flashing operation for the Portenta X8. + +For the **Portenta Breakout**, the `BT_SEL` and `BOOT` DIP switches should be set to the ON position, as illustrated in the figure: + +![Portenta Breakout DIP switches](assets/breakout-dip-switches.png) + +After running the `uuu` tool, perform a long press on the `ON` button of the Portenta Breakout to begin the flashing process. This action enables the tool to identify and connect with the device, continuing with the flashing operation. + +For the **Portenta Hat Carrier**, the `BTSEL` DIP switch must be set to the ON position, as depicted in the figure below: + +![Portenta Hat Carrier DIP switches](assets/hatCarrier-dip-switches.png) + +The `ETH CENTER TAP` DIP switch position does not affect the flashing mode state for the Portenta Hat Carrier. + +Like with the Portenta Max Carrier, once the `uuu` tool is run and starts searching for the device, the flashing process will commence. + +#### Set Flashing Mode without Carrier + +If you decide to flash Portenta X8 without using the carrier, use the following command sequence inside the Portenta X8's terminal via ADB while you are in the root environment with root permission to reset Portenta X8's bootloader sector: + +```arduino +echo 0 > /sys/block/mmcblk2boot0/force_ro +``` + +```arduino +dd if=/dev/zero of=/dev/mmcblk2boot0 bs=1024 count=4096 && sync +``` + +```arduino +echo 0 > /sys/block/mmcblk2boot1/force_ro +``` + +```arduino +dd if=/dev/zero of=/dev/mmcblk2boot1 bs=1024 count=4096 && sync +``` + +#### Flashing the Portenta X8 Using `uuu` Command + +Now that we have the Portenta X8 in programming mode, we need to flash the OS image. Within the previously described OS image file structure, you need to navigate to `mfgtool-files-portenta-x8` directory. Inside the directory, you will find the `uuu` executable and its components. Here, you will open a terminal and run the following command: + +``` +uuu full_image.uuu +``` + +If Portenta X8 is to be flashed without a carrier, you will want to execute the command **first** to let it search for the board. Subsequently, you will recycle the power source for Portenta X8 by unplugging and reconnecting the USB-C® cable. It will let the board begin its boot sequence, allowing it to enter programming mode as set with the defaulted internal bootloader. When the active `uuu` instance detects board has entered programming mode, it will continue with its flashing process. + +Once the flashing operation finishes, you will be greeted with a similar message in the terminal as the following figure: + +![Successful uuu flashing operation](assets/uuu-flashing-success.png) + +This applies to both flashing scenarios. If you have the carrier attached and decide to continue using docked with the platform, you must reset the DIP switch positions for either `BOOT SEL`, `BTSEL`, or `BT_SEL` and `BOOT` to OFF state. Reconnect the board and wait approximately 10 seconds until the Blue LED blinks, confirming the boot was successful. + +In case the Portenta X8 was flashed barebone, you will just need to recycle the power and should be ready with the latest OS image. + +***For more in-depth tutorial for flashing Portenta X8, please check out [How To Flash Your Portenta X8](https://docs.arduino.cc/tutorials/portenta-x8/image-flashing) tutorial.*** + +## First Use Of Your Portenta X8 + +You can now start interacting with your Portenta X8. Portenta X8 comes with an embedded Out-of-the-box experience that will guide you step-by-step in the configuration of your board. + +### Power The Board + +Connect the Portenta X8 to your PC via a USB-C® cable (either USB-C® to USB-A or USB-C® to USB-C®). + +Once connected, you will see the Portenta X8 LEDs start blinking. Portenta X8 features two LEDs, a Power LED and a Status LED, which can blink in parallel. + +![Portenta X8 LEDs](assets/portenta_x8_leds.png "Portenta X8 LEDs") + +The table below describes LEDs meaning and functionalities. + + | LED Type | Colour | Meaning | + | ------------ | ------------ | ------------------------------------------------| + | Power LED | Red | Power ON | + | Status LED | White | OS booting in progress | + | Status LED | Blue | Linux Kernel running | + | Status LED | Green | Board connected to the Internet | + | Status LED | Red | STM32H7 LED, blinking when triggered in the IDE | + +### Out-Of-The-Box Experience + +***It is recommended to have your Portenta X8 with the latest OS version. Check [this section](#portenta-x8-os-image-update) to learn how to have your Portenta X8 up-to-date.*** + +Once the Portenta X8 is correctly powered up, you can start interacting with it. + +In order to do that, you have the possibility to connect to your Portenta X8 through [**ADB**](https://developer.android.com/studio/command-line/adb). Android Debug Bridge (ADB) is a tool included in the SDK software (Software Development Kit) and used, inter alia, to make an Android device and a computer to communicate with each other. + +In the case of the Portenta X8, ADB allows to establish a reliable communication between Portenta X8 and a command-line interface of a computer. In order to check if you have already installed ADB on your computer, you have to verify you installed the latest **Mbed OS Portenta Core** from the IDE. Portenta core contains ADB in it. + +***If you need to install ADB, you can also download the right tool for your Operating System directly from the [official Android website](https://developer.android.com/studio/releases/platform-tools).*** + +At this point, you can open your terminal window and look for ADB inside the directory **Arduino15/packages/arduino/tools/adb/32.0.0**. + +***The Arduino15 folder may have a different location depending on the Operating System you are using. Check [this article](https://support.arduino.cc/hc/en-us/articles/360018448279-Open-the-Arduino15-folder) to learn where your Arduino15 folder is located.*** + +To check if ADB is working correctly, you can type `adb devices`. Your Portenta X8 will be listed there. + +![Connection with ADB](assets/adb-connection.png "Connection with ADB") + +To start the Out-of-the-box experience, you can continue typing in your terminal `adb forward tcp:8080 tcp:80`. With this command, ADB allows to forward the requests of the `8080 TCP-IP port` of your computer to the `80 TCP-IP port` of your device, that for this case it is the device with the name _Portenta X8_. + +![ADB forward command](assets/adb-tcp-port.png "ADB forward command") + +Now you can open your browser, go to [http://localhost:8080](http://localhost:8080) and the same Out-of-the-box dashboard will appear to allow you to configure your Portenta X8. + +![Out-of-the-box Homepage](assets/OOTB_homepage.png "Out-of-the-box Homepage") + +#### Portenta X8 Out-Of-The-Box Homepage + +This web page is hosted on the Portenta X8 and allows a user to: + +- Get board details +- [Configure Portenta X8 Wi-Fi®](#wi-fi-configuration) +- [Interact with the board through the embedded Python® Alpine Shell](#portenta-x8-with-python-alpine-shell) +- [Provision your device to Arduino Cloud](#portenta-x8-with-arduino-cloud) +- Manage the Linux distribution with the dedicated [Portenta X8 Board Manager](#portenta-x8-board-manager) + +#### Wi-Fi® Configuration + +Click **Wi-Fi® Settings** to start configuring your network connectivity. Otherwise, you can also connect your Portenta X8 to the Internet through an Ethernet cable, using a USB-C® hub with an RJ45 port or a Portenta Carrier. In this tutorial, Wi-Fi® connectivity will be used. + +![Out-of-the-box Wi-Fi® Settings](assets/OOTB_homepage_Wifi.png "Out-of-the-box Wi-Fi® Settings") + +Select your Wi-Fi® SSID. You can either select a network from the available list or insert your SSID manually. + +![Out-of-the-box Wi-Fi® SSID set-up](assets/OOTB_wifi_selection.png "Out-of-the-box Wi-Fi® SSID set-up") + +Type your Wi-Fi® password. + +![Out-of-the-box Wi-Fi® password set-up](assets/OOTB_wifi_SSID.png "Out-of-the-box Wi-Fi® password set-up") + +Once it is connected, you will get a notification confirming your Portenta X8 is now connected to the selected network. + +Moreover, you can check the network you are connected to in the bottom left section of this dashboard. + +![Out-of-the-box Wi-Fi® connection successful](assets/OOTB_wifi_connected.png "Out-of-the-box Wi-Fi® connection successful") + +Now you can click **OK** and you will be redirected to the Out-of-the-box homepage shown below. + +![Out-of-the-box Homepage](assets/OOTB_homepage.png "Out-of-the-box Homepage") + +***You can change your network by clicking on the Wi-Fi® Settings button and repeat the steps from above.*** + +#### Portenta X8 with Python Alpine Shell + +Click the **Shell** button to start using your Portenta X8 with Python-Alpine. + +![Out-of-the-box Shell button](assets/OOTB_homepage_shell.png "Out-of-the-box Shell button") + +This shell is running in a Python-Alpine container embedded in Portenta X8. In this shell, you will find multiple examples under the directory `/root/examples`. Additionally, you can either add your own package through the command `apk add ` or start exploring the packages available online at [this link]( https://pkgs.alpinelinux.org/packages). + +![Out-of-the-box Python-Alpine Shell](assets/OOTB_alpine_shell.png "Out-of-the-box Python-Alpine Shell") + +#### Portenta X8 with Arduino Cloud + +***Note: this is an optional step. The Portenta X8 can be also used with a local IDE without the need for any internet connection.*** + +Making Portenta X8 compatible with Arduino Cloud means opening a wide range of new applications. This compatibility is guaranteed by a brand-new Python container, which includes a dedicated [Arduino IoT Cloud Python library](https://github.com/arduino/arduino-iot-cloud-py). Through Arduino Cloud APIs, the Python container ensures full interaction and simple porting of any Python developed application in the Arduino Cloud. + +***Check all the available Arduino Cloud plans [here](https://cloud.arduino.cc/plans#business) and create your Arduino Cloud account in a couple of steps (see the dedicated documentation at [this link](https://docs.arduino.cc/arduino-cloud/)).*** + +With the Out-of-the-box experience, your Portenta X8 can be securely self-provisioned in Arduino Cloud, you just need to create API keys and the Python container running on X8 will do the rest. When provisioned, you can start directly interacting with an example Thing and Dashboard that will be automatically generated for you to guide you step-by-step in this new journey. + +Click the **Arduino Cloud** button to start provisioning your Portenta X8 in Arduino Cloud. + +![Out-of-the-box Arduino Cloud](assets/OOTB_homepage_cloud.png "Out-of-the-box Arduino Cloud") + +Start setting up the device name for your Portenta X8 (in this case *portenta-x8-test*) and click on **CONTINUE**. The same device name will be used and visualized into your Arduino Cloud space, but you can freely change it in the future. + +![Out-of-the-box Arduino Cloud Device Name](assets/OOTB_cloud_device_name.png "Out-of-the-box Arduino Cloud Device Name") + +At this point, you will be asked to insert your API Key credentials and Organization ID. Organization ID is optional and should be filled in only in case you are using a Shared Space in Arduino Cloud for Business. + +![Out-of-the-box Arduino Cloud API Keys](assets/OOTB_cloud_generate_API.png "Out-of-the-box Arduino Cloud API Keys") + +In order to get API keys, you need to log into your Arduino Cloud account and select the Space you would like your X8 to be provisioned into. + +Thus, click on **GENERATE API KEY** in your Out-of-the-box dashboard. A new window will open in your web browser to allow you to login to your Arduino Cloud space. + +***If you want to learn more about what API keys are and how they work, please take a look at the dedicated documentation available at [this link](https://docs.arduino.cc/arduino-cloud/getting-started/arduino-iot-api).*** + +![Arduino Cloud Login](assets/web_Cloud_login.png "Arduino Cloud Login") + +Click on **SIGN IN**. If you do not have an Arduino Cloud account yet, create a new one from the same webpage. + +Sign in to your Arduino Cloud account by adding your credentials, i.e. Username/email and Password. + +![Arduino Cloud Sign in](assets/web_cloud_signin.png "Arduino Cloud Sign in") + +You are now logged into your Arduino Cloud space. Go on by clicking on **API keys** found within the account banner located at the top right corner. + +![Arduino Cloud Homepage](assets/web_cloud_homepage.png "Arduino Cloud Homepage") + +It is time to generate your API keys. Click on **CREATE API KEY** in the upper right-hand corner. + +![Arduino Cloud New API Key](assets/web_cloud_new_api.png "Arduino Cloud New API Key") + +Define a name for your API key, in this case *portenta-x8-test-API*, and click on **CREATE**. These API Keys are personal and visible just from your account. + +![Arduino Cloud API Key name](assets/web_cloud_API_name.png "Arduino Cloud API Key name") + +At this point, your API key has been created. Save the correspondent credentials in a safe storage space by clicking on **download the PDF**. + +Keep this file safely stored, your API credentials cannot be recovered otherwise. If you lose it, you will have to generate new API keys by repeating the above procedure. + +![Arduino Cloud API Key](assets/web_cloud_API_key.png "Arduino Cloud API Key") + +The PDF file will look like the image below and it will include the credentials you need to copy and paste into the Out-of-the-box page. + +![Arduino Cloud API Key PDF](assets/web_cloud_API_key_PDF.png "Arduino Cloud API Key PDF") + +Thus, copy the **Client ID** and the **Client Secret** credentials and paste them into your Out-of-the-box dashboard as shown below. + +![Out-of-the-box with API Keys](assets/OOTB_cloud_API_copy.png "Out-of-the-box with API Keys") + +If you are using an Arduino Cloud for Business account with Shared Spaces, you need to add also the Organization ID you would like your Portenta X8 to be provisioned into by clicking on **ADD ORGANIZATION**. + +![Out-of-the-box successful Cloud provisioning](assets/OOTB_cloud_success.png "Out-of-the-box successful Cloud provisioning") + +In order to recover the Organization ID, known as Space ID, of your Shared Space on Arduino Cloud for Business, open your Arduino Cloud homepage and navigate to **Space Settings > General** in the sidebar on the left. + +![Space ID on Cloud Settings](assets/shared-space-settings.png "Space ID on Cloud Settings") + +At this point, you can copy the **Space ID** of your Shared Space and paste it into your Out-of-the-box dashboard together with your API keys. + +![API keys and Organization ID](assets/OOTB_cloud_organization_ID.png "API keys and Organization ID") + +Click on **SETUP DEVICE** and you are ready to go, your Portenta X8 is now provisioned into your Arduino Cloud space. + +![Out-of-the-box successful Cloud provisioning](assets/OOTB_cloud_success.png "Out-of-the-box successful Cloud provisioning") + +Once provisioned, the Portenta X8 will be automatically linked to an example [Thing](https://create.arduino.cc/iot/things) and [Dashboard](https://create.arduino.cc/iot/dashboards). You can freely check them by clicking on the corresponding links embedded in the Out-of-the-box. + +![Portenta X8 example Thing](assets/cloud_thing_created.png "Portenta X8 example Thing") + +As already said, Arduino provides you with an example dashboard that will automatically set up and be visible live after your Portenta X8 has been provisioned. In order to make this dashboard to automatically update its data, you need to go back to your Out-of-the-box and launch the example. + +To do so, it is sufficient to copy the shown code `python3 examples/arduino_iot_cloud_example.py` and click on **Launch Example**. An Alpine-Python shell will open and you will have to paste the previous code here to launch the example. + +![Launching dashboard example](assets/OOTB_example_dashboard_launch.png "Launching dashboard example") + +Now you can navigate to your dashboard [here](https://create.arduino.cc/iot/dashboards) to see your Portenta X8 LED blinking as well as the live temperature inside the microprocessor. + +![Portenta X8 dashboard working](assets/cloud_dashboard_working.png "Portenta X8 dashboard working") + +***If you face any issues during the provisioning of your Portenta X8, feel free to repeat the procedure above.*** +***If you would like to customize your Portenta X8 Things/Dashboards with your own data, check [this section](#working-with-arduino-cloud) of the user manual.*** + +#### Portenta X8 Board Manager + +***Note: this is an optional step. Although the Portenta X8 Board manager opens a wide range of possibilities that are important for business applications, the Portenta X8 can be used for free without the need of any additional paid license*** + +Now you can start connecting your Portenta X8 to the Portenta X8 Board Manager. To enjoy this feature, you need an Arduino Cloud for business account. + +Check the Arduino Cloud for business plan with Portenta X8 Manager [here](https://cloud.arduino.cc/plans#business) and create your Arduino Cloud account in a couple of steps (see the dedicated documentation at [this link](https://docs.arduino.cc/arduino-cloud/)). + +When your Arduino Cloud for business account is correctly set up, log into it [here](https://cloud.arduino.cc/home/) and click on **Portenta X8 Board Manager**. The feature is located within the **Integrations** section of the Cloud. + +![Arduino Cloud homepage with Portenta X8 Manager](assets/web_board_manager_cloud_integration.png "Arduino Cloud homepage with Portenta X8 Manager") + +At this point, you will be asked to create a new account on [Foundries.io](https://foundries.io/) platform. It is recommended to register with the same email address you are currently using in your Arduino Cloud for business account. + +![Foundries.io login](assets/web_board_manager_foundries_login.png "Foundries.io login") + +Add all your credentials and click on **Sign up**. + +![Foundries.io sign up](assets/web_board_manager_signup.png "Foundries.io sign up") + +So, let's create your brand new FoundriesFactory. Select **Arduino Portenta X8**, define a **Factory name** for your Factory and then click on **Create Factory**. + +![FoundriesFactory name](assets/web_board_manager_factory_name.png "FoundriesFactory name") + +Your FoundriesFactory is correctly set-up. As you can see, the Factory does not have any device connected to it. + +![FoundriesFactory homepage with no devices](assets/web_board_manager_factory_overview.png "FoundriesFactory homepage with no devices") + +To provision your Portenta X8, you need to go back to your Out-of-the-box webpage and click on **Portenta X8 Manager** button. + +![Out-of-the-box Portenta X8 Manager](assets/OOTB_homepage_portenta_x8_manager.png "Out-of-the-box Portenta X8 Manager") + +Enter the Factory name you have just registered, in this case *user-test*, and assign a Board Name to your Portenta X8. This Board Name will be used to correctly identify your Portenta X8 into your FoundriesFactory. You can now click on **REGISTER**. + +![Out-of-the-box Factory and device registration](assets/OOTB_board_manager_factory_registration.png "Out-of-the-box Factory and device registration") + +To complete the registration of the Board with the FoundriesFactory, copy the code that appeared in your Out-of-the-box. + +![Out-of-the-box Factory code challenge](assets/OOTB_board_manager_factory_challenge.png "Out-of-the-box Factory code challenge") + +Click on **COMPLETE REGISTRATION** to be re-directed to the Foundries.io activation page. + +Paste your token in the text box and press **Next**. + +***The token code is valid for 15 minutes; if you do not paste it in this time span, you have to repeat all the above registration steps in your Out-of-the-box to generate a new code.*** + +![FoundriesFactory pasted token](assets/web_board_manager_factory_challenge.png "FoundriesFactory pasted token") + +Confirm the addition of your Portenta X8 by pressing **Connect**. + +![FoundriesFactory device confirmation](assets/web_board_manager_factory_challange_connect.png "FoundriesFactory device confirmation") + +Go to your FoundriesFactory by clicking on **Factories Page**. + +![FoundriesFactory device registration completed](assets/web_board_manager_factory_challenge_approved.png "FoundriesFactory device registration completed") + +Now you will see the number of devices associated with your FoundriesFactory to be equal to 1. + +![FoundriesFactory with 1 device](assets/web_board_manager_factory_device.png "FoundriesFactory with 1 device") + +Your Portenta X8 is correctly provisioned into your FoundriesFactory. + +To verify your device status, click on your FoundriesFactory, go to **Devices** section and check its target update and the installed containers Apps. + +![FoundriesFactory device overview](assets/web_board_manager_factory_device-overview.png "FoundriesFactory device overview") + +***If you want to learn more about Portenta X8 Manager features, check the dedicated section of this user manual called [Working with Portenta X8 Board Manager](#working-with-portenta-x8-board-manager).*** + +## Portenta X8 with Arduino IDE + +In this section you will learn how to upload a sketch to the M4 core on the STM32H747XI MCU. + +Open the Arduino IDE and make sure you downloaded the latest Arduino Mbed OS Portenta Boards Core. Learn how to do it by following [this tutorial](https://docs.arduino.cc/software/ide-v1/tutorials/getting-started/cores/arduino-mbed_portenta). + +Select Portenta X8 in the board selector. + +![IDE Board Selector](assets/x8-IDE.png "IDE Board Selector") + +Create a custom sketch or open one of the example sketches e.g. the blink sketch: + +```arduino +void setup(){ + pinMode(LED_BUILTIN ,OUTPUT); +} + +void loop(){ + digitalWrite(LED_BUILTIN , HIGH); + delay(1000); + digitalWrite(LED_BUILTIN , LOW); + delay(1000); +} +``` + +At this point, select the port of your device in the port selector menu and then press the Compile and Upload button. + +Behind the curtains, the sketch gets compiled into a binary. That binary file is then uploaded to the Linux side of the Portenta X8. The flashing is done on the board itself by the RPC service running on Linux (see [Communication between Linux and Arduino section](#communication-between-linux-and-arduino) of this user manual to learn more). + +When the sketch has been uploaded successfully, the onboard LED of your Portenta X8 will start blinking at an interval of one second. + +You can also upload the firmware manually if you like. To do so, you first need to compile the sketch: select **Export compiled binary** from the Sketch menu in the Arduino IDE. It will compile the sketch and save the binary file in the sketch folder. Alternatively, you can use the [Arduino CLI](https://arduino.github.io/arduino-cli/0.29/) to create an `elf` file. + +To upload the firmware you can use the ADB tool that has been installed as part of the Portenta X8 core. It can be found at `Arduino15\packages\arduino\tools\adb\32.0.0`. + +From that directory, you can use the `adb` tool. To upload your compiled sketch, you just need to type the following command into your terminal window: + +``` +adb push /tmp/arduino/m4-user-sketch.elf +``` + +![ADB upload with a terminal](assets/x8-terminal-ADB-push.png) + +## Working with Linux + +Now it is time to start interacting with the Linux OS embedded in your Portenta X8. To do that, you need to open your terminal window and look for ADB inside the directory **Arduino15/packages/arduino/tools/adb/32.0.0**. + +To check if ADB is working correctly, you can type `adb devices`. Your Portenta X8 will be listed there. + +![Connection with ADB](assets/adb-connection.png "Connection with ADB") + +At this point, you can type `adb shell` to start communicating with your Portenta X8. + +![ADB shell command](assets/adb-shell-command.png "ADB shell command") + +As it is a Linux device, you can do tasks like creating files, changing directories, etc. + +To gain admin (root) access, type `sudo su -` and the password, which by default is `fio`. After that, the terminal prefix should turn red. + +![ADB shell with admin access](assets/adb-sudo-su.png "ADB shell with admin access") + +You can now freely program your Portenta X8 Linux OS. In the sections below you can check some basic commands to get started. + +### Change Default User Password + +Your Portenta X8 comes with the default user fio with password fio. + +For security reasons, we strongly suggest changing the default password. To do so, when logged in to your Portenta X8, launch this command to change the password of the fio account: + +```arduino +passwd fio +``` + +### Manage Your Network Via CLI + +In order to connect to a Wi-Fi® Access Point via CLI, you can use the network manager tool **nmcli**. These are some of the most used commands: + +* `nmcli device wifi connect password ` to connect to a specific SSID +* `nmcli de` to check the connection status +* `nmcli connection show` to visualize the active network interfaces (and their types) on your Portenta X8 + +### Accessing Over SSH Session + +Establishing communication with the Portenta X8 via an SSH session is possible. To do so, a network connection is needed, either over Wi-Fi® or Ethernet. For Ethernet connections, using a device with DHCP server capabilities, such as a network router, is recommended. After setting up the network connection and DHCP, the Portenta X8 will be ready for SSH communication. + +For Windows users, it is necessary to install a service tool to ease the following procedures. While Bonjour, Apple's implementation of zero-configuration networking, comes built into macOS, it is not natively included in Windows and must be installed separately. + +***Before proceeding on __Windows__, please install [Bonjour Print Services for Windows](https://support.apple.com/kb/DL999?locale=en_US) before continuing the following steps.*** + +For macOS and Linux users, _Bonjour_ is pre-installed on macOS, and _Avahi-Browse_ is typically available on Linux by default. Thus, additional installation steps may be unnecessary for these operating systems. + +In the subsequent sections, we will first guide you through the process on Windows, followed by details and instructions for Linux and macOS. + +#### Using the Terminal +

+ +![SSH Services Availability Discovery](assets/ssh-x8-dns-sd-service.png "SSH Services Availability Discovery") + +The command below is used to browse for SSH services on the local network that are advertised over a multicast Domain Name System (mDNS). This protocol resolves hostnames to IP addresses within small networks without a local name server. + +```bash +dns-sd -B _sftp-ssh._tcp local +``` + +By executing this command, you can discover devices offering _SFTP services_ (file transfer over SSH) without prior knowledge of their IP addresses or hostnames. + +The command lists these services, indicating where an SSH connection can be established for secure file transfers or shell access, helping to ease the identification and utilization of networked devices that support this protocol. + +![Network Query for IPv4 and IPv6](assets/ssh-x8-dns-sd-v4v6.png "Network Query for IPv4 and IPv6") + +```bash +dns-sd -G v4v6 portenta-x8-.local +``` + +The command above queries the network for the _IPv4_ and _IPv6_ addresses associated with the hostname `portenta-x8-.local`. The _UUID_ can be found within the instance name listed previously or if you have accessed the Portenta X8 via an ADB shell. An example command would look as follows: + +```bash +dns-sd -G v4v6 portenta-x8-1822aa09dab6fad9.local +``` + +This command is handy for finding the IP addresses of devices such as the Portenta X8 that a DHCP server may assign dynamic IP addresses. It simplifies connecting to such devices over the network by providing their current IP addresses. + +![Device Ping Test](assets/ssh-x8-dns-sd-ping.png "Device Ping Test") + +The following command sends echo requests to the device with the hostname `portenta-x8-.local` to check its network availability and measure round-trip time. + +```bash +ping portenta-x8-.local +``` + +This command helps verify that the Portenta X8 is online and reachable over the network and for diagnosing connectivity issues. The UUID can be ascertained by referring to the findings from an earlier SSH services scan with network query or the ADB shell. + +![Portenta X8 Communication over SSH Session](assets/ssh-x8-session.png "Portenta X8 Communication over SSH Session") + +After verifying that the Portenta X8 is accessible using a simple ping test, it is now possible to start an SSH session using the following command: + +```bash +ssh fio@portenta-x8-1822aa09dab6fad9.local +``` + +The example command above starts an SSH (Secure Shell) connection to the Portenta X8 with the hostname `portenta-x8-1822aa09dab6fad9.local` using the username `fio`. The command format should be as follows: + +```bash +ssh fio@portenta-x8-.local +``` + +When executing the command, substitute the `` placeholder with the actual UUID of the Portenta X8 you are attempting to connect to. You can confirm this UUID by checking the results of a prior SSH services scan with a network query or ADB shell. + +If the device is configured correctly to accept SSH connections and the _fio_ account exists with SSH access, this command will prompt for the password associated with the _fio_ user. + +Upon successful authentication, it will open a secure shell session to the device, allowing for command-line interface access and the execution of commands remotely on the Portenta X8. + +The password and the rest of the configuration for using the Portenta X8 inside the shell remain the same. + +The process is similar for _GNU/Linux_ and _macOS_, with minor differences in the initial steps when browsing for SSH services on the local network. + +- __For GNU/Linux__: + +Use _Avahi-Browse_ to search for SSH services on the local network: + +```bash +avahi-browse -d local _sftp-ssh._tcp --resolve -t +``` + +- __macOS__: + +On macOS, you can use the similar command: + +```bash +dns-sd -B _sftp-ssh._tcp local +``` + +Alternatively, you can use a software called "_Discovery_", which is available [here](https://apps.apple.com/it/app/discovery-dns-sd-browser/id1381004916?l=en&mt=12). + +#### Using Software With GUI +

+ +The SSH session can be initialized using third-party software with a Graphical User Interface (GUI) for easy access. An example is a software called "_Bonjour Browser_", which can be downloaded [here](https://hobbyistsoftware.com/bonjourbrowser). + +![SSH Services Availability Discovery with GUI](assets/ssh-x8-bonjour.png "SSH Services Availability Discovery with GUI") + +This software simplifies browsing SSH services on the local network advertised over mDNS using a GUI. The image above, for example, shows all available services on the network, including those for the Portenta X8. By simply clicking on a service item, you can retrieve the IP address information. + +Once the information is verified, you can use that data with software such as [_PuTTY_](https://www.putty.org/). _PuTTY_ is a free and open-source terminal emulator, serial console, and network file transfer application. It supports several network protocols, including _SSH (Secure Shell)_ and _SFTP (SSH File Transfer Protocol)_. + +![Portenta X8 SSH Session with PuTTY - Setup](assets/ssh-x8-putty.png "Portenta X8 SSH Session with PuTTY - Setup") + +In the PuTTY Configuration window, keeping the default values, you must specify the _Host Name (or IP address)_ field with `portenta-x8-`. For instance, you would use: + +``` +portenta-x8-1822aa09dab6fad9 +``` + +Click on `Open`, and it will prompt a security alert. It displays information about the connection, including fingerprint details. Depending on your connection profile preference, you can choose to `Accept` or `Connect Once`. + +![Portenta X8 SSH Session with PuTTY - Authentication](assets/ssh-x8-putty-auth.png "Portenta X8 SSH Session with PuTTY - Authentication") + +After verifying the security alert and proceeding, you have an SSH session that has begun communicating with the Portenta X8. + +![Portenta X8 SSH Session with PuTTY](assets/ssh-x8-putty-session.png "Portenta X8 SSH Session with PuTTY") + +### Inspect Real-Time Tasks And Logs Via CLI + +Run `journalctl -f` to check the status of active services and possibly their errors, but also various system event logs. + +![ADB shell journalctl package](assets/adb-shell-real-time-tasks.png "ADB shell journalctl package") + +By calling `journalctl` it is possible to take a look at the log of all the running activities, by specifying also the type of log you are looking for. Some logs may be a warning which can be ignored or some may be critical errors. Type `journalctl -p 0` to view emergency system messages, otherwise change the number 0 with the error code you want to investigate according to the following error code numbers: + +| Error code | Meaning | +|------------|-----------| +| 0 | Emergency | +| 1 | Alerts | +| 2 | Critical | +| 3 | Errors | +| 4 | Warning | +| 5 | Notice | +| 6 | Info | +| 7 | Debug | + +When you specify the error code, it shows all messages from that code and above. For example, if you specify error code 2, then it shows all messages with priority 2, 1 and 0. + +Additionally, you can also view logs for a specific time and date duration. You can use the `-- since` switch with a combination of `"yesterday"`, `"now"`, or a specific date and time `"YYYY-MM-DD HH:MM:SS"`. + +An example of how to use the command: + +```arduino +journalctl --since "2022-12-22 12:20:00" --until yesterday +``` + +### Create And Upload Docker Containers To Portenta X8 + +We created dedicated tutorials covering this topic. Go check them out: + +* [Managing Containers with Docker on Portenta X8](https://docs.arduino.cc/tutorials/portenta-x8/docker-container) +* [Deploy a Custom Container with Portenta X8 Manager](https://docs.arduino.cc/tutorials/portenta-x8/custom-container) +* [Running Wordpress & Database Containers on Portenta X8](https://docs.arduino.cc/tutorials/portenta-x8/wordpress-webserver) + +### Output Video Content On A Screen + +The USB-C® port on your Portenta X8 supports video output. As a consequence, you can freely connect a USB-C® monitor or a USB-C® to HDMI hub to your Portenta X8 to start visualizing video or other visual renders. + +Here you can find a list of validated compatible USB-C® to HDMI hubs: + +* [TPX00145](https://store.arduino.cc/products/usb-c-to-hdmi-multiport-adapter-with-ethernet-and-usb-hub) +* [TPX00146](https://store.arduino.cc/products/usb-c-to-hdmi-multiport-adapter-4k-usb-hub-pd-pass-through) + +***Learn more on how to output WebGL content on a screen with Portenta X8 by checking the [dedicated tutorial](https://docs.arduino.cc/tutorials/portenta-x8/display-output-webgl).*** + +### Build A Custom Image For Portenta X8 + +You may want to build a custom image for the Portenta X8 with the source code provided in the public [GitHub repository of lmp-manifest](https://github.com/arduino/lmp-manifest). Building an image locally can help debug certain aspects of the system, such as the bootloader or kernel support. + +***Have a look at [this dedicated tutorial](https://docs.arduino.cc/tutorials/portenta-x8/image-building) to understand how to build your own custom image.*** + +### Additional Tutorials + +If you want to continue working with your Portenta X8, you can find tons of additional tutorials in the **Tutorials** section of our [Arduino Docs](https://docs.arduino.cc/hardware/portenta-x8). Go check them out! + +## Working With Arduino + +You have learned how to use your Portenta X8 with the Arduino IDE in the section [Portenta X8 with Arduino IDE](#portenta-x8-with-arduino-ide), but you can do much more with the Arduino environment, in particular leveraging the RPC communication between the Arduino layer and the Linux layer. + +You can have a look at this [GitHub repository](https://github.com/arduino/ArduinoCore-mbed/tree/master/libraries/RPC/examples) to have access to multiple IDE examples showing how to use RPC communication with Portenta X8. + +***Check [Communication between Linux and Arduino](#communication-between-linux-and-arduino) section of this user manual to learn more about RPC.*** + +You can build an Arduino sketch to manage all the tasks requiring real-time, including sensors communication, Fieldbus management, etc., and then send those data to a Cloud or remote server via multiple connectivity options, by leveraging the high-performance network management capabilities of Linux OS. + +For instance, try [Data Exchange Between Python® on Linux and an Arduino Sketch](https://docs.arduino.cc/tutorials/portenta-x8/python-arduino-data-exchange) tutorial to learn how to exchange sensor data between the Python® container embedded on Portenta X8 and an Arduino sketch. + +Additionally, if you are a more advanced user, you can check [Multi-Protocol Gateway With Portenta X8 & Max Carrier](https://docs.arduino.cc/tutorials/portenta-x8/multi-protocol-gateway) tutorial to develop your own multi-protocol gateway: receive data from a sensor with the Arduino layer via MQTT protocol, take advantage of RPC to establish communication between Arduino and Linux, and then send the acquired data to The Things Network via LoRaWAN® managed by the Linux layer. + +## Working With Arduino Cloud + +To start using your Portenta X8 with Arduino Cloud, provision your device as described in [this section](#portenta-x8-with-arduino-cloud). + +Once ready, you will have the chance to customize Portenta X8 example Thing and Dashboard. This can be done by writing your own Python script leveraging the [Arduino IoT Cloud Python library](https://github.com/arduino/arduino-iot-cloud-py). Check the documentation and the examples inside the library to learn more about how to create your own Python application. + +When your Python script is ready, you have to create a dedicated Dockerfile integrating your new script. The Dockerfile needs the Out-of-the-box Python container (i.e. `arduino-ootb-python-devel`) to be able to correctly interact with your Arduino Cloud account. + +So, open a terminal window and create a Dockerfile integrating the following code together with your Python script: + +```arduino +FROM arduino/arduino-ootb-python-devel:latest +``` + +```arduino +# Copy custom python cloud scripts +COPY ./custom-examples /root/custom-examples +``` + +```arduino +RUN chmod -R 755 /root/custom-examples +``` + +### Build Your Container + +You can create your own custom container and build them inside the Portenta X8. Since Portenta X8 is based on an arm64 architecture, you can use the command `build` only if you are actually building the container directly on an arm64 architecture (e.g. Macbook based on M1/M2 processor or Portenta X8). Open a terminal window and type: + +```arduino +docker build . -t x8-custom-devel +``` + +Otherwise, if you are using a different architecture or building machine, use `buildx` command to specify which architecture your build should compile for: + +```arduino +docker buildx build --platform linux/arm64 -t x8-custom-devel --load . +``` + +In this way, your Docker image will be built and tagged with the name `x8-custom-devel`. + +Now it is time for you to deploy the newly created Docker image. To do so, you need to save it somewhere and then deploy it on your Portenta X8. + +### Deploy Your Container With Docker Hub + +If you have a [Docker Hub account](https://hub.docker.com/), you can freely upload your Docker image to your registry (e.g. `yourhubusername`): + +```arduino +docker push yourhubusername/x8-custom-devel +``` + +Your image is now available in your Docker Hub registry `yourhubusername`. + +At this point, you can directly pull the image to your Portenta X8. To do so, connect to your Portenta X8 through ADB. It can be found at `Arduino15\packages\arduino\tools\adb\32.0.0`. + +From that directory, you can pull the image to the location you prefer. + +```arduino +adb shell +``` + +With the Portenta X8's terminal, following command is used. + +```arduino +docker pull x8-custom-devel +``` + +Now your image is correctly deployed on your Portenta X8. + +### Deploy Your Container Without Docker Hub + +If you do not have a Docker Hub account, you can also save the Docker container locally as a .tar archive, and then you can easily load that to an image. + +To save a Docker image after you have built it, you can use the `docker save` command. For example, let's save a local copy of the `x8-custom-devel` docker image you made: + +```arduino +docker save x8-custom-devel:latest | gzip > x8-custom-devel_latest.tar.gz +``` + +At this point, you can directly pull the image to your Portenta X8. To do so, connect to your Portenta X8 through ADB. It can be found at `Arduino15\packages\arduino\tools\adb\32.0.0`. + +```arduino +docker import /home/fio/x8-custom-devel_latest.tar.gz x8-custom-devel:latest +``` + +Now your image is correctly deployed on your Portenta X8. + +### Launch Your Container + +In order to launch your brand new image, you need to create a new `docker-compose.yml`. To do so, first you must stop the current `docker-compose.yml`. + +```arduino +cd /var/sota/compose-apps/arduino-ootb && docker compose stop +``` + +You can now create the path for the new `docker-compose.yml`: + +```arduino +mkdir /var/sota/compose-apps/custom-devel && cd /var/sota/compose-apps/custom-devel && touch docker-compose.yml +``` + +Before uploading, open the `docker-compose.yml` and edit it as follow to make it use the Docker image you have just created: + +```arduino +services: + custom: + container_name: custom-devel + hostname: "portenta-x8" + image: x8-custom-devel:latest + + restart: unless-stopped + tty: true + read_only: false + user: "0" + volumes: + #- '/dev:/dev' + - '/run/arduino_hw_info.env:/run/arduino_hw_info.env:ro' + - '/sys/devices:/sys/devices' + - '/sys/class/pwm:/sys/class/pwm' + - '/sys/bus/iio:/sys/bus/iio' + - '/var/sota:/var/sota' + - './keys:/tmp/keys:ro' + devices: + - '/dev/gpiochip5' + - '/dev/tee0' +``` + +It is now time to upload the new `docker-compose.yml` to your Portenta X8: + +```arduino +docker-compose up --detach +``` + +And you are ready to go! Your Portenta X8 Dashboards and Things can be customized multiple times with the same process. + +***If you are using the Portenta X8 Manager, go to [this documentation](https://docs.foundries.io/latest/tutorials/getting-started-with-docker/getting-started-with-docker.html) to learn how to upload the newly created container in your FoundriesFactory.*** + +## Working With Portenta X8 Board Manager + +As already mentioned, Portenta X8 Board Manager allows you to easily keep your Portenta X8 Linux image and corresponding containers up to date, even from remote through Over-The-Air (OTA) updates (via wireless connectivity). + +Subscribe to an *Arduino Cloud for business* plan with Portenta X8 Board Manager to have access to all these features. Take a look at [this section](#portenta-x8-board-manager) of the user manual to learn more. + +### Device And Fleet Management With Portenta X8 Board Manager + +Verify that your Portenta X8 is correctly added to your FoundriesFactory by checking if it is listed among the available devices under the **Devices** section. + +![FoundriesFactory device overview](assets/web_board_manager_factory_device-overview.png "FoundriesFactory device overview") + +If you want to check if your Portenta X8 is updated according to the latest available Target (i.e. update), you can check the color of the bulb under the status column. There are three main color options: + +| Bulb color | Meaning | +|-------------|--------------------------------| +| Green | Device online and updated | +| Yellow | Device online and not updated | +| Red | Device offline and not updated | + +In this case, the Portenta X8 is connected to the network (and so to the FoundriesFactory), but it is not updated. + +You can see the Target uploaded on your device under the Target column, i.e. *portenta-x8-lmp-569*, and get additional information about what is included in this specific Target by clicking on it. + +![FoundriesFactory device target specs](assets/web_board_manager_factory_device_specs.png "FoundriesFactory device target specs") + +The above window also shows you all the container apps you have installed on your device and you can start using. + +If you scroll down in the same window, you can also have a look at the update history of that specific device. + +![FoundriesFactory device update history](assets/web_board_manager_factory_update_history.png "FoundriesFactory update history") + +At this point, you can compare the Target uploaded on your Portenta X8 with the Target available in the **Targets** section and decide whether to update your device or not. + +![FoundriesFactory target overview](assets/web_board_manager_factory_target.png "FoundriesFactory target overview") + +***Learn how to update your Portenta X8 with your FoundriesFactory by checking the [dedicated section](#portenta-x8-os-image-update) of this user manual.*** + +This **Target** page contains the Linux images built each time something is committed in the repositories available under the **Source** section. In this section, you can find the four repositories that are used to customize the images: + +* **ci-scripts.git:** Scripts that define the platform and container build jobs on the FoundriesFactory system. +* **containers.git:** This is where containers and docker-compose apps are defined. It allows you to define which containers to build/deploy and how to orchestrate them on the platform. +* **lmp-manifest.git:** The repo manifest for the platform build. It defines which layer versions are included in the platform image. This includes **meta-partner-arduino**, the layer containing Arduino-specific customizations (machine definition, device drivers, etc.). +* **meta-subscriber-overrides.git:** *OE* layer that defines what is included in your FoundriesFactory image. You can add board-specific customizations and overrides or add and remove packages provided in the default Linux microPlatform. + +Committing to **lmp-manifest.git** or **meta-subscriber-overrides.git** repositories will create a platform Target, i.e. base Linux platform image. On the other hand, committing to **containers.git** will create a container Target including all the containers and docker-compose apps you would like to upload on your Portenta X8. Both these Targets will generate the artifacts specified in the **ci-scripts.git**, which includes all the required files to program the Target in case of platform build. + +### RBAC With Portenta X8 Board Manager + +You do not have to be the only one in your organization with permission to update your Portenta X8 devices. The FoundriesFactory integrates a Role-Based-Access-Control functionality (RBAC) to allow users to add multiple teams with multiple members each. + +You can start defining a new team by clicking on **Teams** section. + +![FoundriesFactory Teams](assets/web_board_manager_team.png "FoundriesFactory Teams") + +The level of access and specific permissions are defined by the team’s role in the FoundriesFactory. As you can notice from the image below, multiple roles and permissions are available. + +![FoundriesFactory Team roles and permissions](assets/web_board_manager_factory_team_roles.png "FoundriesFactory Team roles and permissions") + +Once you created the team, you can go to the **Members** section of your FoundriesFactory to invite new members to the team. + +![FoundriesFactory new member](assets/web_board_manager_factory_member.png "FoundriesFactory new member") + +You can type the email addresses of your teammates and they will receive an automatic email with the invitation to join the corresponding team in your FoundriesFactory. + +### FoundriesFactory FIOCTL + +The FoundriesFactory includes a command line tool called [FIOCTL](https://docs.foundries.io/latest/getting-started/install-fioctl/index.html) which allows you to manage your Portenta X8 through your CLI. + +With this tool, you can easily upload containers to a board that is linked to your FoundriesFactory just by stating the FoundriesFactory name, the board name and the app you would like to upload. + +***Learn how to use this tool by checking the dedicated tutorial at [this link](https://docs.arduino.cc/tutorials/portenta-x8/custom-container) or the corresponding [Foundries documentation](https://docs.foundries.io/latest/getting-started/install-fioctl/index.html).*** + +## Pins + +In order to learn how to properly call GPIOs or other peripherals both in the Arduino environment or in Linux, with or without a carrier, you can check the following pinout diagrams: + +* [Portenta X8 pinout](https://docs.arduino.cc/static/019dd9ac3b08f48192dcb1291d37aab9/ABX00049-full-pinout.pdf) +* [Portenta Breakout pinout](https://docs.arduino.cc/static/8d54d1a01d6174ed60fc9698e881ad4c/ASX00031-full-pinout.pdf) +* [Portenta Max Carrier pinout](https://docs.arduino.cc/static/d0bd73b17e97af0fe376b7d518b18660/ABX00043-full-pinout.pdf) +* [Portenta Hat Carrier pinout](https://docs.arduino.cc/resources/pinouts/ASX00049-full-pinout.pdf) + +## Communication + +In this section you will learn how to make your Portenta X8 to communicate with multiple types of sensors or other external devices, leveraging the vast variety of supported interfaces: + +* [SPI](#spi) +* [I2C](#i2c) +* [UART](#uart) +* [Bluetooth®](#bluetooth) + +### SPI + +In this case, a Portenta X8 with Portenta Breakout board is used to connect an external SPI device. + +#### SPI With Linux + +You need to enable SPI support before using SPI devices. + +Open Portenta X8 Shell as explained [here](#working-with-linux). + +```arduino +sudo modprobe spi-dev +``` + +Insert the user password `fio`. + +An upcoming image release for the X8 will load the `spi-dev` modules automatically at boot. In the current version, please create a `/etc/modules-load.d/spi-dev.conf` file with the following content: + +```arduino +spi-dev +``` + +and restart the board. + +```arduino +echo "spi-dev" | sudo tee > /etc/modules-load.d/spi-dev.conf +``` + +```arduino +sudo systemctl reboot +``` + +Add the device you want to communicate within a container in a `docker-compose.yml` file: + +```arduino +services: + my_spi_service: + devices: + - /dev/spi-1 + - /dev/spi-2 + - /dev/spi-3 +``` + +If the Linux user on which the container is running is not `root`, you need to set up the permissions for the user to access the SPI devices. You might add the required comments to an `entrypoint.sh` shell file (to be added to the `Dockerfile` or the `docker-compose.yml` file). + +```arduino +#!/usr/bin/env sh + +# entrypoint.sh example + +chgrp users /dev/spi-* +chmod g+rw /dev/spi-* +usermod -aG users + +# Possible command to execute your application as a non-privileged user with gosu +# Check https://github.com/tianon/gosu for more information +gosu /usr/bin/python my_spi_service.py +``` + +#### SPI Port Mapping + +| Linux | Arduino Portenta Breakout | +|-------|---------------------------| +| 134 | **`SPI1 CK`** | +| 135 | **`SPI1 COPI`** | +| 136 | **`SPI1 CIPO`** | +| 137 | **`SPI1 CS`** | + +#### SPI With Arduino + +The `SPI` object is [mapped](https://github.com/arduino/ArduinoCore-mbed/blob/23e4a5ff8e9c16bece4f0e810acc9760d3dd4462/variants/PORTENTA_X8/pins_arduino.h#L85) as follows on the Portenta Breakout Board and can be deployed as usual: + +| SPI Pin | Arduino Portenta Breakout | +|---------|---------------------------| +| CIPO | Pin 0 (Header GPIO0) | +| COPI | Pin A6 (Header Analog) | +| SCK | Pin A5 (Header Analog) | +| CS | Pin 1 (Header GPIO0) | + +### I2C + +In this case, a Portenta X8 with Portenta Breakout board is used to connect an external I2C device. + +#### I2C With Linux + +You need to enable I2C support before using I2C devices. + +Open Portenta X8 Shell as explained [here](#working-with-linux). + +Thus, execute the following command: + +```arduino +sudo modprobe i2c-dev +``` + +Insert the user password `fio`. + +An upcoming image release for the X8 will load the `i2c-dev` modules automatically at boot. In the current version, please create a `/etc/modules-load.d/i2c-dev.conf` file with the following content: + +```arduino +i2c-dev +``` + +and restart the board. + +```arduino +echo "i2c-dev" | sudo tee > /etc/modules-load.d/i2c-dev.conf +``` + +```arduino +sudo systemctl reboot +``` + +Add the device you want to communicate within a container in a `docker-compose.yml` file: + +```arduino +services: + my_i2c_service: + devices: + - /dev/i2c-1 + - /dev/i2c-2 + - /dev/i2c-3 +``` + +If the Linux user on which the container is running is not `root`, you need to set up the permissions for the user to access the I2C devices. You might add the required comments to an `entrypoint.sh` shell file (to be added to the `Dockerfile` or the `docker-compose.yml` file). + +```arduino +#!/usr/bin/env sh + +# entrypoint.sh example + +chgrp users /dev/i2c-* +chmod g+rw /dev/i2c-* +usermod -aG users + +# Possible command to execute your application as a non-privileged user with gosu +# Check https://github.com/tianon/gosu for more information +gosu /usr/bin/python my_i2c_service.py +``` + +#### I2C Port Mappings + +| Linux | Arduino Portenta Breakout | Notes | +|------------|---------------------------|---------------| +|`/dev/i2c-1`| **`I2C1`** | | +|`/dev/i2c-2`| **`I2C0`** | Recommended | +|`/dev/i2c-3`| **`I2C1`** | | + +#### Examples + +Examples of using SMBus-compatible [libraries](https://github.com/kplindegaard/smbus2): + +```arduino +from smbus2 import SMBus + +# Connect to /dev/i2c-2 +bus = SMBus(2) +b = bus.read_byte_data(80, 0) +print(b) +``` + +Example of using [python-periphery](https://python-periphery.readthedocs.io/en/latest/index.html): + +```arduino +from periphery import I2C + +# Open i2c-0 controller +i2c = I2C("/dev/i2c-2") + +# Read byte at address 0x100 of EEPROM at 0x50 +msgs = [I2C.Message([0x01, 0x00]), I2C.Message([0x00], read=True)] +i2c.transfer(0x50, msgs) +print("0x100: 0x{:02x}".format(msgs[1].data[0])) + +i2c.close() +``` + +#### I2C With Arduino + +The `Wire` object is [mapped](https://github.com/arduino/ArduinoCore-mbed/blob/23e4a5ff8e9c16bece4f0e810acc9760d3dd4462/variants/PORTENTA_X8/pins_arduino.h#L113) to pins `PWM6` (I2C `SCL`) and `PWM8` (I2C `SDA`) on the Portenta Breakout Board and can be deployed as usual. + +Since one of the `I2C` pins is GPIO-multiplexed, you need to detach it from the other GPIO. Just add the following line in the `setup()` definition to have it fully functional for `I2C` operations. + + ```arduino + void setup() { + pinMode(PA_12, INPUT); + } + ``` + +### UART + +In this case, a Portenta X8 with Portenta Breakout board is used to explore UART communication. + +#### UART With Linux + +A standard UART is available as `/dev/ttymxc1` in Linux and is mapped to the **`UART1`** port on the Portenta Breakout. + +### Bluetooth® + +Portenta X8 supports Bluetooth® connectivity just on the Linux side. + +In order to communicate with Bluetooth® devices via the Portenta X8 Shell, you can use the Bluetooth® utility **bluetoothctl**. These are some of the most used commands: + +* `bluetoothctl devices` to list all the available Bluetooth® devices +* `bluetoothctl pair [mac_address]` to pair with a specific device through its MAC address +* `bluetoothctl connect [mac_address]` to connect to a paired device +* `bluetoothctl disconnect [mac_address]` to disconnect from a paired device + +***Do you want to send data from your Nicla to Portenta X8 via BLE? Check [this link](https://github.com/Zalmotek/arduino-environmental-monitoring-with-arduino-pro) to get started.*** + +## Support + +If you encounter any issues or have questions while working with the Portenta X8, we provide various support resources to help you find answers and solutions. + +### Help Center + +Explore our [Help Center](https://support.arduino.cc/hc/en-us), which offers a comprehensive collection of articles and guides for the Portenta X8. The Arduino Help Center is designed to provide in-depth technical assistance and help you make the most of your device. + +- [Portenta Family help center page](https://support.arduino.cc/hc/en-us/sections/360004767859-Portenta-Family) + +### Forum + +Join our community forum to connect with other Portenta X8 users, share your experiences, and ask questions. The forum is an excellent place to learn from others, discuss issues, and discover new ideas and projects related to the Portenta X8. + +- [Portenta X8 category in the Arduino Forum](https://forum.arduino.cc/c/hardware/portenta/portenta-x8/172) + +### Contact Us + +Please get in touch with our support team if you need personalized assistance or have questions not covered by the help and support resources described before. We're happy to help you with any issues or inquiries about the Portenta X8. + +- [Contact us page](https://www.arduino.cc/en/contact-us/) diff --git a/content/hardware/04.pro/carriers/portenta-hat-carrier/tutorials/user-manual/content.md b/content/hardware/04.pro/carriers/portenta-hat-carrier/tutorials/user-manual/content.md index da0a483e6f..b056a695b1 100644 --- a/content/hardware/04.pro/carriers/portenta-hat-carrier/tutorials/user-manual/content.md +++ b/content/hardware/04.pro/carriers/portenta-hat-carrier/tutorials/user-manual/content.md @@ -709,7 +709,7 @@ void setup() { Serial.println("Mass Storage Device connected."); /* - * MOUNTIN SDCARD AS FATFS filesystem + * MOUNTING SDCARD AS FATFS filesystem */ Serial.println("Mounting Mass Storage Device..."); diff --git a/content/hardware/04.pro/carriers/portenta-max-carrier/tutorials/user-manual/content.md b/content/hardware/04.pro/carriers/portenta-max-carrier/tutorials/user-manual/content.md index 46e789befb..64af14ae4d 100644 --- a/content/hardware/04.pro/carriers/portenta-max-carrier/tutorials/user-manual/content.md +++ b/content/hardware/04.pro/carriers/portenta-max-carrier/tutorials/user-manual/content.md @@ -938,7 +938,7 @@ void setup() { Serial.println("Mass Storage Device connected."); /* - * MOUNTIN SDCARD AS FATFS filesystem + * MOUNTING SDCARD AS FATFS filesystem */ Serial.println("Mounting Mass Storage Device..."); diff --git a/content/hardware/04.pro/carriers/portenta-mid-carrier/tutorials/user-manual/content.md b/content/hardware/04.pro/carriers/portenta-mid-carrier/tutorials/user-manual/content.md index 00067077c5..800c903a31 100644 --- a/content/hardware/04.pro/carriers/portenta-mid-carrier/tutorials/user-manual/content.md +++ b/content/hardware/04.pro/carriers/portenta-mid-carrier/tutorials/user-manual/content.md @@ -1690,7 +1690,7 @@ void setup() { Serial.println("Mass Storage Device connected."); /* - * MOUNTIN SDCARD AS FATFS filesystem + * MOUNTING SDCARD AS FATFS filesystem */ Serial.println("Mounting Mass Storage Device..."); diff --git a/content/hardware/06.nicla/boards/nicla-sense-me/tutorials/connecting-to-iot-cloud/content.md b/content/hardware/06.nicla/boards/nicla-sense-me/tutorials/connecting-to-iot-cloud/content.md index b49c6adc06..0b0ba1d1fc 100644 --- a/content/hardware/06.nicla/boards/nicla-sense-me/tutorials/connecting-to-iot-cloud/content.md +++ b/content/hardware/06.nicla/boards/nicla-sense-me/tutorials/connecting-to-iot-cloud/content.md @@ -129,7 +129,7 @@ Inside `void setup()` initialize the `Serial` communication, set up the variable // Connect to Arduino Cloud ArduinoCloud.begin(ArduinoIoTPreferredConnection); - // Wait to be connected before intitalize the communication with the Nicla Sense ME + // Wait to be connected before initialize the communication with the Nicla Sense ME Serial.println("Connecting to the Arduino Cloud"); while (ArduinoCloud.connected() != 1) { ArduinoCloud.update(); diff --git a/content/tutorials/generic/secrets-of-arduino-pwm/secrets-of-arduino-pwm.md b/content/tutorials/generic/secrets-of-arduino-pwm/secrets-of-arduino-pwm.md index 397821d2d5..0a405cb98d 100644 --- a/content/tutorials/generic/secrets-of-arduino-pwm/secrets-of-arduino-pwm.md +++ b/content/tutorials/generic/secrets-of-arduino-pwm/secrets-of-arduino-pwm.md @@ -248,9 +248,9 @@ The Arduino uses Timer 0 internally for the millis() and delay() functions, so b The `analogWrite(pin, duty_cycle)` function sets the appropriate pin to PWM and sets the appropriate output compare register to duty_cycle (with the special case for duty cycle of 0 on Timer 0). The `digitalWrite()` function turns off PWM output if called on a timer pin. The relevant code is wiring_analog.c and wiring_digital.c. -If you use `analogWrite(5, 0)` you get a duty cycle of 0%, even though pin 5's timer (Timer 0) is using fast PWM. How can this be, when a fast PWM value of 0 yields a duty cycle of 1/256 as explained above? The answer is that `analogWrite` "cheats"; it has special-case code to explicitly turn off the pin when called on Timer 0 with a duty cycle of 0. As a consequency, the duty cycle of 1/256 is unavailable when you use `analogWrite`` on Timer0, and there is a jump in the actual duty cycle between values of 0 and 1. +If you use `analogWrite(5, 0)` you get a duty cycle of 0%, even though pin 5's timer (Timer 0) is using fast PWM. How can this be, when a fast PWM value of 0 yields a duty cycle of 1/256 as explained above? The answer is that `analogWrite` "cheats"; it has special-case code to explicitly turn off the pin when called on Timer 0 with a duty cycle of 0. As a consequence, the duty cycle of 1/256 is unavailable when you use `analogWrite`` on Timer0, and there is a jump in the actual duty cycle between values of 0 and 1. -Some other Arduino models use dfferent AVR processors with similar timers. The Arduino Mega uses the ATmega1280 (datasheet), which has four 16-bit timers with 3 outputs each and two 8-bit timers with 2 outputs each. Only 14 of the PWM outputs are supported by the Arduino Wiring library, however. Some older Arduino models use the ATmega8 (datasheet), which has three timers but only 3 PWM outputs: Timer 0 has no PWM, Timer 1 is 16 bits and has two PWM outputs, and Timer 2 is 8 bits and has one PWM output. +Some other Arduino models use different AVR processors with similar timers. The Arduino Mega uses the ATmega1280 (datasheet), which has four 16-bit timers with 3 outputs each and two 8-bit timers with 2 outputs each. Only 14 of the PWM outputs are supported by the Arduino Wiring library, however. Some older Arduino models use the ATmega8 (datasheet), which has three timers but only 3 PWM outputs: Timer 0 has no PWM, Timer 1 is 16 bits and has two PWM outputs, and Timer 2 is 8 bits and has one PWM output. ### Troubleshoot diff --git a/scripts/resources/spell-check-ignore-list.txt b/scripts/resources/spell-check-ignore-list.txt index 18b54b23be..f032b063c7 100644 --- a/scripts/resources/spell-check-ignore-list.txt +++ b/scripts/resources/spell-check-ignore-list.txt @@ -14,4 +14,6 @@ ro som ser Manuel -technic \ No newline at end of file +technic +shiftin +forsee \ No newline at end of file