<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[PINE64 - General Discussion on PINE A64-LTS / SOPINE]]></title>
		<link>https://forum.pine64.org/</link>
		<description><![CDATA[PINE64 - https://forum.pine64.org]]></description>
		<pubDate>Sat, 18 Apr 2026 18:31:40 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Pine 64 Mount hole Dimensions]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=20194</link>
			<pubDate>Wed, 18 Feb 2026 17:27:58 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=29886">Piney64</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=20194</guid>
			<description><![CDATA[I'm looking to add my pine64 to a din rail and am wondering what the dimensions are for the mounting holes and a) does a horizontal din mount exist and b) are the mount holes the same dimensions as any 3d printer boards.]]></description>
			<content:encoded><![CDATA[I'm looking to add my pine64 to a din rail and am wondering what the dimensions are for the mounting holes and a) does a horizontal din mount exist and b) are the mount holes the same dimensions as any 3d printer boards.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[pine64 gpio interrupts]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19556</link>
			<pubDate>Tue, 10 Dec 2024 01:43:15 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=6355">fractal</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19556</guid>
			<description><![CDATA[Not sure if this is a general question or a linux question but here goes.<br />
<br />
I am coming back to a project after an extended interruption -- life got in the way of my play.<br />
<br />
I have a number of GPS units running on a variety of hardware.   The board I use for most of them is also allwiner based and run the same armbian as the pine64.  But, I like pine64's as a general purpose board and have several on my desk so decided to track down why I couldn't get them to work the way I wanted last time.<br />
<br />
That background information is not particularly normative but it offers some background.  You don't need any special hardware to reproduce this issue.<br />
<br />
My notes from many years ago says there was a post on IRC which confirmed we can not get interrupts from some of the GPIO banks.    I can no longer find that reference but that seems to be true.<br />
<br />
I can confirm that<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>overlays=pps-gpio<br />
param_pps_pin=PH9</code></div></div><br />
in armbianEnv.txt works with dmesg containing<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>[Mon Dec  9 23:58:56 2024] pps pps0: new PPS source pps@0.-1<br />
[Mon Dec  9 23:58:56 2024] pps pps0: Registered IRQ 100 as PPS source</code></div></div><br />
I can also confirm that<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>overlays=pps-gpio<br />
param_pps_pin=PC8</code></div></div><br />
in armbianEnv.txt fails with dmesg containing<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>[Tue Dec 10 00:04:25 2024] pps-gpio pps@0: failed to map GPIO to IRQ: -22<br />
[Tue Dec 10 00:04:25 2024] pps-gpio: probe of pps@0 failed with error -22</code></div></div><br />
I got as far as <a href="https://github.com/torvalds/linux/blob/master/drivers/pps/clients/pps-gpio.c#L175" target="_blank" rel="noopener" class="mycode_url">https://github.com/torvalds/linux/blob/m...pio.c#L175</a> returning -EINVAL (-22) where I found it using deprecated functions to get the interrupt so it might just be something to do with the pps-gpio client.<br />
<br />
The board that pps-gpio likes has pin 12 of the pi2 bus going to gpio PA6 whereas the pine64 connects pin 12 to gpio PC8 -- different banks on controller 0.<br />
<br />
Anyway, for the question - are GPIO's on bank C expected to be able to generate interrupts?   If so, I'll queue further investigation.   Otherwise I'll limit my selection to pins in the PH bank, or use the euler bus.]]></description>
			<content:encoded><![CDATA[Not sure if this is a general question or a linux question but here goes.<br />
<br />
I am coming back to a project after an extended interruption -- life got in the way of my play.<br />
<br />
I have a number of GPS units running on a variety of hardware.   The board I use for most of them is also allwiner based and run the same armbian as the pine64.  But, I like pine64's as a general purpose board and have several on my desk so decided to track down why I couldn't get them to work the way I wanted last time.<br />
<br />
That background information is not particularly normative but it offers some background.  You don't need any special hardware to reproduce this issue.<br />
<br />
My notes from many years ago says there was a post on IRC which confirmed we can not get interrupts from some of the GPIO banks.    I can no longer find that reference but that seems to be true.<br />
<br />
I can confirm that<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>overlays=pps-gpio<br />
param_pps_pin=PH9</code></div></div><br />
in armbianEnv.txt works with dmesg containing<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>[Mon Dec  9 23:58:56 2024] pps pps0: new PPS source pps@0.-1<br />
[Mon Dec  9 23:58:56 2024] pps pps0: Registered IRQ 100 as PPS source</code></div></div><br />
I can also confirm that<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>overlays=pps-gpio<br />
param_pps_pin=PC8</code></div></div><br />
in armbianEnv.txt fails with dmesg containing<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>[Tue Dec 10 00:04:25 2024] pps-gpio pps@0: failed to map GPIO to IRQ: -22<br />
[Tue Dec 10 00:04:25 2024] pps-gpio: probe of pps@0 failed with error -22</code></div></div><br />
I got as far as <a href="https://github.com/torvalds/linux/blob/master/drivers/pps/clients/pps-gpio.c#L175" target="_blank" rel="noopener" class="mycode_url">https://github.com/torvalds/linux/blob/m...pio.c#L175</a> returning -EINVAL (-22) where I found it using deprecated functions to get the interrupt so it might just be something to do with the pps-gpio client.<br />
<br />
The board that pps-gpio likes has pin 12 of the pi2 bus going to gpio PA6 whereas the pine64 connects pin 12 to gpio PC8 -- different banks on controller 0.<br />
<br />
Anyway, for the question - are GPIO's on bank C expected to be able to generate interrupts?   If so, I'll queue further investigation.   Otherwise I'll limit my selection to pins in the PH bank, or use the euler bus.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Random Board Shutdown]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=18879</link>
			<pubDate>Fri, 17 Nov 2023 18:18:58 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=27596">Curv0987</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=18879</guid>
			<description><![CDATA[My Pine a64 Lts runs fine, but when I plug in the ethernet cable, after about a few seconds of having internet, my board shuts down and won't fully reboot. It just shows a black screen. I am running Ubuntu. Any Ideas what the problem could be? I am very new to this sort of stuff so I apologize for my lack of knowledge.]]></description>
			<content:encoded><![CDATA[My Pine a64 Lts runs fine, but when I plug in the ethernet cable, after about a few seconds of having internet, my board shuts down and won't fully reboot. It just shows a black screen. I am running Ubuntu. Any Ideas what the problem could be? I am very new to this sort of stuff so I apologize for my lack of knowledge.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[getting second serial port available]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=18853</link>
			<pubDate>Fri, 10 Nov 2023 06:05:58 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=27252">gadgetguy</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=18853</guid>
			<description><![CDATA[I'm trying to get the second serial port working (/dev/ttyS2) on a PINE64-LTS board.<br />
<br />
I created and edited the DTS file as <dvz_me_placeholder id="0" />  posted a while back (<a href="https://forum.pine64.org/showthread.php?tid=648&amp;highlight=ttyS2" target="_blank" rel="noopener" class="mycode_url">https://forum.pine64.org/showthread.php?...ight=ttyS2</a>).<br />
But it didn't seem to work. I am using a logic analyzer to monitor the signals and getting NO data. I am using a simple C program to open and write to the port. the write reports its writing data.<br />
<br />
in /boot/dtb/allwinner I modified the "-lts.dtb" file<br />
-rw-r--r-- 1 root root 41859 Feb 17  2023 sun50i-a64-pine64.dtb<br />
-rw-rw-r-- 1 root root 41973 Nov  1 13:20 sun50i-a64-pine64-lts.dtb<br />
-rw-r--r-- 1 root root 41909 Feb 17  2023 sun50i-a64-pine64-lts-dtb-backup<br />
-rw-r--r-- 1 root root 41981 Feb 17  2023 sun50i-a64-pine64-plus.dtb<br />
<br />
<br />
Is there a way to confirm <br />
a) which DTB file the system is actually using, or<br />
b) that the "okay" on that serial port is enabling the mux mapping for those pins?<br />
<br />
Thanks in advance.]]></description>
			<content:encoded><![CDATA[I'm trying to get the second serial port working (/dev/ttyS2) on a PINE64-LTS board.<br />
<br />
I created and edited the DTS file as <dvz_me_placeholder id="0" />  posted a while back (<a href="https://forum.pine64.org/showthread.php?tid=648&amp;highlight=ttyS2" target="_blank" rel="noopener" class="mycode_url">https://forum.pine64.org/showthread.php?...ight=ttyS2</a>).<br />
But it didn't seem to work. I am using a logic analyzer to monitor the signals and getting NO data. I am using a simple C program to open and write to the port. the write reports its writing data.<br />
<br />
in /boot/dtb/allwinner I modified the "-lts.dtb" file<br />
-rw-r--r-- 1 root root 41859 Feb 17  2023 sun50i-a64-pine64.dtb<br />
-rw-rw-r-- 1 root root 41973 Nov  1 13:20 sun50i-a64-pine64-lts.dtb<br />
-rw-r--r-- 1 root root 41909 Feb 17  2023 sun50i-a64-pine64-lts-dtb-backup<br />
-rw-r--r-- 1 root root 41981 Feb 17  2023 sun50i-a64-pine64-plus.dtb<br />
<br />
<br />
Is there a way to confirm <br />
a) which DTB file the system is actually using, or<br />
b) that the "okay" on that serial port is enabling the mux mapping for those pins?<br />
<br />
Thanks in advance.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Tow-boot on Sopine module?]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=18085</link>
			<pubDate>Tue, 28 Mar 2023 13:42:45 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=17494">poVoq</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=18085</guid>
			<description><![CDATA[Officially Tow-boot only supports the PineA64-LTS: <a href="https://tow-boot.org/devices/pine64-pineA64LTS.html" target="_blank" rel="noopener" class="mycode_url">https://tow-boot.org/devices/pine64-pineA64LTS.html</a><br />
<br />
But it appears that most software works for both PineA64-LTS and the Sopine modules.<br />
<br />
Anyone tried flashing Tow-boot on the SPI?<br />
<br />
I have the older Sopine modules that still include SPIs... apparently newer revisions removed the SPI?]]></description>
			<content:encoded><![CDATA[Officially Tow-boot only supports the PineA64-LTS: <a href="https://tow-boot.org/devices/pine64-pineA64LTS.html" target="_blank" rel="noopener" class="mycode_url">https://tow-boot.org/devices/pine64-pineA64LTS.html</a><br />
<br />
But it appears that most software works for both PineA64-LTS and the Sopine modules.<br />
<br />
Anyone tried flashing Tow-boot on the SPI?<br />
<br />
I have the older Sopine modules that still include SPIs... apparently newer revisions removed the SPI?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[How to connect a pine64-LTS to a serial console?]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=18024</link>
			<pubDate>Sun, 12 Mar 2023 08:03:33 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=26495">zuvmajujo</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=18024</guid>
			<description><![CDATA[I'm trying to get two separate pine64 LTS boards to boot for the first time. Previous troubleshooting attempts here: <a href="https://forum.pine64.org/showthread.php?tid=17961" target="_blank" rel="noopener" class="mycode_url">https://forum.pine64.org/showthread.php?tid=17961</a>.<br />
<br />
I was hoping to monitor the serial port of each board to find some some helpful errors. I couldn't find a post specifically for the pine64 LTS but I did for the rock64: <a href="https://forum.pine64.org/showthread.php?tid=5029" target="_blank" rel="noopener" class="mycode_url">https://forum.pine64.org/showthread.php?tid=5029</a>. I connected to pin 6 (GND &lt;-&gt; GND), pin8 (TX -&gt; RX), and pin10 (RX -&gt; TX). As a sanity check I switched RX and TX to make sure I hadn't mis-connected something. I've tested the serial console on another dev board so I know it's working. I'm on Ubuntu 22.04 and I'm using the following command to read messages: <br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>sudo  minicom  -s  -D  /dev/ttyUSB0  -b  1500000  --color=on</code></div></div>I checked that the serial console is connected to /dev/ttyUSB0 by using the command:<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>ls -l /dev/serial/by-id</code></div></div>Absolutely nothing comes through minicom from both boards. I thought perhaps the steps for the rock64 are different for the pine64. Please enlighten me if so.]]></description>
			<content:encoded><![CDATA[I'm trying to get two separate pine64 LTS boards to boot for the first time. Previous troubleshooting attempts here: <a href="https://forum.pine64.org/showthread.php?tid=17961" target="_blank" rel="noopener" class="mycode_url">https://forum.pine64.org/showthread.php?tid=17961</a>.<br />
<br />
I was hoping to monitor the serial port of each board to find some some helpful errors. I couldn't find a post specifically for the pine64 LTS but I did for the rock64: <a href="https://forum.pine64.org/showthread.php?tid=5029" target="_blank" rel="noopener" class="mycode_url">https://forum.pine64.org/showthread.php?tid=5029</a>. I connected to pin 6 (GND &lt;-&gt; GND), pin8 (TX -&gt; RX), and pin10 (RX -&gt; TX). As a sanity check I switched RX and TX to make sure I hadn't mis-connected something. I've tested the serial console on another dev board so I know it's working. I'm on Ubuntu 22.04 and I'm using the following command to read messages: <br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>sudo  minicom  -s  -D  /dev/ttyUSB0  -b  1500000  --color=on</code></div></div>I checked that the serial console is connected to /dev/ttyUSB0 by using the command:<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>ls -l /dev/serial/by-id</code></div></div>Absolutely nothing comes through minicom from both boards. I thought perhaps the steps for the rock64 are different for the pine64. Please enlighten me if so.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Pine64 LTS won't boot]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=17961</link>
			<pubDate>Thu, 23 Feb 2023 04:10:14 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=26495">zuvmajujo</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=17961</guid>
			<description><![CDATA[I've been troubleshooting two Pine64 2G LTS boards for several days now and I haven't been able to get either to boot. I've read<a href="https://wiki.pine64.org/wiki/Getting_started#Step-by-Step_Instructions_for_Flashing_MicroSD_Cards" target="_blank" rel="noopener" class="mycode_url"> the instructions on flashing an SD card</a> and <a href="https://wiki.pine64.org/wiki/Getting_started#Troubleshooting" target="_blank" rel="noopener" class="mycode_url">the troubleshooting section in the Getting Started section of the wiki</a>. I've also read the relevant threads in the aptly named <a href="https://forum.pine64.org/showthread.php?tid=680" target="_blank" rel="noopener" class="mycode_url">Useful Threads </a>posts, yet I haven't gotten a board to boot yet.<br />
<br />
I've used balenaEtcher to flash two, known good, SD cards with Armbian 22.11 Jammy XFCE. I also tried the CLI version on both SD cards for thoroughness sake. Still no dice. I flashed the devices on a Windows 10 machine and on a Ubuntu 22.04 machine with the same result. The same SD cards can successfully boot other SBCs I have. I've powered both boards with a known good bench top power supply via GPIO pins 1 and 3 and with a 5V 2A power adapter. I can't actually confirm that the power adapter is good because the LTS boards are the only devices I have that accept the barrel connector. But regardless of how I power the boards, a green power LED lights up. My bench top power supply says the LTS boards are pulling ~125mA if that helps troubleshoot. The same supply can power much hungrier dev boards I have.<br />
<br />
I've used two, known good, HDMI monitors with two, known good, HDMI cables to see if screen resolution was the problem, but that still didn't work. I connected a known good Ethernet cable to both LTS boards and there is no activity on the pine 64 nor the port on the router. The same port and same cable plugged into other devices supplies Ethernet and lights up the jacks on both ends. I left a board on for a while and checked devices connected to my router just to see if it had an IP address, but no dice.<br />
<br />
I even tried randomly pressing the power and reset buttons to see if that changed anything, but I'm seeing no signs of life from either of the boards I have. Since I can't even SSH into either device I've basically exhausted all the trouble shooting options I can think of. All the tools I'm using are working with other devices on my bench.<br />
<br />
I tried flashing an SD card with Manjaro to see if it was an Armbian problem but couldn't get the installer to run on my Ubuntu machine. I intentionally buy two devices when bringing up new-to-me devices to rule out a DOA board. The fact that I have two boards that refuse to boot makes me think I'm doing something wrong. This isn't my first rodeo with open source hardware, but I'm out of ideas. Any troubleshooting suggestions will be greatly appreciated.]]></description>
			<content:encoded><![CDATA[I've been troubleshooting two Pine64 2G LTS boards for several days now and I haven't been able to get either to boot. I've read<a href="https://wiki.pine64.org/wiki/Getting_started#Step-by-Step_Instructions_for_Flashing_MicroSD_Cards" target="_blank" rel="noopener" class="mycode_url"> the instructions on flashing an SD card</a> and <a href="https://wiki.pine64.org/wiki/Getting_started#Troubleshooting" target="_blank" rel="noopener" class="mycode_url">the troubleshooting section in the Getting Started section of the wiki</a>. I've also read the relevant threads in the aptly named <a href="https://forum.pine64.org/showthread.php?tid=680" target="_blank" rel="noopener" class="mycode_url">Useful Threads </a>posts, yet I haven't gotten a board to boot yet.<br />
<br />
I've used balenaEtcher to flash two, known good, SD cards with Armbian 22.11 Jammy XFCE. I also tried the CLI version on both SD cards for thoroughness sake. Still no dice. I flashed the devices on a Windows 10 machine and on a Ubuntu 22.04 machine with the same result. The same SD cards can successfully boot other SBCs I have. I've powered both boards with a known good bench top power supply via GPIO pins 1 and 3 and with a 5V 2A power adapter. I can't actually confirm that the power adapter is good because the LTS boards are the only devices I have that accept the barrel connector. But regardless of how I power the boards, a green power LED lights up. My bench top power supply says the LTS boards are pulling ~125mA if that helps troubleshoot. The same supply can power much hungrier dev boards I have.<br />
<br />
I've used two, known good, HDMI monitors with two, known good, HDMI cables to see if screen resolution was the problem, but that still didn't work. I connected a known good Ethernet cable to both LTS boards and there is no activity on the pine 64 nor the port on the router. The same port and same cable plugged into other devices supplies Ethernet and lights up the jacks on both ends. I left a board on for a while and checked devices connected to my router just to see if it had an IP address, but no dice.<br />
<br />
I even tried randomly pressing the power and reset buttons to see if that changed anything, but I'm seeing no signs of life from either of the boards I have. Since I can't even SSH into either device I've basically exhausted all the trouble shooting options I can think of. All the tools I'm using are working with other devices on my bench.<br />
<br />
I tried flashing an SD card with Manjaro to see if it was an Armbian problem but couldn't get the installer to run on my Ubuntu machine. I intentionally buy two devices when bringing up new-to-me devices to rule out a DOA board. The fact that I have two boards that refuse to boot makes me think I'm doing something wrong. This isn't my first rodeo with open source hardware, but I'm out of ideas. Any troubleshooting suggestions will be greatly appreciated.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Article: PineDio LoRa Gateway: Testing The Prototype]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=15311</link>
			<pubDate>Thu, 11 Nov 2021 09:13:09 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=15376">lupyuen</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=15311</guid>
			<description><![CDATA[Here's how we test the pre-production PineDio LoRa Gateway (with PINE A64-LTS inside)... And connect it to The Things Network<br />
<br />
<a href="https://lupyuen.github.io/articles/gateway" target="_blank" rel="noopener" class="mycode_url">PineDio LoRa Gateway: Testing The Prototype</a>]]></description>
			<content:encoded><![CDATA[Here's how we test the pre-production PineDio LoRa Gateway (with PINE A64-LTS inside)... And connect it to The Things Network<br />
<br />
<a href="https://lupyuen.github.io/articles/gateway" target="_blank" rel="noopener" class="mycode_url">PineDio LoRa Gateway: Testing The Prototype</a>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Beginner Question about Clusters]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=15258</link>
			<pubDate>Thu, 04 Nov 2021 15:42:01 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=17881">ragreenburg</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=15258</guid>
			<description><![CDATA[I am looking to make my own cluster but I noticed the clusterboard was out of stock and so is the SOPINE so I was curious if anyone had any recommendations for other similar products? Or if anyone knows when the PINE ones will be back in stock?]]></description>
			<content:encoded><![CDATA[I am looking to make my own cluster but I noticed the clusterboard was out of stock and so is the SOPINE so I was curious if anyone had any recommendations for other similar products? Or if anyone knows when the PINE ones will be back in stock?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Newer Allwinner SOC with Sodimm plugin plans?]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=13966</link>
			<pubDate>Sun, 23 May 2021 11:10:50 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=22028">Daniel972</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=13966</guid>
			<description><![CDATA[I browsed Allwinners homepage and there seems to be new 4GB alternatives to A64 still with 32 bit memory addressing. Any development towards fitting one of these  (4GB RAM is much more than 2, and power consumption seems to be going downwards ) to the A64 sopine baseboard? <br />
<br />
Also would be cool to participate in work with a more mature SOC for implementing automotive security features towards smart devices,<br />
(IE Pinephone 1.0) in regards to financial integrity and privacy regarding personal health applications.]]></description>
			<content:encoded><![CDATA[I browsed Allwinners homepage and there seems to be new 4GB alternatives to A64 still with 32 bit memory addressing. Any development towards fitting one of these  (4GB RAM is much more than 2, and power consumption seems to be going downwards ) to the A64 sopine baseboard? <br />
<br />
Also would be cool to participate in work with a more mature SOC for implementing automotive security features towards smart devices,<br />
(IE Pinephone 1.0) in regards to financial integrity and privacy regarding personal health applications.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Has anyone gotten "reset" to work in U-Boot for Pine64?]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=13431</link>
			<pubDate>Thu, 18 Mar 2021 18:30:21 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=9087">Pine</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=13431</guid>
			<description><![CDATA[Has anyone gotten the "reset" command to work in U-Boot (v2021.01) for Pine64?<br />
<br />
I've tried for days combinations of enabling and disabling PSCI, SYSRESET, and DM_RESET. I've applied and removed various reset patches from people like Chris Blake in 2017 and again in 2019.<br />
<br />
Either the SoC enters an infinite loop walking a DM tree, or a message stating reset isn't supported on the board.<br />
<br />
Let's not ask what combination of CONFIG_* flags I've set, because I've tried permutations of them all.<br />
<br />
Has anyone, anywhere, gotten the SoPine (on a clusterboard) or Pine64-LTS to actually restart as if the reset button had been pressed? What are your defconf settings? What version in U-Boot? Thx!]]></description>
			<content:encoded><![CDATA[Has anyone gotten the "reset" command to work in U-Boot (v2021.01) for Pine64?<br />
<br />
I've tried for days combinations of enabling and disabling PSCI, SYSRESET, and DM_RESET. I've applied and removed various reset patches from people like Chris Blake in 2017 and again in 2019.<br />
<br />
Either the SoC enters an infinite loop walking a DM tree, or a message stating reset isn't supported on the board.<br />
<br />
Let's not ask what combination of CONFIG_* flags I've set, because I've tried permutations of them all.<br />
<br />
Has anyone, anywhere, gotten the SoPine (on a clusterboard) or Pine64-LTS to actually restart as if the reset button had been pressed? What are your defconf settings? What version in U-Boot? Thx!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[power usage for Pine64 LTS + Screen]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=13121</link>
			<pubDate>Mon, 15 Feb 2021 10:28:39 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=4038">Little_Johnny</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=13121</guid>
			<description><![CDATA[my pine doesn't seem to be charging the 5000mAh battery while the screen is on unless i turn the brightness way down using the 2A power supply, <br />
i guessing its using more power then it can get, i have a 5v 3A on its way<br />
does any 1 know how much power the <br />
board + 7inch screen + wifi/ bt module not turned on + camera <span style="color: #333333;" class="mycode_color"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font"><span style="font-size: small;" class="mycode_size">not turned on should be using?</span><br />
</span></span>will a 3A power supply be enough to charge the battery while its on be enough?<br />
has any 1 else had any similar issues to this?]]></description>
			<content:encoded><![CDATA[my pine doesn't seem to be charging the 5000mAh battery while the screen is on unless i turn the brightness way down using the 2A power supply, <br />
i guessing its using more power then it can get, i have a 5v 3A on its way<br />
does any 1 know how much power the <br />
board + 7inch screen + wifi/ bt module not turned on + camera <span style="color: #333333;" class="mycode_color"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font"><span style="font-size: small;" class="mycode_size">not turned on should be using?</span><br />
</span></span>will a 3A power supply be enough to charge the battery while its on be enough?<br />
has any 1 else had any similar issues to this?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Thermal Camera AMG8833 I2C]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=12705</link>
			<pubDate>Tue, 05 Jan 2021 11:44:53 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=4038">Little_Johnny</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=12705</guid>
			<description><![CDATA[can the Thermal Camera module AMG883 <span style="color: #333333;" class="mycode_color"><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font"><span style="font-size: small;" class="mycode_size"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font">be </span></span></span></span></span></span></span><span style="color: #333333;" class="mycode_color"><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font"><span style="font-size: small;" class="mycode_size"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font">used </span></span></span></span></span></span></span><span style="color: #333333;" class="mycode_color"><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font"><span style="font-size: small;" class="mycode_size"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font">with the </span></span></span></span></span></span></span><span style="color: #333333;" class="mycode_color"><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font"><span style="font-size: small;" class="mycode_size"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font">pine64 LTS with Android 6.0,</span></span></span></span></span></span></span><span style="color: #333333;" class="mycode_color"><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font"><span style="font-size: small;" class="mycode_size"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font"> </span></span></span></span></span></span></span><br />
its sold by <span style="color: #030303;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Roboto, Arial, sans-serif;" class="mycode_font">Adafruit</span></span></span> for the Raspberry Pi, it connects to the <span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font">Raspberry Pi </span></span></span>via I2C<br />
im still a noob when it comes to adding hardware and the programing side of things for the pine64<br />
<br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font"><a href="https://www.ebay.com.au/itm/AMG8833-IR-8x8-Thermal-Imager-Array-Temperature-Sensor-Module-For-Raspberry-XJ/143893775441?_trkparms=aid%3D1110006%26algo%3DHOMESPLICE.SIM%26ao%3D1%26asc%3D20200520130048%26meid%3D46a0c68d08b54161a7fb3b2ca8fa58f9%26pid%3D100005%26rk%3D5%26rkt%3D12%26mehot%3Dco%26sd%3D363222363903%26itm%3D143893775441%26pmt%3D1%26noa%3D0%26pg%3D2047675%26algv%3DSimplAMLv5PairwiseWebWithDarwoV3BBEV2b%26brand%3DUnbranded&amp;_trksid=p2047675.c100005.m1851" target="_blank" rel="noopener" class="mycode_url">https://www.ebay.com.au/itm/AMG8833-IR-8...0005.m1851</a></span></span></span>]]></description>
			<content:encoded><![CDATA[can the Thermal Camera module AMG883 <span style="color: #333333;" class="mycode_color"><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font"><span style="font-size: small;" class="mycode_size"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font">be </span></span></span></span></span></span></span><span style="color: #333333;" class="mycode_color"><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font"><span style="font-size: small;" class="mycode_size"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font">used </span></span></span></span></span></span></span><span style="color: #333333;" class="mycode_color"><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font"><span style="font-size: small;" class="mycode_size"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font">with the </span></span></span></span></span></span></span><span style="color: #333333;" class="mycode_color"><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font"><span style="font-size: small;" class="mycode_size"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font">pine64 LTS with Android 6.0,</span></span></span></span></span></span></span><span style="color: #333333;" class="mycode_color"><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font"><span style="font-size: small;" class="mycode_size"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font"> </span></span></span></span></span></span></span><br />
its sold by <span style="color: #030303;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Roboto, Arial, sans-serif;" class="mycode_font">Adafruit</span></span></span> for the Raspberry Pi, it connects to the <span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font">Raspberry Pi </span></span></span>via I2C<br />
im still a noob when it comes to adding hardware and the programing side of things for the pine64<br />
<br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Tahoma, Verdana, Arial, sans-serif;" class="mycode_font"><a href="https://www.ebay.com.au/itm/AMG8833-IR-8x8-Thermal-Imager-Array-Temperature-Sensor-Module-For-Raspberry-XJ/143893775441?_trkparms=aid%3D1110006%26algo%3DHOMESPLICE.SIM%26ao%3D1%26asc%3D20200520130048%26meid%3D46a0c68d08b54161a7fb3b2ca8fa58f9%26pid%3D100005%26rk%3D5%26rkt%3D12%26mehot%3Dco%26sd%3D363222363903%26itm%3D143893775441%26pmt%3D1%26noa%3D0%26pg%3D2047675%26algv%3DSimplAMLv5PairwiseWebWithDarwoV3BBEV2b%26brand%3DUnbranded&amp;_trksid=p2047675.c100005.m1851" target="_blank" rel="noopener" class="mycode_url">https://www.ebay.com.au/itm/AMG8833-IR-8...0005.m1851</a></span></span></span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Problem with EMMC bootup and detection]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=12045</link>
			<pubDate>Fri, 06 Nov 2020 07:47:31 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=20180">khantheengr</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=12045</guid>
			<description><![CDATA[Hello guys,<br />
I have recently bought PINEA64-lts boards with EMMC modules of 16gb. I am having trouble interfacing them now. When I burn any image on EMMC ( I have tried several), it dosen't boot from EMMC. The same image when I burn onto SD card,  it starts booting. When only EMMC is inserted PINE64 shows black screen and there is no sign of booting process. Can you please help me out.<br />
<br />
I have also tried auyfan's image on SD card. and when I insert EMMC onto PINEA64-lts and check EMMC status, it gets detected with uenv.txt "mmc_compact=on". But when i burn the same image on EMMC and repeat all of above process, boot process does not start.<br />
<br />
I am using pine64 usb programmer to program the emmc modules. and i ordered everything from the pine64 official site. EMMC has FORESEE 16 GB IC on it. <br />
<br />
When i plugin emmc module in laptop using programmer, it always gets detected and there is no problem in programming the EMMC module.<br />
<br />
I am newbie here, hope you guys will guide me well.... Thanks in advacnce]]></description>
			<content:encoded><![CDATA[Hello guys,<br />
I have recently bought PINEA64-lts boards with EMMC modules of 16gb. I am having trouble interfacing them now. When I burn any image on EMMC ( I have tried several), it dosen't boot from EMMC. The same image when I burn onto SD card,  it starts booting. When only EMMC is inserted PINE64 shows black screen and there is no sign of booting process. Can you please help me out.<br />
<br />
I have also tried auyfan's image on SD card. and when I insert EMMC onto PINEA64-lts and check EMMC status, it gets detected with uenv.txt "mmc_compact=on". But when i burn the same image on EMMC and repeat all of above process, boot process does not start.<br />
<br />
I am using pine64 usb programmer to program the emmc modules. and i ordered everything from the pine64 official site. EMMC has FORESEE 16 GB IC on it. <br />
<br />
When i plugin emmc module in laptop using programmer, it always gets detected and there is no problem in programming the EMMC module.<br />
<br />
I am newbie here, hope you guys will guide me well.... Thanks in advacnce]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Pine A64 LTS V1.2 LCD DSI Boot Issue]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=10633</link>
			<pubDate>Fri, 10 Jul 2020 20:38:40 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=18626">emud</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=10633</guid>
			<description><![CDATA[I just received my Pine A64 LTS V1.2 board, 7" LCD TOUCH SCREEN PANEL, and playbox enclosure.<br />
<br />
<br />
<br />
<br />
<br />
I flashed an sd card with Linux Armbian Focal:<br />
<br />
<br />
<br />
<a href="https://dl.armbian.com/pine64so/Focal_current" target="_blank" rel="noopener" class="mycode_url">https://dl.armbian.com/pine64so/Focal_current</a><br />
<br />
<br />
<br />
If the LCD is connected via the DSI port, the boot freezes during UBoot:<br />
<br />
<br />
<br />
<img src="https://forum.pine64.org/attachment.php?aid=1981" loading="lazy"  alt="[Image: attachment.php?aid=1981]" class="mycode_img" /><br />
<br />
<br />
<br />
<br />
If I disconnect the LCD from the DSI connector, we get past that part immediately:<br />
<br />
<br />
<img src="https://forum.pine64.org/attachment.php?aid=1981" loading="lazy"  alt="[Image: attachment.php?aid=1981]" class="mycode_img" /><br />
<br />
<br />
<br />
<br />
and it eventually brings us to the login prompt.<br />
<br />
<br />
<br />
<br />
I tried re-seating the LCD connector. What am I missing here?<br />
<br />
<br />
<br />
<br />
<br />
<br />
Cheers!<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.pine64.org/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=1981" target="_blank" title="">2020-07-15 pine64 boot 1.PNG</a> (Size: 20.39 KB / Downloads: 1059)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.pine64.org/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=1982" target="_blank" title="">2020-07-15 pine64 boot 2.PNG</a> (Size: 32.8 KB / Downloads: 613)
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[I just received my Pine A64 LTS V1.2 board, 7" LCD TOUCH SCREEN PANEL, and playbox enclosure.<br />
<br />
<br />
<br />
<br />
<br />
I flashed an sd card with Linux Armbian Focal:<br />
<br />
<br />
<br />
<a href="https://dl.armbian.com/pine64so/Focal_current" target="_blank" rel="noopener" class="mycode_url">https://dl.armbian.com/pine64so/Focal_current</a><br />
<br />
<br />
<br />
If the LCD is connected via the DSI port, the boot freezes during UBoot:<br />
<br />
<br />
<br />
<img src="https://forum.pine64.org/attachment.php?aid=1981" loading="lazy"  alt="[Image: attachment.php?aid=1981]" class="mycode_img" /><br />
<br />
<br />
<br />
<br />
If I disconnect the LCD from the DSI connector, we get past that part immediately:<br />
<br />
<br />
<img src="https://forum.pine64.org/attachment.php?aid=1981" loading="lazy"  alt="[Image: attachment.php?aid=1981]" class="mycode_img" /><br />
<br />
<br />
<br />
<br />
and it eventually brings us to the login prompt.<br />
<br />
<br />
<br />
<br />
I tried re-seating the LCD connector. What am I missing here?<br />
<br />
<br />
<br />
<br />
<br />
<br />
Cheers!<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.pine64.org/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=1981" target="_blank" title="">2020-07-15 pine64 boot 1.PNG</a> (Size: 20.39 KB / Downloads: 1059)
<!-- end: postbit_attachments_attachment --><br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.pine64.org/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=1982" target="_blank" title="">2020-07-15 pine64 boot 2.PNG</a> (Size: 32.8 KB / Downloads: 613)
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
	</channel>
</rss>