<?xml version="1.0"?>
<rss version="2.0"><channel><title>Orange Pi One Latest Topics</title><link>https://testforum.armbian.com/forum/238-orange-pi-one/</link><description>Orange Pi One Latest Topics</description><language>en</language><item><title>Connecting Nokia 5510 LCD to OPi One: pin PA14 already requested by 1c28c00.serial; cannot claim for 1c69000.spi</title><link>https://testforum.armbian.com/topic/60479-connecting-nokia-5510-lcd-to-opi-one-pin-pa14-already-requested-by-1c28c00serial-cannot-claim-for-1c69000spi/</link><description><![CDATA[<p>
	I'm trying to connect Nokia 5110 / PCD8544 LCD to my Orange Pi One H3 (Board v1.1). This is my wiring:
</p>

<table border="1" cellpadding="1" cellspacing="1" style="width:250px;" summary="GND to GND, LIGHT to GND, VCC to 3v, CLK to PC2 (CLK), DIN to PC0 (MOSI),  DC to PA6, CE - PC3 (CE), RST - PA9">
	<caption>
		Connection (LCD to <abbr title="Orange Pi"><abbr title="Orange Pi">OPi</abbr></abbr>)
	</caption>
	<thead>
		<tr>
			<th scope="col">
				Nokia 5110 LCD pin
			</th>
			<th scope="col">
				Orange Pi One pin
			</th>
		</tr>
	</thead>
	<tbody>
		<tr>
			<td>
				GND
			</td>
			<td>
				GND
			</td>
		</tr>
		<tr>
			<td>
				LIGHT
			</td>
			<td>
				GND
			</td>
		</tr>
		<tr>
			<td>
				VCC
			</td>
			<td>
				3.3v
			</td>
		</tr>
		<tr>
			<td>
				CLK
			</td>
			<td>
				PC2 (CLK)
			</td>
		</tr>
		<tr>
			<td>
				DIN
			</td>
			<td>
				PC0 (MOSI)
			</td>
		</tr>
		<tr>
			<td>
				DC
			</td>
			<td>
				PA6
			</td>
		</tr>
		<tr>
			<td>
				CE
			</td>
			<td>
				PC3 (CE)
			</td>
		</tr>
		<tr>
			<td>
				RST
			</td>
			<td>
				PA9
			</td>
		</tr>
	</tbody>
</table>

<p>
	 
</p>

<p>
	This is my LCD:
</p>

<p>
	<img alt="image.png.0fd8b311e8f31013448acb6226e15eb0.png" class="ipsImage ipsImage_thumbnailed" data-fileid="16616" width="320" src="https://testforum.armbian.com/uploads/monthly_2026_06/image.png.0fd8b311e8f31013448acb6226e15eb0.png" loading="lazy" height="320"><img alt="image.png.6515f6b254ad6789e491438a1c3ebd5a.png" class="ipsImage ipsImage_thumbnailed" data-fileid="16617" width="320" src="https://testforum.armbian.com/uploads/monthly_2026_06/image.png.6515f6b254ad6789e491438a1c3ebd5a.png" loading="lazy" height="320">
</p>

<p>
	 
</p>

<p>
	The backlight is working upon turning on <abbr title="Orange Pi"><abbr title="Orange Pi">OPi</abbr></abbr> One.
</p>

<p>
	The official Orange Pi One H3 manual suggests using fbtft_device kernel module, which is LONG deprecated and no longer supported.
</p>

<p>
	On Raspberry Pi forums, someone was suggested to use a Device Tree Overlay  instead.
</p>

<p>
	 
</p>

<p>
	I've stumbled upon an <a href="https://raw.githubusercontent.com/nuharaf/fbtft-dt-overlay/refs/heads/master/nokia5110opizero.dts" rel="external nofollow">Orange Pi Zero overlay file for my LCD</a>. So I've changed a few lines:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">/dts-v1/;
/plugin/;

/ {
	compatible = "allwinner,sun8i-h3";

	fragment@0 {
		target = &lt;&amp;spi1&gt;;
		__overlay__ {
			status = "okay";

			spidev@0{
				status = "disabled";
			};

			spidev@1{
				status = "disabled";
			};
		};
	};

	fragment@1 {
		target = &lt;&amp;pio&gt;;
		__overlay__ {
			opiz_display_pins: opiz_display_pins {
                pins = "PA9", "PA6";
                function = "gpio_out";
			};
		};
	};

	fragment@2 {
		target = &lt;&amp;spi1&gt;;
		__overlay__ {
			/* needed to avoid dtc warning */
			#address-cells = &lt;1&gt;;
			#size-cells = &lt;0&gt;;

			opizdisplay: opiz-display@0{
				compatible = "philips,pcd8544";
				reg = &lt;0&gt;;
				pinctrl-names = "default";
				pinctrl-0 = &lt;&amp;opiz_display_pins&gt;;

				spi-max-frequency = &lt;400000&gt;;
				fps = &lt;30&gt;;
				buswidth = &lt;8&gt;;
				reset-gpios = &lt;&amp;pio 0 33 1&gt;;
				dc-gpios = &lt;&amp;pio 0 7 0&gt;;
			};
		};
	};
};</span></pre>

<p>
	 
</p>

<p>
	And compiled, loaded it into an <abbr title="Device tree source"><abbr title="Device tree source">DTS</abbr></abbr> user directory.
</p>

<p>
	 
</p>

<p>
	I've connected Arduino as a Serial-to-USB convertor to <abbr title="Orange Pi"><abbr title="Orange Pi">OPi</abbr></abbr> and it would seem it has loaded successfully:
</p>

<pre class="ipsCode">Applying user provided DT overlay nokia5110opizero.dtbo
4185 bytes read in 14 ms (291 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 45000000
Kernel image @ 0x42000000 [ 0x000000 - 0xa0ea90 ]
## Loading init Ramdisk from Legacy Image at 43400000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    17670074 Bytes = 16.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
Working FDT set to 43000000
   Loading Ramdisk to 48f26000, end 49ffffba ... OK
   Loading Device Tree to 48eb5000, end 48f25fff ... OK
Working FDT set to 48eb5000</pre>

<p>
	 
</p>

<p>
	 
</p>

<p>
	But according to <a href="https://paste.armbian.com/ebavotuzom" rel="external nofollow">armbianmonitor -u output</a> , the overlay ends up creating new errors:
</p>

<pre class="ipsCode">[    1.630221] sun8i-h3-pinctrl 1c20800.pinctrl: pin PA14 already requested by 1c28c00.serial; cannot claim for 1c69000.spi
[    1.630250] sun8i-h3-pinctrl 1c20800.pinctrl: error -EINVAL: pin-14 (1c69000.spi)
[    1.630269] sun8i-h3-pinctrl 1c20800.pinctrl: error -EINVAL: could not request pin 14 (PA14) from group PA14 on device 1c20800.pinctrl
[    1.630288] sun6i-spi 1c69000.spi: Error applying setting, reverse things back</pre>

<p>
	 
</p>

<p>
	I know the overlay is for Zero series, but i figured it should be the same since H3 is mentioned in there. Or at least I would be glad to know how to modify this for my board.
</p>

<p>
	Attached below are both logs for Serial and the kernel.
</p>

<p>
	 
</p>

<p>
	So far my goal is display anything, even a black square, on the screen. Would be sick to use it as a screen for console (like /dev/fb0).
</p>

<p>
	 
</p>

<p>
	Hoping for your help since I'm stuck. Thanks in advance!
</p>

<p>
	<a class="ipsAttachLink" data-fileext="txt" data-fileid="16618" href="https://testforum.armbian.com/applications/core/interface/file/attachment.php?id=16618&amp;key=aaa7cbeb88a73c0c45281750cdc982aa" rel="">dmesg.txt</a> <a class="ipsAttachLink" data-fileext="txt" data-fileid="16619" href="https://testforum.armbian.com/applications/core/interface/file/attachment.php?id=16619&amp;key=c63e9c00ed783685286826b8bcb72c59" rel="">serial.txt</a>
</p>
]]></description><guid isPermaLink="false">60479</guid><pubDate>Wed, 24 Jun 2026 19:13:23 +0000</pubDate></item><item><title>Composite TV OUT WORKING in Orange Pi One H3, 6.12 current</title><link>https://testforum.armbian.com/topic/53991-composite-tv-out-working-in-orange-pi-one-h3-612-current/</link><description><![CDATA[<p>
	Hello, I found this guide: <a href="https://github.com/robertojguerra/orangepi-zero-full-setup/blob/main/README2.md" rel="external nofollow">https://github.com/robertojguerra/orangepi-zero-full-setup/blob/main/README2.md</a><br />
	I followed the steps and built an Armbian image with current 6.12 kernel and now TV OUT (CVBS, Composite Video), after soldering a cable to the video pin on the board, is working on my Orange Pi One with an Allwinner H3 CPU (the patches might work for other H3/H2+ boards). I would like to get that functionality incorporated into Armbian.
</p>
]]></description><guid isPermaLink="false">53991</guid><pubDate>Tue, 22 Jul 2025 23:13:01 +0000</pubDate></item><item><title>Armbian 25.5.1 Noble 6.12</title><link>https://testforum.armbian.com/topic/53705-armbian-2551-noble-612/</link><description><![CDATA[<p>
	Currently using Armbian as a PiHole DNS server, it seems that after a few days the server just shuts itself down (Armbian 25.5.1 Noble 6.12).  Not sure if it is a hardware related issue, I'll do some more tests and revert back to 25.2.2 Bookworm for now and see if the issue is replicated.
</p>

<p>
	 
</p>

<p>
	Please note that my primary Armbian PiHole DNS does not encounter the same issue, though the version of it is Noble v25.2.3 / 6.12.30. 
</p>
]]></description><guid isPermaLink="false">53705</guid><pubDate>Sat, 12 Jul 2025 04:18:56 +0000</pubDate></item><item><title>Does exist a stable, old, low temperature version of Armbian for OPi1</title><link>https://testforum.armbian.com/topic/53752-does-exist-a-stable-old-low-temperature-version-of-armbian-for-opi1/</link><description><![CDATA[<p>
	Hi,<br />
	I have 2 OPi1 that I want to use for some test projects.
</p>

<p>
	One project consist just on PiHole, the other one on Tailscale.
</p>

<p>
	Since with newer kernel I have high temperature on idle (like 70°C) can you advice me an old version that maybe has a "better" thermal management?<br />
	Thank you so much, if I'm saying something stupid please tell me, maybe I just need to tune something like disable hdmi, <abbr title="Graphic processing unit (3D acceleration)">gpu</abbr> etc...
</p>
]]></description><guid isPermaLink="false">53752</guid><pubDate>Mon, 14 Jul 2025 19:07:50 +0000</pubDate></item><item><title>How to use XPT2046 touch controller 3.5inch RPi Display 480x320 pixels</title><link>https://testforum.armbian.com/topic/48026-how-to-use-xpt2046-touch-controller-35inch-rpi-display-480x320-pixels/</link><description><![CDATA[<p>
	Hi everyone,
</p>

<p>
	I’m trying to get a 3.5-inch <abbr title="Raspberry Pi">RPi</abbr> display with the XPT2046 touch controller (480x320 resolution) to work on my Orange Pi One (H3). I’ve been looking for guides, but most of them are Raspberry Pi-specific and not directly applicable to the Orange Pi.
</p>

<p>
	Here’s what I’ve tried so far:
</p>

<ul>
	<li>
		Installed Armbian on the Orange Pi One.
	</li>
	<li>
		Connected the display via the SPI interface.
	</li>
	<li>
		Installed fbtft and tried different configurations for the screen.
	</li>
</ul>

<p>
	However, I haven’t been able to get the display to show anything or to interact with the touch input.
</p>

<p>
	Does anyone have experience using this specific setup?
</p>

<ul>
	<li>
		What drivers or overlays should I use?
	</li>
	<li>
		Do I need to modify the <abbr title="Device tree blob">dtb</abbr> or <abbr title="Device tree source">dts</abbr> files?
	</li>
	<li>
		Any tips on configuring SPI and touch input in Armbian?
	</li>
</ul>

<p>
	Any help would be greatly appreciated! Thanks in advance.<br>
	<br>
	I have confirmed that the display has power because it turns on.
</p>

<p><a href="https://testforum.armbian.com/uploads/monthly_2024_12/462551740_1593543178219587_7387040162722380434_n.jpg.56a0e49e1b88d3e25cb405ba69d69df6.jpg" class="ipsAttachLink ipsAttachLink_image"><img data-fileid="13636" src="https://testforum.armbian.com/uploads/monthly_2024_12/462551740_1593543178219587_7387040162722380434_n.thumb.jpg.19084e3b2df24a16d2552dab0344abae.jpg" width="422" class="ipsImage ipsImage_thumbnailed" alt="462551740_1593543178219587_7387040162722380434_n.jpg" loading="lazy" height="746.94"></a></p>]]></description><guid isPermaLink="false">48026</guid><pubDate>Tue, 10 Dec 2024 14:29:01 +0000</pubDate></item><item><title>OrangePi One wont boot anymore</title><link>https://testforum.armbian.com/topic/48373-orangepi-one-wont-boot-anymore/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	Ive setup ssh and did some stuff on my OrangePi, when i came back and plugged my phone into power hub my OrangePi was connected to, it restarted and stopped at disk manager, i restarted it and it gave lots of failed messages, i restarted and it didnt work anymore <span>:(</span>
</p>

<p>
	it only gives yellow ethernet led and nothing else, i also reflashed sd card because it got all partitions gone after that incident
</p>

<p>
	 
</p>

<p>
	Please help!!!
</p>
]]></description><guid isPermaLink="false">48373</guid><pubDate>Tue, 17 Dec 2024 10:44:59 +0000</pubDate></item><item><title>6.10.9 breake dtb overlay</title><link>https://testforum.armbian.com/topic/45546-6109-breake-dtb-overlay/</link><description><![CDATA[<p>
	In the latest update，kenel 6.10.9 changes the layout of <abbr title="Device tree blob">dtb</abbr> overlays , all dtbo in one single folder, no “/boot/<abbr title="Device tree blob">dtb</abbr>/allwinner/overlay” folder.
</p>

<p>
	 
</p>

<p>
	Is it a new feather?
</p>
]]></description><guid isPermaLink="false">45546</guid><pubDate>Fri, 27 Sep 2024 01:59:32 +0000</pubDate></item><item><title>linux-image-legacy-sunxi=24.5.1 (kernel 6.1.92) is broken: stuck at "Starting kernel ..."</title><link>https://testforum.armbian.com/topic/41339-linux-image-legacy-sunxi2451-kernel-6192-is-broken-stuck-at-starting-kernel/</link><description><![CDATA[<p>
	The Linux kernel contained in the latest "linux-image-legacy-sunxi" (version 24.5.1) package appears to broken to the point of locking-up right from the start. It prints "Starting kernel ...", and no more messages appear even with "verbosity=7" set in the "armbianEnv.txt". The "linux-image-legacy-sunxi" version 24.2.1 boots just fine.
</p>

<p>
	 
</p>

<p>
	Here are the steps to reproduce the problem. I've done this on "Orange Pi One" board, but exactly the same issue occurs on (community maintained) Banana Pi M1.
</p>

<p>
	1. Download and write the Armbian image to a MicroSD card.
</p>

<p>
	2. Connect the serial console, boot the board, finish setup, do all the upgrades: everything works fine at this point.
</p>

<p>
	3. Set "verbosity=7" in the "armbianEnv.txt", reboot and observe the kernel messages. At this point, the "linux-image-current-sunxi", version 24.5.1 (kernel 6.6.31) is installed.
</p>

<p>
	4. Install "armbian-config" and use it to switch to "linux-image-legacy-sunxi=24.2.1 (6.1.77)". Observe that the board boots up fine.
</p>

<p>
	5. Now switch to "linux-image-legacy-sunxi=24.5.1 (6.1.92)". The boot process now gets stuck at "Starting kernel ..." message.
</p>

<p>
	 
</p>

<p>
	So as a summary:
</p>

<p>
	*  "linux-image-current-sunxi" version 24.5.1 with 6.6.31 kernel: boots fine.
</p>

<p>
	*  "linux-image-legacy-sunxi" version 24.2.1 with "6.1.77" kernel: boots fine.
</p>

<p>
	*  "linux-image-legacy-sunxi" version 24.5.1 with "6.1.92" kernel: broken: stuck at "Starting kernel ..." message.
</p>

<p>
	 
</p>

<p>
	I wonder if anyone could check what could have happened with "linux-image-legacy-sunxi" in the latest Armbian build.
</p>
]]></description><guid isPermaLink="false">41339</guid><pubDate>Mon, 17 Jun 2024 17:52:42 +0000</pubDate></item><item><title>Armbian 24.2 and Orange Pi One</title><link>https://testforum.armbian.com/topic/36670-armbian-242-and-orange-pi-one/</link><description><![CDATA[<p>
	Seems like the OS "malfunctions" after a few hours to a couple of days. The server is still responding to Pings, but services are all down, such as SSH.  Doing a power cycle would make the system available back online, until it becomes non-responsive again.  Moving back to 23.11.1 solves the stability issue.  To add, I'm using a couple of instances for primary and secondary PiHole DNS servers.
</p>

<p>
	 
</p>

<p>
	Probably similar issue on this thread -
</p>
<iframe allowfullscreen="" data-controller="core.front.core.autosizeiframe" data-embedauthorid="6808" data-embedcontent="" data-embedid="embed2890906437" src="https://testforum.armbian.com/topic/35635-armbian-242-is-broken-on-orange-pi-pc2/?do=embed" style="height:211px;max-width:500px;" loading="lazy"></iframe>

<p>
	 
</p>

<p>
	I'm a bit of a noob, <s>if someone can redirect me to pasting logs. Can those be found on /var/logs</s> as I haven't explored much.  I have downgraded both my OPiOnes to 23.11.1 and Frozen the Armbian firmware updates, so I can't provide logs for now at least until I try to update one of the instances.
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">36670</guid><pubDate>Sun, 24 Mar 2024 02:15:50 +0000</pubDate></item><item><title>Armbian 24.2.1 Linux 6.6.16-current-sunxi - deadloop after network link got lost</title><link>https://testforum.armbian.com/topic/37470-armbian-2421-linux-6616-current-sunxi-deadloop-after-network-link-got-lost/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	 
</p>

<p>
	I‘m recently updated to Armbian 24.2.1 Bookworm with Linux 6.6.16-current-sunxi.
</p>

<p>
	 
</p>

<p>
	The system is running fine but if I disconnect the network interface, the system gets stuck in kind of a dead loop.<br />
	This behavior gave me the hint that my WiFi repeater is broken and needs to be exchanged. Anyway, the CPU temperature rises and no further interaction with the system is possible.
</p>

<p>
	 
</p>

<p>
	If I disconnect it, from a normal operating switch, the OpiOne’s behavior looks the same.
</p>

<p>
	 
</p>

<p>
	My problem with this behavior is that after reconnecting the network, it does not get back available, until I do a power cycle.
</p>

<p>
	 
</p>

<p>
	I tried to read out the root of that problem out of the logs but didn’t had success yet.
</p>

<p>
	<br />
	I have uploaded the monitor logs:
</p>

<p>
	<a href="https://paste.armbian.com/cuqayiyimi" rel="external nofollow">https://paste.armbian.com/cuqayiyimi</a><br />
	 
</p>

<p>
	Further information: A cooler is attached to the CPU and my <abbr title="Power supply unit">PSU</abbr> is able to provide 6A current.
</p>

<p>
	I haven’t had a problem with this Orange Pi during the last 4 years of running an older outdated version of Armbian.
</p>

<p>
	I’m only running some docker container with only use minimum resources.
</p>

<p>
	 
</p>

<p>
	I hope that this isn’t a duplicate, haven’t found other topics like that.
</p>

<p>
	 
</p>

<p>
	best regards
</p>

<p>
	kai
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">37470</guid><pubDate>Fri, 12 Apr 2024 11:18:14 +0000</pubDate></item><item><title>armbian-live-patch error</title><link>https://testforum.armbian.com/topic/37441-armbian-live-patch-error/</link><description><![CDATA[<p>
	Hi, since a few weeks I get these errors in multiple Orange pi-s
</p>

<p>
	 
</p>

<p>
	unattended-upgrades-dpkg.log:3:E:Sub-process /usr/lib/armbian/armbian-live-patch apt returned an error code (127), E:Failure running script /usr/lib/armbian/armbian-live-patch apt<br />
	unattended-upgrades.log:7:2024-04-11 11:00:58,211 ERROR Installing the upgrades failed!
</p>

<p>
	 
</p>

<p>
	I have a  local repos for debian and armbian, and the Orange pi-s have no internet access.
</p>

<p>
	 
</p>

<p>
	Has been working fine in the past years
</p>

<p>
	 
</p>

<p>
	Did a fresh install having internet access : ok
</p>

<p>
	Armbian_24.2.1_Orangepione_bookworm_current_6.6.16.img.xz
</p>

<p>
	then changed to offline, using my local repos
</p>

<p>
	as example tried to install ntp and docker.io
</p>

<p>
	All failed, with above like errors
</p>

<p>
	<br />
	So,
</p>

<p>
	Q1 : is it no longer possible to work offline using local repos ?
</p>

<p>
	Q2 <span>:</span> Or is there a work around for this ?
</p>

<p>
	 
</p>

<p>
	Set
</p>
]]></description><guid isPermaLink="false">37441</guid><pubDate>Thu, 11 Apr 2024 17:34:05 +0000</pubDate></item><item><title>armbian orange pi one stuck</title><link>https://testforum.armbian.com/topic/14594-armbian-orange-pi-one-stuck/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	I am new to all this and I have downloaded everything to my sd card.
</p>

<p>
	When I power on the board it gets stuck on "started update UTMP about system runlevel changes" and does nothing more.
</p>

<p>
	 
</p>

<p>
	some images at https://imgur.com/92ZOiwD
</p>
]]></description><guid isPermaLink="false">14594</guid><pubDate>Wed, 08 Jul 2020 20:08:30 +0000</pubDate></item><item><title>Status of orangepione</title><link>https://testforum.armbian.com/topic/33361-status-of-orangepione/</link><description><![CDATA[<p>
	<a contenteditable="false" data-ipshover="" data-ipshover-target="https://testforum.armbian.com/profile/1-igor/?do=hovercard" data-mentionid="1" href="https://testforum.armbian.com/profile/1-igor/" rel="">@Igor</a> What is the status of the orangepione? On the download page there are no images presented yet in the build framework is shows up as "conf" in the support (1st) page.
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">33361</guid><pubDate>Tue, 23 Jan 2024 00:12:45 +0000</pubDate></item><item><title>OV5640 device tree overlay for OrangePi One H3</title><link>https://testforum.armbian.com/topic/13238-ov5640-device-tree-overlay-for-orangepi-one-h3/</link><description><![CDATA[<p>
	Hi!
</p>

<p>
	 
</p>

<p>
	Now that the camera interface has been merged in mainline Kernel, I would like to try to use the OrangePi OV5640 camera module on my OrangePi One.
</p>

<p>
	So with the latest Armbian Bionic (20.02.1, kernel 5.4.20), I have been trying to get a device tree overlay.
</p>

<p>
	 
</p>

<p>
	But for now, it fails to compile with:
</p>

<pre class="ipsCode">
$ sudo armbian-add-overlay sun8i-h3-csi.dts 
Compiling the overlay
Error: sun8i-h3-csi.dts:27.23-24 syntax error
FATAL ERROR: Unable to parse input tree
Error compiling the overlay</pre>

<p>
	My current overlay looks like this:
</p>

<pre class="ipsCode prettyprint lang-c prettyprinted">
<span class="pun">/</span><span class="pln">dts</span><span class="pun">-</span><span class="pln">v1</span><span class="pun">/;</span><span class="pln">
</span><span class="pun">/</span><span class="pln">plugin</span><span class="pun">/;</span><span class="pln">

</span><span class="pun">/</span><span class="pln"> </span><span class="pun">{</span><span class="pln">
	compatible </span><span class="pun">=</span><span class="pln"> </span><span class="str">"allwinner,sun8i-h3"</span><span class="pun">;</span><span class="pln">

	fragment@0 </span><span class="pun">{</span><span class="pln">
		target </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;&amp;</span><span class="pln">pio</span><span class="pun">&gt;;</span><span class="pln">
		__overlay__ </span><span class="pun">{</span><span class="pln">
			csi_mclk_pin</span><span class="pun">:</span><span class="pln"> csi</span><span class="pun">-</span><span class="pln">mclk</span><span class="pun">-</span><span class="pln">pin </span><span class="pun">{</span><span class="pln">
				pins </span><span class="pun">=</span><span class="pln"> </span><span class="str">"PE1"</span><span class="pun">;</span><span class="pln">
				function </span><span class="pun">=</span><span class="pln"> </span><span class="str">"csi"</span><span class="pun">;</span><span class="pln">
			</span><span class="pun">};</span><span class="pln">
		</span><span class="pun">};</span><span class="pln">
	</span><span class="pun">};</span><span class="pln">

	fragment@1 </span><span class="pun">{</span><span class="pln">
		target </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;&amp;</span><span class="pln">i2c2</span><span class="pun">&gt;;</span><span class="pln">
		__overlay__ </span><span class="pun">{</span><span class="pln">
			status </span><span class="pun">=</span><span class="pln"> </span><span class="str">"okay"</span><span class="pun">;</span><span class="pln">

			ov5640</span><span class="pun">:</span><span class="pln"> camera@3c </span><span class="pun">{</span><span class="pln">
				compatible </span><span class="pun">=</span><span class="pln"> </span><span class="str">"ovti,ov5640"</span><span class="pun">;</span><span class="pln">
				reg </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">0x3c</span><span class="pun">&gt;;</span><span class="pln">
				pinctrl</span><span class="pun">-</span><span class="pln">names </span><span class="pun">=</span><span class="pln"> </span><span class="str">"default"</span><span class="pun">;</span><span class="pln">
				pinctrl</span><span class="pun">-</span><span class="lit">0</span><span class="pln"> </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;&amp;</span><span class="pln">csi_mclk_pin</span><span class="pun">&gt;;</span><span class="pln">
				clocks </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;&amp;</span><span class="pln">ccu CLK_CSI_MCLK</span><span class="pun">&gt;;</span><span class="pln">
				clock</span><span class="pun">-</span><span class="pln">names </span><span class="pun">=</span><span class="pln"> </span><span class="str">"xclk"</span><span class="pun">;</span><span class="pln">

				AVDD</span><span class="pun">-</span><span class="pln">supply </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;&amp;</span><span class="pln">reg_aldo1</span><span class="pun">&gt;;</span><span class="pln">
				DOVDD</span><span class="pun">-</span><span class="pln">supply </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;&amp;</span><span class="pln">reg_dldo3</span><span class="pun">&gt;;</span><span class="pln">
				DVDD</span><span class="pun">-</span><span class="pln">supply </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;&amp;</span><span class="pln">reg_eldo3</span><span class="pun">&gt;;</span><span class="pln">
				reset</span><span class="pun">-</span><span class="pln">gpios </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;&amp;</span><span class="pln">pio </span><span class="lit">4</span><span class="pln"> </span><span class="lit">14</span><span class="pln"> GPIO_ACTIVE_LOW</span><span class="pun">&gt;;</span><span class="pln"> </span><span class="com">/* CSI-RST-R: PE14 */</span><span class="pln">
				powerdown</span><span class="pun">-</span><span class="pln">gpios </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;&amp;</span><span class="pln">pio </span><span class="lit">4</span><span class="pln"> </span><span class="lit">15</span><span class="pln"> GPIO_ACTIVE_HIGH</span><span class="pun">&gt;;</span><span class="pln"> </span><span class="com">/* CSI-STBY-R: PE15 */</span><span class="pln">

				port </span><span class="pun">{</span><span class="pln">
					ov5640_ep</span><span class="pun">:</span><span class="pln"> endpoint </span><span class="pun">{</span><span class="pln">
						remote</span><span class="pun">-</span><span class="pln">endpoint </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;&amp;</span><span class="pln">csi_ep</span><span class="pun">&gt;;</span><span class="pln">
						bus</span><span class="pun">-</span><span class="pln">width </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">8</span><span class="pun">&gt;;</span><span class="pln">
						data</span><span class="pun">-</span><span class="pln">shift </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">2</span><span class="pun">&gt;;</span><span class="pln"> </span><span class="com">/* lines 9:2 are used */</span><span class="pln">
						hsync</span><span class="pun">-</span><span class="pln">active </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">1</span><span class="pun">&gt;;</span><span class="pln"> </span><span class="com">/* Active high */</span><span class="pln">
						vsync</span><span class="pun">-</span><span class="pln">active </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">0</span><span class="pun">&gt;;</span><span class="pln"> </span><span class="com">/* Active low */</span><span class="pln">
						data</span><span class="pun">-</span><span class="pln">active </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">1</span><span class="pun">&gt;;</span><span class="pln">  </span><span class="com">/* Active high */</span><span class="pln">
						pclk</span><span class="pun">-</span><span class="pln">sample </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">1</span><span class="pun">&gt;;</span><span class="pln">  </span><span class="com">/* Rising */</span><span class="pln">
					</span><span class="pun">};</span><span class="pln">
				</span><span class="pun">};</span><span class="pln">
			</span><span class="pun">};</span><span class="pln">
		</span><span class="pun">};</span><span class="pln">
	</span><span class="pun">};</span><span class="pln">
	
	fragment@2 </span><span class="pun">{</span><span class="pln">
		target </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;&amp;</span><span class="pln">csi</span><span class="pun">&gt;;</span><span class="pln">
		__overlay__ </span><span class="pun">{</span><span class="pln">
			status </span><span class="pun">=</span><span class="pln"> </span><span class="str">"okay"</span><span class="pun">;</span><span class="pln">
			
			port </span><span class="pun">{</span><span class="pln">
				csi_ep</span><span class="pun">:</span><span class="pln"> endpoint </span><span class="pun">{</span><span class="pln">
					remote</span><span class="pun">-</span><span class="pln">endpoint </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;&amp;</span><span class="pln">ov5640_ep</span><span class="pun">&gt;;</span><span class="pln">
					bus</span><span class="pun">-</span><span class="pln">width </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">8</span><span class="pun">&gt;;</span><span class="pln">
					hsync</span><span class="pun">-</span><span class="pln">active </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">1</span><span class="pun">&gt;;</span><span class="pln"> </span><span class="com">/* Active high */</span><span class="pln">
					vsync</span><span class="pun">-</span><span class="pln">active </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">0</span><span class="pun">&gt;;</span><span class="pln"> </span><span class="com">/* Active low */</span><span class="pln">
					data</span><span class="pun">-</span><span class="pln">active </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">1</span><span class="pun">&gt;;</span><span class="pln">  </span><span class="com">/* Active high */</span><span class="pln">
					pclk</span><span class="pun">-</span><span class="pln">sample </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">1</span><span class="pun">&gt;;</span><span class="pln">  </span><span class="com">/* Rising */</span><span class="pln">
				</span><span class="pun">};</span><span class="pln">
			</span><span class="pun">};</span><span class="pln">
		</span><span class="pun">};</span><span class="pln">
	</span><span class="pun">};</span><span class="pln">
</span><span class="pun">};</span></pre>

<p>
	So the line 27, which seem to trigger the error is: `clocks = &lt;&amp;ccu CLK_CSI_MCLK&gt;;`
</p>

<p>
	 
</p>

<p>
	Also, according to the documentation, the regulator fields are required but this board does not have much regulators (like AXP209), so I have no idea what to write here.
</p>

<p>
	 
</p>

<p>
	But this is my first time writing a device-tree overlay so I am not sure what is wrong with this line.
</p>

<p>
	 
</p>

<p>
	Could someone guide me to get my overlay right?
</p>

<p>
	 
</p>

<p>
	And, does anyone already got the CSI interface working with OV5460 sensor on a H3 based board?
</p>

<p>
	 
</p>

<p>
	Thank you.
</p>
]]></description><guid isPermaLink="false">13238</guid><pubDate>Mon, 02 Mar 2020 23:55:22 +0000</pubDate></item><item><title>OV5640 camera on OrangePiOne</title><link>https://testforum.armbian.com/topic/33455-ov5640-camera-on-orangepione/</link><description><![CDATA[<p>
	Hi all,
</p>

<p>
	 
</p>

<p>
	I am trying to get an OV5640 camera working on the orangePiOne. I found this thread
</p>
<iframe allowfullscreen="" data-controller="core.front.core.autosizeiframe" data-embedauthorid="740" data-embedcontent="" data-embedid="embed812767742" src="https://testforum.armbian.com/topic/13238-ov5640-device-tree-overlay-for-orangepi-one-h3/page/2/?do=embed&amp;comment=120983&amp;embedComment=120983&amp;embedDo=findComment#comment-120983" style="height:357px;max-width:502px;" loading="lazy"></iframe>

<p>
	and was wondering if the overlay (or some overlay) is still required.
</p>

<p>
	Without anything extra, the camera is not detected. It says that sun6i-csi and ov5640 kernel modules should be loaded, so I loaded them manually with modprobe but nothing happens and nothing is shown in dmesg.
</p>

<p>
	Adding the mentioned overlay with  "sudo armbian-add-overlay csi-ov5640.<abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr>" just gives me an error in dmesg at reboot time
</p>

<p>
	"failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND
</p>

<p>
	Error applying DT overlays, restoring original DT"
</p>

<p>
	 
</p>

<p>
	uname -a
</p>

<p>
	Linux orangepione2 6.1.63-current-sunxi #1 SMP Mon Nov 20 10:52:19 UTC 2023 armv7l GNU/Linux
</p>

<p>
	 
</p>

<p>
	boot logs on <a href="https://paste.armbian.com/unoqesepov" rel="external nofollow">https://paste.armbian.com/unoqesepov</a>
</p>

<p>
	 
</p>

<p>
	wondering what to try next...
</p>
]]></description><guid isPermaLink="false">33455</guid><pubDate>Fri, 26 Jan 2024 18:05:24 +0000</pubDate></item><item><title>OrangePi One usb OTG no power in host mode</title><link>https://testforum.armbian.com/topic/33137-orangepi-one-usb-otg-no-power-in-host-mode/</link><description><![CDATA[<p>
	a device hooked up on the microusb OTG port does not power up anymore (webcam, used to work a long time ago then I did system update but did not configure the webcam again, until now...)
</p>

<p>
	 
</p>

<p>
	bruno@orangepione:~$ sudo cat /sys/kernel/debug/<abbr title="General purpose input/output">gpio</abbr><br />
	[sudo] password for bruno:<br />
	gpiochip0: GPIOs 0-223, parent: platform/1c20800.pinctrl, 1c20800.pinctrl:<br />
	 <abbr title="General purpose input/output">gpio</abbr>-15  (                    |orangepi:red:status ) out lo<br />
	 <abbr title="General purpose input/output">gpio</abbr>-166 (                    |cd                  ) in  lo ACTIVE LOW<br />
	 <abbr title="General purpose input/output">gpio</abbr>-204 (                    |usb0_id_det         ) in  lo IRQ
</p>

<p>
	gpiochip1: GPIOs 352-383, parent: platform/1f02c00.pinctrl, 1f02c00.pinctrl:<br />
	 <abbr title="General purpose input/output">gpio</abbr>-354 (                    |usb0-vbus           ) out lo<br />
	 <abbr title="General purpose input/output">gpio</abbr>-355 (                    |sw4                 ) in  hi IRQ ACTIVE LOW<br />
	 <abbr title="General purpose input/output">gpio</abbr>-358 (                    |vdd-cpux            ) out hi<br />
	 <abbr title="General purpose input/output">gpio</abbr>-362 (                    |orangepi:green:pwr  ) out hi<br />
	 
</p>

<p>
	Looks like no power on usb0, which should be enabled in host mode
</p>

<p>
	I enabled in armbian-config hardware configuration usbhost 0 to 4 (shows in armbianEnv.txt )
</p>

<p>
	I edited sun8i-h3-orangepi-one.<abbr title="Device tree blob">dtb</abbr> so that usb0 dr_mode is set to "host" (like shown here <a href="https://testforum.armbian.com/topic/4814-orange-pi-one-usb-otg/?do=findComment&amp;comment=44756" rel="">https://forum.armbian.com/topic/4814-orange-pi-one-usb-otg/?do=findComment&amp;comment=44756</a> )
</p>

<p>
	I perused this thread <a href="https://testforum.armbian.com/topic/8686-orange-pi-lite-using-micro-usb-otg-as-host-for-usb-camera/" rel="">https://forum.armbian.com/topic/8686-orange-pi-lite-using-micro-usb-otg-as-host-for-usb-camera/</a> and verified handles and setting seem to match.
</p>

<p>
	 
</p>

<p>
	Seems no matter what, usb0 is not powered. 
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	What am I missing ?
</p>

<p>
	Any help greatly appreciated...
</p>

<p>
	 
</p>
<p>
<a class="ipsAttachLink" href="https://testforum.armbian.com/applications/core/interface/file/attachment.php?id=11585&amp;key=b5583493d1a10c343c312e94ec54b3bf" data-fileExt='dtb' data-fileid='11585' data-filekey='b5583493d1a10c343c312e94ec54b3bf'>sun8i-h3-orangepi-one.dtb</a> 
<a class="ipsAttachLink" href="https://testforum.armbian.com/applications/core/interface/file/attachment.php?id=11586&amp;key=fe4f9ff1ef28961915eb9637b63b90e1" data-fileExt='dts' data-fileid='11586' data-filekey='fe4f9ff1ef28961915eb9637b63b90e1'>sun8i-h3-orangepi-one.dts</a></p>]]></description><guid isPermaLink="false">33137</guid><pubDate>Tue, 09 Jan 2024 10:43:25 +0000</pubDate></item><item><title>No Touch Response</title><link>https://testforum.armbian.com/topic/30769-no-touch-response/</link><description><![CDATA[<p>
	Hi everyone I just want to ask a question, Im using Miktver 7 inch HDMI touch screen lcd and Orange Pi one. The hdmi port and touch port connects fine to the orange pi one but the touchscreen not responding, but when I connect the Miktver to my laptop the touchscreen is responding. My question is what should I do to have touchscreen response to the orange pi one? Th<span>e OS that i use is android 4.4.2</span>
</p>

<p><a href="https://testforum.armbian.com/uploads/monthly_2023_10/Screenshot_2023-10-15-00-04-03-726_com_miui.gallery.jpg.3023035bd85a6d7c4f8688d772e09016.jpg" class="ipsAttachLink ipsAttachLink_image"><img data-fileid="11160" src="https://testforum.armbian.com/uploads/monthly_2023_10/Screenshot_2023-10-15-00-04-03-726_com_miui.gallery.thumb.jpg.15785fa30a9da46483fd6d6b43414829.jpg" width="347" class="ipsImage ipsImage_thumbnailed" alt="Screenshot_2023-10-15-00-04-03-726_com.miui.gallery.jpg" loading="lazy" height="749.52"></a></p>]]></description><guid isPermaLink="false">30769</guid><pubDate>Sat, 14 Oct 2023 16:04:48 +0000</pubDate></item><item><title>Solution: Orange Pi One i2s Overlay for PCM 5102 DAC</title><link>https://testforum.armbian.com/topic/29363-solution-orange-pi-one-i2s-overlay-for-pcm-5102-dac/</link><description><![CDATA[<p>
	Hey,
</p>

<p>
	 
</p>

<p>
	in lieu of a better place on the internet, I just wanted to document that the i2s overlay found here: <a href="https://gist.github.com/zuigon/65bfb73bb8a3f971774f80d3e2954adb" rel="external nofollow">https://gist.github.com/zuigon/65bfb73bb8a3f971774f80d3e2954adb</a> works flawlessly with Armbian 23.08.0-trunk Bookworm with bleeding edge Linux 6.4.2-sunxi.
</p>

<p>
	 
</p>

<p>
	after executing the script my PCM 5102 DAC works like a charm.
</p>
]]></description><guid isPermaLink="false">29363</guid><pubDate>Sun, 23 Jul 2023 15:50:09 +0000</pubDate></item><item><title>Headers compilation error</title><link>https://testforum.armbian.com/topic/27102-headers-compilation-error/</link><description><![CDATA[<p>
	With new python based build system there is error compiling headers while installing headers deb.
</p>

<p>
	Im not sure is it because of new build system or the problem is in 6.1.15 kernel branch.
</p>

<p>
	 
</p>

<p>
	My compile command was:
</p>

<p>
	./compile.sh BOARD=orangepione BRANCH=current BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=yes KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,img SKIP_EXTERNAL_TOOLCHAINS=no BUILD_KSRC=no PRIVATE_CCACHE=yes RELEASE=bionic ARTIFACT_IGNORE_CACHE=yes BUILD_KSRC=yes KERNEL_GIT=full
</p>

<p>
	 
</p>

<p>
	While installing i got:
</p>

<p>
	igor@honeypot:~/trash/debs$ ls -1<br />
	armbian-config_23.05.0-trunk_all.deb<br />
	armbian-firmware_1-SA56ad-Bf566_all.deb<br />
	linux-<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-current-sunxi_6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8_armhf.deb<br />
	linux-headers-current-sunxi_6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8_armhf.deb<br />
	linux-image-current-sunxi_6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8_armhf.deb<br />
	linux-u-boot-orangepione-current_2022.07-Se092-P12e0-Be261_armhf.deb<br />
	igor@honeypot:~/trash/debs$ sudo dpkg -i *<br />
	[sudo] password for igor:             <br />
	(Reading database ... 107907 files and directories currently installed.)<br />
	Preparing to unpack armbian-config_23.05.0-trunk_all.deb ...<br />
	Unpacking armbian-config (23.05.0-trunk) over (23.02.0-82) ...<br />
	dpkg: warning: downgrading armbian-firmware from 23.02.0-82 to 1-SA56ad-Bf566<br />
	Preparing to unpack armbian-firmware_1-SA56ad-Bf566_all.deb ...<br />
	Unpacking armbian-firmware (1-SA56ad-Bf566) over (23.02.0-82) ...<br />
	dpkg: warning: downgrading linux-<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-current-sunxi from 23.02.0-82 to 6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8<br />
	Preparing to unpack linux-<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-current-sunxi_6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8_armhf.deb ...<br />
	Armbian 'linux-<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-current-sunxi' for '6.1.15-sunxi': 'preinst' starting.<br />
	+ rm -rf /boot/<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr><br />
	+ rm -rf /boot/<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-6.1.15-sunxi<br />
	+ set +x<br />
	Armbian 'linux-<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-current-sunxi' for '6.1.15-sunxi': 'preinst' finishing.<br />
	Unpacking linux-<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-current-sunxi (6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8) over (23.02.0-82) ...<br />
	dpkg: warning: downgrading linux-headers-current-sunxi from 23.02.0-82 to 6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8<br />
	Preparing to unpack linux-headers-current-sunxi_6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8_armhf.deb ...<br />
	Armbian 'linux-headers-current-sunxi' for '6.1.15-sunxi': 'preinst' starting.<br />
	+ [[ -d /usr/src/linux-headers-6.1.15-sunxi ]]<br />
	+ set +x<br />
	Armbian 'linux-headers-current-sunxi' for '6.1.15-sunxi': 'preinst' finishing.<br />
	Unpacking linux-headers-current-sunxi (6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8) over (23.02.0-82) ...<br />
	dpkg: warning: downgrading linux-image-current-sunxi from 23.02.0-82 to 6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8<br />
	Preparing to unpack linux-image-current-sunxi_6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8_armhf.deb ...<br />
	Armbian 'linux-image-current-sunxi' for '6.1.15-sunxi': 'preinst' starting.<br />
	+ export 'DEB_MAINT_PARAMS=upgrade 23.02.0-82 6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8'<br />
	+ DEB_MAINT_PARAMS='upgrade 23.02.0-82 6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8'<br />
	+ export INITRD=Yes<br />
	+ INITRD=Yes<br />
	+ test -d /etc/kernel/preinst.d<br />
	+ run-parts --arg=6.1.15-sunxi --arg=/boot/vmlinuz-6.1.15-sunxi /etc/kernel/preinst.d<br />
	update-initramfs: Deleting /boot/initrd.img-5.15.93-sunxi<br />
	Removing obsolete file uInitrd-5.15.93-sunxi<br />
	+ mountpoint -q /boot<br />
	+ set +x<br />
	Armbian 'linux-image-current-sunxi' for '6.1.15-sunxi': 'preinst' finishing.<br />
	Unpacking linux-image-current-sunxi (6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8) over (23.02.0-82) ...<br />
	Preparing to unpack linux-u-boot-orangepione-current_2022.07-Se092-P12e0-Be261_armhf.deb ...<br />
	Unpacking linux-u-boot-orangepione-current (2022.07-Se092-P12e0-Be261) over (23.02.0-82) ...<br />
	Setting up armbian-config (23.05.0-trunk) ...<br />
	Setting up armbian-firmware (1-SA56ad-Bf566) ...<br />
	Setting up linux-<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-current-sunxi (6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8) ...<br />
	Armbian 'linux-<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-current-sunxi' for '6.1.15-sunxi': 'postinst' starting.<br />
	+ cd /boot<br />
	+ ln -sfT <abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-6.1.15-sunxi <abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr><br />
	+ set +x<br />
	Armbian 'linux-<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-current-sunxi' for '6.1.15-sunxi': 'postinst' finishing.<br />
	Setting up linux-headers-current-sunxi (6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8) ...<br />
	Armbian 'linux-headers-current-sunxi' for '6.1.15-sunxi': 'postinst' starting.<br />
	+ cd /usr/src/linux-headers-6.1.15-sunxi<br />
	++ grep -c processor /proc/cpuinfo<br />
	+ NCPU=4<br />
	+ echo 'Compiling kernel-headers tools (6.1.15-sunxi) using 4 CPUs - please wait ...'<br />
	Compiling kernel-headers tools (6.1.15-sunxi) using 4 CPUs - please wait ...<br />
	+ yes ''<br />
	+ make ARCH=arm oldconfig<br />
	  HOSTCC  scripts/basic/fixdep<br />
	  HOSTCC  scripts/kconfig/conf.o<br />
	  HOSTCC  scripts/kconfig/confdata.o<br />
	  HOSTCC  scripts/kconfig/expr.o<br />
	  LEX     scripts/kconfig/lexer.lex.c<br />
	  YACC    scripts/kconfig/parser.tab.[ch]<br />
	  HOSTCC  scripts/kconfig/lexer.lex.o<br />
	  HOSTCC  scripts/kconfig/menu.o<br />
	  HOSTCC  scripts/kconfig/parser.tab.o<br />
	  HOSTCC  scripts/kconfig/preprocess.o<br />
	  HOSTCC  scripts/kconfig/symbol.o<br />
	  HOSTCC  scripts/kconfig/util.o<br />
	  HOSTLD  scripts/kconfig/conf<br />
	#<br />
	# configuration written to .config<br />
	#<br />
	+ make ARCH=arm -j4 scripts<br />
	  SYNC    include/config/auto.conf.cmd<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/flattree.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/fstree.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/data.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/livetree.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/treesource.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/srcpos.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/checks.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/util.o<br />
	  LEX     scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>-lexer.lex.c<br />
	  YACC    scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>-parser.tab.[ch]<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/libfdt/fdt.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/libfdt/fdt_ro.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/libfdt/fdt_wip.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/libfdt/fdt_sw.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/libfdt/fdt_rw.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/libfdt/fdt_strerror.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/libfdt/fdt_empty_tree.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/libfdt/fdt_addresses.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/libfdt/fdt_overlay.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/fdtoverlay.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>-lexer.lex.o<br />
	  HOSTCC  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>-parser.tab.o<br />
	  HOSTLD  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/fdtoverlay<br />
	  HOSTLD  scripts/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr>/<abbr title="Device tree compiler"><abbr title="Device tree compiler">dtc</abbr></abbr><br />
	  HOSTCC  scripts/bin2c<br />
	  HOSTCC  scripts/kallsyms<br />
	  HOSTCC  scripts/recordmcount<br />
	  HOSTCC  scripts/selinux/genheaders/genheaders<br />
	  HOSTCC  scripts/selinux/mdp/mdp<br />
	  HOSTCC  scripts/sorttable<br />
	  HOSTCC  scripts/asn1_compiler<br />
	  HOSTCC  scripts/insert-sys-cert<br />
	+ make ARCH=arm -j4 M=scripts/mod/<br />
	  CC      scripts/mod/empty.o<br />
	  HOSTCC  scripts/mod/mk_elfconfig<br />
	  CC      scripts/mod/devicetable-offsets.s<br />
	  UPD     scripts/mod/devicetable-offsets.h<br />
	  MKELF   scripts/mod/elfconfig.h<br />
	  HOSTCC  scripts/mod/modpost.o<br />
	  HOSTCC  scripts/mod/sumversion.o<br />
	  HOSTCC  scripts/mod/file2alias.o<br />
	  HOSTLD  scripts/mod/modpost<br />
	  MODPOST scripts/mod/Module.symvers<br />
	+ make ARCH=arm -j4 tools/objtool<br />
	  DESCEND objtool<br />
	  HOSTCC  /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/fixdep.o<br />
	  HOSTLD  /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/fixdep-in.o<br />
	  LINK    /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/fixdep<br />
	  CC      /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/weak.o<br />
	  CC      /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/check.o<br />
	  MKDIR   /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/arch/arm/<br />
	  LD      /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/arch/arm/objtool-in.o<br />
	  CC      /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/special.o<br />
	  CC      /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/exec-cmd.o<br />
	check.c:11:10: fatal error: arch/elf.h: No such file or directory<br />
	   11 | #include &lt;arch/elf.h&gt;<br />
	      |          ^~~~~~~~~~~~<br />
	compilation terminated.<br />
	make[3]: *** [/usr/src/linux-headers-6.1.15-sunxi/tools/build/Makefile.build:97: /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/check.o] Error 1<br />
	make[3]: *** Waiting for unfinished jobs....<br />
	special.c:14:10: fatal error: arch/special.h: No such file or directory<br />
	   14 | #include &lt;arch/special.h&gt;<br />
	      |          ^~~~~~~~~~~~~~~~<br />
	compilation terminated.<br />
	  CC      /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/help.o<br />
	make[3]: *** [/usr/src/linux-headers-6.1.15-sunxi/tools/build/Makefile.build:97: /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/special.o] Error 1<br />
	  CC      /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/pager.o<br />
	make[2]: *** [Makefile:54: /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/objtool-in.o] Error 2<br />
	make[2]: *** Waiting for unfinished jobs....<br />
	  CC      /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/parse-options.o<br />
	  CC      /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/run-command.o<br />
	  CC      /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/sigchain.o<br />
	  CC      /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/subcmd-config.o<br />
	  LD      /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/libsubcmd-in.o<br />
	  AR      /usr/src/linux-headers-6.1.15-sunxi/tools/objtool/libsubcmd.a<br />
	make[1]: *** [Makefile:73: objtool] Error 2<br />
	make: *** [Makefile:1437: tools/objtool] Error 2<br />
	dpkg: error processing package linux-headers-current-sunxi (--install):<br />
	 installed linux-headers-current-sunxi package post-installation script subprocess returned error exit status 2<br />
	Setting up linux-image-current-sunxi (6.1.15-S4261-D4dc8-Pd2ed-C54bbHfe66-Bd6b8) ...<br />
	Armbian 'linux-image-current-sunxi' for '6.1.15-sunxi': 'postinst' starting.<br />
	+ export 'DEB_MAINT_PARAMS=configure 23.02.0-82'<br />
	+ DEB_MAINT_PARAMS='configure 23.02.0-82'<br />
	+ export INITRD=Yes<br />
	+ INITRD=Yes<br />
	+ test -d /etc/kernel/postinst.d<br />
	+ run-parts --arg=6.1.15-sunxi --arg=/boot/vmlinuz-6.1.15-sunxi /etc/kernel/postinst.d<br />
	update-initramfs: Generating /boot/initrd.img-6.1.15-sunxi<br />
	update-initramfs: Converting to u-boot format<br />
	+ echo 'Armbian: update last-installed kernel symlink to '\''zImage'\''...'<br />
	Armbian: update last-installed kernel symlink to 'zImage'...<br />
	+ ln -sfv vmlinuz-6.1.15-sunxi /boot/zImage<br />
	'/boot/zImage' -&gt; 'vmlinuz-6.1.15-sunxi'<br />
	+ touch /boot/.next<br />
	+ set +x<br />
	Armbian 'linux-image-current-sunxi' for '6.1.15-sunxi': 'postinst' finishing.<br />
	Setting up linux-u-boot-orangepione-current (2022.07-Se092-P12e0-Be261) ...<br />
	Errors were encountered while processing:<br />
	 linux-headers-current-sunxi
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">27102</guid><pubDate>Fri, 10 Mar 2023 16:58:57 +0000</pubDate></item><item><title>awus036acm wireless adapter not working</title><link>https://testforum.armbian.com/topic/25019-awus036acm-wireless-adapter-not-working/</link><description><![CDATA[<p>
	i have a alfa awus036acm wireless adapter install on my orange pi one with armbian jammy installed. 
</p>

<p>
	my awus036acm adapter is not recognised , when i type iwconfig it's say no wireless extension
</p>

<p>
	 
</p>

<p>
	is there possible way to make it wo<abbr title="Rockchip"><abbr title="Rockchip">rk</abbr></abbr>?
</p>
]]></description><guid isPermaLink="false">25019</guid><pubDate>Thu, 15 Dec 2022 02:21:52 +0000</pubDate></item></channel></rss>
