[Orange Pi Plus 2E Won't boot Armbian]

Not having a USB-TTL to do debugging is like a carpenter not having any hammer ...

[Orange Pi Win]

@Igor, can you confirm with Steven that PL9 is really on pin 16 of the header ? It doesn't work and since the PDF is named ORANGEPI-Winplus-V1_3.pdf and not ORANGEPI-Win-V1_x.pdf, i suspect some discrepancies ...

Same thing with ORANGEPI-Prime_V1_0.pdf, the STATUS-LED doesn't light up when bring PA15 to HIGH.

And if I remember this is the same issue with ORANGE_PI-PC2-V1_2_schematic.pdf, the STATUS-LED doesn't light up when bring PA15 to HIGH !

Steven should make sure that his schematics are reflecting the reality !!!

 

EDIT : Ok ! I found the discrepancies. In top area of the schematic, it says PA15 = STATUS-LED, but on the CPU pins , it is PA20. Same thing for PC2.

[kernel 4.11-rc7]

The errors with "scripts/dtc/livetree.c" is related to the fact that "scripts-dtc-Update-to-version-with-overlay.patch" failed.

 

[Orange Pi Win]

@Igor, thanks for confirmation !

I will continue digging ...

 

[OPi Win with A64]

Don't expect such feature like LCD interface to be in working state.

A week ago, none of the contributors had any OPiWin to work with.

The current build is booting, eth0 is working, but no WiFi yet.

 

[Orange Pi Win]

On another subject, since this is a new build target only since few days, my recent works as to get R_PIO working on OPiWin to allows getting the WiFi AP6212 working soon.

Unfortunately, I didn't get expected success yet.

R_PIO seems to be properly initialized, but neither wifi_en_pin@0 (PL8) or manual sysfs PL9 on header doesn't work.

 

The sad thin is that the sames R_PIO patches works well on Pine64 where I've been able to blink PL7 LED.

 

That make me think that the schematic we got ORANGEPI-Winplus-V1_3.pdf maybe not matching the real hardware, the "plus" maybe means "another" board, not yet available.

@Igor  could you confirm  with Steven ? There many other schematics that never been published yet, that should be updated ...

 

 

[Orange Pi Win]

Note that most of the above are warning for the HDMI driver, you shouldn't care to much about them.

The real error you faced is :

ERROR: Couldn't open "config.its"

And that reveal to me that I forgot to commit 1 files during my initial commit few days ago :  missing blobs/sun50i_a64_opiwin.its added.

I've just committed it now ...

( @zador.blood.stained, in fact, this forgotten file should be directly in your u-boot proxy repository, but I presume I can't commit it there directly, so, in the mean time, I've done it inside a patch)

 

 

[orangepi-one MAC address]

I maybe wrong, but I remember that several months ago, I was able to over-write it.

But then, after using newer u-boot, I wasn't able, maybe a bug has been introduced elsewhere, not by Armbian.

 

[orangepi-one MAC address]

It is probably hard-coded into u-boot, and not over-writable.

 

 

[Enable 1-wire in kernel 4.9 on BananaPi]

If you can switch to newest image because you simply added tons of applications, and tweaked tons of configs, what you can do is still download newest image, plug into a SDCard reader over one of the USB, then move the old /boot into /boot-OLD and copy the one from the new image from /mnt/boot into /boot. Probably, you will also need to install newest u-boot by doing :

dd if=/usr/lib/linux-u-boot-dev-orangepipc_5.27_armhf/u-boot-sunxi-with-spl.bin of=/dev/mmcblk0 bs=1024 seek=8

The, reboot and see newest kernel, but still able to use you old applications

[second SPI interface on Orange PI - problem]

But why removing the LED PA15 from FEX becomes a pain ?

Is the MFRC522 is 3.3V or 5V ? If 5V, you will need voltage level shifters.

If you wish to keep the SPI-NOR, you can probably use a I2C-to-SPI bridge such SC18IS602, but it will be more trouble on software side.

 

[Boot OPi over network]

For flashing the SPI-NOR, you need to get "mtd-utils", either from apt-get or from sources.

You need to add in the /boot/armbianEnv.txt the following overlay :

overlays=spi-jedec-nor

Then, reboot, and check if SPI-NOR appears by doing "cat /proc/mtd". If you have mtd partitions, then install u-boot-spl using this command (check previous partitions to make sure u-boot is mtd0) :

flashcp /usr/lib/linux-u-boot-dev-orangepipc_5.27_armhf/u-boot-sunxi-with-spl.bin /dev/mtd0

Next steps are for copying your sdcard into you already inserted usb drive by using nand-sata-install. After copy finished, edit the boot.cmd from your usb drive, this means probably /mnt/boot/boot.cmd if drive mounted in /mnt.

Change all "mmc" words by "usb" and add on top of boot.cmd the line "setenv devtype usb", save it and recompile it with "mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr".

Then, shutdown the board, remove the sdcard, and re-power the board. Check the boot log using USB-TTL adaptor. If everything fine, you should get into the login prompt. Bingo !

 

 

[Orange Pi PC 1-Wire]

Unfortunately, I don't have any DS2406 to try to figure out. Maybe there is an issue with the driver itself ...

At least, you've got the DS18B20 working !

 

[Boot OPi over network]

Booting from SPI-NOR doesn't need other things than the u-boot-sunxi-with-spl.bin in the flash, which a bit less than 500K.

The kernel itself along uinitrd and dtb should be located elsewhere.

I've never try to boot in NFS or TFTP yet, but booting from USB drive just works fine.

(BTW, pushing u-boot-sunxi-with-spl.bin into flash isn't done by nand-sata-install, nand-sata-install is used to copy sdcard into other storage such USB drive or eMMC)

[Solved: Banana Pro (A20) SPI not working with mainline kernel (4.9.12)]

The fact that you are seeing spidev in lsmod doesn't mean nothing wrong occured.

Check the kernel logs with "dmesg | grep spidev"

 

[Enable 1-wire in kernel 4.9 on BananaPi]

There is also overlays provide in recent Mainline builds for A20, such /boot/dtb/overlay/sun7i-a20-w1-gpio.dtbo.

To enable it, simple edit /boot/armbianEnv.txt and add this :

overlays=w1-gpio

And then reboot.

(Note : to use such overlays, your need a recent image, not upgrades from old image)

[Orange Pi Zero, Python GPIO Library]

Because the POWER_LED is already in use by the kernel.

It is the same if you try to use it with sysfs.

echo 362 > /sys/class/gpio/export
-bash: echo: write error: Device or resource busy

The only way to free it is to edit DT and removing it from the r_pio section.

 

But the STATUS_LED is already free and available.

[Orange Pi PC 1-Wire]

In Mainline, the FEX (ie script.bin) is not used at all anymore.

It is the DTB that replace all this mechanisms.

You need to load DTB overlay for OneWire, add the following in /boot/armbianEnv.txt

overlays=sun8i-h3-w1

and then reboot ...

[second SPI interface on Orange PI - problem]

You need to remove LED from PA15 in the FEX

[Enable 1-wire in kernel 4.9 on BananaPi]

There are plenty of links on google, but here is one :

http://stackoverflow.com/questions/21670967/how-to-compile-device-tree-source-files-dts

The DTB for your board is normally located in /boot/dtb/<board_name>.dtb.

 

 

 

[How I boot my Orange Pi PC from usb?]

Bonnjour Monsieur,

It can be done, but only with Mainline along with a SPI-NOR Flash attached on SPI bus, where U-Boot SPL need to be installed.

 

[Enable 1-wire in kernel 4.9 on BananaPi]

Mainline kernel doesn't use FEX at all, it is using DeviceTree DTB.

You first need to decompile DTB into DTS and you need to add some thing like that in you DTS in PIO section :

                        w1_pins: w1_pins {
                                allwinner,pins = "PD14";
                                allwinner,function = "gpio_in"; // in (initially)
                                allwinner,pull = <0>; // off
                        };

Then, at the root level :

                        w1: onewire@0 {
                                compatible = "w1-gpio";
                                pinctrl-names = "default";
                                pinctrl-0 = <&w1_pins>;
                                gpios = <&pio 3 14 0>; // PD14
                                status = "okay";
                        };

 

[Orange Pi PC 1-Wire]

If the CONFIG_W1_SLAVE_DS2406=m was not already present in config-3.4.113-sun8i file, this means you have to compile a new kernel to get ds2406.ko modules.

Adding it to config-3.4.113-sun8i file doesn't do the job.

 

[Orange Pi PC 1-Wire]

Which kernel do you use ?

Because in Mainline, the following modules are part of the nightly builds :

CONFIG_W1_SLAVE_DS2408=m
CONFIG_W1_SLAVE_DS2406=m

 

[Orange Pi Plus 2 - GPIO pins numbering ?]

Yes, the triangle is pointing to pinNo.1

Then, you should refer to schematic for actual pin names.