[Orange Pi Zero Plus 2 available]

That would be great !

 

[OrangePi PC GPIO UART and Arduino]

You've probably missed some steps about overlays.

Try manually the following steps, although not the same way as described in the above post :

mkdir /sys/kernel/config/device-tree/overlays/uart1
cat /boot/dtb/overlay/sun8i-h3-uart1.dtbo > /sys/kernel/config/device-tree/overlays/uart1/dtbo
python
import serial
port = serial.Serial("/dev/ttyS1", 115200, timeout=1)
while True:
    while serport.inWaiting() > 0:
        c = serport.read()
        print c

 

[Sending serial data using the UART on Orange Pi Zero]

Simply use python-serial.

http://pyserial.readthedocs.io/en/latest/shortintro.html

 

[Testers wanted: sunxi Device Tree overlays]

Quote

(I remember reading post by Martin where he explained there was a program to test SPI like that)

Yes, the spidev_test.c can be found on any kernel tree under tools/spi/spidev_test.c or on Linus mainline https://github.com/torvalds/linux/blob/master/tools/spi/spidev_test.c

 

[Testers wanted: sunxi Device Tree overlays]

Of course !

[Testers wanted: sunxi Device Tree overlays]

15 hours ago, zador.blood.stained said:

Changing the default pin and enabling the internal pull-up are the most interesting things to test.

Since Dallas Semiconductor strongly suggest to use 4K7 Pull-Up for OneWire bus, I wouldn't rely on weak internal Pull-Ups which one some SoC are greater than 30K, especially if there are multiple sensor on the same bus or if those have long wires.

[Orange Pi PC does not boot]

I have one of my OPiPC+ that has such trouble, it has a false contact with some of SDCard, which thickness could vary a bit, I simply added a piece of folded paper to make it thicker and false contact disappeared.

 

[Orange PI lite GPIO UBOOT problem]

I doubt that OPi Lite is reacting differently than OPiPC/PC+/One, they are using the same SoC.

Since GPIOs are left floating until been initialized as output, your relay driver circuit must take care of that unknown state using pullup or pulldown.

 

[Dual-boot Armbian + Android]

U-Boot is not currently supporting that, although maybe with new FIT functionalities developed by APritzel could bring that possible in the future.

 

[Orange Pi Lite doesn't connect to WiFi networks]

WiFi password must be between 8 and 32 characters. "True" has only 4 characters, your router should have refused that.

 

[Armbian for OrangePi PC2, AllWinner H5]

Is this firmware file present ?

[Armbian for OrangePi PC2, AllWinner H5]

The CONFIG_I2C_MUX is already present.

Maybe it requires something else ...

 

[OPi Win with A64]

Since this SPI-NOR seems to be a SOICW package, not SOIC, it must be bigger than that.

 

[The partition is not resized to full SD card size.]

No, there is no problem about using the whole space.

The issue will be present when cloning, except if the image is first backed-up on external disk bigger than the sdcard and then shrinked.

 

[Armbian for OrangePi PC2, AllWinner H5]

FDTI/CH341/PL2303 have been added for next mainline nightly build

 

[How to enable hardware SPI]

You are probably using Legacy kernel, so, in such case, take a look at Fex Guide under SPI section :

http://linux-sunxi.org/Fex_Guide

 

[Overlays in armbianEnv.txt]

You can try to edit the main DT instead and place "okay" on all I2C.

[Mac Address Assignment on Orange Zero]

I've looked into driver/of/of_net.c, and all those 3 keywords are supported : address/mac-address/local-mac-address.

I've tried it myself, and effectively it doesn't work.

This means that some bug has been introduced in last few months.

I will have to dig further by adding traces into a custom kernel build.

[Mac Address Assignment on Orange Zero]

Although I didn't verify by trying myself, in 4.10.x, it seems that the keyword is now "local-mac-address".

[Orange Pi Zero mainline 1wire devicetree]

"pio" is an alias in DTS simply pointing to "/soc/pinctrl@01c20800", looks at the __symbols__ table at the end of DTS.

Of course, for overlays, you need to use a DTC compiler that support overlays like the one from Pantoniou, and use the "-@" option : take "dt-overlays5" branch (or greater) from https://github.com/pantoniou/dtc.git

 

 

[Overlays in armbianEnv.txt]

Did you simply try to look at i2c-1 instead ?

(because if r_i2c, the one with regulator 0x65, is loaded first, it is actually the first one which get named i2c-0)

[Help wanted changing resolution of DS18B20 on Orange Pi]

Which kernel are you running ?

My above post was for 4.9.x, and I've just verify that the same code is present on 4.10.x.

 

[Overlays in armbianEnv.txt]

So, your I2C-0 is showing a device on 0x65 (with UU meaning that a kernel driver is using it), if other devices on the same bus are not shown, it is probably that you have a wiring issue.

 

[Overlays in armbianEnv.txt]

you wish to have i2c0 with /soc/i2c@01c2ac00 enabled, but you confusingly doing a "cat /proc/device-tree/soc/i2c\@01c2b400/status" which is not the same port.

Are you sure that none of the port shows up ? Did you check "dmesg" output ? Which board do you have ?

 

[Armbian for OrangePi PC2, AllWinner H5]

In older 4.9.x H5 build, the W1 drivers were there. But they have been forgotten in 4.10.x, so I've added them few minutes ago and my build is on-going.

So, you will be able to try it in next nightly builds.