diff --git a/content/documentation/Accessories/Cases/Model_A_Acrylic_Open_Enclosure.adoc b/content/documentation/Accessories/Cases/Model_A_Acrylic_Open_Enclosure.adoc index 51d1666f..f4b24856 100644 --- a/content/documentation/Accessories/Cases/Model_A_Acrylic_Open_Enclosure.adoc +++ b/content/documentation/Accessories/Cases/Model_A_Acrylic_Open_Enclosure.adoc @@ -11,7 +11,7 @@ menu: The *"Model A" Acrylic Open Enclosure* is a case for "Model A" sized single-board computers (Pine A64, ROCKPro64, Quartz64 Model A) sold by PINE64, available from https://pine64.com/product/pine-a64-rockpro64-acrylic-open-enclosure/[the official store]. -image:/documentation/images/Model_a_acrylic_case_with_pine_a64.jpg[A Pine A64 mounted in the "Model A" Acrylic Open Enclosure. The text on the top is "PINE64" nowadays.,title="A Pine A64 mounted in the "Model A" Acrylic Open Enclosure. The text on the top is "PINE64" nowadays."] +{{< figure src="/documentation/images/Model_a_acrylic_case_with_pine_a64.jpg" title="A Pine A64 mounted in the "Model A" Acrylic Open Enclosure. The text on the top is "PINE64" nowadays." >}} == Installation @@ -23,7 +23,7 @@ For the Quartz64 Model A, you may need to file down the inner corner of one of t === 3D-Printable Top With Fan and PCIe Cutout -image:/documentation/images/Model_a_top_render.png[Non-artist's impression of the replacement top plate,title="Non-artist's impression of the replacement top plate"] +{{< figure src="/documentation/images/Model_a_top_render.png" title="Non-artist's impression of the replacement top plate" >}} User:CounterPillow has created an alternate 3D-printable top plate which allows for the mounting of a 40mmx40mmx10mm fan, as well as allowing for PCIe cards to be mounted while the case is assembled. The STL and STEP files are available under https://wiki.pine64.org/wiki/File:Model_A_acrylic_case_top_plate_with_fan_cutout.zip[] free of charge, licensed as CC-BY 4.0. diff --git a/content/documentation/Accessories/Cases/Model_B_Acrylic_Open_Enclosure.adoc b/content/documentation/Accessories/Cases/Model_B_Acrylic_Open_Enclosure.adoc index 8a62970b..ad791479 100644 --- a/content/documentation/Accessories/Cases/Model_B_Acrylic_Open_Enclosure.adoc +++ b/content/documentation/Accessories/Cases/Model_B_Acrylic_Open_Enclosure.adoc @@ -11,7 +11,7 @@ menu: The *"Model B" Acrylic Open Enclosure* is a case for "Model B" sized single-board computers sold by PINE64, available from https://pine64.com/product/model-b-acrylic-open-enclosure/[the official store]. -image:/documentation/ROCK64/images/ROCK64_acrylic_open_enclosure.jpg[A_ROCK64_mounted_in_the_case,_the_correct_way.,title="A_ROCK64_mounted_in_the_case,_the correct way."] +{{< figure src="/documentation/ROCK64/images/ROCK64_acrylic_open_enclosure.jpg" title="A_ROCK64_mounted_in_the_case,_the_correct_way." >}} == Installation @@ -21,8 +21,8 @@ To install the SBC inside the case, stick the long screws into the SBC mounting === 3D-Printable Top With Fan Cutout -image:/documentation/images/Model_b_open_enclosure_top_cad.png[Top_view_of_the_plate,title="Top_view_of_the_plate"] -image:/documentation/images/Model_B_Open_Enclosure_Top_Fan_Mount.jpeg[The assembled modified case with a Noctua NF-A4x10 5V PWM mounted to it. The SBC is mounted in the enclosure upside-down.,title="The assembled modified case with a Noctua NF-A4x10 5V PWM mounted to it. The SBC is mounted in the enclosure upside-down."] +{{< figure src="/documentation/images/Model_b_open_enclosure_top_cad.png" title="Top_view_of_the_plate" >}} +{{< figure src="/documentation/images/Model_B_Open_Enclosure_Top_Fan_Mount.jpeg" title="The assembled modified case with a Noctua NF-A4x10 5V PWM mounted to it. The SBC is mounted in the enclosure upside-down." >}} User:CounterPillow has created an alternate 3D-printable top plate which allows for the mounting of a 40mmx40mmx10mm fan. The STL and STEP files are available free of charge under https://wiki.pine64.org/wiki/File:Model_B_acrylic_case_top_plate_with_fan_cutout.zip[], licensed as CC-BY 4.0. @@ -34,7 +34,7 @@ The print will take approximately 7.8 metres of filament, and take in the order The cooling performance with a Noctua NF-A4x10 5V PWM is enough to no longer throttle after a few minutes of cpuburn, but comfortably sitting at below 75°C instead. The memory has no temperature sensor, but will likely be cooled quite a bit as well. -image:/documentation/images/Arduino_pwm_thing.png[Rough wiring diagram of how to PWM control the fan from a ROCK64 with a helper Arduino,title="Rough wiring diagram of how to PWM control the fan from a ROCK64 with a helper Arduino"] +{{< figure src="/documentation/images/Arduino_pwm_thing.png" title="Rough wiring diagram of how to PWM control the fan from a ROCK64 with a helper Arduino" >}} Since the link:/documentation/ROCK64[ROCK64] has no PWM pins available to control the fan, a slight workaround can be done; with the `gpio-fan` device tree binding, an Arduino can be controlled to soft-PWM a suitable 25 kHz signal for the fan. The ROCK64 uses 3.3V on the GPIO pins, so you'll need to logic level convert it to 5V if you're using a 5V Arduino, and if you're using a 3.3V microcontroller, you'll need to logic level shift the output PWM signal as the 5V fan will be expecting 5V PWM on the PWM pin. diff --git a/content/documentation/Accessories/Cases/NASCase.adoc b/content/documentation/Accessories/Cases/NASCase.adoc index 63cf0fa4..66c08cf3 100644 --- a/content/documentation/Accessories/Cases/NASCase.adoc +++ b/content/documentation/Accessories/Cases/NASCase.adoc @@ -13,11 +13,11 @@ The PINE64 NAS Case is intended for either a Network Attached Storage (NAS) or D An exploded view of the NAS Case, illustrating how all the components come together, can be found http://files.pine64.org/doc/rockpro64/ROCKPro64%20NAS%20Case%20Exploded%20View%20Diagram.pdf[here]. Please refer back to this PDF document during assembly to verify correct orientation of individual components. -image:/documentation/images/NASCaseMain.png[Front View of the PINE64 NAS Case for the ROCKPro64,title="Front View of the PINE64 NAS Case for the ROCKPro64",width=400] +{{< figure src="/documentation/images/NASCaseMain.png" title="Front View of the PINE64 NAS Case for the ROCKPro64" width="400" >}} == What does the NAS Case house? -image:/documentation/images/NAS_Case_internals.jpg[Internal Layout of the NAS Case,title="Internal Layout of the NAS Case",width=200] +{{< figure src="/documentation/images/NAS_Case_internals.jpg" title="Internal Layout of the NAS Case" width="200" >}} The NAS Case can house the following components: @@ -38,7 +38,9 @@ When you purchase the NAS Case from the PINE store the following items are shipp == What other bare-minimum things do I need for a NAS build? -image:/documentation/images/PCIetoSATA.png[You will need the PCIe to SATA adapter from the PINE64 store to connect your disks to your ROCKPro64 board. \https://forum.pine64.org/showthread.php?tid=6932. WARNING: this adapter does not work well with two HDDs, https://forum.pine64.org/showthread.php?tid=6511,width=200] +You will need the PCIe to SATA adapter from the PINE64 store to connect your disks to your ROCKPro64 board. \https://forum.pine64.org/showthread.php?tid=6932. WARNING: this adapter does not work well with two HDDs, see https://forum.pine64.org/showthread.php?tid=6511: + +{{< figure src="/documentation/images/PCIetoSATA.png" width="200" >}} To assemble a functional NAS in the NAS Case you will require a number of additional parts. @@ -65,7 +67,7 @@ There are a few other things which you may wish to consider purchasing for your == Which software should I use? -image:/documentation/images/OMVGUI.png[The OMV WebGUI is easy to understand but also very robust. It offers easy installation of plugins, system administration and overview of available services,title="The OMV WebGUI is easy to understand but also very robust. It offers easy installation of plugins, system administration and overview of available services",width=200] +{{< figure src="/documentation/images/OMVGUI.png" title="The OMV WebGUI is easy to understand but also very robust. It offers easy installation of plugins, system administration and overview of available services" width="200" >}} If you are intending to build a home or small company NAS, then we strongly recommend you use link:/documentation/ROCKPro64/Software#openmediavault[Open Media Vault (OMV)]. OMV is an open source NAS solution that makes setting up user accounts, network shares and services a breeze. It also simplifies installing additional features (called plugins), such as: PLEX media server; Remote Desktop; Encryption; RSync; etc. @@ -90,9 +92,9 @@ You should now be left with a bare case ready for installation of the necessary === Step 2. Installing the ROCKPro64 into the NAS Case -image:/documentation/images/ROCKPro64inNASCase.jpg[Correct Placement of the ROCKPro64 in the empty case, with Ethernet; Power; and HDMI at the back of the NAS Case,title="Correct Placement of the ROCKPro64 in the empty case, with Ethernet; Power; and HDMI at the back of the NAS Case",width=300] +{{< figure src="/documentation/images/ROCKPro64inNASCase.jpg" title="Correct Placement of the ROCKPro64 in the empty case, with Ethernet; Power; and HDMI at the back of the NAS Case" width="300" >}} -image:/documentation/images/FrontIO.png[Front IO with IR and LED relay installed,title="Front IO with IR and LED relay installed",width=300] +{{< figure src="/documentation/images/FrontIO.png" title="Front IO with IR and LED relay installed" width="300" >}} Make sure nothing is plugged into your ROCKPro64 - including a micro SD card. If you intend to use a heatsink with your board then please install it now before proceeding. If you bought the heatsink from the Pine64 store it comes with thermal paste and/or a thermal pad. You can use one or the other (not both!). The thermal pad is easier to apply but the thermal paste should be better at cooling if properly applied. @@ -107,9 +109,9 @@ If you wish to install an IRx receiver into your case then you should also place === Step 3 PCIe to SATA adapter and Cabling -image:/documentation/images/DC_Location.jpg[DC header on the ROCKPro64 for the power cable,title="DC header on the ROCKPro64 for the power cable",width=200] +{{< figure src="/documentation/images/DC_Location.jpg" title="DC header on the ROCKPro64 for the power cable" width="200" >}} -image:/documentation/images/PCIeFittedSATAsockets.png[PCIe to SATA installed. Note the SATA connection orientation,title="PCIe to SATA installed. Note the SATA connection orientation",width=200] +{{< figure src="/documentation/images/PCIeFittedSATAsockets.png" title="PCIe to SATA installed. Note the SATA connection orientation" width="200" >}} With the board in place it's time to set up the PCIe to SATA adapter and do the cabling necessary to attach HDDs / SSDs. @@ -124,7 +126,7 @@ Have the cables hang outside the case or to the side for now so that they do not === Step 4. Installing HDDs / SSDs into the Holding Bracket -image:/documentation/images/Bracket_Orientation.png[Bracket Orientation in the NAS Case,title="Bracket Orientation in the NAS Case",width=300] +{{< figure src="/documentation/images/Bracket_Orientation.png" title="Bracket Orientation in the NAS Case" width="300" >}} The next step is to install HDDs/ SSDs into their holding bracket; 2.5 inches drives need to be installed at the very bottom of the bracket whi inchese 3.5 inches drives are at the top of the the bracket. @@ -138,7 +140,7 @@ Once the holding bracket is assembled and you have your drives mounted, please s === Step 5. Installing Extras (eMMC; WiFi BT module + SMA Antennas; 80mm Fan) -image:/documentation/images/80mmfan.png[The 80mm fan is a worthwhile addition to the NAS Case build,title="The 80mm fan is a worthwhile addition to the NAS Case build",width=200] +{{< figure src="/documentation/images/80mmfan.png" title="The 80mm fan is a worthwhile addition to the NAS Case build" width="200" >}} If you have additional peripherals, such as an eMMC or WiFi/BT module as well as the 80mm fan, then now is the right time to install them. If you have *none of the above*, please *proceed to step 6* of this guide. @@ -152,9 +154,9 @@ Plug in the fan at this stage of the installation and route the cable at the bot === Step 6. Installing the HDD / SSD Bracket and Routing Cables -image:/documentation/images/NASCAsewithdrives.jpg[Complete assembly of the NAS Case,title="Complete assembly of the NAS Case",width=300] +{{< figure src="/documentation/images/NASCAsewithdrives.jpg" title="Complete assembly of the NAS Case" width="300" >}} -image:/documentation/images/TopViewAssembly.png[Top view of a complete NAS Case Assembly,title="Top view of a complete NAS Case Assembly",width=300] +{{< figure src="/documentation/images/TopViewAssembly.png" title="Top view of a complete NAS Case Assembly" width="300" >}} Installing the HDD/SSD bracket into the case and wiring it up is the last step before closing up the case. diff --git a/content/documentation/Accessories/POT.adoc b/content/documentation/Accessories/POT.adoc index 066db0fd..fb21e4de 100644 --- a/content/documentation/Accessories/POT.adoc +++ b/content/documentation/Accessories/POT.adoc @@ -18,7 +18,7 @@ Peripheral On Top (POT) == USB/UART Programming/Console Adapter (PMPROG01) -image:/documentation/images/USB_Prog.JPG[] +{{< figure src="/documentation/images/USB_Prog.JPG" >}} === Feature @@ -43,17 +43,17 @@ https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx[Virtual https://www.silabs.com/products/mcu/Pages/USBXpress.aspx[USBXpress Driver] -image:/documentation/images/PMPROG01_Rev2_USB_Serial_Programmer-4.jpg[] +{{< figure src="/documentation/images/PMPROG01_Rev2_USB_Serial_Programmer-4.jpg" >}} -image:/documentation/images/PMPROG01_Rev2_USB_Serial_Programmer-1.jpg[] +{{< figure src="/documentation/images/PMPROG01_Rev2_USB_Serial_Programmer-1.jpg" >}} -image:/documentation/images/PMPROG01_Rev2_USB_Serial_Programmer-3.jpg[] +{{< figure src="/documentation/images/PMPROG01_Rev2_USB_Serial_Programmer-3.jpg" >}} -image:/documentation/images/PMWF01A_Wifi_Remote_IO_Rev3-1.jpg[] +{{< figure src="/documentation/images/PMWF01A_Wifi_Remote_IO_Rev3-1.jpg" >}} == POT: Veroboard (PMVRB01) -image:/documentation/images/PMVRB01_board_layout.JPG[] +{{< figure src="/documentation/images/PMVRB01_board_layout.JPG" >}} === Feature @@ -66,17 +66,17 @@ On board 4pcs of Tact switch On board XH5 2.54mm pitch connector for UART0 allow easy connection to USB/UART adapter for console access ``` -image:/documentation/images/PMVRB01_POT_Veroboard_Rev1-5.jpg[] +{{< figure src="/documentation/images/PMVRB01_POT_Veroboard_Rev1-5.jpg" >}} -image:/documentation/images/PMVRB01_POT_Veroboard_Rev1-3B.png[] +{{< figure src="/documentation/images/PMVRB01_POT_Veroboard_Rev1-3B.png" >}} -image:/documentation/images/PMVRB01_POT_Veroboard_Rev1-2B.png[] POT Veroboard on Pine A64 +{{< figure src="/documentation/images/PMVRB01_POT_Veroboard_Rev1-2B.png" >}} POT Veroboard on Pine A64 -image:/documentation/images/PMVRB01_POT_Veroboard_Rev1-1B.png[] POT Veroboard 2 board stack on top of Pine A64 +{{< figure src="/documentation/images/PMVRB01_POT_Veroboard_Rev1-1B.png" >}} POT Veroboard 2 board stack on top of Pine A64 == POT: Multi I2C Bus (PMI2C01) -image:/documentation/images/PMI2C01_Board_Layout.JPG[] +{{< figure src="/documentation/images/PMI2C01_Board_Layout.JPG" >}} === Feature @@ -108,19 +108,19 @@ https://wiki.pine64.org/images/d/d8/EnableI2cPullup.tar.gz[Program to Enable I2c https://pine.myggns.com/bozon/index.php?f=157836a20d7b7e[Multi I2c Bus Schematic] -image:/documentation/images/PMI2C01_I2C_Board_Rev1-1.jpg[] +{{< figure src="/documentation/images/PMI2C01_I2C_Board_Rev1-1.jpg" >}} -image:/documentation/images/PMI2C01_I2C_Board_Rev1-2.jpg[] +{{< figure src="/documentation/images/PMI2C01_I2C_Board_Rev1-2.jpg" >}} -image:/documentation/images/PMI2C01_I2C_Board_Rev1-3.jpg[] +{{< figure src="/documentation/images/PMI2C01_I2C_Board_Rev1-3.jpg" >}} -image:/documentation/images/PMVRB01_POT_Veroboard_Rev1-4.jpg[] +{{< figure src="/documentation/images/PMVRB01_POT_Veroboard_Rev1-4.jpg" >}} == POT: Shield Adapter (PMARD01) -image:/documentation/images/PMARD01_Shield_Adpater_POT.JPG[] +{{< figure src="/documentation/images/PMARD01_Shield_Adpater_POT.JPG" >}} -image:/documentation/images/PMARD01_Arduino_Pin_Mapping.JPG[] +{{< figure src="/documentation/images/PMARD01_Arduino_Pin_Mapping.JPG" >}} ``` Adapter for Arduino Shield @@ -135,7 +135,7 @@ https:/ / https://www.maximintegrated.com/en/products/analog/data-converters/ana == I2C Device: Humidity and Temperature Sensor (PMSDP01) -image:/documentation/images/PMSDO01_Dew_Point_Sensor.JPG[] +{{< figure src="/documentation/images/PMSDO01_Dew_Point_Sensor.JPG" >}} === Feature @@ -152,11 +152,11 @@ On board 3.3V regulator https://www.silabs.com/Support%20Documents/TechnicalDocs/Si7021-A20.pdf[Si7021-A20 Datasheet] -image:/documentation/images/PMSDO01_Dew_Point_Sensor_Rev1-1.jpg[] +{{< figure src="/documentation/images/PMSDO01_Dew_Point_Sensor_Rev1-1.jpg" >}} == I2C Device: Ambient Light Sensor (PMSAL01) -image:/documentation/images/PMSAL01_Light_Sensor.JPG[] +{{< figure src="/documentation/images/PMSAL01_Light_Sensor.JPG" >}} === Feature @@ -175,13 +175,13 @@ On board 3.3V regulator https://ams.com/eng/content/download/250094/975485/file/TSL2560_Datasheet_EN_v1.pdf[TSL2561T Datasheet] -image:/documentation/images/PMSAL01_Light_Sensor_Rev1-1.jpg[] +{{< figure src="/documentation/images/PMSAL01_Light_Sensor_Rev1-1.jpg" >}} -image:/documentation/images/PMSAL01_Light_Sensor_Rev1-2.jpg[] +{{< figure src="/documentation/images/PMSAL01_Light_Sensor_Rev1-2.jpg" >}} == WiFi Remote I2C (PMWF01A) -image:/documentation/images/PMWF01A.JPG[] +{{< figure src="/documentation/images/PMWF01A.JPG" >}} === Feature @@ -208,23 +208,23 @@ https://drive.google.com/file/d/0B0cEs0lxTtL3SDdCcWd0LVI2bk0/view?usp=sharing[ES https://bbs.espressif.com/[ESP8266 forum] -image:/documentation/images/PMWF01A_Wifi_Remote_IO_Rev3-2.jpg[] +{{< figure src="/documentation/images/PMWF01A_Wifi_Remote_IO_Rev3-2.jpg" >}} -image:/documentation/images/PMWF01A_Wifi_Remote_IO_Rev3-3.jpg[] +{{< figure src="/documentation/images/PMWF01A_Wifi_Remote_IO_Rev3-3.jpg" >}} -image:/documentation/images/PMWF01A_Wifi_Remote_IO_Rev3-4.jpg[] +{{< figure src="/documentation/images/PMWF01A_Wifi_Remote_IO_Rev3-4.jpg" >}} -image:/documentation/images/PMWF01A_Wifi_Remote_IO_Rev3-5.jpg[] +{{< figure src="/documentation/images/PMWF01A_Wifi_Remote_IO_Rev3-5.jpg" >}} == Inter Connection Wire -image:/documentation/images/I2c_Cable_Connection.JPG[] +{{< figure src="/documentation/images/I2c_Cable_Connection.JPG" >}} -image:/documentation/images/W5T4-01-15_UART_Programming_Console_Cable.JPG[] +{{< figure src="/documentation/images/W5T4-01-15_UART_Programming_Console_Cable.JPG" >}} -image:/documentation/images/W5T4-02-15_5Way_to_4Way_I2C_Cable.JPG[] +{{< figure src="/documentation/images/W5T4-02-15_5Way_to_4Way_I2C_Cable.JPG" >}} -image:/documentation/images/W4T4-03-15_4Way_I2C_Cable.JPG[] +{{< figure src="/documentation/images/W4T4-03-15_4Way_I2C_Cable.JPG" >}} -image:/documentation/images/W5T5-04-15_5Way_I2C_Cable.JPG[] +{{< figure src="/documentation/images/W5T5-04-15_5Way_I2C_Cable.JPG" >}} diff --git a/content/documentation/Accessories/Wifi_remote_i2c.adoc b/content/documentation/Accessories/Wifi_remote_i2c.adoc index 82669168..d8e7d6dd 100644 --- a/content/documentation/Accessories/Wifi_remote_i2c.adoc +++ b/content/documentation/Accessories/Wifi_remote_i2c.adoc @@ -9,12 +9,12 @@ menu: weight: --- -image:/documentation/images/PMWF01A_Description.jpg[PMWF01A: Wifi Remote I2c Module,title="PMWF01A: Wifi Remote I2c Module"] +{{< figure src="/documentation/images/PMWF01A_Description.jpg" title="PMWF01A: Wifi Remote I2c Module" >}} == Quick Start Guide === Hardware Setup -image:/documentation/images/PMWF01A_Wifi_Remote_IO_Rev3-1.jpg[Hardware Setup,title="Hardware Setup"] +{{< figure src="/documentation/images/PMWF01A_Wifi_Remote_IO_Rev3-1.jpg" title="Hardware Setup" >}} * Make sure that the driver for USB/UART Programming/Console Adapter (PMPROG01) is properly install and the PC is detected it as Comm Port. * The USB/UART Bridge is base on http://www.silabs.com/products/interface/usb-bridges/classic-usb-bridges/Pages/usb-to-uart-bridge.aspx[Silicon Lab CP2012 chipset]. @@ -22,14 +22,14 @@ image:/documentation/images/PMWF01A_Wifi_Remote_IO_Rev3-1.jpg[Hardware Setup,tit * Connect the USB/UART Programming/Console Adapter (PMPROG01) to the Wifi Remote I2c Device. * You can power-up the WiFI Remote I2c module through the USB Bus for configuration and programming. -image:/documentation/images/Wr_USB_Adpt_5v.jpg[width=100] +{{< figure src="/documentation/images/Wr_USB_Adpt_5v.jpg" width="100" >}} Place the jumper J2 on USB/UART Programming/Console Adapter (PMPROG01) to 5V output selection. === Setting Configuration -image:/documentation/images/Wr_Termite2.JPG[Termite Setup Screen,title="Termite Setup Screen"] -image:/documentation/images/Wr_cfghelp_scr.JPG[Help Command,title="Help Command"] +{{< figure src="/documentation/images/Wr_Termite2.JPG" title="Termite Setup Screen" >}} +{{< figure src="/documentation/images/Wr_cfghelp_scr.JPG" title="Help Command" >}} * For windows system, you can use terminal emulator program Termite to configure the device. * Termite can be downloaded at http://www.compuphase.com/software_termite.htm[CompuPhase Website ] @@ -37,7 +37,7 @@ image:/documentation/images/Wr_cfghelp_scr.JPG[Help Command,title="Help Command" * Follow the setting according to the setup screen capture. (57600Baud 8-N-1) * Once Termite configuration is done, press 'OK' to save the setting. * On the Wifi Remote I2c Device, Press the configuration button to allow the device to go into configuration mode. -image:/documentation/images/Wr_Config_Mode_Sw.jpg[] +{{< figure src="/documentation/images/Wr_Config_Mode_Sw.jpg" >}} Press Config Mode button to go into configuration mode * Type 'help' to show the command available for configuration. @@ -68,7 +68,7 @@ Press Config Mode button to go into configuration mode * To login into the server, telnet into localhost port 10000 telnet localhost 10000 -image:/documentation/images/Wr_putty_login.JPG[PineWifiServer Login Screen,title="PineWifiServer Login Screen"] +{{< figure src="/documentation/images/Wr_putty_login.JPG" title="PineWifiServer Login Screen" >}} * To show current connect Wifi Remote I2c type 'list' in small capital letter. * To see all available command, type 'help'. @@ -89,18 +89,18 @@ image:/documentation/images/Wr_putty_login.JPG[PineWifiServer Login Screen,title ./WifiAppDemo * The Application will connect the PineWifiServer currently running in the localhost. -image:/documentation/images/Wr_demo_application.JPG[] +{{< figure src="/documentation/images/Wr_demo_application.JPG" >}} Example of screen shot with WifiAppDemo polling multiple Wifi Remote I2c with Ambient Light Sensor and Humidity/Temperature Sensor connected on it. The speed for each round of polling is 1 second per poll. == Firmware Upgrade === Hardware Setup -image:/documentation/images/Wr_Programming_Mode_Jumper.jpg[width=100] +{{< figure src="/documentation/images/Wr_Programming_Mode_Jumper.jpg" width="100" >}} Short Jumper S2 on the WiFI Remote I2c module (before power up the board) to allow the board to go in to firmware programming mode. -image:/documentation/images/PMWF01A_Wifi_Remote_IO_Rev3-1.jpg[Hardware Setup,title="Hardware Setup"] +{{< figure src="/documentation/images/PMWF01A_Wifi_Remote_IO_Rev3-1.jpg" title="Hardware Setup" >}} * Make sure that the driver for USB/UART Programming/Console Adapter (PMPROG01) is properly install and the PC is detected it as Comm Port. * The USB/UART Bridge is base on http://www.silabs.com/products/interface/usb-bridges/classic-usb-bridges/Pages/usb-to-uart-bridge.aspx[Silicon Lab CP2012 chipset]. @@ -108,7 +108,7 @@ image:/documentation/images/PMWF01A_Wifi_Remote_IO_Rev3-1.jpg[Hardware Setup,tit * Connect the USB/UART Programming/Console Adapter (PMPROG01) to the Wifi Remote I2c Device. * You can power-up the WiFI Remote I2c module through the USB Bus for configuration and programming. -image:/documentation/images/Wr_USB_Adpt_5v.jpg[width=100] +{{< figure src="/documentation/images/Wr_USB_Adpt_5v.jpg" width="100" >}} Place the jumper J2 on USB/UART Programming/Console Adapter (PMPROG01) to 5V output selection. === Software Setup @@ -117,7 +117,7 @@ Place the jumper J2 on USB/UART Programming/Console Adapter (PMPROG01) to 5V out * Download the windows Python base Flash Download Tools by Espressif from http://espressif.com/en/products/hardware/esp8266ex/resources[Espressif website]. * Setup the ESP Flash Download tools according to the screen short. -image:/documentation/images/Esp_prog_tool.JPG[width=400] +{{< figure src="/documentation/images/Esp_prog_tool.JPG" width="400" >}} * Make sure that the firmware address is set correctly. Baud rate is set to 115200baud and Com Port is set according to the Virtual Com Port of your PC. * Once the ESP Flash Download tool and hardware is setup properly, press the 'Start' button to start the firmware uploading process. @@ -134,7 +134,7 @@ image:/documentation/images/Esp_prog_tool.JPG[width=400] == I/O Pin Out -image:/documentation/images/IO_Pin.JPG[] +{{< figure src="/documentation/images/IO_Pin.JPG" >}} == Download diff --git a/content/documentation/Clusterboard/Layout.adoc b/content/documentation/Clusterboard/Layout.adoc index ccc53496..676bcb3c 100644 --- a/content/documentation/Clusterboard/Layout.adoc +++ b/content/documentation/Clusterboard/Layout.adoc @@ -9,7 +9,7 @@ menu: weight: 1 --- -image:/documentation/Clusterboard/images/clusterboard_labels.png[title="The Clusterboard with labels",width=400] +{{< figure src="/documentation/Clusterboard/images/clusterboard_labels.png" title="The Clusterboard with labels" width="400" >}} [cols="1,1"] |=== @@ -76,9 +76,9 @@ The 20-pin expansion connector is the part 10 decribed in the section above, ava == SOPINE Module -image:/documentation/SOPINE/images/sopine_front_labels.png[Front view of the SOPINE module with labels,title="Front view of the SOPINE module with labels",width=400] +{{< figure src="/documentation/SOPINE/images/sopine_front_labels.png" title="Front view of the SOPINE module with labels" width="400" >}} -image:/documentation/SOPINE/images/sopine_back_labels.png[Rear view of the SOPINE module with labels,title="Rear view of the SOPINE module with labels",width=400] +{{< figure src="/documentation/SOPINE/images/sopine_back_labels.png" title="Rear view of the SOPINE module with labels" width="400" >}} [cols="1,1"] |=== diff --git a/content/documentation/Clusterboard/_index.adoc b/content/documentation/Clusterboard/_index.adoc index 63e5bb9b..6cd7066f 100644 --- a/content/documentation/Clusterboard/_index.adoc +++ b/content/documentation/Clusterboard/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/Clusterboard/images/Clusterboard_rev_2.2.jpg[Front view of the Clusterboard (revision 2.2),title="Front view of the Clusterboard (revision 2.2)",width=400] +{{< figure src="/documentation/Clusterboard/images/Clusterboard_rev_2.2.jpg" title="Front view of the Clusterboard (revision 2.2)" width="400" >}} The *Clusterboard* is a PINE64 board that makes it possible to set up a compact cluster of headless ARM-based single-board computers. It can hold up to a total of seven link:/documentation/SOPINE[SOPINE] or link:/documentation/SOEDGE[SOEDGE] modules. The Clusterboard is an open-hardware project, but please note that it does not mean this project is "OSH" compliant. diff --git a/content/documentation/General/PineModems.adoc b/content/documentation/General/PineModems.adoc index 2806ff78..09b3f131 100644 --- a/content/documentation/General/PineModems.adoc +++ b/content/documentation/General/PineModems.adoc @@ -131,7 +131,7 @@ WARNING: The following instructions are directed towards expert-level users and The System partition is mounted as read-only mode, but the data partition is writable. It might be possible, if there's an unexpected reset or power is lost while running, that the data partition gets corrupt and thus unable to boot. -image:/documentation/images/Pinephone-EG25-Recovery.jpg[PinePhone USB_BOOT test points,title="PinePhone USB_BOOT test points"] +{{< figure src="/documentation/images/Pinephone-EG25-Recovery.jpg" title="PinePhone USB_BOOT test points" >}} The modem has 4 different boot modes: diff --git a/content/documentation/Ox64/Software/Flashing.adoc b/content/documentation/Ox64/Software/Flashing.adoc index 260b6539..58caa44a 100644 --- a/content/documentation/Ox64/Software/Flashing.adoc +++ b/content/documentation/Ox64/Software/Flashing.adoc @@ -243,7 +243,7 @@ Expected result: === Option 3: Generic UART adapter -image:/documentation/Ox64/images/ox64_pinout.png[Ox64 pinout,title="Ox64 pinout", 300, float="right"] +{{< figure src="/documentation/Ox64/images/ox64_pinout.png" title="Ox64 pinout" >}} Check that your serial adapter is on the link:/documentation/Ox64/Further_information/Compatible_UARTs/[Compatible UARTs] list. You will (most likely) only have one serial interface available to you; unlike the previous options you will be using this same serial interface for both flashing and testing the system. diff --git a/content/documentation/Oz64/Features.adoc b/content/documentation/Oz64/Features.adoc index df74548e..0f5b02c2 100644 --- a/content/documentation/Oz64/Features.adoc +++ b/content/documentation/Oz64/Features.adoc @@ -13,7 +13,7 @@ menu: Board Dimensions: 85mm x 56mm x 18.8mm, see the https://files.pine64.org/doc/rock64/rock64%20board%20dimension.pdf[model-B board dimension drawing] -image:/documentation/Oz64/images/Oz64_3D_model.png[The Oz64 3D model,title="The Oz64 3D model", 300] +{{< figure src="/documentation/Oz64/images/Oz64_3D_model.png" title="The Oz64 3D model" width="300" >}} == Network @@ -42,7 +42,7 @@ Input Power: +5V @2A with 3.5mm/1.35mm Type H Barrel type DC connector (@1.5A wi Based on the https://en.sophgo.com/sophon-u/product/introduce/sg200x.html[Sophgo SG-200x] -image:/documentation/Oz64/images/SG2000_Block_Diagram.png[SG2000 block diagram,title="SG2000 block diagram", 300] +{{< figure src="/documentation/Oz64/images/SG2000_Block_Diagram.png" title="SG2000 block diagram" width="300" >}} === CPU Architecture diff --git a/content/documentation/Oz64/_index.adoc b/content/documentation/Oz64/_index.adoc index 19dde8cc..ddddcea2 100644 --- a/content/documentation/Oz64/_index.adoc +++ b/content/documentation/Oz64/_index.adoc @@ -13,4 +13,4 @@ The *Oz64* is a low cost single-board computer based on the Sophgo SG2000 SoC wi The Oz64 SBC comes in a model-B form-factor, has a microSD card slot, an eMMC plugin connector, an USB 2.0 Type-A host port, and many other peripheral interfaces for makers to integrate with sensors and other devices. -image:/devices/images/oz64.jpg[The Oz64,title="The Oz64", 300] \ No newline at end of file +{{< figure src="/devices/images/oz64.jpg" title="The Oz64" width="300" >}} \ No newline at end of file diff --git a/content/documentation/PINE_H64_Model_A/_index.adoc b/content/documentation/PINE_H64_Model_A/_index.adoc index ad71ef18..61600aa8 100644 --- a/content/documentation/PINE_H64_Model_A/_index.adoc +++ b/content/documentation/PINE_H64_Model_A/_index.adoc @@ -9,6 +9,6 @@ menu: weight: --- -image:images/pineh64modela.jpg[The PINE H64 Model A,title="The PINE H64 Model A",width=400] +{{< figure src="images/pineh64modela.jpg" title="The PINE H64 Model A" width="400" >}} The *PINE H64 Model A* is a discontinued Single Board Computer by _PINE64_. It is powered by an Allwinner "H6" Quad-Core ARM Cortex A53 64-Bit Processor with a MALI T-722 GPU. \ No newline at end of file diff --git a/content/documentation/PINE_H64_Model_B/Software/Releases.adoc b/content/documentation/PINE_H64_Model_B/Software/Releases.adoc index a4bfa798..643263ef 100644 --- a/content/documentation/PINE_H64_Model_B/Software/Releases.adoc +++ b/content/documentation/PINE_H64_Model_B/Software/Releases.adoc @@ -15,7 +15,7 @@ The following releases are for the PINE H64 Model B === Armbian -image:/documentation/images/armbian.png[width=100] +{{< figure src="/documentation/images/armbian.png" width="100" >}} *Armbian* is a Linux distribution designed for ARM boards. They are usually Debian or Ubuntu flavored. @@ -25,7 +25,7 @@ Download: === Manjaro ARM -image:/documentation/images/Manjaro-logo.svg[width=100] +{{< figure src="/documentation/images/Manjaro-logo.svg" width="100" >}} *Manjaro* is a user-friendly Linux distribution based on the independently developed Arch operating system. To learn more about Manjaro please visit the https://forum.manjaro.org/tags/manjaroarm[Manjaro Forum]. Download: @@ -34,7 +34,7 @@ Download: === DietPi -image:/documentation/images/dietpi.png[width=100] +{{< figure src="/documentation/images/dietpi.png" width="100" >}} *DietPi* is a lightweight yet easy to setup and feature-rich Linux distribution, based on Debian. To find out more about DietPi, please visit the https://dietpi.com/docs/[official documentation]. Discuss the PINE H64 build on the https://forum.pine64.org/showthread.php?tid=12531[PINE64 forum thread]. @@ -52,7 +52,7 @@ Download: === LibreELEC -image:/documentation/images/libreelec.jpg[width=100] +{{< figure src="/documentation/images/libreelec.jpg" width="100" >}} *LibreELEC* is a "Just enough OS" Linux distribution combining the Kodi media center with an operating system. @@ -68,7 +68,7 @@ Notes: === FreeBSD -image:/documentation/images/FreeBSD.jpeg[width=100] +{{< figure src="/documentation/images/FreeBSD.jpeg" width="100" >}} *FreeBSD* is an operating system used to power modern servers, desktops, and embedded platforms. To learn more about FreeBSD, please visit https://www.FreeBSD.org/[FreeBSD main page]. @@ -82,7 +82,7 @@ Notes: === NetBSD -image:/documentation/images/netbsd.png[width=100] +{{< figure src="/documentation/images/netbsd.png" width="100" >}} *NetBSD* is a free, fast, secure, and highly portable Unix-like Open Source operating system. To learn more about NetBSD please visit https://www.netbsd.org/[NetBSD main page]. diff --git a/content/documentation/PINE_H64_Model_B/_index.adoc b/content/documentation/PINE_H64_Model_B/_index.adoc index 1d38f185..4ae0f04b 100644 --- a/content/documentation/PINE_H64_Model_B/_index.adoc +++ b/content/documentation/PINE_H64_Model_B/_index.adoc @@ -9,6 +9,6 @@ menu: weight: --- -image:images/pineh64modelb.png[The PINE H64 Model B,title="The PINE H64 Model B",width=400] +{{< figure src="images/pineh64modelb.png" title="The PINE H64 Model B" width="400" >}} The *PINE H64 Model B* is a Single Board Computer by _PINE64_. It is powered by an Allwinner "H6" Quad-Core ARM Cortex A53 64-Bit Processor with a MALI T-722 GPU. The PINE H64 is equipped with up to 3GB of LPDDR3 PC-1600 system memory and 128Mbit of SPI boot Flash. There is also an optional eMMC module (up to 128GB) and a microSD slot for booting. The board is equipped with an onboard 802.11n Wifi/BT chipset, one USB 3.0 host port, two USB 2.0 host ports, Gigabit Ethernet, a PI-2 GPIO bus, an Euler GPIO bus as well as many other peripheral device interfaces such as UART, SPI, and I^2^C. \ No newline at end of file diff --git a/content/documentation/Phone_Accessories/Fingerprint_reader.adoc b/content/documentation/Phone_Accessories/Fingerprint_reader.adoc index aa01741a..e5d35dfe 100644 --- a/content/documentation/Phone_Accessories/Fingerprint_reader.adoc +++ b/content/documentation/Phone_Accessories/Fingerprint_reader.adoc @@ -11,7 +11,7 @@ menu: Store page: https://pine64.com/product/pinephone-pinephone-pro-fingerprint-reader-add-on-case/[pine64.com] -image:/documentation/images/PinePhone-FP-Addon.jpg[width=250] +{{< figure src="/documentation/images/PinePhone-FP-Addon.jpg" width="250" >}} Uses the pogo pins to interface a high quality fingerprint sensor, which uses open firmware for it's i2c bridge, and can also be used for gesture navigation thanks to it's ability to detect directional swipes. diff --git a/content/documentation/Phone_Accessories/Keyboard.adoc b/content/documentation/Phone_Accessories/Keyboard.adoc index d9dde696..cad32108 100644 --- a/content/documentation/Phone_Accessories/Keyboard.adoc +++ b/content/documentation/Phone_Accessories/Keyboard.adoc @@ -9,13 +9,13 @@ menu: weight: 3 --- -image:/documentation/images/PP_KB_Front-1024x576.jpg[Picture of the PinePhone (Pro) Keyboard,title="Picture of the PinePhone (Pro) Keyboard",width=400] +{{< figure src="/documentation/images/PP_KB_Front-1024x576.jpg" title="Picture of the PinePhone (Pro) Keyboard" width="400" >}} The *PinePhone (Pro) Keyboard Case* is a case compatible with the link:/documentation/PinePhone[PinePhone] and link:/documentation/PinePhone_Pro[PinePhone Pro], adding a keyboard functionality to the phone. It features a clam-shell design and uses the pogo pins located on the smartphone’s midsection and attaches by replacing the default back cover. This add-on effectively turns the PinePhone (Pro) into a PDA with an in-built LTE modem. == Getting started -image:/documentation/images/Ppkb_description.png[] +{{< figure src="/documentation/images/Ppkb_description.png" >}} ① Contact pads @@ -106,7 +106,7 @@ In *Sxmo* disabling the keyboard is not required, as the keyboard will only show The keyboard features a default layout (pictured below) created and agreed upon by the community. The keyboard layout can be altered using software as well as by physically repositioning keycaps. All keycaps, with the _exception_ of space and return keys, can be easily and safely relocated for alternative layouts corresponding to software settings. -image:/documentation/images/Ppkb_layout2.png[The keyboard layout how the keys were originally intended] +{{< figure src="/documentation/images/Ppkb_layout2.png" title="The keyboard layout how the keys were originally intended" >}} == Keyboard firmware diff --git a/content/documentation/Phone_Accessories/LoRa.adoc b/content/documentation/Phone_Accessories/LoRa.adoc index e908075e..6b2177be 100644 --- a/content/documentation/Phone_Accessories/LoRa.adoc +++ b/content/documentation/Phone_Accessories/LoRa.adoc @@ -11,7 +11,7 @@ menu: Store page: https://pine64.com/product/pinephone-pinephone-pro-pindio-lora-add-on-case/[pine64.com] -image:/documentation/images/PP_LoRa.jpg[width=250] +{{< figure src="/documentation/images/PP_LoRa.jpg" width="250" >}} Uses the pogo pins to interface a Semtech SX1262 LoRa module with the PinePhone (Pro). diff --git a/content/documentation/Phone_Accessories/Qi_wireless_charging.adoc b/content/documentation/Phone_Accessories/Qi_wireless_charging.adoc index 5a0bc48e..471060c8 100644 --- a/content/documentation/Phone_Accessories/Qi_wireless_charging.adoc +++ b/content/documentation/Phone_Accessories/Qi_wireless_charging.adoc @@ -18,7 +18,7 @@ Album of damage caused by reverse current: https://imgur.com/a/dJsp5wD Until the cause of this is determined, it is recommended NOT to use the wireless charging add-on. ==== -image:/documentation/images/PinePhone-Wireless-charger.jpg[width=250] +{{< figure src="/documentation/images/PinePhone-Wireless-charger.jpg" width="250" >}} Uses the pogo pins to supply Qi Wireless and Wireless Power Consortium compatible charging. No software required. diff --git a/content/documentation/PineBuds_Pro/Features.adoc b/content/documentation/PineBuds_Pro/Features.adoc index 28cd0017..5560e7eb 100644 --- a/content/documentation/PineBuds_Pro/Features.adoc +++ b/content/documentation/PineBuds_Pro/Features.adoc @@ -11,7 +11,7 @@ menu: The PineBuds Pro's buds are based on the http://www.bestechnic.com/home/product/index/cate_id/6[BES 2300YP]. -image:/documentation/images/BES2300YP_Block_Diagram.jpg[width=430] +{{< figure src="/documentation/images/BES2300YP_Block_Diagram.jpg" width="430" >}} CPU Features: diff --git a/content/documentation/PineBuds_Pro/_index.adoc b/content/documentation/PineBuds_Pro/_index.adoc index 9818827f..54d39729 100644 --- a/content/documentation/PineBuds_Pro/_index.adoc +++ b/content/documentation/PineBuds_Pro/_index.adoc @@ -9,7 +9,7 @@ menu: weight: 1 --- -image:images/pinebudspro.jpg[The PineBuds Pro,title="The PineBuds Pro",width=400] +{{< figure src="images/pinebudspro.jpg" title="The PineBuds Pro" width="400" >}} The *PineBuds Pro* are open firmware capable ANC wireless earbuds. Some of the notable features include their light weight, 3 Microphones, ANC (Active Noise Cancellation), ENC (Environment Noise Cancellation) and high fidelity 6mm speaker. It is a fully community-driven side-project which anyone can contribute to, allowing you to keep control of your device even though hardware is proprietary. diff --git a/content/documentation/PineCone/Further_information/BL602_specifications.adoc b/content/documentation/PineCone/Further_information/BL602_specifications.adoc index 144b0833..6f01ac40 100644 --- a/content/documentation/PineCone/Further_information/BL602_specifications.adoc +++ b/content/documentation/PineCone/Further_information/BL602_specifications.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/BL602_Block_Diagram.jpg[] +{{< figure src="/documentation/images/BL602_Block_Diagram.jpg" >}} CPU: diff --git a/content/documentation/PineCone/Further_information/Pinenut-12S_Module_information.adoc b/content/documentation/PineCone/Further_information/Pinenut-12S_Module_information.adoc index 5b5dfae1..3f24f126 100644 --- a/content/documentation/PineCone/Further_information/Pinenut-12S_Module_information.adoc +++ b/content/documentation/PineCone/Further_information/Pinenut-12S_Module_information.adoc @@ -9,8 +9,8 @@ menu: weight: --- -image:/documentation/images/NUT-12S_module-front.jpg[width=200] -image:/documentation/images/NUT-12S_module-back.jpg[width=200] +{{< figure src="/documentation/images/NUT-12S_module-front.jpg" width="200" >}} +{{< figure src="/documentation/images/NUT-12S_module-back.jpg" width="200" >}} GPIO definition: https://files.pine64.org/doc/Pinenut/NUT-12S%20GPIO%20Definition%20ver%201.0.pdf[Pinenut-12S GPIO Definition ver 1.0] diff --git a/content/documentation/PineCone/_index.adoc b/content/documentation/PineCone/_index.adoc index 219e7bba..06b85635 100644 --- a/content/documentation/PineCone/_index.adoc +++ b/content/documentation/PineCone/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/Pine64_BL602_EVB_photo-3-small.jpg[width=602] +{{< figure src="/documentation/images/Pine64_BL602_EVB_photo-3-small.jpg" width="602" >}} The *PineCone* is a BL602 evaluation board, which was developed with the goal to challenge the open source community to achieve blob-free and free and open source WiFi and Bluetooth, see the https://www.pine64.org/2020/10/28/nutcracker-challenge-blob-free-wifi-ble/[Nutcracker Challenge]. diff --git a/content/documentation/PineCube/Cases.adoc b/content/documentation/PineCube/Cases.adoc index d193458f..f14cc3ed 100644 --- a/content/documentation/PineCube/Cases.adoc +++ b/content/documentation/PineCube/Cases.adoc @@ -9,8 +9,8 @@ menu: weight: 3 --- -image:/documentation/PineCube/images/PineCube_Case-1.jpg[] -image:/documentation/PineCube/images/PineCube_Case-2.jpg[] +{{< figure src="/documentation/PineCube/images/PineCube_Case-1.jpg" >}} +{{< figure src="/documentation/PineCube/images/PineCube_Case-2.jpg" >}} Model: diff --git a/content/documentation/PineCube/Pinout.adoc b/content/documentation/PineCube/Pinout.adoc index 3d6497bf..a8c782a3 100644 --- a/content/documentation/PineCube/Pinout.adoc +++ b/content/documentation/PineCube/Pinout.adoc @@ -9,7 +9,7 @@ menu: weight: 2 --- -image:/documentation/PineCube/images/PineCube_GPIO_Pinout.png[width=700] +{{< figure src="/documentation/PineCube/images/PineCube_GPIO_Pinout.png" width="700" >}} Note: Pin1 is marked on the board by a white dot on the PCB. See the https://wiki.pine64.org/wiki/File:PineCube_GPIO.pdf[PDF] and https://pine64.gami.ee/pinecube/gpio-pinout.html[HTML] for details. diff --git a/content/documentation/PineCube/Software/Armbian_notes.adoc b/content/documentation/PineCube/Software/Armbian_notes.adoc index 684aafb9..99db0f4c 100644 --- a/content/documentation/PineCube/Software/Armbian_notes.adoc +++ b/content/documentation/PineCube/Software/Armbian_notes.adoc @@ -37,7 +37,7 @@ After this you can either use the Arduino IDE and it's Serial monitor after sele `screen /dev/ttyACM0 115200` -image:/documentation/images/ArduinoSerialPinecube.jpg[width=400] +{{< figure src="/documentation/images/ArduinoSerialPinecube.jpg" width="400" >}} == Serial connection using pinephone/pinebook pro serial debugging cable diff --git a/content/documentation/PineCube/Software/Releases.adoc b/content/documentation/PineCube/Software/Releases.adoc index 4e925bc8..0f8a2434 100644 --- a/content/documentation/PineCube/Software/Releases.adoc +++ b/content/documentation/PineCube/Software/Releases.adoc @@ -11,7 +11,7 @@ menu: == Armbian -image:/documentation/images/armbian.png[width=100] +{{< figure src="/documentation/images/armbian.png" width="100" >}} *Armbian* is a Linux distribution designed for ARM boards. They are usually Debian or Ubuntu flavored. @@ -25,7 +25,7 @@ Notes: == NixOS -image:/documentation/images/NixOS.webp[width=100] +{{< figure src="/documentation/images/NixOS.webp" width="100" >}} *NixOS* is a Linux distribution built on top of the Nix package manager using declarative configuration to allow reliable system upgrades. diff --git a/content/documentation/PineCube/Tuning/Sound_controls.adoc b/content/documentation/PineCube/Tuning/Sound_controls.adoc index 669602f3..2d6b1ad6 100644 --- a/content/documentation/PineCube/Tuning/Sound_controls.adoc +++ b/content/documentation/PineCube/Tuning/Sound_controls.adoc @@ -11,5 +11,5 @@ menu: Note that sound is only currently available with special patches on top of a 5.13.13 or higher kernel with Armbian or NixOS. Once you have a kernel that supports sound you can install alsa-utils to get the alsamixer tool. The following mixer settings have been found to work with both playback and record. Note that you'll need to press F5 to get the capture controls and space bar to turn on/off capture for a device. The speaker dangles on a wire from the device. The microphone is located about 1cm below the lens on the front facing circuit board. -image:/documentation/PineCube/images/Pinecube_sound_mixer.png[width=800] +{{< figure src="/documentation/PineCube/images/Pinecube_sound_mixer.png" width="800" >}} diff --git a/content/documentation/PineCube/_index.adoc b/content/documentation/PineCube/_index.adoc index 44dffd20..a2d2c64d 100644 --- a/content/documentation/PineCube/_index.adoc +++ b/content/documentation/PineCube/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/PineCube/images/PineCube.jpg[The PineCube,title="The PineCube",width=400] +{{< figure src="/documentation/PineCube/images/PineCube.jpg" title="The PineCube" width="400" >}} The *PineCube* is a small, low-powered, open source IP camera. Whether you’re a parent looking for a FOSS baby-camera, a privacy oriented shop keeper, home owner looking for a security camera, or perhaps a tinkerer needing a camera for your drone – the CUBE can be the device for you. It features an 5MPx Omnivision sensor and IR LEDs for night vision, as well as Power Over Ethernet, as well as a microphone. diff --git a/content/documentation/PineNote/Development/Flashing.adoc b/content/documentation/PineNote/Development/Flashing.adoc index 780f16de..8a1c0489 100644 --- a/content/documentation/PineNote/Development/Flashing.adoc +++ b/content/documentation/PineNote/Development/Flashing.adoc @@ -75,7 +75,7 @@ If the bootloader is broken/corrupted, you cannot get to Maskrom without opening Once inside, short TP1301 (GND) and TP1302 (eMMC_D0/FLASH_D0) with a small tweezers, this is how it looks on board view (credit to Caleb): -image:/documentation/PineNote/images/PineNote_Maskrom_TP.png[width=500px] +{{< figure src="/documentation/PineNote/images/PineNote_Maskrom_TP.png" width="500px" >}} === Success diff --git a/content/documentation/PineNote/Development/UART.adoc b/content/documentation/PineNote/Development/UART.adoc index 61882f64..75fc354c 100644 --- a/content/documentation/PineNote/Development/UART.adoc +++ b/content/documentation/PineNote/Development/UART.adoc @@ -9,7 +9,7 @@ menu: weight: 4 --- -image::/documentation/PineNote/images/Pinenote-uart-dongle.jpeg[Basic non-stock PineNote UART dongle,title="Basic non-stock PineNote UART dongle",width=400] +{{< figure src="/documentation/PineNote/images/Pinenote-uart-dongle.jpeg" title="Basic non-stock PineNote UART dongle" width="400" >}} This page contains information on creating and using a https://en.wikipedia.org/wiki/Universal_asynchronous_receiver-transmitter[UART] dongle for the PineNote. The PineNote was shipped with a compatible UART dongle, but replacements are not available to order in case of loss or hardware fault. Thankfully it is not difficult to make your own from easily-acquired components and a small bit of soldering. @@ -29,8 +29,8 @@ The PineNote factory firmware runs UART at a baud rate of 1500000 bps, 8 data bi The stock UART dongle included with the PineNote was a simple device plugging directly into the PineNote's USB-C port. The dongle exposed a female USB-C port, which the user plugged into to get UART access. This design unfortunately ruled out passthrough USB connections, where the user connects to the PineNote via UART and USB simultaneously. The dongle is not currently available for purchase. -image::/documentation/PineNote/images/Pinenote-stock-uart-dongle-front.jpg[Front,title="Front",width=200] -image::/documentation/PineNote/images/Pinenote-stock-uart-dongle-back.jpg[Back,title="Back",width=200] +{{< figure src="/documentation/PineNote/images/Pinenote-stock-uart-dongle-front.jpg" title="Front" width="200" >}} +{{< figure src="/documentation/PineNote/images/Pinenote-stock-uart-dongle-back.jpg" title="Back" width="200" >}} == Creating a dongle @@ -67,7 +67,7 @@ All other necessary components of our UART dongle are readily & cheaply availabl === Splicing resistors -image::/documentation/PineNote/images/PineNote-UART-Y-pull-up-resistor-cable.jpg[title="The desired end result; wrap removed from resistors for illustration purposes.",width=400] +{{< figure src="/documentation/PineNote/images/PineNote-UART-Y-pull-up-resistor-cable.jpg" title="The desired end result; wrap removed from resistors for illustration purposes." width="400" >}} This is the only difficult part of the whole process. Your goal is to create a Y-shaped jump wire with 1,000 Ohm through-hole resistors spliced into each of the twin arms. The solitary leg will connect to a 3.3V source on your USB-UART adapter. The twin arms will connect to the configuration channel pins on your USB-C breakout board. Per the USB-C standard, when these pins are pulled high this indicates the device should enter https://en.wikipedia.org/wiki/USB-C#Debug_Accessory_Mode[Debug Accessory Mode]; connecting them to a voltage source & limiting the current with https://www.electronics-tutorials.ws/logic/pull-up-resistor.html[pull-up resistors] accomplishes this. diff --git a/content/documentation/PineNote/Further_information/Closed_Case_UART.adoc b/content/documentation/PineNote/Further_information/Closed_Case_UART.adoc index c3f26de3..8e51eca3 100644 --- a/content/documentation/PineNote/Further_information/Closed_Case_UART.adoc +++ b/content/documentation/PineNote/Further_information/Closed_Case_UART.adoc @@ -39,7 +39,7 @@ It should be possible to make the UART connection and breakout cable magically f == Resolution -image:/documentation/images/PineNote_USB-C_DAM_Schematic_Addition.png[This proposed circuitry is added to the PineNote v1.1 schematic,title="This proposed circuitry is added to the PineNote v1.1 schematic"] +{{< figure src="/documentation/images/PineNote_USB-C_DAM_Schematic_Addition.png" title="This proposed circuitry is added to the PineNote v1.1 schematic" >}} On August 19, 2021, TL posted the results of the hardware team's efforts. This includes link::File:PineNote USB-C DAM Schematic Addition.png[], shown on this page, as well as the following additional documentation: diff --git a/content/documentation/PineNote/Further_information/Press.adoc b/content/documentation/PineNote/Further_information/Press.adoc index 2e2ddf63..43a93bda 100644 --- a/content/documentation/PineNote/Further_information/Press.adoc +++ b/content/documentation/PineNote/Further_information/Press.adoc @@ -15,8 +15,8 @@ Vector images and pictures for the PineNote you can freely use for projects and Background ideas: -image::/documentation/images/Pinenotebg1.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0",width=400] -image::/documentation/images/Pinenotebg2.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0",width=400] -image::/documentation/images/Pinenotebg3.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0",width=400] -image::/documentation/images/Pinenotebg4.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0",width=400] +{{< figure src="/documentation/images/Pinenotebg1.png" title="Author: Funeral, License: CC0" width="400" >}} +{{< figure src="/documentation/images/Pinenotebg2.png" title="Author: Funeral, License: CC0" width="400" >}} +{{< figure src="/documentation/images/Pinenotebg3.png" title="Author: Funeral, License: CC0" width="400" >}} +{{< figure src="/documentation/images/Pinenotebg4.png" title="Author: Funeral, License: CC0" width="400" >}} diff --git a/content/documentation/PineNote/Further_information/Specification.adoc b/content/documentation/PineNote/Further_information/Specification.adoc index bd98dd6f..c7cf30f8 100644 --- a/content/documentation/PineNote/Further_information/Specification.adoc +++ b/content/documentation/PineNote/Further_information/Specification.adoc @@ -9,8 +9,8 @@ menu: weight: 1 --- -image:/documentation/images/PineNote_Pen_function.jpg[width=300] -image:/documentation/images/PineNote_Cover-1.jpg[width=300] +{{< figure src="/documentation/images/PineNote_Pen_function.jpg" width="300" >}} +{{< figure src="/documentation/images/PineNote_Cover-1.jpg" width="300" >}} == General Information diff --git a/content/documentation/PineNote/_index.adoc b/content/documentation/PineNote/_index.adoc index 8676fd6c..f5fd37f7 100644 --- a/content/documentation/PineNote/_index.adoc +++ b/content/documentation/PineNote/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/PineNote-1.jpg[The PineNote,title="The PineNote",width=400] +{{< figure src="/documentation/images/PineNote-1.jpg" title="The PineNote" width="400" >}} The *PineNote* is the first hybrid notepad computer device combination of notebook, tablet and e-reader using an e-ink panel. It is derived from the Quartz64 model A SBC and powered by a Rockchip RK3566 quad-core ARM Cortex A55 64-bit processor with a MALI G-52 GPU. diff --git a/content/documentation/PinePhone/Accessory.adoc b/content/documentation/PinePhone/Accessory.adoc index 1d17054d..9daee5dc 100644 --- a/content/documentation/PinePhone/Accessory.adoc +++ b/content/documentation/PinePhone/Accessory.adoc @@ -22,7 +22,7 @@ The USB-C can be used to power the device, and offers USB2 host and OTG capabili == Pogo pins -image:/documentation/images/Pinephone_pogo.png[The pogo pins, as visible under the back cover.,title="The pogo pins, as visible under the back cover.",width=400] +{{< figure src="/documentation/images/Pinephone_pogo.png" title="The pogo pins, as visible under the back cover." width="400" >}} The PinePhone has six pogo pins on the back allowing for custom hardware extensions such as wireless charging, an IR blaster, a keyboard extension or extended battery case. The pogo pins provide access to an interrupt line, power inputs/outputs and an I2C interface. @@ -55,7 +55,7 @@ A step file for the back cover for creating custom cases is freely available htt == Serial console -image:/documentation/images/PinePhone_Serial_Cable.png[Pinout of the serial adapter.,title="Pinout of the serial adapter.",width=400] +{{< figure src="/documentation/images/PinePhone_Serial_Cable.png" title="Pinout of the serial adapter." width="400" >}} The PinePhone has a serial port in the headphone connector, it's activated by the 6th contact on the dipswitch. If the switch is set to "on", the headphone connector is in audio mode, if it is set to "off" it's in UART mode. The UART serial connection can also be used for communication with other devices from the PinePhone. diff --git a/content/documentation/PinePhone/Camera.adoc b/content/documentation/PinePhone/Camera.adoc index 2c880cee..4a3378eb 100644 --- a/content/documentation/PinePhone/Camera.adoc +++ b/content/documentation/PinePhone/Camera.adoc @@ -11,7 +11,7 @@ menu: The PinePhone has two cameras, OmniVision OV5640 with 5MP (up to 2592 x 1944 pixels) as rear camera and GalaxyCore GC2145 with 2MP (up to 1600 x 1200 pixels) as front camera. -image:/documentation/images/Rose.jpg[Example picture taken on the PinePhone's rear camera by Martijn Braam using his app _Megapixels_.,title="Example picture taken on the PinePhone's rear camera by Martijn Braam using his app _Megapixels_.",width=400] +{{< figure src="/documentation/images/Rose.jpg" title="Example picture taken on the PinePhone's rear camera by Martijn Braam using his app _Megapixels_." width="400" >}} Further details regarding the camera and the Megapixels camera app can be found on https://blog.brixit.nl/tag/phones/[Martijn's blog]. diff --git a/content/documentation/PinePhone/FAQ.adoc b/content/documentation/PinePhone/FAQ.adoc index a91c0fab..588223a6 100644 --- a/content/documentation/PinePhone/FAQ.adoc +++ b/content/documentation/PinePhone/FAQ.adoc @@ -205,12 +205,12 @@ If you removed the battery isolator and the battery contacts are intact, the bat If nothing works please don't hesitate to contact the community, they are eager to help and booting issues are usually very easy to solve (as they are typically either battery or installation related). The phones itself are all tested individually at the factory. Do not contact PINE64's support for booting issues. -image:/documentation/images/Pinephone_warning.png[A protection foil isolates the battery for the shipping.] -image:/documentation/images/Pinephone_backside.png[The microSD belongs in the upper slot, the micro SIM in the lower slot.] +{{< figure src="/documentation/images/Pinephone_warning.png" title="A protection foil isolates the battery for the shipping." >}} +{{< figure src="/documentation/images/Pinephone_backside.png" title="The microSD belongs in the upper slot, the micro SIM in the lower slot." >}} ==== Can I install a different OS on my Community Edition? -Yes|While all the Community Edition PinePhones come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card, see link:/documentation/PinePhone/Installation_instructions[Installation instructions] and link:/documentation/PinePhone/Software/Releases[Operating systems] on how to install them. +Yes. While all the Community Edition PinePhones come with an OS preinstalled, you are free to use any OS on the integrated storage (the eMMC) or an SD card, see link:/documentation/PinePhone/Installation_instructions[Installation instructions] and link:/documentation/PinePhone/Software/Releases[Operating systems] on how to install them. === Other diff --git a/content/documentation/PinePhone/Further_information/Press.adoc b/content/documentation/PinePhone/Further_information/Press.adoc index 6b0feaa0..c98cf117 100644 --- a/content/documentation/PinePhone/Further_information/Press.adoc +++ b/content/documentation/PinePhone/Further_information/Press.adoc @@ -13,22 +13,22 @@ Vector images and pictures of the link:/documentation/PinePhone[PinePhone] and l == PinePhone Pro -image:/documentation/images/Pinephone_airplane.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] -image:/documentation/images/pinephone_unbranded.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] -image:/documentation/images/Pinephone_table.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] -image:/documentation/images/Pinephone_killswitches.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] -image:/documentation/images/Pinephone_convergence.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] -image:/documentation/images/Pinephone_revisions.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] -image:/documentation/images/Pinephone_box1.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] -image:/documentation/images/Pinephone_box2.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] -image:/documentation/images/Pinephone_double.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] -image:/documentation/images/Pinephone_double2.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] -image:/documentation/images/Pinephone_features.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] +{{< figure src="/documentation/images/Pinephone_airplane.png" title="Author: Funeral, License: CC0" >}} +{{< figure src="/documentation/images/pinephone_unbranded.png" title="Author: Funeral, License: CC0" >}} +{{< figure src="/documentation/images/Pinephone_table.png" title="Author: Funeral, License: CC0" >}} +{{< figure src="/documentation/images/Pinephone_killswitches.png" title="Author: Funeral, License: CC0" >}} +{{< figure src="/documentation/images/Pinephone_convergence.png" title="Author: Funeral, License: CC0" >}} +{{< figure src="/documentation/images/Pinephone_revisions.png" title="Author: Funeral, License: CC0" >}} +{{< figure src="/documentation/images/Pinephone_box1.png" title="Author: Funeral, License: CC0" >}} +{{< figure src="/documentation/images/Pinephone_box2.png" title="Author: Funeral, License: CC0" >}} +{{< figure src="/documentation/images/Pinephone_double.png" title="Author: Funeral, License: CC0" >}} +{{< figure src="/documentation/images/Pinephone_double2.png" title="Author: Funeral, License: CC0" >}} +{{< figure src="/documentation/images/Pinephone_features.png" title="Author: Funeral, License: CC0" >}} == PinePhone -image:/documentation/images/PinePhone_Beta_Edition.png[Beta Edition. Author: Funeral, License: CC0,title="Beta Edition. Author: Funeral, License: CC0"] -image:/documentation/images/pinephone_unbranded.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] +{{< figure src="/documentation/images/PinePhone_Beta_Edition.png" title="Beta Edition. Author: Funeral, License: CC0" >}} +{{< figure src="/documentation/images/pinephone_unbranded.png" title="Author: Funeral, License: CC0" >}} == 3D model @@ -38,45 +38,45 @@ The 3D model can be used for a wide variety of purposes, for example for product Example rendering: -image:/documentation/images/Pinephone_rendering_example.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] -image:/documentation/images/Pinephone_rendering.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] +{{< figure src="/documentation/images/Pinephone_rendering_example.png" title="Author: Funeral, License: CC0" >}} +{{< figure src="/documentation/images/Pinephone_rendering.png" title="Author: Funeral, License: CC0" >}} New template: -image:/documentation/images/Pinephone_rendering_blank_new.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] +{{< figure src="/documentation/images/Pinephone_rendering_blank_new.png" title="Author: Funeral, License: CC0" >}} Old template: -image:/documentation/images/Pinephone_rendering_blank.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] +{{< figure src="/documentation/images/Pinephone_rendering_blank.png" title="Author: Funeral, License: CC0" >}} == Lockscreen template For renderings you can use and modify this template: -image:/documentation/images/Phosh_lockscreen.png[Version_with_black_background._Author: Funeral, License: CC0.,title="Version_with_black_background._Author: Funeral, License: CC0.] -image:/documentation/images/Phosh_lockscreen_blank.png[Version_with_no_background._Author: Funeral, License: CC0.,title="Version_with_no_background._Author: Funeral, License: CC0.] +{{< figure src="/documentation/images/Phosh_lockscreen.png" title="Version with black background. Author: Funeral, License: CC0." >}} +{{< figure src="/documentation/images/Phosh_lockscreen_blank.png" title="Version with no background. Author: Funeral, License: CC0." >}} == Manual and Instructions -image:/documentation/images/PinePhoneSides.svg[Author: Jedi2light, License: CC BY 4.0,title="Author: Jedi2light, License: CC BY 4.0"] +{{< figure src="/documentation/images/PinePhoneSides.svg" title="Author: Jedi2light, License: CC BY 4.0" >}} -image:/documentation/images/PinePhone_Vector.svg[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] +{{< figure src="/documentation/images/PinePhone_Vector.svg" title="Author: Funeral, License: CC0" >}} -image:/documentation/images/Pinephone_warning.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] +{{< figure src="/documentation/images/Pinephone_warning.png" title="Author: Funeral, License: CC0" >}} -image:/documentation/images/Pinephone_drawing1.svg[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] -image:/documentation/images/Pinephone_drawing2.svg[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] -image:/documentation/images/Pinephone_drawing3.svg[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] +{{< figure src="/documentation/images/Pinephone_drawing1.svg" title="Author: Funeral, License: CC0" >}} +{{< figure src="/documentation/images/Pinephone_drawing2.svg" title="Author: Funeral, License: CC0" >}} +{{< figure src="/documentation/images/Pinephone_drawing3.svg" title="Author: Funeral, License: CC0" >}} -image:/documentation/images/Pinephone_drawing1_manual.svg[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] -image:/documentation/images/Pinephone_drawing2_manual.svg[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] -image:/documentation/images/Pinephone_drawing3_manual.svg[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] +{{< figure src="/documentation/images/Pinephone_drawing1_manual.svg" title="Author: Funeral, License: CC0" >}} +{{< figure src="/documentation/images/Pinephone_drawing2_manual.svg" title="Author: Funeral, License: CC0" >}} +{{< figure src="/documentation/images/Pinephone_drawing3_manual.svg" title="Author: Funeral, License: CC0" >}} -image:/documentation/images/Pinephone_slots.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] +{{< figure src="/documentation/images/Pinephone_slots.png" title="Author: Funeral, License: CC0" >}} -image:/documentation/images/Pinephone_backside.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] +{{< figure src="/documentation/images/Pinephone_backside.png" title="Author: Funeral, License: CC0" >}} -image:/documentation/images/Pinephone_pogo.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] +{{< figure src="/documentation/images/Pinephone_pogo.png" title="Author: Funeral, License: CC0" >}} -image:/documentation/images/PinePhone_Serial_Cable.png[Author: Funeral, License: CC0,title="Author: Funeral, License: CC0"] +{{< figure src="/documentation/images/PinePhone_Serial_Cable.png" title="Author: Funeral, License: CC0" >}} diff --git a/content/documentation/PinePhone/Further_information/Sensors_and_navigation.adoc b/content/documentation/PinePhone/Further_information/Sensors_and_navigation.adoc index 27c8b8a8..d4433c36 100644 --- a/content/documentation/PinePhone/Further_information/Sensors_and_navigation.adoc +++ b/content/documentation/PinePhone/Further_information/Sensors_and_navigation.adoc @@ -19,7 +19,7 @@ The PinePhone contains various components that enable or aid orientation and nav * IMU (Inertial Measurement Unit), combined Accelerometer and Gyroscope sensor (MPU6050) * Magnetometer (LIS3MDL or AF8133J) -image:/documentation/images/Pp_sensors_block.png[PinePhone navigation sensors,title="PinePhone navigation sensors",width=500] +{{< figure src="/documentation/images/Pp_sensors_block.png" title="PinePhone navigation sensors" width="500" >}} == Hardware @@ -55,7 +55,7 @@ Key features: The sensors are mounted on the PinePhone's mainboard in different positions and orientations. For the purpose of orientation and navigation it is important to know the relationship between the sensor coordinate frames and the body frame of the phone. -image:/documentation/images/pp_coordinates.png[PinePhone sensor coordinates systems (red) and body coordinate system (cyan),title="PinePhone sensor coordinates systems (red) and body coordinate system (cyan)",width=500] +{{< figure src="/documentation/images/pp_coordinates.png" title="PinePhone sensor coordinates systems (red) and body coordinate system (cyan)" width="500" >}} As a basis for software development, a common body coordinate system has to be established along with it's relation to a world coordinate system. "iio-sensor-proxy expects the (sensor) readings to match those defined in the Linux IIO documentation, the Windows Integrating Motion and Orientation Sensors whitepaper, and the Android sensor documentation"[ref]. To transform the sensor coordinate systems into body coordinates, 'mount matrices' have to be defined. diff --git a/content/documentation/PinePhone/Getting_started.adoc b/content/documentation/PinePhone/Getting_started.adoc index f8eaf771..6ee0342c 100644 --- a/content/documentation/PinePhone/Getting_started.adoc +++ b/content/documentation/PinePhone/Getting_started.adoc @@ -10,7 +10,7 @@ menu: weight: 2 --- -image:/documentation/images/Pinephone_warning.png[A protection foil isolates the battery for the shipping.,title="A protection foil isolates the battery for the shipping.",width=320] +{{< figure src="/documentation/images/Pinephone_warning.png" title="A protection foil isolates the battery for the shipping." width="320" >}} When shipped the battery is isolated from the device using a protective plastic tab, which is required to be removed before using the phone. The battery *will not* charge or boot until it is removed and the battery is connected again. @@ -20,7 +20,7 @@ The PinePhone's SIM slot only accepts a micro-SIM, please do not insert a nano-S NOTE: Do not insert an empty micro-SIM adapter into the phone and do not release the nano-SIM inside the adapter, as it will get stuck on the contact pins. If the nano-SIM got released inside the adapter inside the phone, carefully reinsert the nano-SIM card without moving the adapter. In that case do not pull on the empty adapter as it will get stuck on the contact pins and damage them! -image:/documentation/images/Pinephone_slots.png[The microSD belongs in the upper slot, the micro-SIM in the lower slot.,title="The microSD belongs in the upper slot, the micro-SIM in the lower slot.",width=600] +{{< figure src="/documentation/images/Pinephone_slots.png" title="The microSD belongs in the upper slot, the micro-SIM in the lower slot." width="600" >}} An adapter from a nano to a micro-SIM might be included under tape in the camera notch of the phone's packaging. Some nano-SIMs will not fit firmly into that adapter that comes with the PinePhone and if the included adapter is used without a well-fitting nano-SIM, the contact pins might get damaged. In that case it is highly recommended to acquire a better fitting adapter. diff --git a/content/documentation/PinePhone/Hardware_fixes_and_mods/Modifications_and_repairs.adoc b/content/documentation/PinePhone/Hardware_fixes_and_mods/Modifications_and_repairs.adoc index ee450d1e..b262b2b1 100644 --- a/content/documentation/PinePhone/Hardware_fixes_and_mods/Modifications_and_repairs.adoc +++ b/content/documentation/PinePhone/Hardware_fixes_and_mods/Modifications_and_repairs.adoc @@ -33,7 +33,7 @@ After swapping the mainboard the phone won't boot as there is no OS on the repla A video tutorial by _Martijn Braam_ can be found here (or alternatively a video tutorial by user _brigadan_ with additional notes about the camera swap and proximity sensor isolator https://www.youtube.com/watch?v=J3AJEF7akkw[here]): -image:/documentation/images/Pinephone_martijn_pcb_replacement.png[width=600] +{{< figure src="/documentation/images/Pinephone_martijn_pcb_replacement.png" width="600" >}} === Flashing the ANX firmware diff --git a/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2_VCONN_Hardware_Fix.adoc b/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2_VCONN_Hardware_Fix.adoc index 2160d667..2f86c865 100644 --- a/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2_VCONN_Hardware_Fix.adoc +++ b/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2_VCONN_Hardware_Fix.adoc @@ -27,9 +27,9 @@ This fix requires desoldering tiny (1 mm per 1 mm, from the datasheet) BGA compo == Issue description -image:/documentation/images/Martjin_VCONN_switches_1.1.jpg[Close-up picture of the two identical switches the issue originates from, with the ANX USB controller in the frame,title="Close-up picture of the two identical switches the issue originates from, with the ANX USB controller in the frame"] +{{< figure src="/documentation/images/Martjin_VCONN_switches_1.1.jpg" title="Close-up picture of the two identical switches the issue originates from, with the ANX USB controller in the frame" >}} -image:/documentation/images/Schematic_VCONN_switches.png[Excerpt from the PinePhone schematic showing the two components.,title="Excerpt from the PinePhone schematic showing the two components."] +{{< figure src="/documentation/images/Schematic_VCONN_switches.png" title="Excerpt from the PinePhone schematic showing the two components." >}} The USB standard https://microchipdeveloper.com/usb:tc-pins[specifies] that both halves (top and bottom) of the USB-C port contains one "CC" pin (CC1 and CC2, respectively). A regular cable will connect a CC pin from one end to the other end. This allows detecting which way the cable is plugged. Some active USB-C cables exist (both "e-marked" and "managed active cables"); they contain a chip, which needs to be powered. This is done by having one of the cable end connect its CC pins to 5V and VCONN, and requires switches to plug the right CC pin to the right voltage. @@ -43,7 +43,7 @@ In SW this could theoretically be worked around by manual selection of PinePhone == Workaround -image:/documentation/images/Pinephone_v1.1_VCONN_fix_diagram.svg[width=130])]] +{{< figure src="/documentation/images/Pinephone_v1.1_VCONN_fix_diagram.svg" width="130])]" >}} Hardware workaround is desoldering U1305 and U1309 switches (BGA like packages). This will void the VCONN control, but it will release the CC pins for their proper connection detection and negotiation roles. diff --git a/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2b_R1318_backlight_Hardware_Fix.adoc b/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2b_R1318_backlight_Hardware_Fix.adoc index 3225c7d2..17b9bcc5 100644 --- a/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2b_R1318_backlight_Hardware_Fix.adoc +++ b/content/documentation/PinePhone/Hardware_fixes_and_mods/PinePhone_1.2b_R1318_backlight_Hardware_Fix.adoc @@ -30,7 +30,7 @@ When connecting a VBUS powered device to the affected devices, like USB-C docks The fix of the issue is to remove the R1318 resistor. A detailed instruction will follow here. -image:/documentation/images/Pinephone-pcb-r1318.png[R1318 location on the board,title="R1318 location on the board",width=400] +{{< figure src="/documentation/images/Pinephone-pcb-r1318.png" title="R1318 location on the board" width="400" >}} == Sources and tutorials diff --git a/content/documentation/PinePhone/Installation/Installation_to_the_eMMC.adoc b/content/documentation/PinePhone/Installation/Installation_to_the_eMMC.adoc index a6929898..e7c2d6af 100644 --- a/content/documentation/PinePhone/Installation/Installation_to_the_eMMC.adoc +++ b/content/documentation/PinePhone/Installation/Installation_to_the_eMMC.adoc @@ -25,7 +25,7 @@ The internal memory of the PinePhone (eMMC) can be flashed using multiple differ NOTE: This only applies to the regular *PinePhone*, not the *PinePhone Pro*. -image:/documentation/images/jumpdrive.jpg[Jumpdrive running on the PinePhone,title="Jumpdrive running on the PinePhone",width=400] +{{< figure src="/documentation/images/jumpdrive.jpg" title="Jumpdrive running on the PinePhone" width="400" >}} The internal eMMC flash storage can be flashed using the Jumpdrive utility by Danct12 and Martijn from postmarketOS. This utility boots from micro SD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer. The process of flashing an OS to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card. You can use the _dd_ command or a utility such as Etcher or Gnome Disks, etc. diff --git a/content/documentation/PinePhone/Installation/Installation_to_the_microSD_card.adoc b/content/documentation/PinePhone/Installation/Installation_to_the_microSD_card.adoc index bbbae958..b66cc1a8 100644 --- a/content/documentation/PinePhone/Installation/Installation_to_the_microSD_card.adoc +++ b/content/documentation/PinePhone/Installation/Installation_to_the_microSD_card.adoc @@ -20,7 +20,7 @@ To install an image to the microSD card: . Plug microSD card into phone (make sure to use the top slot, not the bottom slot) . Boot up the phone -image:/documentation/images/Pinephone_slots.png[The microSD belongs in the upper slot, the micro-SIM in the lower slot.,title="The microSD belongs in the upper slot, the micro-SIM in the lower slot.",width=600] +{{< figure src="/documentation/images/Pinephone_slots.png" title="The microSD belongs in the upper slot, the micro-SIM in the lower slot." width="600" >}} == Using Balena Etcher @@ -30,7 +30,7 @@ Download and install the application: https://etcher.balena.io/#download-etcher Then start it and click the button _Flash from file_: -image:../Etcher1.png[width=600] +{{< figure src="../Etcher1.png" width="600" >}} Select the downloaded image and make sure that you downloaded the correct one. Images for the PinePhone and the PinePhone Pro are _'not compatible_' with each other. Images for the PinePhone typically have the word "PinePhone" in the filename, while images for the PinePhone Pro typically have "PinePhone Pro" in their filename. @@ -38,13 +38,13 @@ NOTE: At this the image file does not have to be extracted from the archive form Then click on _Select target_: -image:../Etcher3.png[width=600] +{{< figure src="../Etcher3.png" width="600" >}} NOTE: Make sure to select the correct target by comparing the name and the disk capacity with the label on the microSD card. Then click on _Flash!_: -image:../Etcher4.png[width=600] +{{< figure src="../Etcher4.png" width="600" >}} That's it! diff --git a/content/documentation/PinePhone/Modem/_index.adoc b/content/documentation/PinePhone/Modem/_index.adoc index 4ac508bb..f0378c86 100644 --- a/content/documentation/PinePhone/Modem/_index.adoc +++ b/content/documentation/PinePhone/Modem/_index.adoc @@ -153,7 +153,7 @@ As with most smartphones, the PinePhone has a small antenna and has difficulty g Basic testing of GNSS reception can be done by using the AT command interface (_/dev/ttyUSB2_) from a terminal program like _minicom_ and the data output interface (_/dev/ttyUSB1_) to feed NMEA data into gpsmon or some other program that can parse standard NMEA sentences. -image:/documentation/images/Gpsmon_eg25g.png[gpsmon decoding GPS data from _/dev/ttyUSB1_,title="gpsmon decoding GPS data from _/dev/ttyUSB1_",width=400] +{{< figure src="/documentation/images/Gpsmon_eg25g.png" title="gpsmon decoding GPS data from _/dev/ttyUSB1_" width="400" >}} To check if GNSS data output is enabled, you can diff --git a/content/documentation/PinePhone/Privacy_switches.adoc b/content/documentation/PinePhone/Privacy_switches.adoc index e58b9522..b5a1a2de 100644 --- a/content/documentation/PinePhone/Privacy_switches.adoc +++ b/content/documentation/PinePhone/Privacy_switches.adoc @@ -9,7 +9,7 @@ menu: weight: 7 --- -image:/documentation/images/PinePhone_Kill_Interruptors_de_Maquinari_del_PinePhone_4529.jpg[Picture of the privacy switches,title="Picture of the privacy switches",width=320] +{{< figure src="/documentation/images/PinePhone_Kill_Interruptors_de_Maquinari_del_PinePhone_4529.jpg" title="Picture of the privacy switches" width="320" >}} The PinePhone features six switches that can be used to configure its hardware. They are numbered 1-6, with switch 1 located nearest to the modem. Their "on" position is toward the top of the phone. diff --git a/content/documentation/PinePhone/Revisions/Project_Anakin.adoc b/content/documentation/PinePhone/Revisions/Project_Anakin.adoc index 1ae53e22..7db878bb 100644 --- a/content/documentation/PinePhone/Revisions/Project_Anakin.adoc +++ b/content/documentation/PinePhone/Revisions/Project_Anakin.adoc @@ -32,10 +32,10 @@ The Anakin kit consists of following components: * Lithium Ion Battery case (note: battery not included, can accommodate 1-3 pieces of 18650 size Lithium Ion batter. In general, one is good enough) * Quectel EC20 R2.1 LTE Module (note: The SIM tray design not distinguish polarity well and all reverse slot in) -image:/documentation/images/Anakin_kit_1.jpg[] -image:/documentation/images/Anakin_kit_2.jpg[] -image:/documentation/images/Anakin_kit_4.jpg[] -image:/documentation/images/Anakin_kit_3.jpg[] +{{< figure src="/documentation/images/Anakin_kit_1.jpg" >}} +{{< figure src="/documentation/images/Anakin_kit_2.jpg" >}} +{{< figure src="/documentation/images/Anakin_kit_4.jpg" >}} +{{< figure src="/documentation/images/Anakin_kit_3.jpg" >}} == Accessories Step-by-Step Guides @@ -168,7 +168,7 @@ Connector information: * https://files.pine64.org/doc/datasheet/pine64/ePH.pdf[2.0mm PH Type connector specification use in Lithium Battery (VBAT) port and RTC Battery port] * https://files.pine64.org/doc/datasheet/pine64/0.5FPC%20Front%20Open%20Connector%20H=1.5.pdf[0.5mm Pitch cover type FPC connector specification use in DSI port, TP port and CSI port] -image:/documentation/images/QUECTEL_EC20_Dongle-small.jpg[right,title="right"] +{{< figure src="/documentation/images/QUECTEL_EC20_Dongle-small.jpg" title="right" >}} LTE module information: diff --git a/content/documentation/PinePhone/Revisions/Project_Dont_be_evil.adoc b/content/documentation/PinePhone/Revisions/Project_Dont_be_evil.adoc index f29c2198..7953a42b 100644 --- a/content/documentation/PinePhone/Revisions/Project_Dont_be_evil.adoc +++ b/content/documentation/PinePhone/Revisions/Project_Dont_be_evil.adoc @@ -10,7 +10,7 @@ menu: weight: --- -image:/documentation/images/Qee3ovj.jpg[] +{{< figure src="/documentation/images/Qee3ovj.jpg" >}} The Project *Don't be evil* is the phase two of _PINE64's_ smartphone, the link:/documentation/PinePhone[PinePhone] Development Kit. Project Don't be evil is an actual smartphone developer kit for the PINE64 Smartphone dubbed "PinePhone". It is used in the early stages of development as a starting point for affiliated projects. @@ -20,8 +20,8 @@ The PinePhone development has been broken down into three distinct phases: * Second phase - purpose-built development kit code named "Don't be evil" and introduced at FOSDEM 2019 * Lastly, the third phase which is the PinePhone itself - scheduled to be prototype released in Q3 2019 and BTO batch released with mobile OS parents in Q4 2019 (pending on software development). -image:/documentation/images/Qsud2Gt.jpg[] -image:/documentation/images/Martijnpocket.jpg[] +{{< figure src="/documentation/images/Qsud2Gt.jpg" >}} +{{< figure src="/documentation/images/Martijnpocket.jpg" >}} == Baseboard and SOPine Module Information, and Schematics @@ -168,7 +168,7 @@ Some these OS images labelled as *beta or nightly builds* which means they are o === postmarketOS -image:/documentation/images/PostmarketOS_logo.png[width=100] +{{< figure src="/documentation/images/PostmarketOS_logo.png" width="100" >}} Download: @@ -187,7 +187,7 @@ Notes: === Sailfish OS -image:/documentation/images/SailfishOS_logo.png[width=100] +{{< figure src="/documentation/images/SailfishOS_logo.png" width="100" >}} The Sailfish OS image is build on Gitlab CI, the latest image can be installed using our https://raw.githubusercontent.com/sailfish-on-dontbeevil/flash-it/master/flash-it.sh[flashing script] written in Bash. @@ -207,7 +207,7 @@ Notes: === Maemo Leste -image:/documentation/images/Maemoleste-logo.png[width=100] +{{< figure src="/documentation/images/Maemoleste-logo.png" width="100" >}} Download: @@ -220,7 +220,7 @@ Notes: === LuneOS -image:/documentation/images/Luneos-logo-256.png[width=100] +{{< figure src="/documentation/images/Luneos-logo-256.png" width="100" >}} Download: @@ -239,23 +239,23 @@ For the Mali driver see link:/documentation/General/Mali_driver[Mali Driver]. . Please DON'T insert micro SIM card to dev kit board micro SIM card slot, the SIM data, VPP, and GND signal have been misplaced. A miciPCIe adapter with sim card holder 9shown as below photo) will be provide to developers to correct this mistake. -image:/documentation/images/MiniPCIe_with_sim_slot_adapter.png[width=200] +{{< figure src="/documentation/images/MiniPCIe_with_sim_slot_adapter.png" width="200" >}} . The PinePhone dev kit doesn't charge due to VBUS on SOPine module is not connected. Please connect R9688 solder pads with 0 ohm resistor or using thin wire bridge up the solder pads. Location shows as below: -image:/documentation/images/PinePhone_VBUS_charging_small.png[width=200] +{{< figure src="/documentation/images/PinePhone_VBUS_charging_small.png" width="200" >}} . The SOPINE's SPI NOR flash storage and the devkit's camera flash (heh) share the same GPIO pins. The flash storage may not be used. -image:/documentation/images/SOPINE-SPI-Flash.png[width=200] +{{< figure src="/documentation/images/SOPINE-SPI-Flash.png" width="200" >}} . On the camera flash GPIO conflict, the new assignment of GPIO PB3 pin for SGM3140 FLASH_EN and GPIP PD7 for FLASH_TRIGOUT. Please note that PD7 is also LCD_ID pin which may not be used. Images: -image:/documentation/images/GPIO_PB3_location.jpg[GPIO_PB3_location,title="GPIO_PB3_location"] -image:/documentation/images/U54_SGM3140_FLASH_EN_pin_location.jpg[width=314] -image:/documentation/images/Flash_GPIO_Reassigned.jpg[Flash GPIOs Reassigned wiring,title="Flash GPIOs Reassigned wiring"] +{{< figure src="/documentation/images/GPIO_PB3_location.jpg" title="GPIO_PB3_location" >}} +{{< figure src="/documentation/images/U54_SGM3140_FLASH_EN_pin_location.jpg" width="314" >}} +{{< figure src="/documentation/images/Flash_GPIO_Reassigned.jpg" title="Flash GPIOs Reassigned wiring" >}} == Other Resources diff --git a/content/documentation/PinePhone/Revisions/_index.adoc b/content/documentation/PinePhone/Revisions/_index.adoc index ce93624e..39b7997c 100644 --- a/content/documentation/PinePhone/Revisions/_index.adoc +++ b/content/documentation/PinePhone/Revisions/_index.adoc @@ -9,7 +9,7 @@ menu: weight: 98 --- -image:/documentation/images/Pinephone_revisions.png[The history of the PinePhone CEs,title="The history of the PinePhone CEs",width=400] +{{< figure src="/documentation/images/Pinephone_revisions.png" title="The history of the PinePhone CEs" width="400" >}} The following are all hardware revisions of the PinePhone that have existed, ordered by the time of their releases: diff --git a/content/documentation/PinePhone/Software/Releases.adoc b/content/documentation/PinePhone/Software/Releases.adoc index b524cc39..49c529bc 100644 --- a/content/documentation/PinePhone/Software/Releases.adoc +++ b/content/documentation/PinePhone/Software/Releases.adoc @@ -21,7 +21,7 @@ See link:/documentation/PinePhone/Installation/[Installation instructions] on ho === Arch Linux ARM -image:/documentation/images/Archlinux-logo.png[width=100] +{{< figure src="/documentation/images/Archlinux-logo.png" width="100" >}} (Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, sxmo or barebones. @@ -48,7 +48,7 @@ Get both stable and test builds at https://github.com/dreemurrs-embedded/Pine64- === Fedora -image:/documentation/images/fedora1.png[width=100] +{{< figure src="/documentation/images/fedora1.png" width="100" >}} An (unofficial) vanilla Fedora rawhide build for aarch64 with megi's kernel and https://copr.fedorainfracloud.org/coprs/njha/mobile/packages/[some additional packages] to tie it all together. It aims to eventually be an upstream part of the Fedora project, rather than a phone-specific distribution. @@ -78,7 +78,7 @@ Please send your bug reports to https://github.com/nikhiljha/pp-fedora-sdsetup/i === Gentoo -image:/documentation/images/GentooLogo.png[width=100] +{{< figure src="/documentation/images/GentooLogo.png" width="100" >}} There are unofficial Gentoo overlays with ebuilds for the PinePhone. There are no images - the image must be built manually, including picking the kernel, bootloader and the desired desktop environment. The ARM64 version of Gentoo has to be selected. @@ -120,7 +120,7 @@ Feature overview: === Kali Linux -image:/documentation/images/Kali-logo.png[width=200] +{{< figure src="/documentation/images/Kali-logo.png" width="200" >}} The official Kali Nethunter images for PinePhone and PinePhone Pro have been released now. For older/unofficial releases, you can still download from the GitHub releases page. Get https://github.com/Shubhamvis98/nethunter-pinephone[Nethunter App] for your PinePhone's Kali Linux. Packet Injection is working now, use iwconfig instead of airmon-ng. @@ -142,7 +142,7 @@ The official Kali Nethunter images for PinePhone and PinePhone Pro have been rel === LuneOS -image:/documentation/images/Luneos-logo-256.png[width=100] +{{< figure src="/documentation/images/Luneos-logo-256.png" width="100" >}} LuneOS is one of the original multi-tasking OS-es that runs on Linux. Based on HP/Palm's webOS, merged with latest technology stack from LG called webOS OSE (a derivative of what LG uses on their Smart TV's), software such as Qt5 and makes use of the Yocto build system. @@ -167,7 +167,7 @@ In order to connect to the device using SSH/SCP via WiFi: You can simply connect === Maemo Leste -image:/documentation/images/Maemoleste-logo.png[width=100] +{{< figure src="/documentation/images/Maemoleste-logo.png" width="100" >}} Maemo is a trimmed-down version of Debian for mobile devices, originally a collaboration between Nokia and many open source projects (the http://maemo.org/intro/[Maemo community]) before Nokia abandoned it. The more well-known devices Maemo supports are the OpenMoko and N900. The community now takes full responsibility in developing fully open source Maemo for a variety of mobile devices. You may be interested to learn more about the features in their https://leste.maemo.org/Leste_FAQ[Maemo Leste FAQ]. @@ -200,7 +200,7 @@ Submit https://github.com/maemo-leste/bugtracker/issues[bug reports] on GitHub. === Manjaro ARM -image:/documentation/images/Manjaro-logo.svg[width=100] +{{< figure src="/documentation/images/Manjaro-logo.svg" width="100" >}} Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile and Phosh desktop environment. @@ -226,7 +226,7 @@ The installation of the stable images is strongly suggested. The dev images migh === Mobian -image:/documentation/images/Debian-logo.png[width=100] +{{< figure src="/documentation/images/Debian-logo.png" width="100" >}} An unofficial https://www.debian.org[Debian] build for ARM64 running with Phosh (developed by Purism, uses Wayland instead of Xorg). The base system is pure Debian, with only the GUI applications and a few others (ModemManager, WiFi chip firmware) being built from modified sources (as well as the kernel and u-boot). @@ -311,7 +311,7 @@ Also see link:/documentation/PinePhone/Installation_instructions[Installation in === Nemo Mobile -image:/documentation/images/nemo_mobile.png[width=100] +{{< figure src="/documentation/images/nemo_mobile.png" width="100" >}} Nemo Mobile is the open source build of Sailfish OS with a open source UI called http://nemomobile.net/glacier-home/[Glacier], http://nemomobile.net/pages/Hello_manjaro/[based on Manjaro]. @@ -335,7 +335,7 @@ The website of the Nemo Mobile UX Team can be found https://nemomobile.net/[here === NixOS -image:/documentation/images/NixOS.webp[width=100] +{{< figure src="/documentation/images/NixOS.webp" width="100" >}} NixOS is a Linux distribution built on top of the Nix package manager using declarative configuration to allow reliable system upgrades. @@ -352,7 +352,7 @@ Project home page: https://mobile.nixos.org/[Mobile NixOS] === OpenMandriva Lx -image:/documentation/images/Oma-logo-22042013_300pp.png[width=100] +{{< figure src="/documentation/images/Oma-logo-22042013_300pp.png" width="100" >}} OpenMandriva Lx with Plasma Mobile as UI. @@ -367,7 +367,7 @@ NOTE: This image is solely for testing purposes. === openSUSE -image:/documentation/images/SLEM-OS-logo.png[width=100] +{{< figure src="/documentation/images/SLEM-OS-logo.png" width="100" >}} Our images use the same https://en.opensuse.org/Portal:Tumbleweed[openSUSE Tumbleweed] base as our desktop images, except what needs to be changed for the PinePhone. @@ -404,7 +404,7 @@ You will also find information in our wiki on how to report issues (Contributing === postmarketOS -image:/documentation/images/PostmarketOS_logo.png[width=100] +{{< figure src="/documentation/images/PostmarketOS_logo.png" width="100" >}} postmarketOS extends https://www.alpinelinux.org/[Alpine Linux] to run on smartphones and other mobile devices. It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4 and others). @@ -460,7 +460,7 @@ https://discord.gg/reSvc8Ztk3[Discord] - https://matrix.to/#/#rolling-rhino-remi === Sailfish OS -image:/documentation/images/SailfishOS_logo.png[width=100] +{{< figure src="/documentation/images/SailfishOS_logo.png" width="100" >}} https://sailfishos.org/[Sailfish OS] is a Linux-based operating system based on open source projects such as https://wiki.merproject.org/wiki/Main_Page[Mer], and a closed source UI based on https://sailfishos.org/wiki/Lipstick[Lipstick]. @@ -526,7 +526,7 @@ OTA is supported: `zypper refresh && zypper update` as root (`devel-su` to get r === SkiffOS -image:/documentation/images/SkiffOS-Icon-1.png[width=100] +{{< figure src="/documentation/images/SkiffOS-Icon-1.png" width="100" >}} Minimal in-memory cross-compiled OS optimized for hosting multiple in parallel Docker containers. Provides the reliability of firmware with the ease-of-use of package managers. @@ -585,7 +585,7 @@ Discussion: https://forum.pine64.org/showthread.php?tid=12181&highlight=slackwar === Ubuntu Touch -image:/documentation/images/Ubports-logo.png[width=100] +{{< figure src="/documentation/images/Ubports-logo.png" width="100" >}} A Mobile Version of the Ubuntu Operating System made and maintained by the UBports Community. The port is currently maintained by Oren Klopfer (oklopfer). diff --git a/content/documentation/PinePhone/Software_tricks/MMS_with_Matrix.adoc b/content/documentation/PinePhone/Software_tricks/MMS_with_Matrix.adoc index 53697d30..04e81503 100644 --- a/content/documentation/PinePhone/Software_tricks/MMS_with_Matrix.adoc +++ b/content/documentation/PinePhone/Software_tricks/MMS_with_Matrix.adoc @@ -10,7 +10,7 @@ menu: weight: --- -image:/documentation/images/Pinephonematrixfractalmmsscreenshot.jpg[Screenshot of fractal displaying an MMS conversation,title="Screenshot of fractal displaying an MMS conversation"] +{{< figure src="/documentation/images/Pinephonematrixfractalmmsscreenshot.jpg" title="Screenshot of fractal displaying an MMS conversation" >}} The one known way to get MMS fully (meaning pictures and group messages) working is by relaying all SMS and MMS to a matrix server and using a matrix client to interact with them. https://gitlab.com/untidylamp/mmmpuppet is the bridge used here diff --git a/content/documentation/PinePhone/_index.adoc b/content/documentation/PinePhone/_index.adoc index 91fa7171..499117a1 100644 --- a/content/documentation/PinePhone/_index.adoc +++ b/content/documentation/PinePhone/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/PinePhone_Beta_Edition.png[Rendering of the PinePhone Beta Edition,title="Rendering of the PinePhone Beta Edition",width=400] +{{< figure src="/documentation/images/PinePhone_Beta_Edition.png" title="Rendering of the PinePhone Beta Edition" width="400" >}} The *PinePhone* is a smartphone created by PINE64. It is capable of running mainline Linux and is supported by many partner projects. diff --git a/content/documentation/PinePhone_Pro/Factory_tests/Factory_test_battery_charging.adoc b/content/documentation/PinePhone_Pro/Factory_tests/Factory_test_battery_charging.adoc index 799c0999..a30cdfc6 100644 --- a/content/documentation/PinePhone_Pro/Factory_tests/Factory_test_battery_charging.adoc +++ b/content/documentation/PinePhone_Pro/Factory_tests/Factory_test_battery_charging.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/PPP_Abdroid_Test_Utility-1.jpg[width=300] +{{< figure src="/documentation/images/PPP_Abdroid_Test_Utility-1.jpg" width="300" >}} Please note that this Android build solely for PinePhone Pro hardware checking purpose and solely used by support team. This is NOT a general release build. diff --git a/content/documentation/PinePhone_Pro/Factory_tests/Factory_test_hardware_checking.adoc b/content/documentation/PinePhone_Pro/Factory_tests/Factory_test_hardware_checking.adoc index b2f44742..4a403e73 100644 --- a/content/documentation/PinePhone_Pro/Factory_tests/Factory_test_hardware_checking.adoc +++ b/content/documentation/PinePhone_Pro/Factory_tests/Factory_test_hardware_checking.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/PPP_Abdroid_Test_Utility-5.jpg[width=400] +{{< figure src="/documentation/images/PPP_Abdroid_Test_Utility-5.jpg" width="400" >}} Please note that this Android build solely for PinePhone Pro hardware checking purpose and solely used by the support team. This is NOT a general release build. @@ -23,7 +23,7 @@ Instructions: * Insert battery, press the RE button (bypass SPI and eMMC boot) underneath the back cover while plugging in the USB-C power. After 3 seconds release the RE button. * When powering up, a battery icon screen will show up blow, press power key for two seconds, then the Rockchip logo screen shows up. -image:/documentation/images/PPP_Abdroid_Test_Utility-1.jpg[width=300] +{{< figure src="/documentation/images/PPP_Abdroid_Test_Utility-1.jpg" width="300" >}} * Wait for the home screen, double tap on the test app icon (mark red circuit) and this will bring up the factory test screen. Please note that the SD test is disabled due in this is SD boot build. * After running a particular test function, please snapshot the test result and pass it back to support team @@ -34,5 +34,5 @@ Notes: * When perform GPS test, the first result may fail and please ignore this false message. * For light sensing test, please have a light shine to the PinePhone Pro when performing the test. -image:/documentation/images/PPP_Abdroid_Test_Utility-4.jpg[width=300] +{{< figure src="/documentation/images/PPP_Abdroid_Test_Utility-4.jpg" width="300" >}} diff --git a/content/documentation/PinePhone_Pro/First_time_setup.adoc b/content/documentation/PinePhone_Pro/First_time_setup.adoc index 38c6783a..29e4ab04 100644 --- a/content/documentation/PinePhone_Pro/First_time_setup.adoc +++ b/content/documentation/PinePhone_Pro/First_time_setup.adoc @@ -9,7 +9,7 @@ menu: weight: 2 --- -image:/documentation/images/Pinephone_warning.png[A protection foil isolates the battery for the shipping.,title="A protection foil isolates the battery for the shipping.",width=320] +{{< figure src="/documentation/images/Pinephone_warning.png" title="A protection foil isolates the battery for the shipping." width="320" >}} When shipped the battery is isolated from the device using a protective plastic tab, which is required to be removed before using the phone. The battery *will not* charge or boot until it is removed and the battery is connected again. @@ -17,6 +17,6 @@ NOTE: To remove the sticker after unboxing the phone: Carefully remove the back The SIM card has to be placed in the lower slot, while the microSD has to be placed in the upper slot. Devices shipped after the end of July 2022 do only accept a nano-SIM, the SIM is inserted into a carriage released by slightly pulling on the handle in the lower slot (for information regarding devices shipped prior to end of July 2022 see below). -image:/documentation/PinePhone_Pro/images/pinephone_slots.png[The microSD belongs in the upper slot, the SIM card in the lower slot.,title="The microSD belongs in the upper slot, the SIM card in the lower slot.",width=600] +{{< figure src="/documentation/PinePhone_Pro/images/pinephone_slots.png" title="The microSD belongs in the upper slot, the SIM card in the lower slot." width="600" >}} NOTE: The PinePhone Pros shipped prior to the end of July 2022 come with a micro-SIM slot instead of a nano-SIM slot. Do not insert an empty micro-SIM adapter into the phone and do not release the nano-SIM inside the adapter, as it will get stuck on the contact pins. If the nano-SIM got released inside the adapter inside the phone, carefully reinsert the nano-SIM card without moving the adapter. In that case do not pull on the empty adapter as it will get stuck on the contact pins and damage them! \ No newline at end of file diff --git a/content/documentation/PinePhone_Pro/Modem.adoc b/content/documentation/PinePhone_Pro/Modem.adoc index 2d80e14d..f3497b3b 100644 --- a/content/documentation/PinePhone_Pro/Modem.adoc +++ b/content/documentation/PinePhone_Pro/Modem.adoc @@ -146,7 +146,7 @@ As with most smartphones, the PinePhone Pro has a small antenna and has difficul Basic testing of GNSS reception can be done by using the AT command interface (_/dev/ttyUSB2_) from a terminal program like _minicom_ and the data output interface (_/dev/ttyUSB1_) to feed NMEA data into gpsmon or some other program that can parse standard NMEA sentences. -image:/documentation/images/Gpsmon_eg25g.png[gpsmon decoding GPS data from _/dev/ttyUSB1_,title="gpsmon decoding GPS data from _/dev/ttyUSB1_",width=400] +{{< figure src="/documentation/images/Gpsmon_eg25g.png" title="gpsmon decoding GPS data from _/dev/ttyUSB1_" width="400" >}} To check if GNSS data output is enabled, you can diff --git a/content/documentation/PinePhone_Pro/Privacy_switches.adoc b/content/documentation/PinePhone_Pro/Privacy_switches.adoc index 549d7183..a9118f5c 100644 --- a/content/documentation/PinePhone_Pro/Privacy_switches.adoc +++ b/content/documentation/PinePhone_Pro/Privacy_switches.adoc @@ -9,7 +9,7 @@ menu: weight: 6 --- -image:/documentation/images/PinePhone_Kill_Interruptors_de_Maquinari_del_PinePhone_4529.jpg[Picture of the privacy switches,title="Picture of the privacy switches",width=320] +{{< figure src="/documentation/images/PinePhone_Kill_Interruptors_de_Maquinari_del_PinePhone_4529.jpg" title="Picture of the privacy switches" width="320" >}} The PinePhone features six switches that can be used to configure its hardware. They are numbered 1-6, with switch 1 located nearest to the modem. Their "on" position is toward the top of the phone. diff --git a/content/documentation/PinePhone_Pro/Software/Installation_instructions.adoc b/content/documentation/PinePhone_Pro/Software/Installation_instructions.adoc index 967f52f1..3f936f01 100644 --- a/content/documentation/PinePhone_Pro/Software/Installation_instructions.adoc +++ b/content/documentation/PinePhone_Pro/Software/Installation_instructions.adoc @@ -17,7 +17,7 @@ The software releases can be installed (the process is being referred to as _fla The images can be installed to an microSD card and be booted from it. -image:/documentation/PinePhone_Pro/images/pinephone_slots.png[The microSD belongs in the upper slot, the SIM in the lower slot.,title="The microSD belongs in the upper slot, the SIM in the lower slot.",width=600] +{{< figure src="/documentation/PinePhone_Pro/images/pinephone_slots.png" title="The microSD belongs in the upper slot, the SIM in the lower slot." width="600" >}} NOTE: Compared to installations to the eMMC, running operating systems from the microSD card is slower than to the eMMC due to the microSD card’s slower reading and writing speeds. diff --git a/content/documentation/PinePhone_Pro/Software/Releases.adoc b/content/documentation/PinePhone_Pro/Software/Releases.adoc index 74f4f419..8de3fbb8 100644 --- a/content/documentation/PinePhone_Pro/Software/Releases.adoc +++ b/content/documentation/PinePhone_Pro/Software/Releases.adoc @@ -37,7 +37,7 @@ Download the build, extract the image and dd it to a 8 GB or larger microSD card == Arch Linux ARM -image:/documentation/images/Archlinux-logo.png[width=100] +{{< figure src="/documentation/images/Archlinux-logo.png" width="100" >}} (Unofficial) Arch Linux ARM with choice of Phosh UI, Plasma Mobile, sxmo or barebones. Currently being maintained by the https://danctnix.org/[DanctNIX] community (GitHub: https://github.com/DanctNIX/danctnix[danctnix], https://github.com/dreemurrs-embedded[dreemurrs-embedded]). @@ -64,7 +64,7 @@ A re-image of the above Arch image providing a Btrfs root partitioning has been == Gentoo -image:/documentation/images/GentooLogo.png[width=100] +{{< figure src="/documentation/images/GentooLogo.png" width="100" >}} There are unofficial Gentoo overlays with ebuilds for the PinePhone Pro. There are no images - the image must be built manually, including picking the kernel, bootloader and the desired desktop environment. The ARM64 version of Gentoo has to be selected. The PinePhone Pro will not boot with P-Boot but will boot with U-Boot, there is an ebuild for it. @@ -94,7 +94,7 @@ Project status https://github.com/GloDroidCommunity/pine64-pinephonepro/issues/1 == LuneOS -image:/documentation/images/Luneos-logo-256.png[width=100] +{{< figure src="/documentation/images/Luneos-logo-256.png" width="100" >}} LuneOS is one of the original multi-tasking OS-es that runs on Linux. Based on HP/Palm's webOS, merged with latest technology stack from LG called webOS OSE (a derivative of what LG uses on their Smart TV's), software such as Qt5 and makes use of the Yocto build system. @@ -115,7 +115,7 @@ In order to connect to the device using SSH/SCP via WiFi: You can simply connect == Manjaro ARM -image:/documentation/images/Manjaro-logo.svg[width=100] +{{< figure src="/documentation/images/Manjaro-logo.svg" width="100" >}} Manjaro is a user-friendly Linux distribution based on the independently developed Arch operating system with the Plasma Mobile and Phosh desktop environment. @@ -136,7 +136,7 @@ Manjaro is a user-friendly Linux distribution based on the independently develop == Mobian -image:/documentation/images/Debian-logo.png[width=100] +{{< figure src="/documentation/images/Debian-logo.png" width="100" >}} An unofficial https://www.debian.org[Debian] build for ARM64 running with Phosh. The current version of the base Debian system is Debian Bookworm. See the installation instructions https://wiki.debian.org/InstallingDebianOn/PINE64/PinePhonePro[here]. If you have questions about Mobian, please ask them in the https://matrix.to/#/#mobian:matrix.org[Mobian Matrix room]. @@ -161,7 +161,7 @@ In order to connect to the device using SSH/SCP via WiFi, you need to install SS == Kali Linux -image:/documentation/images/Kali-logo.png[width=200] +{{< figure src="/documentation/images/Kali-logo.png" width="200" >}} The official Kali Nethunter images for PinePhone and PinePhone Pro have been released now. Get https://github.com/Shubhamvis98/nethunter-pinephone[Nethunter App] for your PinePhone's Kali Linux. @@ -182,7 +182,7 @@ The official Kali Nethunter images for PinePhone and PinePhone Pro have been rel == Nemo Mobile -image:/documentation/images/nemo_mobile.png[width=100] +{{< figure src="/documentation/images/nemo_mobile.png" width="100" >}} Nemo Mobile is the open source build of Sailfish OS with a open source UI called http://nemomobile.net/glacier-home/[Glacier], http://nemomobile.net/pages/Hello_manjaro/[based on Manjaro]. @@ -206,7 +206,7 @@ The website of the Nemo Mobile UX Team can be found https://nemomobile.net/[here == NixOS -image:/documentation/images/NixOS.webp[width=100] +{{< figure src="/documentation/images/NixOS.webp" width="100" >}} NixOS is a Linux distribution built on top of the Nix package manager using declarative configuration to allow reliable system upgrades. @@ -220,7 +220,7 @@ WIP. See https://github.com/NixOS/mobile-nixos/issues/440 == postmarketOS -image:/documentation/images/PostmarketOS_logo.png[width=100] +{{< figure src="/documentation/images/PostmarketOS_logo.png" width="100" >}} postmarketOS extends https://www.alpinelinux.org/[Alpine Linux] to run on smartphones and other mobile devices. It offers various user interfaces (Phosh, Plasma Mobile, Sxmo, Plasma Desktop, Gnome 3, Kodi, XFCE4, [...]). diff --git a/content/documentation/PinePhone_Pro/_index.adoc b/content/documentation/PinePhone_Pro/_index.adoc index 53d58bc3..f2ece24f 100644 --- a/content/documentation/PinePhone_Pro/_index.adoc +++ b/content/documentation/PinePhone_Pro/_index.adoc @@ -9,6 +9,6 @@ menu: weight: --- -image:/documentation/images/Pinephone_double.png[Rendering of the PinePhone Pro,title="Rendering of the PinePhone Pro",width=400] +{{< figure src="/documentation/images/Pinephone_double.png" title="Rendering of the PinePhone Pro" width="400" >}} The *PinePhone Pro* is PINE64's flagship smartphone announced on October 15, 2021. It features 4GB of RAM, an 128GB eMMC and is using an Rockchip RK3399S SoC, which is a specialized version of the RK3399 made specifically for the PinePhone Pro. \ No newline at end of file diff --git a/content/documentation/PinePower/Versions/120W_Desktop_Power_Supply.adoc b/content/documentation/PinePower/Versions/120W_Desktop_Power_Supply.adoc index 43170bed..b29d1d88 100644 --- a/content/documentation/PinePower/Versions/120W_Desktop_Power_Supply.adoc +++ b/content/documentation/PinePower/Versions/120W_Desktop_Power_Supply.adoc @@ -9,7 +9,7 @@ menu: weight: 2 --- -image:/documentation/images/PinePower-Desktop-2.jpg[PinePower Desktop 120W render,title="PinePower Desktop 120W render",width=400] +{{< figure src="/documentation/images/PinePower-Desktop-2.jpg" title="PinePower Desktop 120W render" width="400" >}} A 120W desktop power adapter. It features 1 USB-C port and 4 USB-A port. The 120W output is not per port, but total output power. This is calculated by combining the 65W USB-C, 3x15W USB-A and the 18W USB-A QC, making a total of 128W. The only difference between the US and EU edition is the supplied power cable. Every port, with exception of the wireless Q-charger, has a display, portraying the output voltage and amps. The display back light can be turned on and off by capacitive touch button, located on the top left side of the unit. @@ -82,12 +82,12 @@ Connections: The power unit is not made to be disassembled, do so at your own risk. The front plate is secured with 4 tabs, that can be disengaged with a screwdriver. The complete assembly can be slid out, but do mind the same tab in the casing. The power button at the back of the case has a plug that can be disconnected from the main PCB. The wireless charging PCB has to be de-soldered, or forcefully removed from the inner casing, as it is glued to the top of the case. -image:/documentation/images/PinPower-Desktop-front-plate-removal.jpg[(Removal_of_the_front_plate),title="(Removal_of_the_front_plate)"] -image:/documentation/images/PinPower-Desktop-Display-front.jpg[(Front_view_display_PCB),title="(Front_view display PCB)"] -image:/documentation/images/PinPower-Desktop-Display-back.jpg[(Back_side_display_PCB),title="(Back_side_display_PCB)"] -image:/documentation/images/PinPower-Desktop-PCB-top.jpg[(Top_side_main_PCB),title="(Top_side_main_PCB)"] -image:/documentation/images/PinPower-Desktop-PCB-bottom.jpg[(Bottom_view_main_PCB),title="(Bottom_view_main_PCB)"] -image:/documentation/images/PinPower-Desktop-wireless-charger.jpg[(Wireless charger),title="(Wireless charger)"] +{{< figure src="/documentation/images/PinPower-Desktop-front-plate-removal.jpg" title="(Removal_of_the_front_plate)" >}} +{{< figure src="/documentation/images/PinPower-Desktop-Display-front.jpg" title="(Front_view_display_PCB)" >}} +{{< figure src="/documentation/images/PinPower-Desktop-Display-back.jpg" title="(Back_side_display_PCB)" >}} +{{< figure src="/documentation/images/PinPower-Desktop-PCB-top.jpg" title="(Top_side_main_PCB)" >}} +{{< figure src="/documentation/images/PinPower-Desktop-PCB-bottom.jpg" title="(Bottom_view_main_PCB)" >}} +{{< figure src="/documentation/images/PinPower-Desktop-wireless-charger.jpg" title="(Wireless charger)" >}} Some remarks: diff --git a/content/documentation/PinePower/_index.adoc b/content/documentation/PinePower/_index.adoc index a3e660d8..af94772b 100644 --- a/content/documentation/PinePower/_index.adoc +++ b/content/documentation/PinePower/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/PinePower_Charger_65W.jpeg[PinePower 65W render,title="PinePower 65W render",width=400] +{{< figure src="/documentation/images/PinePower_Charger_65W.jpeg" title="PinePower 65W render" width="400" >}} The *PinePower* devices (the _PinePower_ and the _PinePower Desktop_) are power supplies, which pack plenty of power. They capable of powering or charging multiple PINE64 devices, such as the Pinebook Pro, PinePhone and the PineTime simultaneously. diff --git a/content/documentation/PineTab-V/Features.adoc b/content/documentation/PineTab-V/Features.adoc index 8bcfbd95..6e8abe19 100644 --- a/content/documentation/PineTab-V/Features.adoc +++ b/content/documentation/PineTab-V/Features.adoc @@ -9,8 +9,8 @@ menu: weight: 1 --- -image:/documentation/PineTab-V/images/Pinetabv_2.jpg[Front- and backside of the PineTab-V,title="Front- and backside of the PineTab-V",width=250] -image:/documentation/PineTab-V/images/Pinetabv_3.jpg[Backside of the PineTab-V,title="Backside of the PineTab-V",width=250] +{{< figure src="/documentation/PineTab-V/images/Pinetabv_2.jpg" title="Front- and backside of the PineTab-V" width="250" >}} +{{< figure src="/documentation/PineTab-V/images/Pinetabv_3.jpg" title="Backside of the PineTab-V" width="250" >}} Chassis: diff --git a/content/documentation/PineTab-V/UART_adapter.adoc b/content/documentation/PineTab-V/UART_adapter.adoc index 0d2ed811..a90e880e 100644 --- a/content/documentation/PineTab-V/UART_adapter.adoc +++ b/content/documentation/PineTab-V/UART_adapter.adoc @@ -13,7 +13,7 @@ The UART serves as a console for early boot and kernel messages, and also offers == Connecting the UART adapter -image:/documentation/PineTab-V/images/PineTab2_USB_UARTv2.jpg[UART Adapter,title="UART Adapter",width=450] +{{< figure src="/documentation/PineTab-V/images/PineTab2_USB_UARTv2.jpg" title="UART Adapter" width="450" >}} The UART adapter allows access to the UART through the USB 2.0 Type-C port: diff --git a/content/documentation/PineTab-V/_index.adoc b/content/documentation/PineTab-V/_index.adoc index 5e91f9ee..5f405d3c 100644 --- a/content/documentation/PineTab-V/_index.adoc +++ b/content/documentation/PineTab-V/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/PineTab-V/images/Pinetabv_1.jpg[The PineTab-V with the detachable keyboard attached,title="The PineTab-V with the detachable keyboard attached",width=250] +{{< figure src="/documentation/PineTab-V/images/Pinetabv_1.jpg" title="The PineTab-V with the detachable keyboard attached" width="250" >}} The _PineTab-V_ is _PINE64's_ first RISC-V tablet. It is based on the JH7110 64-bit RISC-V SoC. diff --git a/content/documentation/PineTab/Operating_systems.adoc b/content/documentation/PineTab/Operating_systems.adoc index 71e47fbe..d7de9e32 100644 --- a/content/documentation/PineTab/Operating_systems.adoc +++ b/content/documentation/PineTab/Operating_systems.adoc @@ -13,7 +13,7 @@ The PineTab will automatically boot from microSD if a bootable card is inserted. == Arch Linux ARM -image:/documentation/images/Archlinux-logo.png[width=100] +{{< figure src="/documentation/images/Archlinux-logo.png" width="100" >}} Unofficial *Arch Linux ARM* with Phosh as the UI selection, maintained by the DanctNIX community. @@ -23,7 +23,7 @@ Download: == Manjaro ARM -image:/documentation/images/Manjaro-logo.svg[width=100] +{{< figure src="/documentation/images/Manjaro-logo.svg" width="100" >}} *Manjaro* is a Linux based alternative operating system with no adverts or licensing fees, it respects user privacy and gives them full control over their hardware. The PineTab "Early Adopter" edition is currently the only device supported by Manjaro ARM. @@ -36,7 +36,7 @@ Both Beta releases and weekly unstable builds for Phosh and Plasma Mobile can be == Mobian -image:/documentation/images/Debian-logo.png[width=100] +{{< figure src="/documentation/images/Debian-logo.png" width="100" >}} *Mobian* is an unofficial https://www.debian.org[Debian] build for ARM64 running with Phosh. The current version of the base Debian system is Debian Bookworm. See the installation instructions https://wiki.debian.org/InstallingDebianOn/PINE64/PineTab[here]. If you have questions about Mobian, please ask them in the https://matrix.to/#/#mobian:matrix.org[Mobian Matrix room]. @@ -53,7 +53,7 @@ Download: == postmarketOS -image:/documentation/images/PostmarketOS_logo.png[width=100] +{{< figure src="/documentation/images/PostmarketOS_logo.png" width="100" >}} *postmarketOS* extends https://www.alpinelinux.org/[Alpine Linux] to run on smartphones and other mobile devices. @@ -72,7 +72,7 @@ Getting postmarketOS for the PineTab: == Rhino Linux -image:/documentation/images/Rhino-linux-logo.png[width=100] +{{< figure src="/documentation/images/Rhino-linux-logo.png" width="100" >}} *Rhino Linux* is an Ubuntu-based distribution that uses the rolling-release model by tracking the `devel` branch of repositories. The port is currently maintained by Oren Klopfer (oklopfer). @@ -97,7 +97,7 @@ https://discord.gg/reSvc8Ztk3[Discord] - https://matrix.to/#/#rolling-rhino-remi == Sailfish OS -image:/documentation/images/SailfishOS_logo.png[width=100] +{{< figure src="/documentation/images/SailfishOS_logo.png" width="100" >}} You can get *SailfishOS* on your with the flash-it script, which will write an image on a SD card. https://github.com/sailfish-on-dontbeevil/flash-it @@ -109,7 +109,7 @@ Many things are still broken but Bluetooth, Audio, Rotation and Keyboard are wor == Ubuntu Touch -image:/documentation/images/Ubports-logo.png[width=100] +{{< figure src="/documentation/images/Ubports-logo.png" width="100" >}} *Ubuntu Touch* is a mobile version of the Ubuntu distribution made and maintained by the UBports community. The port is currently maintained by Oren Klopfer (oklopfer). diff --git a/content/documentation/PineTab/Revisions/_index.adoc b/content/documentation/PineTab/Revisions/_index.adoc index e2d04965..21c5a4fd 100644 --- a/content/documentation/PineTab/Revisions/_index.adoc +++ b/content/documentation/PineTab/Revisions/_index.adoc @@ -12,7 +12,7 @@ menu: * Developer Edition - development version sent to roughly 100 developers. Close to the Early Adopter Edition, but with a different display panel * link:/documentation/PineTab/Revisions/Early_adopters[Early Adopter Edition] - the first hardware revision of the PineTab -image:/documentation/images/PineTabBoard.jpeg[The insides of the PineTab,title="The insides of the PineTab",width=400] +{{< figure src="/documentation/images/PineTabBoard.jpeg" title="The insides of the PineTab" width="400" >}} -image:/documentation/images/PineTab_Board.jpg[Pinetab Board,title="Pinetab Board"] +{{< figure src="/documentation/images/PineTab_Board.jpg" title="Pinetab Board" >}} diff --git a/content/documentation/PineTab/_index.adoc b/content/documentation/PineTab/_index.adoc index f10a13de..310b47cc 100644 --- a/content/documentation/PineTab/_index.adoc +++ b/content/documentation/PineTab/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/Pinetab.jpg[The PineTab,title="The PineTab",width=400] +{{< figure src="/documentation/images/Pinetab.jpg" title="The PineTab" width="400" >}} The *PineTab* is a 10" tablet created by PINE64. The PineTab is similar in both form, function and underlying ARM64 architecture to the original 11.6″ Pinebook. It is powered by the same quad-core ARM Cortex A53 64-Bit Processor used in our popular PINE A64 Single Board Computer. The optional keyboard and trackpad – which doubles-up as a screen cover – effectively converts the PineTab into a petite on-the-go laptop with a touch screen functionality. It runs numerous mainline Linux distributions as well as *BSD and Android.  diff --git a/content/documentation/PineTab2/Development/UART_adapter.adoc b/content/documentation/PineTab2/Development/UART_adapter.adoc index 8e1af839..c9d0e8cb 100644 --- a/content/documentation/PineTab2/Development/UART_adapter.adoc +++ b/content/documentation/PineTab2/Development/UART_adapter.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/PineTab2/images/PineTab2_USB_UARTv2.jpg[The UART adapter,title="The UART adapter",width=450] +{{< figure src="/documentation/PineTab2/images/PineTab2_USB_UARTv2.jpg" title="The UART adapter" width="450" >}} The USB-C UART adapter can be connected to the PineTab2 to debug boot issues at the early boot: diff --git a/content/documentation/PineTab2/Software/Installation_instructions.adoc b/content/documentation/PineTab2/Software/Installation_instructions.adoc index c7ba5701..52315a4b 100644 --- a/content/documentation/PineTab2/Software/Installation_instructions.adoc +++ b/content/documentation/PineTab2/Software/Installation_instructions.adoc @@ -37,7 +37,7 @@ Then insert the microSD card into the PineTab2. [NOTE] ==== -image:/documentation/PineTab2/images/PineTab2_USB_UARTv2.jpg[The UART adapter,title="The UART adapter",width=450] +{{< figure src="/documentation/PineTab2/images/PineTab2_USB_UARTv2.jpg" title="The UART adapter" width="450" >}} Using the USB UART adapter can be required in some cases as explained in the info box about the boot order. The adapter is shipped with the PineTab2 in the box which is also containing the charging cable. The switch to disable the eMMC and SPI is located on the top right of the image. ==== diff --git a/content/documentation/PineTab2/_index.adoc b/content/documentation/PineTab2/_index.adoc index 44843df2..689ea84f 100644 --- a/content/documentation/PineTab2/_index.adoc +++ b/content/documentation/PineTab2/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/PineTab2/images/PineTab2_Front.jpg[The PineTab2 with the detachable keyboard attached,title="The PineTab2 with the detachable keyboard attached",width=250] +{{< figure src="/documentation/PineTab2/images/PineTab2_Front.jpg" title="The PineTab2 with the detachable keyboard attached" width="250" >}} The *PineTab2* is PINE64's successor to the original link:/documentation/PineTab[PineTab] Linux tablet computer, featuring a faster processor and better availability. The tablet is available in two configurations, 4GB of RAM and 64GB of internal storage or 8GB of RAM and 128GB of internal storage. The tablet ships with a detachable keyboard that doubles as a protective cover. diff --git a/content/documentation/PineTime/Discussions/Bootloader_improvements.adoc b/content/documentation/PineTime/Discussions/Bootloader_improvements.adoc index 1103cb36..ea0fc975 100644 --- a/content/documentation/PineTime/Discussions/Bootloader_improvements.adoc +++ b/content/documentation/PineTime/Discussions/Bootloader_improvements.adoc @@ -34,7 +34,7 @@ My goals are: Pinetime Devkit0 is using a nRF52832-QFAA MCU with 512kB flash and a https://datasheet.lcsc.com/szlcsc/2005251035_XTX-XT25F32BSOIGU-S_C558851.pdf[XT25F32B SPI NOR external flash] with 4096kB. -image:/documentation/images/MemoryMap.png[] +{{< figure src="/documentation/images/MemoryMap.png" >}} Internal flash (512Kb): @@ -95,7 +95,7 @@ In order to simplify the code, the graphics will be stored into the bootloader c === Bootloader workflow -image:/documentation/images/PineTimeBootloaderWorkflow.png[] +{{< figure src="/documentation/images/PineTimeBootloaderWorkflow.png" >}} === Upgrade & Reloader diff --git a/content/documentation/PineTime/Further_information/Devkit_wiring.adoc b/content/documentation/PineTime/Further_information/Devkit_wiring.adoc index ee6e0db7..6cb25b84 100644 --- a/content/documentation/PineTime/Further_information/Devkit_wiring.adoc +++ b/content/documentation/PineTime/Further_information/Devkit_wiring.adoc @@ -31,17 +31,17 @@ The devkits have exposed SWD pins for flashing and debugging. The pinout is: -image:/documentation/images/PineTime_SWD_location.jpg[width=400] +{{< figure src="/documentation/images/PineTime_SWD_location.jpg" width="400" >}} == Pogo Pins connection The https://pine64.com/product/pinetime-pogopin-jig/[PineTime Pogo Pins] are spring-loaded pins with diamond-shaped tips. -image:/documentation/images/PineTime_pogo_tip.jpg[width=400] +{{< figure src="/documentation/images/PineTime_pogo_tip.jpg" width="400" >}} The Pogo Pins are meant to be connected temporarily to PineTime's SWD port for firmware flashing and simple firmware debugging. -image:/documentation/images/PineTime_pogo_stlink.jpg[width=400] +{{< figure src="/documentation/images/PineTime_pogo_stlink.jpg" width="400" >}} The other end of the Pogo Pins connects to ST-Link v2 or JLink for flashing and debugging. (ST-Link v2 is shown in the background) @@ -55,13 +55,13 @@ To connect PineTime Pogo Pins to PineTime's SWD Port: The tips of the Pogo Pins will partially penetrate the SWD holes like this. Don't force them in! -image:/documentation/images/PineTime_pogo_swd.jpg[width=400] +{{< figure src="/documentation/images/PineTime_pogo_swd.jpg" width="400" >}} == Soldered wires example Before attempting this, make sure you have a good soldering iron, some magnification and you haven't set your iron too high. If you haven't ever before soldered things this small, you really really do not want to start out on something this dense, small and thus fragile. -image:/documentation/images/PineTime_soldered_wires.jpg[width=400] +{{< figure src="/documentation/images/PineTime_soldered_wires.jpg" width="400" >}} == Raspberry Pi connection diff --git a/content/documentation/PineTime/Software/Reprogramming.adoc b/content/documentation/PineTime/Software/Reprogramming.adoc index 95c09392..e67182bd 100644 --- a/content/documentation/PineTime/Software/Reprogramming.adoc +++ b/content/documentation/PineTime/Software/Reprogramming.adoc @@ -143,7 +143,7 @@ Connect PineTime SWD Pins to ST-Link v2 as follows: |3.3V |=== -image:/documentation/images/pinetime-stlink.jpg[width=400] +{{< figure src="/documentation/images/pinetime-stlink.jpg" width="400" >}} Note that only the bottom row of pins on ST-Link are used. diff --git a/content/documentation/PineTime/Software/Switching_between_InfiniTime_and_Wasp-os.adoc b/content/documentation/PineTime/Software/Switching_between_InfiniTime_and_Wasp-os.adoc index 6474e245..1f131375 100644 --- a/content/documentation/PineTime/Software/Switching_between_InfiniTime_and_Wasp-os.adoc +++ b/content/documentation/PineTime/Software/Switching_between_InfiniTime_and_Wasp-os.adoc @@ -9,8 +9,8 @@ menu: weight: --- -image:/documentation/images/Flash-reloader-mcuboot.jpg[Flashing_`reloader-mcuboot.zip`,title="Flashing_`reloader-mcuboot.zip`",width=600] -image:/documentation/images/Flash-micropython.jpg[Flashing `micropython.zip`,title="Flashing `micropython.zip`",width=400] +{{< figure src="/documentation/images/Flash-reloader-mcuboot.jpg" title="Flashing_`reloader-mcuboot.zip`" width="600" >}} +{{< figure src="/documentation/images/Flash-micropython.jpg" title="Flashing `micropython.zip`" width="400" >}} == Introduction @@ -45,8 +45,8 @@ All the zips you need can be found from the https://wasp-os.readthedocs.io/en/la == Wasp-os to InfiniTime -image:/documentation/images/Flash-reloader-infinitime-recovery.jpg[Flashing_`reloader-infinitime-recovery-0.14.1.zip.zip`,title="Flashing_`reloader-infinitime-recovery-0.14.1.zip.zip`",width=500] -image:/documentation/images/Flash-infinitime.jpg[Flashing `pinetime-mcuboot-app-dfu-1.1.0.zip.zip`,title="Flashing `pinetime-mcuboot-app-dfu-1.1.0.zip.zip`",width=600] +{{< figure src="/documentation/images/Flash-reloader-infinitime-recovery.jpg" title="Flashing_`reloader-infinitime-recovery-0.14.1.zip.zip`" width="500" >}} +{{< figure src="/documentation/images/Flash-infinitime.jpg" title="Flashing `pinetime-mcuboot-app-dfu-1.1.0.zip.zip`" width="600" >}} The `reloader-factory.zip` was broken in the original wasp-os 0.4 but was fixed in wasp-os 0.4.1. However the Infinitime binaries are outdated the 0.4 release and I do not recommend flashing these. Older InfiniTime versions have flaky BLE which makes upgrading from there very unreliable. diff --git a/content/documentation/PineTime/Watchfaces/Custom_watchface.adoc b/content/documentation/PineTime/Watchfaces/Custom_watchface.adoc index 7c960b23..0b2bf2f7 100644 --- a/content/documentation/PineTime/Watchfaces/Custom_watchface.adoc +++ b/content/documentation/PineTime/Watchfaces/Custom_watchface.adoc @@ -52,7 +52,7 @@ Labels are considered as "elemental" parts that make up a screen's Text-based UI let's observe something small like the word "BPM" near the bottom of the watch face. -image:/documentation/images/PineTimeCustom-1.png[width=200] +{{< figure src="/documentation/images/PineTimeCustom-1.png" width="200" >}} If we take a look at the source file of the watchface, (a.k.a. the clock.cpp file) we can observe that these particular lines are what attributes to the word "BPM" being displayed. @@ -203,7 +203,7 @@ NOTE: When making the custom array, don't forget to leave an empty "" as the fir The locational placement in LVGL is done on a Cartesian plane, where each object can have dynamic origin placement, and the Y-axis is inverted. So going down is done with a positive Y-axis value and not negative as it is by default. -image:/documentation/images/LVGL_coord_system.png[LVGL coord system,title="LVGL coord system",width=200] +{{< figure src="/documentation/images/LVGL_coord_system.png" title="LVGL coord system" width="200" >}} The position of the various objects in WatchFaceDigital.cpp are set by the line, diff --git a/content/documentation/PineTime/Watchfaces/PineTimeStyle.adoc b/content/documentation/PineTime/Watchfaces/PineTimeStyle.adoc index dfd50415..fad24cb5 100644 --- a/content/documentation/PineTime/Watchfaces/PineTimeStyle.adoc +++ b/content/documentation/PineTime/Watchfaces/PineTimeStyle.adoc @@ -13,7 +13,7 @@ PineTimeStyle is a watchface created for Infinitime and has been included since It is based on https://www.dantilden.com/projects/timestyle/[TimeStyle for Pebble by Dan Tilden] with permission. -image:/documentation/PineTime/images/InfiniSim_Watchface.png[PineTimeStyle Watchface,title="PineTimeStyle Watchface"] +{{< figure src="/documentation/PineTime/images/InfiniSim_Watchface.png" title="PineTimeStyle Watchface" >}} == Layout @@ -27,11 +27,11 @@ The current date is displayed in the middle, and at the bottom there is a small Since version 1.4 of Infinitime, a color picker is available for PineTimeStyle. As of version 1.11, an addition page of customisation has been added which allows the user to customise the sidebar. These settings can be accessed by long pressing on the watchface which will display two buttons, one with a palette icon to access the color settings, one with a cog icon for the sidebar options. -image:/documentation/PineTime/images/InfiniSim_Settings.png[PineTimeStyle Settings Button,title="PineTimeStyle Settings Button"] +{{< figure src="/documentation/PineTime/images/InfiniSim_Settings.png" title="PineTimeStyle Settings Button" >}} === The color picker -image:/documentation/PineTime/images/InfiniSim_Color.png[PineTimeStyle Color Settings Interface,title="PineTimeStyle Color Settings Interface"] +{{< figure src="/documentation/PineTime/images/InfiniSim_Color.png" title="PineTimeStyle Color Settings Interface" >}} There are 3 pairs of buttons with left and right arrows which scroll through 17 standard colors. The top pair changes the time text color, middle for the sidebar color and bottom for the time background color. @@ -39,7 +39,7 @@ There is also a 'Rnd' button which randomises all colors, a 'Rst' button which r === The sidebar settings -image:/documentation/PineTime/images/InfiniSim_SidebarSettings.png[PineTimeStyle Sidebar Settings,title="PineTimeStyle Sidebar Settings"] +{{< figure src="/documentation/PineTime/images/InfiniSim_SidebarSettings.png" title="PineTimeStyle Sidebar Settings" >}} As of Infinitime version 1.13, there are 2 options available in the sidebar settings page - Steps style and Weather. diff --git a/content/documentation/PineTime/_index.adoc b/content/documentation/PineTime/_index.adoc index 7f529aa4..661cbd2f 100644 --- a/content/documentation/PineTime/_index.adoc +++ b/content/documentation/PineTime/_index.adoc @@ -9,6 +9,6 @@ menu: weight: --- -image:/documentation/images/Pinetime.png[The PineTime,title="The PineTime",width=400] +{{< figure src="/documentation/images/Pinetime.png" title="The PineTime" width="400" >}} The *PineTime* is a free and open source smartwatch capable of running custom-built open operating systems. Some of the notable features include a heart rate monitor, a week-long battery, and a capacitive touch IPS display that is legible in direct sunlight. It is a fully community driven side-project which anyone can contribute to, allowing you to keep control of your device. \ No newline at end of file diff --git a/content/documentation/PineVox/_index.adoc b/content/documentation/PineVox/_index.adoc index 4ef84e83..1d6ea85a 100644 --- a/content/documentation/PineVox/_index.adoc +++ b/content/documentation/PineVox/_index.adoc @@ -9,6 +9,6 @@ menu: weight: --- -image:/documentation/PineVox/images/pinevox.jpg[The PineVox,title="The PineVox",width=600] +{{< figure src="/documentation/PineVox/images/pinevox.jpg" title="The PineVox" width="600" >}} The *PineVox* is a BL606P-based home assistant smart speaker. Designed to help build a good community option for voice interactions with software such as _Home Assistant_. \ No newline at end of file diff --git a/content/documentation/Pine_A64-LTS/Board_features.adoc b/content/documentation/Pine_A64-LTS/Board_features.adoc index ea39d4a6..6cf18cdf 100644 --- a/content/documentation/Pine_A64-LTS/Board_features.adoc +++ b/content/documentation/Pine_A64-LTS/Board_features.adoc @@ -9,8 +9,8 @@ menu: weight: 1 --- -image:/documentation/images/PINEA64_LTS_board_front.jpg[width=400] -image:/documentation/images/PINEA64_LTS_board_back.jpg[width=400] +{{< figure src="/documentation/images/PINEA64_LTS_board_front.jpg" width="400" >}} +{{< figure src="/documentation/images/PINEA64_LTS_board_back.jpg" width="400" >}} == Layout diff --git a/content/documentation/Pine_A64-LTS/_index.adoc b/content/documentation/Pine_A64-LTS/_index.adoc index c854676d..0a1a0b24 100644 --- a/content/documentation/Pine_A64-LTS/_index.adoc +++ b/content/documentation/Pine_A64-LTS/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/PINEA64_LTS_sideimg.jpg[The PINE A64-LTS,title="The PINE A64-LTS",width=400] +{{< figure src="/documentation/images/PINEA64_LTS_sideimg.jpg" title="The PINE A64-LTS" width="400" >}} The *PINE64-LTS* is the long term supply version of the PINE A64 (+), _PINE64's_ first single board computer, powered by Allwinner’s A64 quad-core ARM Cortex A53 64-Bit SoC. There are many operating systems available for the PINE A64-LTS created by the open source community and various partner projects. The PINE A64-LTS is guaranteed to be supplied until the year 2025 at the very least. diff --git a/content/documentation/Pine_A64/Board_features.adoc b/content/documentation/Pine_A64/Board_features.adoc index b151afca..e3a0a091 100644 --- a/content/documentation/Pine_A64/Board_features.adoc +++ b/content/documentation/Pine_A64/Board_features.adoc @@ -13,7 +13,7 @@ menu: Board Dimensions: 133mm x 80mm x 19mm -image:/documentation/Pine_A64/images/pine_a64_labels.png[Board layout,title="Board layout",width=500] +{{< figure src="/documentation/Pine_A64/images/pine_a64_labels.png" title="Board layout" width="500" >}} [cols="1,1"] |=== diff --git a/content/documentation/Pine_A64/Further_information/Heat_sinks.adoc b/content/documentation/Pine_A64/Further_information/Heat_sinks.adoc index 08edde67..6d0afbce 100644 --- a/content/documentation/Pine_A64/Further_information/Heat_sinks.adoc +++ b/content/documentation/Pine_A64/Further_information/Heat_sinks.adoc @@ -11,5 +11,5 @@ menu: Overclocking requires heat sinks: -image:/documentation/Pine_A64/images/pine_a64_heatsink.png[Position of the heat sinks,title="Position of the heat sinks",width=500] +{{< figure src="/documentation/Pine_A64/images/pine_a64_heatsink.png" title="Position of the heat sinks" width="500" >}} diff --git a/content/documentation/Pine_A64/Software.adoc b/content/documentation/Pine_A64/Software.adoc index e37b400f..9d4513e2 100644 --- a/content/documentation/Pine_A64/Software.adoc +++ b/content/documentation/Pine_A64/Software.adoc @@ -17,7 +17,7 @@ NOTE: The images for the PINE A64 and PINE A64+ are *not compatible with the PIN === AOSC -image:/documentation/images/aosc.png[width=100] +{{< figure src="/documentation/images/aosc.png" width="100" >}} *AOSC OS* is a general purpose Linux distribution that strives to simplify user experience and improve free and open source software for day-to-day productivity. To learn more about AOSC, please visit the official https://aosc.io/[AOSC website]. @@ -34,7 +34,7 @@ Download: === Arch Linux ARM -image:/documentation/images/Archlinux-logo.png[width=100] +{{< figure src="/documentation/images/Archlinux-logo.png" width="100" >}} *Arch Linux ARM* is a distribution of Linux for ARM computers. @@ -44,7 +44,7 @@ Installation: === Armbian -image:/documentation/images/armbian.png[width=100] +{{< figure src="/documentation/images/armbian.png" width="100" >}} *Armbian* is a Linux distribution designed for ARM boards. They are usually Debian or Ubuntu flavored. @@ -54,7 +54,7 @@ Download: === Debian -image:/documentation/images/Debian-logo.png[width=100] +{{< figure src="/documentation/images/Debian-logo.png" width="100" >}} *Debian* is an operating system and a distribution of free software. See the forum thread https://forum.pine64.org/showthread.php?tid=9744[here]. @@ -81,7 +81,7 @@ Notes: === DietPi -image:/documentation/images/dietpi.png[width=100] +{{< figure src="/documentation/images/dietpi.png" width="100" >}} *DietPi* is a lightweight yet easy to setup and feature-rich Linux distribution, based on Debian. To find out more about DietPi, please visit the https://dietpi.com/docs/[official documentation]. Discuss the PINE A64 build on the https://forum.pine64.org/showthread.php?tid=12513[PINE64 forum thread]. @@ -99,7 +99,7 @@ Download: === FreedomBox -image:/documentation/images/FreedomBox.jpg[width=100] +{{< figure src="/documentation/images/FreedomBox.jpg" width="100" >}} *FreedomBox* is a private server for non-experts: it lets you install and configure server applications with only a few clicks. For more information about FreedomBox, please visit http://www.freedombox.org. @@ -117,7 +117,7 @@ Notes: === LibreELEC -image:/documentation/images/libreelec.jpg[width=100] +{{< figure src="/documentation/images/libreelec.jpg" width="100" >}} *LibreELEC* is a "Just enough OS" Linux distribution combining the Kodi media center with an operating system. @@ -132,7 +132,7 @@ Notes: === motionEyeOS -image:/documentation/images/motioneyeos.png[width=100] +{{< figure src="/documentation/images/motioneyeos.png" width="100" >}} *motionEyeOS* is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend. Visit the https://github.com/ccrisan/motioneyeos/releases/[motionEyeOS GitHub] and its https://github.com/ccrisan/motioneyeos/wiki[GitHub Wiki] for more information @@ -156,7 +156,7 @@ Notes: === NEMS Linux -image:/documentation/images/nems.jpg[width=100] +{{< figure src="/documentation/images/nems.jpg" width="100" >}} *NEMS* stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers. To find out more on NEMS Linux, please visit their https://nemslinux.com/[site]. @@ -180,7 +180,7 @@ Notes: === openSUSE -image:/documentation/images/opensuse-distribution.png[width=100] +{{< figure src="/documentation/images/opensuse-distribution.png" width="100" >}} *openSUSE* is a free and open source RPM-based Linux distribution developed by the openSUSE project. More details can be found under https://en.opensuse.org/HCL:Pine64. @@ -191,7 +191,7 @@ Download: === OpenWRT -image:/documentation/images/Openwrt_logo_square.png[width=100] +{{< figure src="/documentation/images/Openwrt_logo_square.png" width="100" >}} The *OpenWrt* Project is a Linux operating system targeting embedded devices. @@ -215,7 +215,7 @@ Notes: === NetBSD -image:/documentation/images/netbsd.png[width=100] +{{< figure src="/documentation/images/netbsd.png" width="100" >}} *NetBSD* is a free, fast, secure, and highly portable Unix-like Open Source operating system. To learn more about NetBSD please visit https://www.netbsd.org/[NetBSD main page]. @@ -237,7 +237,7 @@ Notes: == Windows 10 IoT -image:/documentation/images/win10iot.png[width=100] +{{< figure src="/documentation/images/win10iot.png" width="100" >}} Download: diff --git a/content/documentation/Pine_A64/_index.adoc b/content/documentation/Pine_A64/_index.adoc index 516a9322..b2633178 100644 --- a/content/documentation/Pine_A64/_index.adoc +++ b/content/documentation/Pine_A64/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/PINEA64_sideimg.jpg[The PINE A64,title="The PINE A64",width=400] +{{< figure src="/documentation/images/PINEA64_sideimg.jpg" title="The PINE A64" width="400" >}} The *PINE A64* and the *PINE A64+* is _PINE64's_ first Single Board Computer powered by Allwinner’s A64 quad-core ARM Cortex A53 64-Bit SoC. There are many Operating Systems available for the PINE A64 created by the open source community and various partner projects. diff --git a/content/documentation/Pinebook/Software.adoc b/content/documentation/Pinebook/Software.adoc index e69a8057..0dcae9f8 100644 --- a/content/documentation/Pinebook/Software.adoc +++ b/content/documentation/Pinebook/Software.adoc @@ -15,7 +15,7 @@ This page contains a list of all available releases and tools for the link:/docu === AOSC -image:/documentation/images/aosc.png[width=100] +{{< figure src="/documentation/images/aosc.png" width="100" >}} *AOSC OS* is a general purpose Linux distribution that strives to simplify user experience and improve free and open source software for day-to-day productivity. To learn more about AOSC, please visit the official https://aosc.io/[AOSC website]. @@ -32,7 +32,7 @@ Download: === Armbian -image:/documentation/images/armbian.png[width=100] +{{< figure src="/documentation/images/armbian.png" width="100" >}} *Armbian* is a Linux distribution designed for ARM boards. They are usually Debian or Ubuntu flavored. To find out more about Armbian and available download options please visit the https://www.armbian.com/rock64/[Armbian ROCK64 site]. @@ -88,7 +88,7 @@ Notes: === DietPi -image:/documentation/images/dietpi.png[width=100] +{{< figure src="/documentation/images/dietpi.png" width="100" >}} *DietPi* is a lightweight yet easy to setup and feature-rich Linux distribution, based on Debian. To find out more about DietPi, please visit the https://dietpi.com/docs/[official documentation]. Discuss the ROCK64 build on the https://forum.pine64.org/showthread.php?tid=12512[PINE64 forum thread]. @@ -106,7 +106,7 @@ Download: === Kali -image:/documentation/images/Kali-logo.png[width=100] +{{< figure src="/documentation/images/Kali-logo.png" width="100" >}} *Kali Linux* is an Advanced Penetration Testing Linux distribution used for Penetration Testing, Ethical Hacking and network security assessments. @@ -132,7 +132,7 @@ Download: === Slackware -image:/documentation/images/slackware.jpg[width=100] +{{< figure src="/documentation/images/slackware.jpg" width="100" >}} *Slackware* is a very old, interesting, convenient and easy distribution. Visit the project's website here (https://fail.pp.ua). You can follow the ongoing discussion about Slackware on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=9439). @@ -160,7 +160,7 @@ Download: === NetBSD -image:/documentation/images/netbsd.png[width=100] +{{< figure src="/documentation/images/netbsd.png" width="100" >}} NetBSD community build. To learn more about NetBSD please visit the https://www.netbsd.org/[NetBSD main page]. @@ -190,7 +190,7 @@ Notes: === OpenBSD -image:/documentation/images/Puffy_mascot_openbsd.png[width=100] +{{< figure src="/documentation/images/Puffy_mascot_openbsd.png" width="100" >}} OpenBSD 6.6-snapshot, Community Build Image (FVWM2 WM). To learn more about OpenBSD please visit https://www.openbsd.org[OpenBSD main page]. If you need more information please ping: https://forum.pine64.org/member.php?action=profile&uid=12423. @@ -213,7 +213,7 @@ Download: == Android Image Releases -image:/documentation/images/Android_logo_2019_(stacked).svg[width=100] +{{< figure src="/documentation/images/Android_logo_2019_(stacked).svg" width="100" >}} === Android 7.x @@ -305,7 +305,7 @@ Notes: === /e/ -image:/documentation/images/e.png[width=100] +{{< figure src="/documentation/images/e.png" width="100" >}} /e/OS community build. To learn more about /e/OS, please visit the https://e.foundation/[official website]. Please check out https://medium.com/@edevelopers.blog/e-os-ports-for-the-pinebook-and-pinephone-596139c76479[this article] on the Pinebook /e/ build. For a thread discussion please visit the https://forum.pine64.org/showthread.php?tid=7954[PINE64 forum] diff --git a/content/documentation/Pinebook/_index.adoc b/content/documentation/Pinebook/_index.adoc index fe738e84..03e95ab8 100644 --- a/content/documentation/Pinebook/_index.adoc +++ b/content/documentation/Pinebook/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:images/pinebook.jpg[The Pinebook,title="The Pinebook",width=400] +{{< figure src="images/pinebook.jpg" title="The Pinebook" width="400" >}} The *Pinebook* is an 11.6″ or 11.6″ with 1080P IPS panel or 14″ notebook powered by the same quad-core ARM Cortex A53 64-Bit Processor used in our popular PINE A64 Single Board Computer. It is very lightweight, hackable and comes equipped with a full-sized keyboard and large multi-touch trackpad. It runs numerous mainline Linux distributions as well as *BSD and Android. diff --git a/content/documentation/Pinebook_Pro/Features/Bluetooth_and_WiFi.adoc b/content/documentation/Pinebook_Pro/Features/Bluetooth_and_WiFi.adoc index 1a13984b..d86bb2d8 100644 --- a/content/documentation/Pinebook_Pro/Features/Bluetooth_and_WiFi.adoc +++ b/content/documentation/Pinebook_Pro/Features/Bluetooth_and_WiFi.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/PinebookPro_WirelessIC_Location.jpg[The Pinebook Pro's AP6256 wireless module,title="The Pinebook Pro's AP6256 wireless module",width=400] +{{< figure src="/documentation/images/PinebookPro_WirelessIC_Location.jpg" title="The Pinebook Pro's AP6256 wireless module" width="400" >}} == Hardware Overview diff --git a/content/documentation/Pinebook_Pro/Features/Bootable_storage.adoc b/content/documentation/Pinebook_Pro/Features/Bootable_storage.adoc index 835af5f3..10e284fa 100644 --- a/content/documentation/Pinebook_Pro/Features/Bootable_storage.adoc +++ b/content/documentation/Pinebook_Pro/Features/Bootable_storage.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/Pbp_emmc_disable_sw.jpg[The PineBook Pro eMMC module and switch, shown in 'enabled' position,title="The PineBook Pro eMMC module and switch, shown in 'enabled' position",width=480] +{{< figure src="/documentation/images/Pbp_emmc_disable_sw.jpg" title="The PineBook Pro eMMC module and switch, shown in 'enabled' position" width="480" >}} == Boot sequence details diff --git a/content/documentation/Pinebook_Pro/Features/Internal_layout.adoc b/content/documentation/Pinebook_Pro/Features/Internal_layout.adoc index c3b6e360..d455d5f5 100644 --- a/content/documentation/Pinebook_Pro/Features/Internal_layout.adoc +++ b/content/documentation/Pinebook_Pro/Features/Internal_layout.adoc @@ -23,7 +23,7 @@ There are two switches on the main board: disabling the eMMC module (24), and en The Reset and Recovery buttons (28): the reset button performs an immediate reset of the laptop. The Recovery button is used to place the device in maskrom mode. This mode allows flashing eMMC using Rockchip tools (e.g. rkflashtools). -image:/documentation/images/PBPL_S.jpg[width=500] +{{< figure src="/documentation/images/PBPL_S.jpg" width="500" >}} == Key Internal Parts @@ -136,5 +136,5 @@ image:/documentation/images/PBPL_S.jpg[width=500] == Smallboard detailed picture -image:/documentation/images/Pinebook_pro_smallboard.jpg[width=600] +{{< figure src="/documentation/images/Pinebook_pro_smallboard.jpg" width="600" >}} diff --git a/content/documentation/Pinebook_Pro/Features/SPI.adoc b/content/documentation/Pinebook_Pro/Features/SPI.adoc index 0415222c..87330d2c 100644 --- a/content/documentation/Pinebook_Pro/Features/SPI.adoc +++ b/content/documentation/Pinebook_Pro/Features/SPI.adoc @@ -52,7 +52,7 @@ WARNING: **When removing the large RF shield found on the mainboard, to be able . Disconnect all boot devices, i.e. eMMC, microSD card and USB. . Locate SPI flash (component number 29 on https://wiki.pine64.org/images/4/45/PBPL_S.jpg[this photo of the Pinebook Pro internals]). . Connect your Pinebook Pro with USB-C to USB-A cable to second machine (Pinebook Pro on the USB-C side) -. Short pins CLK and VSS (see chip diagram to the right for the names of pins). This can be done with a pair of tweezers when short on tools. image:/documentation/images/Spi.png[right,title="right"] +. Short pins CLK and VSS (see chip diagram to the right for the names of pins). This can be done with a pair of tweezers when short on tools. {{< figure src="/documentation/images/Spi.png" title="right" >}} . Power on the Pinebook Pro. . Press the reset button (component number 28). . Check if there is new output from `journalctl` program. diff --git a/content/documentation/Pinebook_Pro/Guides/Disassembly_and_Reassembly.adoc b/content/documentation/Pinebook_Pro/Guides/Disassembly_and_Reassembly.adoc index 4349b1df..5d4041f9 100644 --- a/content/documentation/Pinebook_Pro/Guides/Disassembly_and_Reassembly.adoc +++ b/content/documentation/Pinebook_Pro/Guides/Disassembly_and_Reassembly.adoc @@ -9,10 +9,10 @@ menu: weight: --- -image:/documentation/images/Standoffs.png[Pinebook Screw stand-offs correct placement and location,title="Pinebook Screw stand-offs correct placement and location",width=400] +{{< figure src="/documentation/images/Standoffs.png" title="Pinebook Screw stand-offs correct placement and location" width="400" >}} -image:/documentation/images/Hinges_cover_removed_1.jpeg[Hinge_area_of_the_Pinebook_Pro_lid_with_the_cover_removed,title="Hinge_area_of_the_Pinebook_Pro_lid_with the cover removed",width=300] -image:/documentation/images/Hinges_cover_removed_2.jpeg[Close-up of a Pinebook Pro lid hinge,title="Close-up of a Pinebook Pro lid hinge",width=300] +{{< figure src="/documentation/images/Hinges_cover_removed_1.jpeg" title="Hinge_area_of_the_Pinebook_Pro_lid_with the cover removed" width="300" >}} +{{< figure src="/documentation/images/Hinges_cover_removed_2.jpeg" title="Close-up of a Pinebook Pro lid hinge" width="300" >}} There are a few *mandatory* precautions to be taken: @@ -20,7 +20,7 @@ There are a few *mandatory* precautions to be taken: * When removing the back cover plate, *do not, under any circumstances, slide your fingertips between the metal shell and the plastic frame!* The back cover plate edges are sharp, and when combined with the pressure and movement generated from, specifically, attempting to slide the tips of your fingers along the bottom edge of the plate along the lid-hinge, they *will* slice open the tips of your fingers like a knife. * When removing the back cover plate, use care to avoid damaging the speakers. They can be stuck to the back cover with double-sided tape, and the thin wires are very delicate. Newer Pinebook Pro laptops (as of the May 2021 batch, and perhaps earlier) seem to lack the double-sided tape to the rear cover, instead opting for tape or glue that makes them stick to the front cover. Nevertheless, be gentle when removing the back cover. -image:/documentation/images/PinebookProScrewGuide.png[Pinebook Pro external screws (this particular unit has suffered damage on screw (4)L),title="Pinebook Pro external screws (this particular unit has suffered damage on screw (4)L)",width=400] +{{< figure src="/documentation/images/PinebookProScrewGuide.png" title="Pinebook Pro external screws (this particular unit has suffered damage on screw (4)L)" width="400" >}} When disassembling the laptop make sure that it is powered off and folded closed. To remove the bottom cover of the Pinebook Pro, first remove the ten (10) Phillips head screws that hold the bottom section of the laptop in place. There are four (4) short screws along the front edge, and six (6) long screws along the 3 remaining sides. Remove the cover from the back where the hinges are situated by lifting it up and away from the rest of the chassis. The aluminum case is held on only by screws. There are no plastic snaps, and the shell should pull away without any effort. If you experience any resistance at all stop and ensure all ten (10) screws are accounted for. diff --git a/content/documentation/Pinebook_Pro/Keyboard/Assembly.adoc b/content/documentation/Pinebook_Pro/Keyboard/Assembly.adoc index 9d195b63..de767f55 100644 --- a/content/documentation/Pinebook_Pro/Keyboard/Assembly.adoc +++ b/content/documentation/Pinebook_Pro/Keyboard/Assembly.adoc @@ -30,11 +30,11 @@ TIP: The keys might be removable without taking the keyboard out of the frame, t To remove a key, first push it all the way in, slide it upwards slightly, and lift the top half of the key, this should dislodge the upper half of the scissor mechanism, this step can be tricky, the keys were designed to be assembled once and never removed again. -image:/documentation/images/pinebookpro_keyboard_key-half-removed.jpg[width=400] +{{< figure src="/documentation/images/pinebookpro_keyboard_key-half-removed.jpg" width="400" >}} Next you can just slide the key down slightly, this will dislodge the lower half of the scissor mechanism and the key should come completely off the keyboard. -image:/documentation/images/pinebookpro_keyboard_key-removed.jpg[width=400] +{{< figure src="/documentation/images/pinebookpro_keyboard_key-removed.jpg" width="400" >}} Re-attaching a key can be quite fiddly since the mechanism stays attached to the key rather than the keyboard like older scissor designs. @@ -42,7 +42,7 @@ The assembly process is the same as disassembly, just reversed, but you have to Note that if a key mechanism is damaged, pressing in the upper corners of the key will cause it to dislodge and fall off the keyboard. -image:/documentation/images/pinebookpro_keyboard_key.jpg[width=400] +{{< figure src="/documentation/images/pinebookpro_keyboard_key.jpg" width="400" >}} Damaged keys might look like this, note that the pin on the lower right side of the mechanism is slightly deformed and the latch on the upper half of the mechanism is bowed out slightly and cracked. This is enough damage to cause the key to pop out when pressed in the upper corners. diff --git a/content/documentation/Pinebook_Pro/Keyboard/_index.adoc b/content/documentation/Pinebook_Pro/Keyboard/_index.adoc index 99a52f5b..3f961626 100644 --- a/content/documentation/Pinebook_Pro/Keyboard/_index.adoc +++ b/content/documentation/Pinebook_Pro/Keyboard/_index.adoc @@ -82,8 +82,8 @@ This guide is very basic and should be fleshed out with (better) pictures. There Here's what the replacement keyboard looks like: -image:/documentation/images/Pinebook_Pro_new_keyboard-front.jpg[width=300] -image:/documentation/images/Pinebook_Pro_new_keyboard-front.jpg[width=300] +{{< figure src="/documentation/images/Pinebook_Pro_new_keyboard-front.jpg" width="300" >}} +{{< figure src="/documentation/images/Pinebook_Pro_new_keyboard-front.jpg" width="300" >}} _Step 0_: If changing from ISO keyboard to ANSI keyboard, or vice versa, be sure to have a system capable of running the firmware updater that you can access either remotely or with a USB keyboard beyond the internal keyboard, as the firmware for each is very different and keys won't work correctly. See https://forum.pine64.org/showthread.php?tid=8407 (and for NetBSD, https://forum.pine64.org/showthread.php?tid=8716). @@ -91,20 +91,20 @@ _Step 1_: The remove back back panel. There are 10 screws on the back that must be removed, and the back panel detached. I recommend using a PH0 bit. The speakers may remain attached via glue to the case and should be carefully pried off. When this is done, taking photos of how everything looks now can help put it all back together later. -image:/documentation/images/Pinebook_Pro_keyboard-replacement-screws.jpg[width=300] +{{< figure src="/documentation/images/Pinebook_Pro_keyboard-replacement-screws.jpg" width="300" >}} _Step 2_: Places to unscrew. There are 3 items screwed into the keyboard frame that must be removed. There are 2 large screws for daughter board, 3 large screws and 1 small screw for mainboard, and 4 small screws for battery. Be sure to not lose them. I recommend a PH00 bit for the large screws on the daughter and main boards and a PH1 bit for the small screws on the battery and mainboard. -image:/documentation/images/Pinebook_Pro_new_keyboard-back-removed.jpg[width=300] +{{< figure src="/documentation/images/Pinebook_Pro_new_keyboard-back-removed.jpg" width="300" >}} _Step 3_: Remove the battery. Once the battery screws are removed, it should be unplugged from the mainboard and removed. Note that there are two unconnected cables lying around, that should remain unconnected. They are used when the battery is disconnected entirely. -image:/documentation/images/Pinebook_Pro_new_keyboard-zoom-mainboard.jpg.jpg[width=300] -image:/documentation/images/Pinebook_Pro_new_keyboard-zoom-daughterboard.jpg[width=300] +{{< figure src="/documentation/images/Pinebook_Pro_new_keyboard-zoom-mainboard.jpg.jpg" width="300" >}} +{{< figure src="/documentation/images/Pinebook_Pro_new_keyboard-zoom-daughterboard.jpg" width="300" >}} _Step 4_: Unplug the ribbon cables. @@ -119,7 +119,7 @@ There are several ribbon cables. To remove, flip up the tab and gentle pull the _Step 5_: Detach microphone, speakers, and antenna. -image:/documentation/images/Pinebook_Pro_microphone_removed.jpg[One of the Pinebook Pro microphones after removal,title="One of the Pinebook Pro microphones after removal",width=300] +{{< figure src="/documentation/images/Pinebook_Pro_microphone_removed.jpg" title="One of the Pinebook Pro microphones after removal" width="300" >}} The speakers, microphone, and antenna don't have to be detached from the mainboard, but they need to be detached from the keyboard shell. The microphones are held in place by tape, and the speakers have sticky sides. The speakers are found obviously, but the microphones (two of) can be found between the battery and the hinge area. Each microphone can be carefully pulled/wedged out of its position by a small screwdriver or pick. The antenna, similar to the microphones, is found near the hinge area and to the top left of the battery. @@ -127,14 +127,14 @@ _Step 6_: Remove mainboard and daughterboard. At this point, the mainboard and daughterboards should be removed. When unscrewed (see Step 2) they should pull out fairly easily. Put them aside (including microphones and speakers if left attached.) -image:/documentation/images/Pinebook_Pro_new_keyboard-all-boards-removed.jpg[width=300] +{{< figure src="/documentation/images/Pinebook_Pro_new_keyboard-all-boards-removed.jpg" width="300" >}} _Step 7_: Detach the LCD panel. Step 2 didn't tell you, there are 6 more screws to remove here, 3 for each of the hinges. I recommend a PH1 bit for these screws. Unscrew these and the LCD panel will be able to be removed. You may have to jiggle or move the hinges for this. When detached, be sure to place the LCD panel such that the display is protected. -image:/documentation/images/Pinebook_Pro_new_keyboard-detached-display.jpg[width=300] -image:/documentation/images/Pinebook_Pro_new_keyboard-detached-display2.jpg[width=300] +{{< figure src="/documentation/images/Pinebook_Pro_new_keyboard-detached-display.jpg" width="300" >}} +{{< figure src="/documentation/images/Pinebook_Pro_new_keyboard-detached-display2.jpg" width="300" >}} _Step 8_: Try not to break your touchpad @@ -144,15 +144,15 @@ The touchpad is glued to the keyboard shell and it's glued well. There are two p I found it helpful to lift the top left plastic bit on the keyboard to unstick that portion of the touchpad, then push on the top left portion of the touchpad to unstick the rest of the touchpad. -image:/documentation/images/Pinebook_Pro_new_keyboard-touchpad1.jpg[width=300] -image:/documentation/images/Pinebook_Pro_new_keyboard-touchpad2.jpg[width=300] -image:/documentation/images/Pinebook_Pro_new_keyboard-touchpad3.jpg[width=300] +{{< figure src="/documentation/images/Pinebook_Pro_new_keyboard-touchpad1.jpg" width="300" >}} +{{< figure src="/documentation/images/Pinebook_Pro_new_keyboard-touchpad2.jpg" width="300" >}} +{{< figure src="/documentation/images/Pinebook_Pro_new_keyboard-touchpad3.jpg" width="300" >}} _Step 9_: Over the hill, touchpad goes into new shell. In the new keyboard shell put the touchpad back where it was, hopefully the glue will remain sufficiently attached. If there is a glue issue, this guide unfortunately has no advice currently. -image:/documentation/images/Pinebook_Pro_new_keyboard-install-touchpad.jpg[width=300] +{{< figure src="/documentation/images/Pinebook_Pro_new_keyboard-install-touchpad.jpg" width="300" >}} _Step 10_: Reattach the LCD panel. diff --git a/content/documentation/Pinebook_Pro/Power_and_charging.adoc b/content/documentation/Pinebook_Pro/Power_and_charging.adoc index 9afd2686..15a9b53d 100644 --- a/content/documentation/Pinebook_Pro/Power_and_charging.adoc +++ b/content/documentation/Pinebook_Pro/Power_and_charging.adoc @@ -44,7 +44,7 @@ With the external chargers disconnected the system is powered by the battery, so === Overview -image:/documentation/Pinebook_Pro/images/Pbp-charging-simplified.png[title="Pinebook Pro simplified charging schematics",width=300] +{{< figure src="/documentation/Pinebook_Pro/images/Pbp-charging-simplified.png" title="Pinebook Pro simplified charging schematics" width="300" >}} When an external charger is connected, the battery charging process is automatically activated, it doesn't depend on any software interactions and works all the same even with the main SoC powered down. The system automatically chooses between the barrel socket (limiting current draw to 3 A) and Type-C source (limited to 2.5 A), with the former preferred when both are connected at the same time (but the current limit is enforced as if Type-C was used). diff --git a/content/documentation/Pinebook_Pro/Software/Releases.adoc b/content/documentation/Pinebook_Pro/Software/Releases.adoc index e0995317..0abbd4c5 100644 --- a/content/documentation/Pinebook_Pro/Software/Releases.adoc +++ b/content/documentation/Pinebook_Pro/Software/Releases.adoc @@ -17,7 +17,7 @@ For information on how to install these images onto your device, please see the === Manjaro ARM -image:/documentation/images/Manjaro-logo.svg[width=100] +{{< figure src="/documentation/images/Manjaro-logo.svg" width="100" >}} The Manjaro project offers a mainline kernel with patches and modules to support the Pinebook Pro hardware. To learn more about Manjaro please visit https://forum.manjaro.org/c/arm/[Manjaro Forum]. You can follow the ongoing discussion about Manjaro on the https://forum.pine64.org/showthread.php?tid=8207[PINE64 forum]. All images boot from both SD card and the internal eMMC module. @@ -29,7 +29,7 @@ Download: === Armbian -image:/documentation/images/armbian.png[width=100] +{{< figure src="/documentation/images/armbian.png" width="100" >}} Armbian is a base operating system platform for single board computers (_SBCs_) that other projects can trust to build upon. It is a lightweight Debian or Ubuntu based Linux distribution specialized for ARM development boards. Each system is compiled, assembled and optimized by the Armbian Build Tools. It has powerful build and software development tools to make custom builds and a vibrant community. @@ -44,7 +44,7 @@ Notes: === Twister OS -image:/documentation/images/Twister_OS.png[width=100] +{{< figure src="/documentation/images/Twister_OS.png" width="100" >}} Twister OS Armbian-Reforged with Xfce. It boots from microSD card and from eMMC. For more information on Twister OS, please visit this https://twisteros.com/[official site]. You can follow the ongoing discussion about Twister OS on the https://forum.pine64.org/showthread.php?tid=12192[PINE64 forum]. @@ -67,7 +67,7 @@ Get the latest image here: https://twisteros.com/twisterarmbian.html[Direct down === Fedora -image:/documentation/images/fedora1.png[width=100] +{{< figure src="/documentation/images/fedora1.png" width="100" >}} Fedora Linux is a Linux distribution developed by the Fedora Project. It creates an innovative, free, and open source platform for hardware, clouds, and containers that enables software developers and community members to build tailored solutions for their users. @@ -81,7 +81,7 @@ Notes: === Arch Linux ARM -image:/documentation/images/Archlinux-logo.png[width=100] +{{< figure src="/documentation/images/Archlinux-logo.png" width="100" >}} ==== Official Installation @@ -115,7 +115,7 @@ The default Arch Linux ARM user credentials. === postmarketOS -image:/documentation/images/PostmarketOS_logo.png[width=100] +{{< figure src="/documentation/images/PostmarketOS_logo.png" width="100" >}} Official postmarketOS stable builds are available for the Pinebook Pro with the following interfaces: @@ -144,7 +144,7 @@ The installer images allows setting up an encrypted installation on SD or eMMC. === Kali Linux -image:/documentation/images/Kali-logo.png[width=100] +{{< figure src="/documentation/images/Kali-logo.png" width="100" >}} Official pre-built OS images of Kali Linux for the Pinebook Pro featuring all tools you'd expect from the distribution. It boots from microSD card and from eMMC. @@ -163,7 +163,7 @@ Get the latest image here: https://www.offensive-security.com/kali-linux-arm-ima === R-Cade -image:/documentation/images/RCadeLogo.jpg[width=100] +{{< figure src="/documentation/images/RCadeLogo.jpg" width="100" >}} Retro Center's R-Cade [USB / microSD / eMMC Boot] @@ -183,7 +183,7 @@ Retro Center's R-Cade [USB / microSD / eMMC Boot] === Q4OS -image:/documentation/images/q4os.png[width=100] +{{< figure src="/documentation/images/q4os.png" width="100" >}} Q4OS is advertised as a 'fast and powerful operating system based on the latest technologies while offering highly productive desktop environment'. It boots from microSD card and from eMMC. To learn more please visit the https://forum.pine64.org/showthread.php?tid=8385[PINE64 forum] or official https://q4os.org/index.html[Q4OS website]. @@ -197,7 +197,7 @@ User account and password are created on first run. === DietPi -image:/documentation/images/dietpi.png[width=100] +{{< figure src="/documentation/images/dietpi.png" width="100" >}} DietPi is a lightweight, yet easy to setup and feature-rich Linux distribution, based on Debian. To find out more about DietPi, please visit the https://dietpi.com/docs/[official documentation]. Discuss the Pinebook Pro build on the https://forum.pine64.org/showthread.php?tid=14061[PINE64 forum thread]. @@ -214,7 +214,7 @@ Download: === openSUSE -image:/documentation/images/opensuse-distribution.png[width=100] +{{< figure src="/documentation/images/opensuse-distribution.png" width="100" >}} *Download location* @@ -245,7 +245,7 @@ https://fydeos.io/download/device/pinebook-pro === Void Linux -image:/documentation/images/void_bg.png[width=100] +{{< figure src="/documentation/images/void_bg.png" width="100" >}} ==== Images @@ -281,7 +281,7 @@ You can also manually install Void from a rootfs tarball: link:/documentation/Pi === NetBSD -image:/documentation/images/netbsd.png[width=100] +{{< figure src="/documentation/images/netbsd.png" width="100" >}} The image boots from microSD card and from eMMC. To learn more about NetBSD please visit https://www.netbsd.org/[NetBSD main page] @@ -303,7 +303,7 @@ Instructions concerning enabling SSH can be found https://www.netbsd.org/docs/gu === OpenBSD -image:/documentation/images/Puffy_mascot_openbsd.png[width=100] +{{< figure src="/documentation/images/Puffy_mascot_openbsd.png" width="100" >}} The image boots from microSD card and from eMMC. To learn more about OpenBSD, please visit https://www.openbsd.org/[OpenBSD main page] @@ -315,7 +315,7 @@ ARM64 images, (including support for Pinebook Pro), can be found here https://ww === Manjaro ARM -image:/documentation/images/Manjaro-logo.svg[width=100] +{{< figure src="/documentation/images/Manjaro-logo.svg" width="100" >}} The https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer[manjaro-arm-installer] script is intended to install Manjaro ARM directly to SD/eMMC cards without the need for images (including LXQT, Mate & CuboCore editions, as well as full disk encryption). @@ -323,7 +323,7 @@ Running on a Linux x86 computer, it can install Manjaro ARM directly to an empty === Armbian -image:/documentation/images/armbian.png[width=100] +{{< figure src="/documentation/images/armbian.png" width="100" >}} You can use the https://github.com/armbian/build[Armbian Builder] to generate your own Armbian images of various types. @@ -342,7 +342,7 @@ The builder supports building any version of Debian and any version of Ubuntu wi === Debian -image:/documentation/images/Debian-logo.png[width=100] +{{< figure src="/documentation/images/Debian-logo.png" width="100" >}} * Uses only the upstream kernel and firmware without special patches * Display doesn't always work properly on first boot of installer, usually fixed after a couple tries @@ -357,7 +357,7 @@ The official images are *not* recommended yet until the display begins working c === Gentoo -image:/documentation/images/GentooLogo.png[width=100] +{{< figure src="/documentation/images/GentooLogo.png" width="100" >}} There is a script that prepares a Gentoo arm64 stage 3 tarball for the Pinebook Pro. Unfortunately, this script is not currently functional, and requires extensive troubleshooting to make work. New instructions are currently being created and will be available here. @@ -510,7 +510,7 @@ Now you should reboot the machine and see if it boots into gentoo. If it does: c === Kali Linux -image:/documentation/images/Kali-logo.png[width=100] +{{< figure src="/documentation/images/Kali-logo.png" width="100" >}} There is a script to create official Kali Linux OS images for the Pinebook Pro. The script carries out the build process in entirety and is Pinebook Pro specific. @@ -521,7 +521,7 @@ There is a script to create official Kali Linux OS images for the Pinebook Pro. === NixOS -image:/documentation/images/NixOS.webp[width=100] +{{< figure src="/documentation/images/NixOS.webp" width="100" >}} You can follow the ongoing discussion about NixOS on the https://forum.pine64.org/showthread.php?tid=10524[PINE64 forum]. There is a good chance we will see Tier 1 support for aarch64, including the Pinebook Pro, in 2021 (see https://github.com/NixOS/rfcs/pull/87). @@ -532,7 +532,7 @@ You can follow the ongoing discussion about NixOS on the https://forum.pine64.or === SkiffOS -image:/documentation/images/SkiffOS-Icon-1.png[width=100] +{{< figure src="/documentation/images/SkiffOS-Icon-1.png" width="100" >}} *Installation* @@ -544,7 +544,7 @@ image:/documentation/images/SkiffOS-Icon-1.png[width=100] === Slackware -image:/documentation/images/slackware.jpg[width=100] +{{< figure src="/documentation/images/slackware.jpg" width="100" >}} https://arm.slackware.com/[Slackware] is the world's oldest actively developed Linux distribution, providing a modern user land (applications) and Linux Kernel, within a more classic Unix Operating System environment. diff --git a/content/documentation/Pinebook_Pro/UART.adoc b/content/documentation/Pinebook_Pro/UART.adoc index 0fece831..4652a3b2 100644 --- a/content/documentation/Pinebook_Pro/UART.adoc +++ b/content/documentation/Pinebook_Pro/UART.adoc @@ -9,7 +9,7 @@ menu: weight: 6 --- -image::/documentation/images/PinePhone_Serial_Cable.png[title="This shows signals from the Pinebook Pro's point of view, so connect the adapter's RX to ring 1, and TX to the tip. See also the link:https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf[Pine64 official document] describing this.",width=400] +{{< figure src="/documentation/images/PinePhone_Serial_Cable.png" title="This shows signals from the Pinebook Pro's point of view, so connect the adapter's RX to ring 1, and TX to the tip. See also the link:https://files.pine64.org/doc/pinebook/guide/Pinebook_Earphone_Serial_Console_Developer_Guide.pdf[Pine64 official document] describing this." width="400" >}} Serial console UART is enabled by flipping the UART switch to the ON position (item 9). To do so, you need to remove the Pinebook Pro's bottom cover by following the disassembly and reassembly guidelines. The OFF position is towards the touchpad, while the ON position is towards the display hinges. diff --git a/content/documentation/Pinebook_Pro/_index.adoc b/content/documentation/Pinebook_Pro/_index.adoc index 1242728f..0c00af53 100644 --- a/content/documentation/Pinebook_Pro/_index.adoc +++ b/content/documentation/Pinebook_Pro/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/PBP.jpg[Pinebook Pro running Debian with MATE,title="Pinebook Pro running Debian with MATE",width=400] +{{< figure src="/documentation/images/PBP.jpg" title="Pinebook Pro running Debian with MATE" width="400" >}} The *Pinebook Pro* is a Linux and *BSD ARM laptop from PINE64. It is built to be a compelling alternative to mid-ranged Chromebooks that people convert into Linux laptops. diff --git a/content/documentation/Pinecil/Breakout_board.adoc b/content/documentation/Pinecil/Breakout_board.adoc index 048f983b..8b295742 100644 --- a/content/documentation/Pinecil/Breakout_board.adoc +++ b/content/documentation/Pinecil/Breakout_board.adoc @@ -20,7 +20,7 @@ The Pinecil Break out board has these features: Photos: -image:/documentation/images/Pinecil_breakout_top.jpg[Top_view,title="Top_view"] -image:/documentation/images/Pinecil_breakout_bottom.jpg[Bottom_view,title="Bottom_view"] -image:/documentation/images/UART-pinecil-breakout-board-testing30.png[ UART Debugging,title=" UART Debugging"] +{{< figure src="/documentation/images/Pinecil_breakout_top.jpg" title="Top_view" >}} +{{< figure src="/documentation/images/Pinecil_breakout_bottom.jpg" title="Bottom_view" >}} +{{< figure src="/documentation/images/UART-pinecil-breakout-board-testing30.png" title=" UART Debugging" >}} diff --git a/content/documentation/Pinecil/Firmware.adoc b/content/documentation/Pinecil/Firmware.adoc index 185237a5..57f1894a 100644 --- a/content/documentation/Pinecil/Firmware.adoc +++ b/content/documentation/Pinecil/Firmware.adoc @@ -15,7 +15,7 @@ This article is about updating/flashing the link:/documentation/Pinecil[Pinecil] TIP: Pinecil is designed to use *only 1 power port* at any time. Only the USB-C cable should be plugged in during firmware updates. Never attempt to use both rear ports at the same time or the PC and Pinecil will be damaged. -image:/documentation/images/Pinecil-V1andV2.png[right,title="right",width=400] +{{< figure src="/documentation/images/Pinecil-V1andV2.png" title="right" width="400" >}} The firmware that comes with the Pinecil is https://ralim.github.io/IronOS/[open source Ralim's IronOS]. It's a good idea to check for updates regularly as development is very active and there may be enhancements or bug fixes. @@ -144,7 +144,7 @@ This is a CLI that runs in a terminal console. Get the latest zip file for Linux == Update V1 -image:/documentation/images/Pinecil-V1andV2.png[right,title="right",width=400] +{{< figure src="/documentation/images/Pinecil-V1andV2.png" title="right" width="400" >}} . Pinecil V1 uses a *.dfu file type for firmware. The newer Pinecil V2 only uses *.bin firmware type files. . Pinecil V1 models were sold until July 2022 and then discontinued. @@ -183,7 +183,7 @@ IMPORTANT: Do not use the DC barrel jack while updating firmware or you may dest == Boot Logo Art -image:/documentation/images/Boot-logo-dogbone.jpg[Dog bone by River M.] +{{< figure src="/documentation/images/Boot-logo-dogbone.jpg" title="Dog bone by River M." >}} === Get Art @@ -195,7 +195,7 @@ image:/documentation/images/Boot-logo-dogbone.jpg[Dog bone by River M.] * To make custom art, https://github.com/Ralim/IronOS-Meta[follow instructions here]. * Some art is animated: the very small file size limit for boot logos prevents too many frames from being possible. -image:/documentation/images/IronOS.gif[] +{{< figure src="/documentation/images/IronOS.gif" >}} === Install diff --git a/content/documentation/Pinecil/Further_information/Pictures.adoc b/content/documentation/Pinecil/Further_information/Pictures.adoc index 38de2f9e..b951541a 100644 --- a/content/documentation/Pinecil/Further_information/Pictures.adoc +++ b/content/documentation/Pinecil/Further_information/Pictures.adoc @@ -11,30 +11,30 @@ menu: Pre-release: -image:/documentation/images/Pinecil_Exploded_Diagram_ver_0.9.png[Pinecil_renders,title="Pinecil_renders"] -image:/documentation/images/PinecilPrototype.jpg[Pinecil prototype,title="Pinecil prototype"] +{{< figure src="/documentation/images/Pinecil_Exploded_Diagram_ver_0.9.png" title="Pinecil_renders" >}} +{{< figure src="/documentation/images/PinecilPrototype.jpg" title="Pinecil prototype" >}} Production: -image:/documentation/images/Pinecil-V2-box-1024x1024.jpg[width=202] -image:/documentation/images/Pinecilv2-2.jpg[https://pine64.com/product-category/pinecil/[Pinecil_V2,_side_view] -image:/documentation/images/Pinecil-V2-dissasebled.jpg[Pinecil_V2_disassembled,_newly_designed_shorter_6.2_ohm_tip,title="Pinecil_V2_disassembled,_newly_designed shorter 6.2 ohm tip"] -image:/documentation/images/Pinecil-Clear-Case1.png[Transparent_handle,title="Transparent handle"] -image:/documentation/images/Pinecil-Contact2.png[https://pine64.com/product-category/pinecil/[Replacement_internal_contacts] -image:/documentation/images/Pinecil-bb2-01.jpg[width=202] +{{< figure src="/documentation/images/Pinecil-V2-box-1024x1024.jpg" width="202" >}} +{{< figure src="/documentation/images/Pinecilv2-2.jpg" title="Pinecil V2, side view">}} +{{< figure src="/documentation/images/Pinecil-V2-dissasebled.jpg" title="Pinecil_V2_disassembled,_newly_designed_shorter_6.2_ohm_tip" >}} +{{< figure src="/documentation/images/Pinecil-Clear-Case1.png" title="Transparent_handle" >}} +{{< figure src="/documentation/images/Pinecil-Contact2.png" title="Replacement internal contacts" >}} +{{< figure src="/documentation/images/Pinecil-bb2-01.jpg" width="202" >}} Cartridge/Tips: -image:/documentation/images/Pinecil-Short-Tip-SetFine-1.jpeg[https://pine64.com/product/pinecil-soldering-short-tip-set-fine/[Short_Tips,_Fine_Set] -image:/documentation/images/Pinecil-Short-Tip-SetGross-1.jpeg[_https://pine64.com/product/pinecil-soldering-short-tip-set-gross/[Short_Tips,_Gross_Set] -image:/documentation/images/Pinecil-Tip-SetFine-1.jpg[_https://pine64.com/product/pinecil-soldering-tip-set-fine/[Normal_Tips,_Fine_Set] -image:/documentation/images/Pinecil-Tip-SetGross-1.jpg[_https://pine64.com/product/pinecil-soldering-tip-set-gross/[Normal_Tips,_Gross_Set] +{{< figure src="/documentation/images/Pinecil-Short-Tip-SetFine-1.jpeg" title="Short tips, fine set" >}} +{{< figure src="/documentation/images/Pinecil-Short-Tip-SetGross-1.jpeg" title="Short tips, gross set" >}} +{{< figure src="/documentation/images/Pinecil-Tip-SetFine-1.jpg" title="Normal tips, fine set" >}} +{{< figure src="/documentation/images/Pinecil-Tip-SetGross-1.jpg" title="Normal tips, gross set" >}} PCB: -image:/documentation/images/PCP-Top-side-screen.jpg[Pinecil_PCB_screen_side,_V2_on_top,_V1_on_bottom,title="Pinecil_PCB_screen_side,_V2_on_top,_V1 on bottom"] -image:/documentation/images/PCP-Bottom-Side.jpg[Pinecil PCB bottom side, V2 on top, V1 on bottom,title="Pinecil PCB bottom side, V2 on top, V1 on bottom"] +{{< figure src="/documentation/images/PCP-Top-side-screen.jpg" title="Pinecil_PCB_screen_side,_V2_on_top,_V1_on_bottom" >}} +{{< figure src="/documentation/images/PCP-Bottom-Side.jpg" title="Pinecil PCB bottom side, V2 on top, V1 on bottom" >}} Accessories: -image:/documentation/images/Pinecil-Thumb-Screws.png[Thumb screws on V1 & V2 ,title="Thumb screws on V1 & V2 "] \ No newline at end of file +{{< figure src="/documentation/images/Pinecil-Thumb-Screws.png" title="Thumb screws on V1 & V2 " >}} \ No newline at end of file diff --git a/content/documentation/Pinecil/Further_information/Pinecil_in_the_Media.adoc b/content/documentation/Pinecil/Further_information/Pinecil_in_the_Media.adoc index df5f0b27..05cd6145 100644 --- a/content/documentation/Pinecil/Further_information/Pinecil_in_the_Media.adoc +++ b/content/documentation/Pinecil/Further_information/Pinecil_in_the_Media.adoc @@ -14,7 +14,7 @@ menu: * https://www.reddit.com/r/PINE64official/comments/xk9vxu/most_interesting_man_in_the_world_i_dont_always/[Most interesting man] * Science Pinecil -image:/documentation/images/Science-pinecil-v2-01.png[] +{{< figure src="/documentation/images/Science-pinecil-v2-01.png" >}} == Videos diff --git a/content/documentation/Pinecil/How_to_repair.adoc b/content/documentation/Pinecil/How_to_repair.adoc index 0e9ce60c..57787850 100644 --- a/content/documentation/Pinecil/How_to_repair.adoc +++ b/content/documentation/Pinecil/How_to_repair.adoc @@ -140,26 +140,26 @@ Pinecil requires a center-positive DC power supply which most are, but some are IMPORTANT: *Check the polarity* of the DC barrel plug before plugging in a random charger. Incorrect polarity will break the Pinecil. The https://www.youtube.com/watch?v=5DBTNplNTfA[video here] shows how to check. -image:/documentation/images/AC_adaptor_polarity.png[width=400] +{{< figure src="/documentation/images/AC_adaptor_polarity.png" width="400" >}} -image:/documentation/images/Nintendo-center-negative.png[width=300] +{{< figure src="/documentation/images/Nintendo-center-negative.png" width="300" >}} Reference the article on [[Pinecil_Power_Supplies#DC_Barrel_Power| DC barrel chargers here]], (i.e., laptop bricks) for appropriate USB-C and DC chargers that will work with the Pinecil. == Images -image:/documentation/images/PCP-Top-side-screen.jpg[Screen side: V2 on top, V1 below] -image:/documentation/images/PCP-Bottom-Side.jpg[Pinecone side: V2 on top, V1 below] -image:/documentation/images/Pinecil_v2_MOSFET.JPG[MOSFET V2,title="MOSFET V2"] -image:/documentation/images/FUSB302-V2-02.JPG[width=302] -image:/documentation/images/Pinecil_LDOandOP-Amp.png[_LDO_and_OP-Amp,title="_LDO_and_OP-Amp"] -image:/documentation/images/Under_OLED_screen01.png[ Under the OLED screen, V2,title=" Under the OLED screen, V2"] +{{< figure src="/documentation/images/PCP-Top-side-screen.jpg" title="Screen side: V2 on top, V1 below" >}} +{{< figure src="/documentation/images/PCP-Bottom-Side.jpg" title="Pinecone side: V2 on top, V1 below" >}} +{{< figure src="/documentation/images/Pinecil_v2_MOSFET.JPG" title="MOSFET V2" >}} +{{< figure src="/documentation/images/FUSB302-V2-02.JPG" width="302" >}} +{{< figure src="/documentation/images/Pinecil_LDOandOP-Amp.png" title="_LDO_and_OP-Amp" >}} +{{< figure src="/documentation/images/Under_OLED_screen01.png" title=" Under the OLED screen, V2" >}} == Pinecil V1, 24V Mod WARNING: Do this at your own risk, read everything in this section and related/linked articles, and go to the Pinecil community chat if you desire advice. An incorrect cut of the trace could render the Pinecil non-working. -image:/documentation/images/Pinecil-V1andV2.png[Pinecil V1 has blue rubber. Newer Pinecil V2 has green rubber & Bluetooth LE chip] +{{< figure src="/documentation/images/Pinecil-V1andV2.png" title="Pinecil V1 has blue rubber. Newer Pinecil V2 has green rubber & Bluetooth LE chip" >}} . This modification is not for the V2 (sold after Aug 1, 2022 with green thumb grip) as the V2 already has 24V DC barrel charger capability. . If you have an older V1 model, then first upgrade to the newest link:/documentation/Pinecil/Firmware/[firmware here] before starting this modification. The PD debug menu was added to the firmware in 2.17 and other important fixes came later. Access to the hidden PD debug menu is necessary to assist with this mod. @@ -169,7 +169,7 @@ image:/documentation/images/Pinecil-V1andV2.png[Pinecil V1 has blue rubber. Newe . See the February 2022 https://www.pine64.org/2022/02/15/february-update-chat-with-the-machine/[Community update here]. The photo is incorrect in the article. It is _not_ a before and after photo. * Photo shows two separate PCBs of Pinecil V1 made at different times; therefore, the trace is cut in a slightly different location depending on which one it looks like. * The PCB with 2 small via holes and is harder to cut in the correct location to avoid damaging the holes. This is called the "whalecil" in community chat (looks like a whale). -image:/documentation/images/Pinecil_V1_24V_Mod.png[width=400] +{{< figure src="/documentation/images/Pinecil_V1_24V_Mod.png" width="400" >}} PCB 1 style (left photo) is easier to cut the trace. Cut all the way across the trace and deep enough to cut the copper contact. PCB 2 style (right photo) is harder because the trace has to be cut without damaging the 2 via holes. . Don't plug in 24V until you first check with a USB-C PD charger that PD debug says *No VBUS* which means the mod is complete. If it still says *W. Vbus*, then the connection still exist. Cut a little deeper and clean the cut with some IPA (isopropyl alcohol) to remove any copper dust, dry it and check again. Taking a macro photo with a phone helps to examine the cut. If a USB-C charger is not available, often a phone with a USB-C port is a PD type, and can be used like a charger to plug in and check the PD debug messages (unfortunately, a PC port is not normally "PD" and won't give proper PD Debug). diff --git a/content/documentation/Pinecil/Modifications/Hall_effect_sensor.adoc b/content/documentation/Pinecil/Modifications/Hall_effect_sensor.adoc index 40a8e5a8..74f93013 100644 --- a/content/documentation/Pinecil/Modifications/Hall_effect_sensor.adoc +++ b/content/documentation/Pinecil/Modifications/Hall_effect_sensor.adoc @@ -49,16 +49,16 @@ The Hall Effect Sensor (HES) is an optional end user installed sensor that activ == Images Before installation, location at U14: -image:/documentation/Pinecil/images/hall_effect_1.jpg[] +{{< figure src="/documentation/Pinecil/images/hall_effect_1.jpg" >}} After installation: -image:/documentation/Pinecil/images/hall_effect_2.jpg[] +{{< figure src="/documentation/Pinecil/images/hall_effect_2.jpg" >}} Only needs small amount of solder: -image:/documentation/Pinecil/images/hall_effect_3.jpg[] +{{< figure src="/documentation/Pinecil/images/hall_effect_3.jpg" >}} Kapton tape/protect the 3 Via holes above 3-pin side,title="Kapton tape/protect the 3 Via holes above 3-pin side": -image:/documentation/Pinecil/images/hall_effect_4.jpg[] +{{< figure src="/documentation/Pinecil/images/hall_effect_4.jpg" >}} Kapton tape/protect the NTC sensor on opposite side of V2 (V1 does not have this): -image:/documentation/Pinecil/images/NTC-temp-Sensor.jpg[] \ No newline at end of file +{{< figure src="/documentation/Pinecil/images/NTC-temp-Sensor.jpg" >}} \ No newline at end of file diff --git a/content/documentation/Pinecil/Power_supplies/Power_supplies.adoc b/content/documentation/Pinecil/Power_supplies/Power_supplies.adoc index 35c8172a..585f8795 100644 --- a/content/documentation/Pinecil/Power_supplies/Power_supplies.adoc +++ b/content/documentation/Pinecil/Power_supplies/Power_supplies.adoc @@ -74,7 +74,7 @@ NOTE: a PD3.1 240W cable needs to be purchased if you want the full 28V performa ==== PD3.0 65w 20V Chargers -image:/documentation/images/USB_C_PD_shared_watts_charger.jpg[width=400] +{{< figure src="/documentation/images/USB_C_PD_shared_watts_charger.jpg" width="400" >}} . https://pine64.com/product-category/pinepower/[PD120w PinePower Desktop w/Grounded 3-pin plug] . https://pine64.com/product/pinepower-65w-gan-2c1a-charger-with-international-plugs/[PD65w GAN II Pinepower Portable Travel charger] (PD@20V) @@ -103,9 +103,9 @@ image:/documentation/images/USB_C_PD_shared_watts_charger.jpg[width=400] IMPORTANT: *Check the polarity* of the DC Barrel plug before plugging in a random charger or it could break the Pinecil. -image:/documentation/images/AC_adaptor_polarity.png[width=350] +{{< figure src="/documentation/images/AC_adaptor_polarity.png" width="350" >}} -image:/documentation/images/Nintendo-center-negative.png[width=350] +{{< figure src="/documentation/images/Nintendo-center-negative.png" width="350" >}} === DC Laptop Brick @@ -120,7 +120,7 @@ image:/documentation/images/Nintendo-center-negative.png[width=350] === Tool Batteries 18V-21V -image:/documentation/images/Power_Wheel_Adapters_for_18-21V_Tool_Batteries.png[width=475] +{{< figure src="/documentation/images/Power_Wheel_Adapters_for_18-21V_Tool_Batteries.png" width="475" >}} https://a.co/bo626Nk[Power-Wheels adapter link] with Ryobi battery diff --git a/content/documentation/Pinecil/Tips.adoc b/content/documentation/Pinecil/Tips.adoc index 5b3e30a2..2ea34270 100644 --- a/content/documentation/Pinecil/Tips.adoc +++ b/content/documentation/Pinecil/Tips.adoc @@ -30,11 +30,11 @@ TIP: Pay attention to the length! Pine Store sells two different lengths of tips === How to check new tips? -image:/documentation/images/Multimeter_measuring_Short_Tip.png[Short Tip 6.2 Ω,title=" Short Tip 6.2 Ω",width=200] +{{< figure src="/documentation/images/Multimeter_measuring_Short_Tip.png" title=" Short Tip 6.2 Ω" width="200" >}} 1. Remove the screw on top, then remove the cartridge. Clean new cartridges/tips with isopropyl alcohol (IPA) to remove any factory residue before installing (avoid strange behavior). If you have no IPA, use a dry clean towel, especially the white end with the two silver contacts (do not use water; it could get into the seam line on the white end). This often resolves issues with glitchy temperatures or random no-tip symbol from poor or dirty electric contact [https://github.com/Ralim/IronOS/issues/1601 reference]. -image:/documentation/images/CleanTip-Cartridge-Contacts.jpg[Clean contacts with IPA] +{{< figure src="/documentation/images/CleanTip-Cartridge-Contacts.jpg" title="Clean contacts with IPA" >}} . Then install the cartridge/tip, re-install the screw on top, and heat the tip a few times to 350 °C for a couple minutes. . If you don't have a multimeter, then after you initially heat the tips a few times to 350 °C. Then change the temperature to the link:/documentation/Pinecil/Guides_to_soldering#what_temperature_should_i_use?[correct range] for the solder you purchased and check if it melts solder (add a little solder to the tip end also before storing it). @@ -72,9 +72,9 @@ IMPORTANT: *Pay attention to the length in your cart!* Pine Store sells two diff NOTE: Older Pinecil V1 can not use the short tips until firmware code is written to enable manual selection of 6.2 Ω or 8.0 Ω tip. *Only the V2 model* has the hardware to auto-detect the two kinds of tips short 6.2 Ω or regular length 8.0 Ω. If you would like to help with the code, see https://github.com/Ralim/IronOS[GitHub/IronOS]. -image:/documentation/images/Pinecil-Short-Tip-SetGross-1.jpeg[https://pine64.com/product/pinecil-soldering-short-tip-set-gross/[Short_Gross_set,_white_box] -image:/documentation/images/Pinecil-Short-Tip-SetFine-1.jpeg[https://pine64.com/product/pinecil-soldering-short-tip-set-fine/[Short_Fine_set,_white_box] -image:/documentation/images/Pinecil-ST-B2.jpg[ST-B2 conical short tip included with the V2 Pinecil,title="ST-B2 conical short tip included with the V2 Pinecil",width=250] +{{< figure src="/documentation/images/Pinecil-Short-Tip-SetGross-1.jpeg" title="Short gross set, white box" >}} +{{< figure src="/documentation/images/Pinecil-Short-Tip-SetFine-1.jpeg" title="Short fine set, white box" >}} +{{< figure src="/documentation/images/Pinecil-ST-B2.jpg" title="ST-B2 conical short tip included with the V2 Pinecil" width="250" >}} * The shorter tip is designed for higher performance and requires more power than longer traditional TS100 tips * Recommend using minimum of usb-C PD65W-3.25A-20V or higher voltage charger when using Short tips (short tip draws more power than longer tips because of the lower ohms). @@ -91,21 +91,21 @@ IMPORTANT: *Pay attention to the length!* Pine Store sells two different lengths * Normal Length https://pine64.com/product/pinecil-soldering-tip-set-gross/[Gross Set here] (~8.0 Ω) * Normal Length https://pine64.com/product/pinecil-soldering-tip-set-fine/[Fine Set here] (~8.0 Ω) -image:/documentation/images/Pinecil-Tip-SetFine-1.jpg[Fine Set, Normal length,title=" Fine Set, Normal length",width=250] +{{< figure src="/documentation/images/Pinecil-Tip-SetFine-1.jpg" title=" Fine Set, Normal length" width="250" >}} -image:/documentation/images/Pinecil-Tip-SetGross-1.jpg[Gross Set, Normal length,title=" Gross Set, Normal length",width=250] +{{< figure src="/documentation/images/Pinecil-Tip-SetGross-1.jpg" title=" Gross Set, Normal length" width="250" >}} -image:/documentation/images/PinecilTipSets.jpg[Regular Length TS Tips: Left= Fine set, Right = Gross set. Both TS sets have ~8.0 ohm tips and are the standard length similar to other TS100 style tips.,title=" Regular Length TS Tips: Left= Fine set, Right = Gross set. Both TS sets have ~8.0 ohm tips and are the standard length similar to other TS100 style tips.",width=500] +{{< figure src="/documentation/images/PinecilTipSets.jpg" title=" Regular Length TS Tips: Left= Fine set, Right = Gross set. Both TS sets have ~8.0 ohm tips and are the standard length similar to other TS100 style tips." width="500" >}} IMPORTANT: Currently, Pinecil V1 original uses the normal length ts100 style tips and not the newer Short tips designed for V2. Ralim is working on adding a feature to the firmware to allow people with the older V1 Pinecil to manually switch a profile setting which allows toggling between Normal Tip and Short tip profiles (adequate power supply must also be used min. PD65w 3.25A, 20V recommended). Check Github Ralim's IronOS for progress information. Always unplug when swapping tips. === Other compatible tips -image:/documentation/images/TS100-Tip-Styles.png[BC3 and JL02 are not sold by Pine Store, ~8.0 Ω,title=" BC3 and JL02 are not sold by Pine Store, ~8.0 Ω",width=300] +{{< figure src="/documentation/images/TS100-Tip-Styles.png" title=" BC3 and JL02 are not sold by Pine Store, ~8.0 Ω" width="300" >}} *Common resistances for tips:* -image:/documentation/images/TipResistance2.png[width=200] +{{< figure src="/documentation/images/TipResistance2.png" width="200" >}} * PINE64 designed short tip 6.2 Ω, shorter length, only at pine64.com. * no brand long tip 7.9 Ω, normal length ts100 style @@ -116,5 +116,5 @@ image:/documentation/images/TipResistance2.png[width=200] This photo shows common irons to compare the distance from the finger grip to the work surface. -image:/documentation/images/Compare-iron-tip-sizes.jpg[width=500] -image:/documentation/images/Compare-PinecilV2-iron-sizes.png[width=500] +{{< figure src="/documentation/images/Compare-iron-tip-sizes.jpg" width="500" >}} +{{< figure src="/documentation/images/Compare-PinecilV2-iron-sizes.png" width="500" >}} diff --git a/content/documentation/Pinecil/_index.adoc b/content/documentation/Pinecil/_index.adoc index f6d5d3f0..99521aa1 100644 --- a/content/documentation/Pinecil/_index.adoc +++ b/content/documentation/Pinecil/_index.adoc @@ -13,8 +13,8 @@ menu: Note: Other irons only care if they can solder. The Pinecil is held to an additional standard; how well can it meet the needs of the open source community as a RISC-V development tool. It includes hardware features not found on other soldering irons such as BLE Bluetooth in the V2 in order to support FOSS community feature requests for both fun and science. -image:/documentation/images/Pinecil_GraphicGreenRISCV.png[width=500] +{{< figure src="/documentation/images/Pinecil_GraphicGreenRISCV.png" width="500" >}} -image:/documentation/images/Pinecilv2-1.jpg[Pinecil_V2,_launched_Aug_2,_2022,title="Pinecil_V2,_launched_Aug_2,_2022",width=300] -image:/documentation/images/Pinecilv2-2-transparent-background.png[ Pinecil V2, side view,title=" Pinecil V2, side view",width=300] +{{< figure src="/documentation/images/Pinecilv2-1.jpg" title="Pinecil_V2,_launched_Aug_2,_2022" width="300" >}} +{{< figure src="/documentation/images/Pinecilv2-2-transparent-background.png" title=" Pinecil V2, side view" width="300" >}} diff --git a/content/documentation/Pinedio/Gateway.adoc b/content/documentation/Pinedio/Gateway.adoc index f80cb7a4..ba325e40 100644 --- a/content/documentation/Pinedio/Gateway.adoc +++ b/content/documentation/Pinedio/Gateway.adoc @@ -50,10 +50,10 @@ Pin 10 = RX == Pictures -image:/documentation/images/Blog-april-InsideLoRaGateway.jpg[] -image:/documentation/images/Blog-april-InsideLoRaGateway2.jpeg[] -image:/documentation/images/Discord-lora-gateway-20210413_143615.jpg[] -image:/documentation/images/Discord-lora-gateway-20210413_1435271.jpg[] +{{< figure src="/documentation/images/Blog-april-InsideLoRaGateway.jpg" >}} +{{< figure src="/documentation/images/Blog-april-InsideLoRaGateway2.jpeg" >}} +{{< figure src="/documentation/images/Discord-lora-gateway-20210413_143615.jpg" >}} +{{< figure src="/documentation/images/Discord-lora-gateway-20210413_1435271.jpg" >}} == Operating systems diff --git a/content/documentation/Pinedio/Other_end_nodes.adoc b/content/documentation/Pinedio/Other_end_nodes.adoc index 092082be..b9aa0b3b 100644 --- a/content/documentation/Pinedio/Other_end_nodes.adoc +++ b/content/documentation/Pinedio/Other_end_nodes.adoc @@ -21,7 +21,7 @@ All the end-nodes use the SX1262 chip. == Pictures -image:/documentation/images/Blog-april-USB-LoRa-1024x655.jpg[] -image:/documentation/images/Blog-april-LoRa-something-839x1024.jpg[] -image:/documentation/images/Discord_20210421_lora_usb_closeup.jpg[] +{{< figure src="/documentation/images/Blog-april-USB-LoRa-1024x655.jpg" >}} +{{< figure src="/documentation/images/Blog-april-LoRa-something-839x1024.jpg" >}} +{{< figure src="/documentation/images/Discord_20210421_lora_usb_closeup.jpg" >}} diff --git a/content/documentation/Pinedio/USB_adapter.adoc b/content/documentation/Pinedio/USB_adapter.adoc index 23f7b5fe..b8566bfb 100644 --- a/content/documentation/Pinedio/USB_adapter.adoc +++ b/content/documentation/Pinedio/USB_adapter.adoc @@ -9,7 +9,7 @@ menu: weight: 2 --- -image:/documentation/images/Pine64-lora-usb-adapter.jpg[The PINE64 USB LoRa adapter,title="The PINE64 USB LoRa adapter"] +{{< figure src="/documentation/images/Pine64-lora-usb-adapter.jpg" title="The PINE64 USB LoRa adapter" >}} The PINE64 USB LoRa adapter is based on the Semtech SX1262 LoRa module and the CH341 USB bus converter chip. The *CH341* chip can be configured in multiple mode to convert USB to various serial and parallel ports. In this case, it's configured in *synchronous serial mode*, which allows this chip to convert from USB to the SPI bus needed to talk to the SX1262 LoRa module: @@ -23,7 +23,7 @@ The PINE64 USB LoRa adapter is based on the Semtech SX1262 LoRa module and the C == Pins -image:/documentation/images/Lora-usb-pins.jpg[Pinout] +{{< figure src="/documentation/images/Lora-usb-pins.jpg" title="Pinout" >}} [cols="1,1,1"] |=== @@ -359,5 +359,5 @@ I found https://github.com/YukiWorkshop/sx126x_driver[this C++ driver]. It's wel As I don't have any 'raw' LoRa device on hands, I check that it was actually transmitting something using my SDR setup (simple TNT usb key and *Gqrx* software): -image:/documentation/images/pine64-lora-usb-adapter-sdr.png[width=500] +{{< figure src="/documentation/images/pine64-lora-usb-adapter-sdr.png" width="500" >}} diff --git a/content/documentation/Quartz64/Accessories/Premium_aluminium_case.adoc b/content/documentation/Quartz64/Accessories/Premium_aluminium_case.adoc index 2cfb25e3..676e31d8 100644 --- a/content/documentation/Quartz64/Accessories/Premium_aluminium_case.adoc +++ b/content/documentation/Quartz64/Accessories/Premium_aluminium_case.adoc @@ -15,15 +15,15 @@ The Quartz64 model A can be made to fit this case, however some filing of one of Interference between Quartz64 model A and the case as supplied:- -image:/documentation/images/quartz64a-rockpro64case-1.jpg[width=400] +{{< figure src="/documentation/images/quartz64a-rockpro64case-1.jpg" width="400" >}} Fitment once the case has been filed:- -image:/documentation/images/quartz64a-rockpro64case-2.jpg[width=400] +{{< figure src="/documentation/images/quartz64a-rockpro64case-2.jpg" width="400" >}} Fitment of the other end (no modification necessary):- -image:/documentation/images/quartz64a-rockpro64case-3.jpg[width=400] +{{< figure src="/documentation/images/quartz64a-rockpro64case-3.jpg" width="400" >}} Also note that the SoC in the Quartz64-A is slightly lower than the Rock64 Pro one (apparently about 0.6mm). This case includes an internal post which (using a thermal pad) touches the SoC to transfer heat from the SoC to the case. However it does not make good contact with the RK3566. The best solution is probably to source a thicker thermal pad. diff --git a/content/documentation/Quartz64/How-Tos/Connecting_a_MIPI-DSI_display.adoc b/content/documentation/Quartz64/How-Tos/Connecting_a_MIPI-DSI_display.adoc index 7169e0bf..1e10bd35 100644 --- a/content/documentation/Quartz64/How-Tos/Connecting_a_MIPI-DSI_display.adoc +++ b/content/documentation/Quartz64/How-Tos/Connecting_a_MIPI-DSI_display.adoc @@ -19,7 +19,7 @@ When connecting the display, please make sure the board is powered off and unplu === Model A -image:/documentation/images/Quartz64-model-a-dsi.jpg[] +{{< figure src="/documentation/images/Quartz64-model-a-dsi.jpg" >}} To connect the hardware, lift up the dark flap of the part marked with "DSI" in red in the above picture. Then, insert the flat flex cable with the contacts pointing down (and the blue backing pointing up). In the same fashion, connect the thinner touch panel controller cable to the port marked with "TP" in blue. diff --git a/content/documentation/Quartz64/How-Tos/Using_a_battery.adoc b/content/documentation/Quartz64/How-Tos/Using_a_battery.adoc index c8a01d39..c24d24de 100644 --- a/content/documentation/Quartz64/How-Tos/Using_a_battery.adoc +++ b/content/documentation/Quartz64/How-Tos/Using_a_battery.adoc @@ -13,7 +13,7 @@ The link:/documentation/Quartz64[Quartz64 Model A] allows for it to be powered f == Pin-out -image:/documentation/images/Quartz64_Model_A_VBAT_Connector_Pinout.png[right,title="right"] +{{< figure src="/documentation/images/Quartz64_Model_A_VBAT_Connector_Pinout.png" title="right" >}} The pins on the board are a JST PH-3 compatible header labelled _+VBAT-_. As one might guess, the positive wire should be towards the +, and the ground wire towards -. The center pin of the connector is for a temperature probe. @@ -67,7 +67,7 @@ Not all parts of the board can be supplied from the battery. When you use batter * All USB ports except for the black one * Black USB port's VBUS (the one above the USB 3.0 port) will go through a 22ms brownout to approximately VCC_SYS - 0.6V voltage, before the RK817 BOOST regulator kicks in. This will likely cause the connected USB device to reset or have its internal state corrupted. -image:/documentation/images/Quartz_64_Model_A_VBUS_Brownout.png[width=640] +{{< figure src="/documentation/images/Quartz_64_Model_A_VBUS_Brownout.png" width="640" >}} === Software diff --git a/content/documentation/Quartz64/Software/Releases.adoc b/content/documentation/Quartz64/Software/Releases.adoc index 6cdec68d..9a40e4c0 100644 --- a/content/documentation/Quartz64/Software/Releases.adoc +++ b/content/documentation/Quartz64/Software/Releases.adoc @@ -21,7 +21,7 @@ IMPORTANT: *Note:* The images are provided by the community, not by PINE64. Most === Armbian -image:/documentation/images/armbian.png[width=100] +{{< figure src="/documentation/images/armbian.png" width="100" >}} *Armbian* is a base operating system platform for single board computers @@ -41,7 +41,7 @@ Notes: === DietPi -image:/documentation/images/dietpi.png[width=100] +{{< figure src="/documentation/images/dietpi.png" width="100" >}} *DietPi* is a lightweight, yet easy to setup and feature-rich Linux distribution, based on _Debian_. To find out more about DietPi, please visit the https://dietpi.com/docs/[official documentation]. Discuss the Quartz64 builds on the https://forum.pine64.org/showthread.php?tid=17601[PINE64 forum thread]. @@ -60,7 +60,7 @@ Download: === Manjaro ARM -image:/documentation/images/Manjaro-logo.svg[width=100] +{{< figure src="/documentation/images/Manjaro-logo.svg" width="100" >}} *Manjaro ARM* is a user friendly rolling release distribution, based on Arch Linux ARM. diff --git a/content/documentation/Quartz64/Troubleshooting.adoc b/content/documentation/Quartz64/Troubleshooting.adoc index 7b1b059f..2e97bf14 100644 --- a/content/documentation/Quartz64/Troubleshooting.adoc +++ b/content/documentation/Quartz64/Troubleshooting.adoc @@ -25,7 +25,7 @@ Note: Starting with https://salsa.debian.org/kernel-team/linux/-/merge_requests/ The Quartz64 does not really fit onto the bottom plate of the link:/documentation//Accessories/Cases/Model_A_Acrylic_Open_Enclosure[Model A Acrylic Open Enclosure]. This is because the "Mic" connector at the bottom of the board interferes with one of the posts. A workaround is to find out which post that is (you have a 50% chance of guessing it right, accounting for rotating the board) and then filing away the corner of the post pointing inwards by a few millimeters. -image:/documentation/images/Quartz64-audio-jack-spacer-issue.jpg[width=400] +{{< figure src="/documentation/images/Quartz64-audio-jack-spacer-issue.jpg" width="400" >}} An alternate solution may be to place plastic spacers with a smaller outer diameter in between the acrylic bottom plate posts and the SBC board. diff --git a/content/documentation/Quartz64/_index.adoc b/content/documentation/Quartz64/_index.adoc index 41346f1c..eff94125 100644 --- a/content/documentation/Quartz64/_index.adoc +++ b/content/documentation/Quartz64/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/Quartz64modelb.png[The Quartz64 Model B,title="The Quartz64 Model B",width=400] +{{< figure src="/documentation/images/Quartz64modelb.png" title="The Quartz64 Model B" width="400" >}} The *Quartz64* is the most recent Single Board Computer offering from PINE64, with Model A initially released in June of 2021 and Model B in May of 2022. It is powered by a Rockchip RK3566 Quad-Core ARM Cortex A55 64-Bit Processor with a MALI G-52 GPU. diff --git a/content/documentation/QuartzPro64/Hardware.adoc b/content/documentation/QuartzPro64/Hardware.adoc index 2c05be4d..5739a8e4 100644 --- a/content/documentation/QuartzPro64/Hardware.adoc +++ b/content/documentation/QuartzPro64/Hardware.adoc @@ -9,7 +9,7 @@ menu: weight: 3 --- -image:/documentation/images/Quartzpro64_soc_and_ram_resized.jpeg[The SoC and RAM packages,title="The SoC and RAM packages",width=200] +{{< figure src="/documentation/images/Quartzpro64_soc_and_ram_resized.jpeg" title="The SoC and RAM packages" width="200" >}} == General @@ -110,7 +110,7 @@ The height from the bottom of the PCB to the top of the USB ports as the tallest == Storage -image:/documentation/images/Quartzpro64_emmc_resized.jpeg[The eMMC on the dev board,title="The eMMC on the dev board",width=200] +{{< figure src="/documentation/images/Quartzpro64_emmc_resized.jpeg" title="The eMMC on the dev board" width="200" >}} * Soldered 64 GB FORESEE eMMC chip, which comes pre-flashed with some Android build * One microSD card slot @@ -118,7 +118,7 @@ image:/documentation/images/Quartzpro64_emmc_resized.jpeg[The eMMC on the dev bo == Power -image:/documentation/images/Power_and_switch.jpg[Power switch & barrel connector,title="Power switch & barrel connector",width=100] +{{< figure src="/documentation/images/Power_and_switch.jpg" title="Power switch & barrel connector" width="100" >}} You can provide power to the board via the 12V barrel connector, it's 5.5mm OD/2.1mm ID barrel 'coaxial' type "M" centre-positive, the ROCKPro64 5A power supply from the PINE64 store will work. (TODO: add alternative ways). @@ -126,7 +126,7 @@ There is a hardware flip switch to power up / down the board. == PMU -image:/documentation/images/Quartzpro64_pmu.jpeg[The PMU,title="The PMU",width=100] +{{< figure src="/documentation/images/Quartzpro64_pmu.jpeg" title="The PMU" width="100" >}} 2x RK806-2, not RK808 compatible. It's a dual PMU configuration where one PMU is a subordinate of the other. diff --git a/content/documentation/QuartzPro64/_index.adoc b/content/documentation/QuartzPro64/_index.adoc index b36ef7bd..128b1617 100644 --- a/content/documentation/QuartzPro64/_index.adoc +++ b/content/documentation/QuartzPro64/_index.adoc @@ -9,8 +9,8 @@ menu: weight: 1 --- -image:/documentation/images/Quartzpro64_whole_board_top_resized.jpeg[title="The QuartzPro64 development board, front side",height=250] -image:/documentation/images/BoardBackSide.jpg[title="Back side of the board",height=250] +{{< figure src="/documentation/images/Quartzpro64_whole_board_top_resized.jpeg" title="The QuartzPro64 development board, front side" height="250" >}} +{{< figure src="/documentation/images/BoardBackSide.jpg" title="Back side of the board" height="250" >}} A *QuartzPro64* page before a *QuartzPro64* release? It's more likely than you think! diff --git a/content/documentation/ROCK64/Board_features.adoc b/content/documentation/ROCK64/Board_features.adoc index d93cdf4d..05728d13 100644 --- a/content/documentation/ROCK64/Board_features.adoc +++ b/content/documentation/ROCK64/Board_features.adoc @@ -9,7 +9,7 @@ menu: weight: 1 --- -image:/documentation/ROCK64/images/ROCK64_sideimg.jpg[The ROCK64 and a size comparison,title="The ROCK64 and a size comparison",width=400] +{{< figure src="/documentation/ROCK64/images/ROCK64_sideimg.jpg" title="The ROCK64 and a size comparison" width="400" >}} == Video @@ -41,7 +41,7 @@ image:/documentation/ROCK64/images/ROCK64_sideimg.jpg[The ROCK64 and a size comp * 1 USB3.0 Dedicated Host port * 2 USB2.0 Dedicated Host port (top one is USB-OTG) -image:/documentation/ROCK64/images/Rock64-emmc-disable-jumper.png[width=400, title="Position of the two-pin header for disabling the optionally installed eMMC module (highlighted in red)"] +{{< figure src="/documentation/ROCK64/images/Rock64-emmc-disable-jumper.png" title="Position of the two-pin header for disabling the optionally installed eMMC module (highlighted in red)" width="400">}} Position of the two-pin header for disabling the optionally installed eMMC module (highlighted in red) diff --git a/content/documentation/ROCK64/Cases/Premium_aluminum_casing.adoc b/content/documentation/ROCK64/Cases/Premium_aluminum_casing.adoc index 5627c5e7..09c3927b 100644 --- a/content/documentation/ROCK64/Cases/Premium_aluminum_casing.adoc +++ b/content/documentation/ROCK64/Cases/Premium_aluminum_casing.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/ROCK64/images/Rock64-Al-Case1-1.jpg[The case, fully assembled with a ROCK64 inside of it,title="The case, fully assembled with a ROCK64 inside of it"] +{{< figure src="/documentation/ROCK64/images/Rock64-Al-Case1-1.jpg" title="The case, fully assembled with a ROCK64 inside of it" >}} The *ROCK64 Premium Aluminum Casing* is an aluminum case for the link:/documentation/ROCK64[ROCK64] single-board computer sold by Pine64 through their https://pine64.com/product/model-b-premium-aluminum-casing/?v=0446c16e2e66[official store]. It includes an integrated heat spreader with an included thermal pad that allows the SoC to sink its generated heat into the metal case. @@ -35,13 +35,13 @@ Some cases may not allow the ROCK64 IO to snugly fit into its predestined cutout === Plastic Pegs for PWR and RST Buttons -image:/documentation/ROCK64/images/Button_peg_cad.png[FreeCAD displaying the peg. Bottom part goes inside the case.,title="FreeCAD displaying the peg. Bottom part goes inside the case."] +{{< figure src="/documentation/ROCK64/images/Button_peg_cad.png" title="FreeCAD displaying the peg. Bottom part goes inside the case." >}} If you are tired of using a pen or a toothpick to push the buttons, there are https://wiki.pine64.org/wiki/File:Button.zip[3d-printable plastic pegs you can download] and print yourself. Recommended material is PLA, excellent results can be obtained using a 0.25mm nozzle, though slightly larger sizes should work fine as well. To use the pegs, open your case and remove the ROCK64 from within. Be sure to pull out the light guide and rubber plug to remove it, or else it will catch on them. Once it is removed, turn your bottom half of the case such that the holes for PWR and RST are pointing towards the floor, and drop the pegs into the holes from inside the case, so that the lip prevents them from falling through. Hold them in position with your finger, turn the case the right side up again, and reinstall your ROCK64. -image:/documentation/ROCK64/images/ROCK64_Aluminum_Casing_Plastic_Peg_Mod_Photo.jpeg[Plastic Pegs in their place,title="Plastic Pegs in their place"] +{{< figure src="/documentation/ROCK64/images/ROCK64_Aluminum_Casing_Plastic_Peg_Mod_Photo.jpeg" title="Plastic Pegs in their place" >}} You should now have buttons that can be pressed from outside the case without any utensils. diff --git a/content/documentation/ROCK64/Cases/_index.adoc b/content/documentation/ROCK64/Cases/_index.adoc index e22a5bca..64d8be61 100644 --- a/content/documentation/ROCK64/Cases/_index.adoc +++ b/content/documentation/ROCK64/Cases/_index.adoc @@ -9,7 +9,7 @@ menu: weight: 5 --- -image:/documentation/ROCK64/images/Rock64-Al-Case1-1.jpg[width=400] +{{< figure src="/documentation/ROCK64/images/Rock64-Al-Case1-1.jpg" width="400" >}} The ROCK64 fits in three officially sold cases. diff --git a/content/documentation/ROCK64/Software/Releases.adoc b/content/documentation/ROCK64/Software/Releases.adoc index 8a25ed61..b4f3c617 100644 --- a/content/documentation/ROCK64/Software/Releases.adoc +++ b/content/documentation/ROCK64/Software/Releases.adoc @@ -15,7 +15,7 @@ This page contains a list of all available releases for the link:/documentation/ === AOSC -image:/documentation/images/aosc.png[width=100] +{{< figure src="/documentation/images/aosc.png" width="100" >}} *AOSC OS* is a general purpose Linux distribution that strives to simplify user experience and improve free and open source software for day-to-day productivity. To learn more about AOSC, please visit the official https://aosc.io/[AOSC website]. @@ -32,7 +32,7 @@ Download: === Arch Linux ARM -image:/documentation/images/Archlinux-logo.png[width=100] +{{< figure src="/documentation/images/Archlinux-logo.png" width="100" >}} Official *Arch Linux ARM* release. Installation: @@ -41,7 +41,7 @@ Installation: === Armbian -image:/documentation/images/armbian.png[width=100] +{{< figure src="/documentation/images/armbian.png" width="100" >}} *Armbian* is a Linux distribution designed for ARM boards. They are usually Debian or Ubuntu flavored. @@ -52,7 +52,7 @@ Download: === ayufan's Linux releases -image:/documentation/images/penguin.png[width=100] +{{< figure src="/documentation/images/penguin.png" width="100" >}} The community member _ayufan_ offers multiple ROCK64 Linux releases based on Debian and Ubuntu. The forum thread for release can be found https://forum.pine64.org/showthread.php?tid=6309[here]. @@ -71,7 +71,7 @@ NOTE: Make sure to download images for the _ROCK64_. === Debian -image:/documentation/images/Debian-logo.png[width=100] +{{< figure src="/documentation/images/Debian-logo.png" width="100" >}} *Debian* is an operating system and a distribution of Free Software. @@ -104,7 +104,7 @@ Notes: === Debian by mrfixit2001 -image:/documentation/images/Debian-logo.png[width=100] +{{< figure src="/documentation/images/Debian-logo.png" width="100" >}} Mrfixit2001's minimal *Debian* build. Version 190514 onward support Rock64-v3 board @@ -121,7 +121,7 @@ Download: === DietPi -image:/documentation/images/dietpi.png[width=100] +{{< figure src="/documentation/images/dietpi.png" width="100" >}} *DietPi* is a lightweight yet easy to setup and feature-rich Linux distribution, based on Debian. To find out more about DietPi, please visit the https://dietpi.com/docs/[official documentation]. Discuss the ROCK64 build on the https://forum.pine64.org/showthread.php?tid=12514[PINE64 forum thread]. @@ -139,7 +139,7 @@ Download: === Lakka -image:/documentation/images/lakka.png[width=100] +{{< figure src="/documentation/images/lakka.png" width="100" >}} *Lakka* is a lightweight Linux distribution that transforms a small computer into a full blown retrogaming console. Visit https://forum.pine64.org/showthread.php?tid=5354[PINE64 forum] for more information about the Lakka release. @@ -149,7 +149,7 @@ Download: === LibreELEC -image:/documentation/images/libreelec.jpg[width=100] +{{< figure src="/documentation/images/libreelec.jpg" width="100" >}} *LibreELEC* is a "Just enough OS" Linux distribution combining the Kodi media center with an operating system. @@ -160,7 +160,7 @@ Download: === Manjaro ARM -image:/documentation/images/Manjaro-logo.svg[width=100] +{{< figure src="/documentation/images/Manjaro-logo.svg" width="100" >}} *Manjaro* is a user-friendly Linux distribution based on the independently developed Arch operating system. Manjaro editions for Rock64 are available directly from Manjaro. To learn more about Manjaro please visit the https://forum.manjaro.org/tags/manjaroarm[Manjaro Forum]. @@ -172,7 +172,7 @@ Download: === NEMS Linux -image:/documentation/images/nems.jpg[width=100] +{{< figure src="/documentation/images/nems.jpg" width="100" >}} *NEMS* stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers. To find out more on NEMS Linux, please visit their https://nemslinux.com/[site]. @@ -196,7 +196,7 @@ NOTE: The installation guide can be found https://docs.nemslinux.com/installatio === NextCloudPi -image:/documentation/images/nextcloudpi.png[width=100] +{{< figure src="/documentation/images/nextcloudpi.png" width="100" >}} *NextCloudPi* comes not only with NextCloud preinstalled, but also with management tools for backups, SSL certificates, SAMBA, enhanced security and more. Visit the project's https://nextcloudpi.com[website]. You can follow the ongoing discussion about NextCloudPi on the https://forum.pine64.org/showthread.php?tid=6047[PINE64 forum]. @@ -217,7 +217,7 @@ NOTE: The MD5 hash of the .gz file is _2d3eb799e99a3bb90d5aa7731baf27c6_ === OpenMediaVault -image:/documentation/images/omv.png[width=100] +{{< figure src="/documentation/images/omv.png" width="100" >}} *Openmediavault* is the next generation network attached storage (NAS) solution. The forum thread concerning this release can be found https://forum.pine64.org/showthread.php?tid=6309[here]. @@ -248,7 +248,7 @@ NOTE: The MD5 hash of the .xz file is _bf5d2ea2bc7a5623ba958ed358a80c2a_ === Recalbox -image:/documentation/images/RB.png[width=100] +{{< figure src="/documentation/images/RB.png" width="100" >}} *Recalbox* is a free and open-source operating system created for the emulation and preservation for retro games. Recalbox allows you to re-play a variety of videogame consoles and platforms in your living room with ease. To find out more about Recalbox and available tweaks to the installation please visit the https://forum.pine64.org/showthread.php?tid=7111[PINE64 forum thread]. Visit the project's https://www.recalbox.com/[website] for more details. @@ -260,7 +260,7 @@ Download: === R-Cade -image:/documentation/images/RCadeLogo.jpg[width=100] +{{< figure src="/documentation/images/RCadeLogo.jpg" width="100" >}} Retro Center's *R-Cade*, the 4K Media Center Arcade. https://www.retro-center.com/about-r-cade/[RCade] Features 100+ retro-gaming systems, a lightweight web browser, and full 4K UHD media playback. @@ -270,7 +270,7 @@ Download: === Slackware -image:/documentation/images/slackware.jpg[width=100] +{{< figure src="/documentation/images/slackware.jpg" width="100" >}} *Slackware* is a very old, interesting, convenient and easy distribution. Visit the project's website here (https://fail.pp.ua). You can follow the ongoing discussion about Slackware on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=5868) @@ -304,7 +304,7 @@ Flashing the distribution to the eMMC: === FreeBSD -image:/documentation/images/Freebsd_Logo.png[width=100] +{{< figure src="/documentation/images/Freebsd_Logo.png" width="100" >}} *FreeBSD* is an operating system used to power modern servers, desktops, and embedded platforms. The https://wiki.freebsd.org/arm/RockChip#Rock64[RockChip FreeBSD page] has instructions for installing FreeBSD. Version 13.0 and greater include prebuilt images. @@ -324,7 +324,7 @@ Download: === NetBSD -image:/documentation/images/netbsd.png[width=100] +{{< figure src="/documentation/images/netbsd.png" width="100" >}} *NetBSD* is a free, fast, secure, and highly portable Unix-like Open Source operating system. To learn more about NetBSD please visit https://www.netbsd.org/[NetBSD main page]. @@ -345,13 +345,13 @@ Notes: === OpenBSD -image:/documentation/images/Puffy_mascot_openbsd.png[width=100] +{{< figure src="/documentation/images/Puffy_mascot_openbsd.png" width="100" >}} *OpenBSD* is a security-focused, free and open-source, Unix-like operating system based on the Berkeley Software Distribution. You can install OpenBSD on your Rock64 by following https://github.com/krjdev/rock64_openbsd[these instructions]. == Android -image:/documentation/images/Android_logo_2019_(stacked).svg[width=100] +{{< figure src="/documentation/images/Android_logo_2019_(stacked).svg" width="100" >}} === Android TV 9.x eMMC (No Google Play) diff --git a/content/documentation/ROCK64/_index.adoc b/content/documentation/ROCK64/_index.adoc index b8ff3b47..35d1c3c1 100644 --- a/content/documentation/ROCK64/_index.adoc +++ b/content/documentation/ROCK64/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/ROCK64/images/Rock64.jpg[The ROCK64,title="The ROCK64",width=400] +{{< figure src="/documentation/ROCK64/images/Rock64.jpg" title="The ROCK64" width="400" >}} The *ROCK64* is a credit-card size 4K60P HDR Media Board Computer powered by Rockchip RK3328 Quad-Core ARM Cortex A53 64-Bit Processor and supports up to 4GB 1866MHz LPDDR3 memory. It provides an eMMC module socket, MicroSD Card slot, Pi-2 Bus, Pi-P5+ Bus, USB 3.0, and many other peripheral interfaces for makers to integrate with sensors and other devices. diff --git a/content/documentation/ROCKPro64/Board/Layout.adoc b/content/documentation/ROCKPro64/Board/Layout.adoc index 8f7c6b1a..3f162aad 100644 --- a/content/documentation/ROCKPro64/Board/Layout.adoc +++ b/content/documentation/ROCKPro64/Board/Layout.adoc @@ -9,9 +9,9 @@ menu: weight: --- -image:/documentation/images/ROCKPro64v21REAR.jpg[width=400] -image:/documentation/images/FLIR_20220619_125451_686.jpg[width=230] -image:/documentation/images/ROCKPro64_annotated.jpg[width=500] +{{< figure src="/documentation/images/ROCKPro64v21REAR.jpg" width="400" >}} +{{< figure src="/documentation/images/FLIR_20220619_125451_686.jpg" width="230" >}} +{{< figure src="/documentation/images/ROCKPro64_annotated.jpg" width="500" >}} == Main Chips diff --git a/content/documentation/ROCKPro64/Hardware/3D_printable_ITX_mounting_brackets.adoc b/content/documentation/ROCKPro64/Hardware/3D_printable_ITX_mounting_brackets.adoc index 321608c2..050d4abb 100644 --- a/content/documentation/ROCKPro64/Hardware/3D_printable_ITX_mounting_brackets.adoc +++ b/content/documentation/ROCKPro64/Hardware/3D_printable_ITX_mounting_brackets.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/ITX-Bracket-Mounted.jpg[A Quartz64-A mounted in an ITX case using 3D printed brackets,title="A Quartz64-A mounted in an ITX case using 3D printed brackets",width=300] +{{< figure src="/documentation/images/ITX-Bracket-Mounted.jpg" title="A Quartz64-A mounted in an ITX case using 3D printed brackets" width="300" >}} Allows mounting a ROCKPro64-A or Quartz64-A board inside a regular PC case that conforms to the ITX standard, using 3D printed brackets: diff --git a/content/documentation/ROCKPro64/Hardware/Cases.adoc b/content/documentation/ROCKPro64/Hardware/Cases.adoc index fb0ff223..ddb4949b 100644 --- a/content/documentation/ROCKPro64/Hardware/Cases.adoc +++ b/content/documentation/ROCKPro64/Hardware/Cases.adoc @@ -15,7 +15,7 @@ menu: == NAS case -image:/documentation/images/NASCaseMain.png[Front View of the PINE64 NAS Case for the ROCKPro64,title="Front View of the PINE64 NAS Case for the ROCKPro64"] +{{< figure src="/documentation/images/NASCaseMain.png" title="Front View of the PINE64 NAS Case for the ROCKPro64" >}} Please link:/documentation/Accessories/Cases/NASCase[follow this this link] for *detailed instructions on how to assemble the ROCKPro64 NAS Case*. diff --git a/content/documentation/ROCKPro64/Hardware/Serial_buffer_circuit.adoc b/content/documentation/ROCKPro64/Hardware/Serial_buffer_circuit.adoc index ad7f0288..441a34b6 100644 --- a/content/documentation/ROCKPro64/Hardware/Serial_buffer_circuit.adoc +++ b/content/documentation/ROCKPro64/Hardware/Serial_buffer_circuit.adoc @@ -60,5 +60,5 @@ You may have some or all of these in your junk/parts drawer. They're all common == Circuit -image:/documentation/images/RockPro64-serial-buffer.png[] +{{< figure src="/documentation/images/RockPro64-serial-buffer.png" >}} diff --git a/content/documentation/ROCKPro64/Software/Releases.adoc b/content/documentation/ROCKPro64/Software/Releases.adoc index 402164f5..9f099605 100644 --- a/content/documentation/ROCKPro64/Software/Releases.adoc +++ b/content/documentation/ROCKPro64/Software/Releases.adoc @@ -16,7 +16,7 @@ This page contains a list of all available releases and tools for the link:/docu == Linux === AOSC -image:/documentation/images/aosc.png[width=100] +{{< figure src="/documentation/images/aosc.png" width="100" >}} *AOSC OS* is a general purpose Linux distribution that strives to simplify user experience and improve free and open source software for day-to-day productivity. Originally AnthonOS (an OpenSUSE derivative built with SUSE Studio), then remade as a Debian derivative with customized KDE 4 UI and CJK support. To learn more about AOSC, please visit the official https://aosc.io/[AOSC website] @@ -33,7 +33,7 @@ Download: === Armbian -image:/documentation/images/armbian.png[width=100] +{{< figure src="/documentation/images/armbian.png" width="100" >}} *Armbian* is a Linux distribution designed for ARM boards. They are usually Debian or Ubuntu flavored. To find out more about Armbian and available options please visit their https://www.armbian.com/rockpro64/[site]. If you are booting from a Micro SD card, then both Linux kernel versions will work. If you are trying to boot from an eMMC module then the 4.4.y will work, but the newer 5.10.y will not. @@ -43,7 +43,7 @@ Download: === Batocera Linux -image:/documentation/images/batocera.png[width=100] +{{< figure src="/documentation/images/batocera.png" width="100" >}} *Batocera Linux* is an open-source and completely free retro-gaming distribution that can be copied to a USB stick or an SD card with the aim of turning any computer/nano computer into a gaming console during a game or permanently. Visit the project's website here (https://batocera.org/). You can follow the ongoing discussion about batocera.linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7084) @@ -53,7 +53,7 @@ Download: === Debian -image:/documentation/images/Debian-logo.png[width=100] +{{< figure src="/documentation/images/Debian-logo.png" width="100" >}} *Debian* is an operating system and a distribution of free software. See the forum thread https://forum.pine64.org/showthread.php?tid=9744[here]. @@ -82,7 +82,7 @@ Notes: === DietPi -image:/documentation/images/dietpi.png[width=100] +{{< figure src="/documentation/images/dietpi.png" width="100" >}} *DietPi* is a lightweight, yet easy to setup and feature-rich Linux distribution, based on Debian. To find out more about DietPi, please visit the https://dietpi.com/docs/[official documentation]. Discuss the ROCKPro64 build on the https://forum.pine64.org/showthread.php?tid=12532[PINE64 forum thread]. @@ -99,7 +99,7 @@ Download: === LibreELEC -image:/documentation/images/libreelec.jpg[width=100] +{{< figure src="/documentation/images/libreelec.jpg" width="100" >}} *LibreELEC* is a lightweight 'Just enough OS' Linux distribution purpose-built for Kodi on current and popular mediacentre hardware. Download: @@ -110,7 +110,7 @@ NOTE: Unzip and flash the image to a microSD card or eMMC module, for example us === Manjaro ARM -image:/documentation/images/Manjaro-logo.svg[width=100] +{{< figure src="/documentation/images/Manjaro-logo.svg" width="100" >}} *Manjaro* is a user-friendly Linux distribution based on the independently developed Arch operating system. To learn more about Manjaro please visit https://forum.manjaro.org/c/arm/releases/102[Manjaro forum]. @@ -127,7 +127,7 @@ Notes: === Nems Linux -image:/documentation/images/nems.jpg[width=100] +{{< figure src="/documentation/images/nems.jpg" width="100" >}} *NEMS* stands for _Nagios Enterprise Monitoring Server_ and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers. To find out more about NEMS on the PINE64 and available tweaks to the installation please visit the https://forum.pine64.org/showthread.php?tid=7306[PINE64 forum thread]. @@ -144,7 +144,7 @@ Download: === NixOS -image:/documentation/images/NixOS.webp[width=100] +{{< figure src="/documentation/images/NixOS.webp" width="100" >}} *NixOS* is a Linux distribution built on top of the Nix package manager using declarative configuration to allow reliable system upgrades. More information can be found on the https://wiki.nixos.org/wiki/NixOS_on_ARM/PINE64_ROCKPro64[NixOS wiki]. @@ -154,7 +154,7 @@ Download: === OpenMediaVault -image:/documentation/images/omv.png[width=100] +{{< figure src="/documentation/images/omv.png" width="100" >}} *OpenMediaVault* is the next generation network attached storage (NAS) solution, https://www.openmediavault.org/[click this link to OMV main page] to learn more. Forum thread concerning this release can be found https://forum.pine64.org/showthread.php?tid=6308[here] @@ -183,7 +183,7 @@ Notes: === OpenWrt -image:/documentation/images/Openwrt_logo_square.png[width=100] +{{< figure src="/documentation/images/Openwrt_logo_square.png" width="100" >}} *OpenWrt* ​is a highly extensible ​GNU/​Linux ​distribution for embedded devices ​(typically wireless routers). Unlike many other distributions for these routers, OpenWrt ​is built from the ground up to be a full-featured, easily modifiable operating system for your router. In practice, this means that you can have all the features you need with none of the bloat, powered by a Linux kernel ​that's more recent than most other distributions. @@ -193,7 +193,7 @@ Download: === postmarketOS -image:/documentation/images/PostmarketOS_logo.png[width=100] +{{< figure src="/documentation/images/PostmarketOS_logo.png" width="100" >}} postmarketOS extends https://www.alpinelinux.org/[Alpine Linux] to run on smartphones and other devices. At the time of writing, the only user interface provided through prebuilt images for the ROCKPro64 is https://plasma-bigscreen.org/[Plasma Bigscreen]. @@ -211,7 +211,7 @@ Download: === R-Cade -image:/documentation/images/RCadeLogo.jpg[width=100] +{{< figure src="/documentation/images/RCadeLogo.jpg" width="100" >}} Retro Center's *R-Cade*, the 4K Media Center Arcade. https://www.retro-center.com/about-r-cade/[RCade] Features 100+ retro-gaming systems, a lightweight web browser, and full 4K UHD media playback. @@ -221,7 +221,7 @@ Download: === Recalbox -image:/documentation/images/RB.png[width=100] +{{< figure src="/documentation/images/RB.png" width="100" >}} *Recalbox* allows you to re-play a variety of videogame consoles and platforms in your living room, with ease|Visit the project's website here (https://www.recalbox.com/). You can follow the ongoing discussion about Recalbox on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=7194) @@ -232,7 +232,7 @@ Download: === SkiffOS -image:/documentation/images/SkiffOS-Icon-1.png[width=100]_Minimal_cross-compiled_OS_optimized_for_hosting_distributions_in_Docker_containers._Provides_the_reliability_of_firmware_with_the_ease-of-use of package managers. Uses the http://buildroot.org[Buildroot] cross-compilation tool for support for all Pine64 boards. +{{< figure src="/documentation/images/SkiffOS-Icon-1.png" width="100]_Minimal_cross-compiled_OS_optimized_for_hosting_distributions_in_Docker_containers._Provides_the_reliability_of_firmware_with_the_ease-of-use of package managers. Uses the http://buildroot.org[Buildroot" >}} cross-compilation tool for support for all Pine64 boards. Use configuration packages to configure the distribution: @@ -249,7 +249,7 @@ Download: === Slackware -image:/documentation/images/slackware.jpg[width=100] +{{< figure src="/documentation/images/slackware.jpg" width="100" >}} *Slackware* is the world's oldest actively developed Linux distribution, providing a modern user land (applications) and Linux Kernel, within a more classic Unix Operating System environment. @@ -288,7 +288,7 @@ Flashing the distribution to the eMMC: === Twister OS -image:/documentation/images/Twister_OS.png[width=100] +{{< figure src="/documentation/images/Twister_OS.png" width="100" >}} *Twister OS* brings a desktop computing experience for SBCs, right out-of-the-box. Including themes, applications, tools, and optimizations to get the most out of your SBC. For more information on Twister OS, please visit the https://twisteros.com/[official site]. You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=12192). @@ -333,7 +333,7 @@ The following creates a bootable image from an existing Void Linux installation: == BSD Images === FreeBSD -image:/documentation/images/Freebsd_Logo.png[width=100] +{{< figure src="/documentation/images/Freebsd_Logo.png" width="100" >}} *FreeBSD* is an operating system used to power modern servers, desktops, and embedded platforms. The https://wiki.freebsd.org/arm/RockChip#RockPro64[RockChip FreeBSD page] has instructions for installing FreeBSD. Version 13.0 and greater include prebuilt images. @@ -357,7 +357,7 @@ Notes: === NetBSD -image:/documentation/images/netbsd.png[width=100]_*NetBSD*_is_a_free,_fast,_secure,_and_highly_portable_Unix-like_Open_Source_operating_system._To_learn_more_about NetBSD please visit https://www.netbsd.org/[NetBSD main page] +{{< figure src="/documentation/images/netbsd.png" width="100]_*NetBSD*_is_a_free,_fast,_secure,_and_highly_portable_Unix-like_Open_Source_operating_system._To_learn_more_about NetBSD please visit https://www.netbsd.org/[NetBSD main page" >}} Download: @@ -376,13 +376,13 @@ Notes: === OpenBSD -image:/documentation/images/Puffy_mascot_openbsd.png[width=100] +{{< figure src="/documentation/images/Puffy_mascot_openbsd.png" width="100" >}} *OpenBSD* is a security-focused, free and open-source, Unix-like operating system based on the Berkeley Software Distribution. Official instruction to get OpenBSD on ROCKPro64 is https://www.openbsd.org/arm64.html[here], and blogs on installation https://github.com/jasperla/openbsd-rockpro64[is here] and https://bsandro.tech/posts/openbsd-7.1-on-pine64-rockpro64/[here]. Forum discussion is https://forum.pine64.org/forumdisplay.php?fid=109[here]. == Chromium OS -image:/documentation/images/chromium.jpg[width=100] +{{< figure src="/documentation/images/chromium.jpg" width="100" >}} The *Chromium OS* community build image for microSD card and eMMC module, version beta (R76). To learn more please visit the https://forum.pine64.org/showthread.php?tid=7659[forum]. @@ -394,7 +394,7 @@ NOTE: Flash the image to a microSD card or an eMMC module, for example using _dd == Android -image:/documentation/images/Android_logo_2019_(stacked).svg[width=100] +{{< figure src="/documentation/images/Android_logo_2019_(stacked).svg" width="100" >}} === Android 9.0.0 diff --git a/content/documentation/ROCKPro64/_index.adoc b/content/documentation/ROCKPro64/_index.adoc index b12c104b..22ffcce8 100644 --- a/content/documentation/ROCKPro64/_index.adoc +++ b/content/documentation/ROCKPro64/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/rockpro64.svg[The ROCKPro64,title="The ROCKPro64",width=400] +{{< figure src="/documentation/images/rockpro64.svg" title="The ROCKPro64" width="400" >}} The *ROCKPro64* is the most powerful single-board computer released by PINE64. It is powered by a Rockchip RK3399 hexa-core (dual ARM Cortex A72 and quad ARM Cortex A53) 64-bit processor with a Mali T-860 quad-core GPU. The key features include a PCI Express (PCIe) x4 open-ended slot, the use of LPDDR4 DRAM, and industry-standard heatsink mounting holes. diff --git a/content/documentation/RockBox/Development/UART.adoc b/content/documentation/RockBox/Development/UART.adoc index dd397869..6f90e6b9 100644 --- a/content/documentation/RockBox/Development/UART.adoc +++ b/content/documentation/RockBox/Development/UART.adoc @@ -9,7 +9,7 @@ menu: weight: 3 --- -image:/documentation/RockBox/images/rockbox_internals.jpg[Internals of the RockBox with the UART contacts visible on the bottom right,title="Internals of the RockBox with the UART contacts visible on the bottom right",width=400] +{{< figure src="/documentation/RockBox/images/rockbox_internals.jpg" title="Internals of the RockBox with the UART contacts visible on the bottom right" width="400" >}} A serial console can be connected to the RockBox to retrieve the UART boot logs. A device such as a USB to TTL converter can be used to connect the RockBox. Simply set the USB device to 3.3 volts and connect GND to the GND connector on the mainboard, RTX to TX and TXD to RX. The fourth unlabelled contact on the mainboard should not be connected. diff --git a/content/documentation/RockBox/_index.adoc b/content/documentation/RockBox/_index.adoc index a92ebf2d..a3ec039f 100644 --- a/content/documentation/RockBox/_index.adoc +++ b/content/documentation/RockBox/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:images/rockbox.png[Rendering of the RockBox,title="Rendering of the RockBox",width=400] +{{< figure src="images/rockbox.png" title="Rendering of the RockBox" width="400" >}} The *Popcorn Hour RockBox Basic* is a TV box from the Cloud Media company in partnership with _PINE64_ and the _PINE64_ community. It is running a Rockchip RK3328 SoC and is supporting multiple different operating systems. The device is similar to the link:/documentation/ROCK64[ROCK64] and runs some of its operating systems, it has a custom PCB and multiple hardware differences however. diff --git a/content/documentation/SOEDGE/Debugging.adoc b/content/documentation/SOEDGE/Debugging.adoc index c06c702d..160291f1 100644 --- a/content/documentation/SOEDGE/Debugging.adoc +++ b/content/documentation/SOEDGE/Debugging.adoc @@ -17,7 +17,7 @@ System Serial is located on PI-5 bus (11x2 GPIO header). * RXD: Pin 8 (Orange cable) (Connect to TXD on Serial adapter) * GND: Pin 10 (Black cable) (Connect to GND on Serial adapter) -image:/documentation/SOEDGE/images/Soedge_serial_pins.jpg[width=400] +{{< figure src="/documentation/SOEDGE/images/Soedge_serial_pins.jpg" width="400" >}} The default baudrate is 1500000, note that not all serial adapters support this high baudrate. diff --git a/content/documentation/SOEDGE/Further_information/Specification.adoc b/content/documentation/SOEDGE/Further_information/Specification.adoc index 37a97b18..49a9d978 100644 --- a/content/documentation/SOEDGE/Further_information/Specification.adoc +++ b/content/documentation/SOEDGE/Further_information/Specification.adoc @@ -30,7 +30,7 @@ Based on the https://www.rock-chips.com/a/en/products/RK18_Series/2019/0529/989. == Neural Process Unit NPU Capability -image:/documentation/images/Vivante_Acuity_SDK.jpg[width=400] +{{< figure src="/documentation/images/Vivante_Acuity_SDK.jpg" width="400" >}} * https://www.verisilicon.com/en/IPPortfolio/VivanteNPUIP[NPU IP from Verisilicon Vivante] * Support max 1920 Int8 MAC operation per cycle diff --git a/content/documentation/SOEDGE/_index.adoc b/content/documentation/SOEDGE/_index.adoc index 7eddcd0b..c59bbc74 100644 --- a/content/documentation/SOEDGE/_index.adoc +++ b/content/documentation/SOEDGE/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:images/SOEdge.png[The SOEDGE,title="The SOEDGE",width=400] +{{< figure src="images/SOEdge.png" title="The SOEDGE" width="400" >}} The *SOEDGE* is a 3TOPS compute module that can be paired with the link:/documentation/SOEDGE_Baseboard[SOEDGE Baseboard], the link:/documentation/Clusterboard[Clusterboard] or USB 3.0 and PCIe adapters for development. It can connect to a SBC, such as the ROCKPro64 or a regular PC. diff --git a/content/documentation/SOEDGE_Baseboard/_index.adoc b/content/documentation/SOEDGE_Baseboard/_index.adoc index 5947fc1b..fd17848e 100644 --- a/content/documentation/SOEDGE_Baseboard/_index.adoc +++ b/content/documentation/SOEDGE_Baseboard/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/SOEDGE_Baseboard.png[The SOEDGE Baseboard,title="The SOEDGE Baseboard",width=400] +{{< figure src="/documentation/images/SOEDGE_Baseboard.png" title="The SOEDGE Baseboard" width="400" >}} The *SOEDGE Baseboard* is a baseboard that hosts the link:/documentation/SOEDGE[SOEDGE] compute module and turns it into a full single board computer. Makers can use this baseboard as reference to develop their own PCBs and for software development during early stages for custom hardware or PCB development. diff --git a/content/documentation/SOPINE/Software/Releases.adoc b/content/documentation/SOPINE/Software/Releases.adoc index 93b96288..b7ac4f7b 100644 --- a/content/documentation/SOPINE/Software/Releases.adoc +++ b/content/documentation/SOPINE/Software/Releases.adoc @@ -14,7 +14,7 @@ Note that SOPINE images are also compatible with the PINE A64-LTS. == Linux === AOSC -image:/documentation/images/aosc.png[] +{{< figure src="/documentation/images/aosc.png" >}} AOSC OS is a general purpose Linux distribution that strives to simplify user experience and improve free and open source software for day-to-day productivity. To learn more about AOSC, please visit the official https://aosc.io/[AOSC website]. @@ -30,7 +30,7 @@ Download: |=== === Armbian -image:/documentation/images/armbian.png[] +{{< figure src="/documentation/images/armbian.png" >}} Armbian is a Linux distribution designed for ARM boards. They are usually Debian or Ubuntu flavored. @@ -39,7 +39,7 @@ Download: * https://armbian.hosthatch.com/archive/pine64so/archive/ === FreedomBox -image:/documentation/images/FreedomBox.jpg[] +{{< figure src="/documentation/images/FreedomBox.jpg" >}} FreedomBox is a private server for non-experts: it lets you install and configure server applications with only a few clicks. For more information about FreedomBox, please visit http://www.freedombox.org. @@ -56,7 +56,7 @@ Notes: * Freedom Manual: https://wiki.debian.org/FreedomBox/Manual === LibreELEC -image:/documentation/images/libreelec.jpg[] +{{< figure src="/documentation/images/libreelec.jpg" >}} LibreELEC is a "Just enough OS" Linux distribution combining the Kodi media center with an operating system. @@ -69,7 +69,7 @@ Notes: * Nightly build for microSD and eMMC boot. === NEMS Linux -image:/documentation/images/nems.jpg[] +{{< figure src="/documentation/images/nems.jpg" >}} NEMS stands for "Nagios Enterprise Monitoring Server" and it is a modern pre-configured, customized and ready-to-deploy Nagios Core image designed to run on low-cost micro computers. To find out more on NEMS Linux, please visit their https://nemslinux.com/[site]. @@ -90,7 +90,7 @@ Info:The installation guide can be found https://docs.nemslinux.com/installation |=== === OpenEmbedded -image:/documentation/images/openembedded.png[] +{{< figure src="/documentation/images/openembedded.png" >}} OpenEmbedded is the build framework for embedded Linux. OpenEmbedded offers a best-in-class cross-compile environment. It allows developers to create a complete Linux Distribution for embedded systems. See https://www.openembedded.org/wiki/Main_Page for more information on OpenEmbedded. @@ -105,7 +105,7 @@ Notes: * More information and instructions can be found in the repo readme: https://github.com/alistair23/meta-pine64/#building === OpenWRT -image:/documentation/images/Openwrt_logo_square.png[] +{{< figure src="/documentation/images/Openwrt_logo_square.png" >}} OpenWRT community build for microSD boot. The OpenWrt Project is a Linux operating system targeting embedded devices. @@ -127,7 +127,7 @@ Notes: == BSD === NetBSD -image:/documentation/images/netbsd.png[] +{{< figure src="/documentation/images/netbsd.png" >}} NetBSD is a free, fast, secure, and highly portable Unix-like Open Source operating system. To learn more about NetBSD please visit https://www.netbsd.org/[NetBSD main page]. diff --git a/content/documentation/SOPINE/_index.adoc b/content/documentation/SOPINE/_index.adoc index 40c94b33..61d09b09 100644 --- a/content/documentation/SOPINE/_index.adoc +++ b/content/documentation/SOPINE/_index.adoc @@ -9,8 +9,8 @@ menu: weight: --- -image:/documentation/images/SOPINE_front.jpg[width=400] -image:/documentation/images/SOPINE_back.jpg[width=400] +{{< figure src="/documentation/images/SOPINE_front.jpg" width="400" >}} +{{< figure src="/documentation/images/SOPINE_back.jpg" width="400" >}} The *SOPINE* is a compute module powered by the same quad-core ARM Cortex A53 64-bit processor used in the PINE A64 with 2 GB of LPDDR3 RAM memory, power management unit, SPI flash and integrated bootable microSD slot. The module features a SODIMM-DDR3 form-factor and can be paired with either the link:/documentation/SOPINE_Baseboard[SOPINE Baseboard], the link:/documentation/Clusterboard[Clusterboard] or a custom host PCB for industrial or other embedded applications. diff --git a/content/documentation/SOPINE_Baseboard/_index.adoc b/content/documentation/SOPINE_Baseboard/_index.adoc index 83feed1c..ac1a9181 100644 --- a/content/documentation/SOPINE_Baseboard/_index.adoc +++ b/content/documentation/SOPINE_Baseboard/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/images/SOPINE_Baseboard_front.jpg[width=400] +{{< figure src="/documentation/images/SOPINE_Baseboard_front.jpg" width="400" >}} The *SOPINE Baseboard Model A* is a baseboard that hosts the link:/documentation/SOPINE[SOPINE A64 Compute Module] and turns it into a full single board computer. Makers can use this baseboard as reference to develop their own PCBs and for software development during early stages for custom hardware or PCB development. diff --git a/content/documentation/SOQuartz/Baseboards/BLADE.adoc b/content/documentation/SOQuartz/Baseboards/BLADE.adoc index bfd087c6..b5d1800a 100644 --- a/content/documentation/SOQuartz/Baseboards/BLADE.adoc +++ b/content/documentation/SOQuartz/Baseboards/BLADE.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/SOQuartz/images/SOQuartz_BLADE_Dimension.jpg[SOQuartz BLADE Baseboard,title="SOQuartz BLADE Baseboard",width=400] +{{< figure src="/documentation/SOQuartz/images/SOQuartz_BLADE_Dimension.jpg" title="SOQuartz BLADE Baseboard" width="400" >}} * SOQuartz BLADE Baseboard Dimensions: 200mm x 40mm x 15mm * Input Power: diff --git a/content/documentation/SOQuartz/Baseboards/Model-A.adoc b/content/documentation/SOQuartz/Baseboards/Model-A.adoc index 1689201d..570a82fc 100644 --- a/content/documentation/SOQuartz/Baseboards/Model-A.adoc +++ b/content/documentation/SOQuartz/Baseboards/Model-A.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/SOQuartz/images/SOQuartz_model-A_baseboard.jpg[SOQuartz Model-A Baseboard,title="SOQuartz Model-A Baseboard",width=400] +{{< figure src="/documentation/SOQuartz/images/SOQuartz_model-A_baseboard.jpg" title="SOQuartz Model-A Baseboard" width="400" >}} * Model "A" Baseboard Dimensions: 133mm x 80mm x 19mm * Input Power: DC 5V @ 3A 3.5OD/1.35ID (IEC 60130-10 Type H) Barrel DC Jack connector diff --git a/content/documentation/SOQuartz/Baseboards/Various_CM4_carrier_boards.adoc b/content/documentation/SOQuartz/Baseboards/Various_CM4_carrier_boards.adoc index 5320e18f..7c8a382f 100644 --- a/content/documentation/SOQuartz/Baseboards/Various_CM4_carrier_boards.adoc +++ b/content/documentation/SOQuartz/Baseboards/Various_CM4_carrier_boards.adoc @@ -11,9 +11,9 @@ menu: * For CM4 carrier board comprehensive list, please visit https://pipci.jeffgeerling.com/boards_cm[Jeff Geerling collection] -image:/documentation/SOQuartz/images/SOQuartz_with_DF_Robot_carrier_board.jpg[SOQuartz with DF Robot CM4 Carrier Board,title="SOQuartz with DF Robot CM4 Carrier Board",width=400] +{{< figure src="/documentation/SOQuartz/images/SOQuartz_with_DF_Robot_carrier_board.jpg" title="SOQuartz with DF Robot CM4 Carrier Board" width="400" >}} -image:/documentation/SOQuartz/images/SOQuartz_with_Waveshare_carrier_board.jpg[SOQuartz with Waveshare CM4 Carrier Board,title="SOQuartz with Waveshare CM4 Carrier Board",width=400] +{{< figure src="/documentation/SOQuartz/images/SOQuartz_with_Waveshare_carrier_board.jpg" title="SOQuartz with Waveshare CM4 Carrier Board" width="400" >}} -image:/documentation/SOQuartz/images/SOQuartz_with_Waveshare_PoE_carrier_board.jpg[SOQuartz with Waveshare CM4 PoE Board,title="SOQuartz with Waveshare CM4 PoE Board",width=400] +{{< figure src="/documentation/SOQuartz/images/SOQuartz_with_Waveshare_PoE_carrier_board.jpg" title="SOQuartz with Waveshare CM4 PoE Board" width="400" >}} diff --git a/content/documentation/SOQuartz/Software/Releases.adoc b/content/documentation/SOQuartz/Software/Releases.adoc index 2a1ccb43..78371d05 100644 --- a/content/documentation/SOQuartz/Software/Releases.adoc +++ b/content/documentation/SOQuartz/Software/Releases.adoc @@ -13,7 +13,7 @@ NOTE: The images are provided by the PINE64 community, not by Pine Store Ltd. Mo == DietPi -image:/documentation/images/dietpi.png[width=100] +{{< figure src="/documentation/images/dietpi.png" width="100" >}} **DietPi** is a lightweight, yet easy to setup and feature-rich Linux distribution, based on _Debian_. To find out more about DietPi, please visit the https://dietpi.com/docs/[official documentation]. Discuss the Quartz64 builds on the https://forum.pine64.org/showthread.php?tid=17601[PINE64 forum thread]. @@ -31,7 +31,7 @@ Download: == Manjaro ARM -image:/documentation/images/Manjaro-logo.svg[width=100] +{{< figure src="/documentation/images/Manjaro-logo.svg" width="100" >}} Manjaro ARM is a user friendly rolling release distribution, based on Arch Linux ARM. @@ -51,7 +51,7 @@ For headless installation, simply enter "root" at the login: prompt and complete == Plebian -image:/documentation/images/Plebian-logo.svg[width=100] +{{< figure src="/documentation/images/Plebian-logo.svg" width="100" >}} Plebian stands for **P**INE64 **L**ive D**ebian** and aims to be a fairly vanilla live Debian image for Quartz64 and SOQuartz devices, based on Debian Bookworm. It supports both of PINE64's officially released SOQuartz base boards. diff --git a/content/documentation/SOQuartz/_index.adoc b/content/documentation/SOQuartz/_index.adoc index 2ce59a65..5adb3658 100644 --- a/content/documentation/SOQuartz/_index.adoc +++ b/content/documentation/SOQuartz/_index.adoc @@ -9,7 +9,7 @@ menu: weight: --- -image:/documentation/SOQuartz/images/SOQuartz_module-1s.jpg[The SOQuartz,title="The SOQuartz",width=400] +{{< figure src="/documentation/SOQuartz/images/SOQuartz_module-1s.jpg" title="The SOQuartz" width="400" >}} The *SOQuartz* is a RK3566 based compute module and parts of Quartz64 series. diff --git a/content/documentation/STAR64/Further_information/Specification.adoc b/content/documentation/STAR64/Further_information/Specification.adoc index 7d527858..5f622ff2 100644 --- a/content/documentation/STAR64/Further_information/Specification.adoc +++ b/content/documentation/STAR64/Further_information/Specification.adoc @@ -11,11 +11,11 @@ menu: * Based on https://www.starfivetech.com/en/site/soc[StarFive JH7110] -image:/documentation/images/StarFive.jpg[] -image:/documentation/images/JH7110_Block_Diagram.png[width=800] +{{< figure src="/documentation/images/StarFive.jpg" >}} +{{< figure src="/documentation/images/JH7110_Block_Diagram.png" width="800" >}} == CPU Architecture -image:/documentation/images/SiFive.jpg[width=200] +{{< figure src="/documentation/images/SiFive.jpg" width="200" >}} * https://www.sifive.com/cores/u74[Quad-core U74 up to 1.5GHz CPU] * Fully compliant with the RISC-V ISA specification @@ -29,7 +29,7 @@ image:/documentation/images/SiFive.jpg[width=200] * 32-bit RISC-V CPU core (E24) for real time control, support RV32IMFC RISC-V ISA == GPU Architecture -image:/documentation/images/imgtech.png[width=200] +{{< figure src="/documentation/images/imgtech.png" width="200" >}} * https://www.imaginationtech.com/product/img-bxe-4-32-mc4/[Imagination Technology BXE-4-32 up to 600Mhz GPU] * Support OpenCL 3.0 diff --git a/content/documentation/STAR64/_index.adoc b/content/documentation/STAR64/_index.adoc index c072ef5f..146f3918 100644 --- a/content/documentation/STAR64/_index.adoc +++ b/content/documentation/STAR64/_index.adoc @@ -9,6 +9,6 @@ menu: weight: --- -image:images/Star64.jpg[The STAR64,title="The STAR64",width=400] +{{< figure src="images/Star64.jpg" title="The STAR64" width="400" >}} The *Star64* is a RISC-V based Single Board Computer powered by StarFive JH7110 Quad-Core SiFive U74 64-Bit CPU, Imagination Technology BX-4-32 GPU and supports up to 8GB 1866MHz LPDDR4 memory. It provides an eMMC module socket, MicroSD Card slot, PCI-e, Pi-2 Bus, USB 3.0, and many other peripheral interfaces for makers to integrate with sensors and other devices. \ No newline at end of file diff --git a/content/documentation/Unsorted/PhoenixCard.adoc b/content/documentation/Unsorted/PhoenixCard.adoc index 37086838..992cacdc 100644 --- a/content/documentation/Unsorted/PhoenixCard.adoc +++ b/content/documentation/Unsorted/PhoenixCard.adoc @@ -22,7 +22,7 @@ menu: === Step to create the SD-Card -image:/documentation/images/PCard_Main.jpg[width=750] +{{< figure src="/documentation/images/PCard_Main.jpg" width="750" >}} . Extract the PhonixCard-xx.rar file into an empty directory. . Navigate into the directory where you installed PhoenixCard and start PhoenixCard.exe.