[[559] - GPIO Support for H2/H3 boards with a unified WiringPI library in a neat little package]

Personally, I prefer python. But C libs can be usefull when speed is needed. Sysfs should be already handled by kernels.

[[559] - GPIO Support for H2/H3 boards with a unified WiringPI library in a neat little package]

Yes, RPi.GPIO is coming from RaspberryPi community, I'm using the RPi.GPIO-PineA64 derivative since it is already as most pins there, I've submit a PR yesterday to add SPI/I2C borrowed from Olimex pyA20 to this pineA64 derivative, original Pi version still don't support those yet.

 

On H3, I prefer using the orangepi_PC_gpio_pyH3 since it is a derivative directly from Olimex pyA20 : https://github.com/duxingkei33/orangepi_PC_gpio_pyH3

[Orange Pi Zero went to the market]

Yes, I've read the irclog you've provided.

I don't know why it should not have been done that way in first place.

Something Mainline gurus are taking shortcuts ... ;-)

[Orange pi pc plus Armbian unable to boot from emmc]

Did you verify the rootfs in /boot/boot.cmd and /etc/fstab ?

If those are perfect, then, you will need to hook some USB-TTL Serial on Debug port and provide us the boot log output.

[Shrink boot partition on SD card]

Right ! This method could also be used when you wish to re-install a small image on smaller SDCard.

[Shrink boot partition on SD card]

Here is how to shrink an existing image.

In "gparted", do "edit/resize" of the partition, but leave a certain percentage of free space, then "Apply".

Replace the "endsect" by the actual number shown by fdisk.

sudo modprobe loop
sudo losetup -f
sudo losetup /dev/loop0 myimage.img
sudo partprobe /dev/loop0
sudo gparted /dev/loop0
sudo losetup -d /dev/loop0
fdisk -l myimage.img
truncate --size=$[(endsect+1)*512] myimage.img

[Orange pi pc plus Armbian unable to boot from emmc]

Yes, indeed, my previous post could help.

Check also the root partition in /boot/boot.cmd and also in /etc/fstab files located in the eMMC.

[Orange Pi Zero went to the market]

No, he did a lot more work that Icenowy has not done yet. Many empty stubs were still there in her branch.

https://github.com/Icenowy/xradio/compare/master...fifteenhex:master

 

For the MAC, he merged a commit from her :

https://github.com/fifteenhex/xradio/commit/911c488ebab45d075215ae4967044134df358ad7

[Orange Pi Zero went to the market]

Hoping that fifteenhex will send a PR to Icenowy for his work.

[Orange Pi Zero went to the market]

It seems that Icenowy is working to port the XRadio WiFi driver into mainline. Not ready yet, but should be there soon.

 

https://github.com/Icenowy/xradio

[NanoPI NEO / AIR]

 

(alphabet - 1) * 31 + pin no.  = A3 = (0-1)*31+3 = 3

This is not true !

it should be calculated as :

(alphabet - 'A') * 32 + pin no.  = A3 = (0)*32 + 3 = 3

And for PG11 :

(alphabet - 'A') * 32 + pin no.  = A3 = (6)*32 + 11 = 203

[Orange PI PC+ eMMC wont boot]

Yes, this is true for all Soc from AllWinner.

[port forwarding does NOT work]

If you OPi doesn't act as a router between 2 ethernet ports, there is no reason to add port forwarding on the OPi.

If the OPi is inside your network and works perfectly from inside, then your issue is really on your external router.

[[397] - maintain/fix DTS entries for some devices such I2C/SPI/W1]

 

dtc: invalid option -- '@'

This means that you have the stock version of DTC which is unaware of overlays, not the one which understand overlays.

You can get the good one, version DTC 1.4.1-g47216cdb, from :

 https://github.com/pantoniou/dtc.git

and choose the proper branch :

dt-overlays5

[[397] - maintain/fix DTS entries for some devices such I2C/SPI/W1]

Yes, if you do the change directly into the main DTS, only "okay" should be required.

 

For overlay, your issue is probably that you didn't use "-@" option of DTC, the command line should be :

 

dtc -@ -I dts -O dtb -o i2c-enable.dtb i2c-enable.dts

[Orange Pi PC+ Vanilla Kernel Image]

That is probably a completely different issue...

[Armbian running on Pine64 (and other A64/H5 devices)]

I have M64 which has similar Gbe issue as Pine64 if not the exact same issue, unfortunately this possible fix did not work on M64.

 

Oh ! this is bad news !

So, maybe it won't work for Pine64 too ...

[Refactoring for Dev 4.8.x broken]

Yes, those "Unable to handle kernel NULL pointer dereference at virtual address" is what I've seen.

 

For now, I've switched to 4.9.x, and have updated all my H3 boards.

[Armbian running on Pine64 (and other A64/H5 devices)]

BTW, it seems that the GMAC issue on PineA64 has been narrowed and that a fix has been provided :

 

http://forum.pine64.org/showthread.php?tid=293&pid=21791#pid21791

https://github.com/longsleep/linux-pine64/compare/pine64-hacks-1.2-gmactxonly

[Orange Pi PC+ Vanilla Kernel Image]

BTW, this "{ .compatible = "spidev" },  //TCM:FIX " is only a workaround to avoid the warning "buggy DT: spidev listed directly in DT" been display in dmesg.

Not having this patch would still load the DT, since it is only a warning. There was a lot of discussion between kernel developpers about this message.

The fix you proposed have been discussed as well, and it has been rejected months ago ...

I presume this warning check will eventually be refactored : https://patchwork.kernel.org/patch/9201131/

For the patch, I doubt it will fix the issue I'm facing, since it is only handling FIFO size, but I will give it a try.

 

EDIT : For SPI issue, I don't have it on OPiPlus2E neither than OPiPC, it is working properly. So, something probably went wrong with my OPiPCPlus, which I didn't found yet.

[Orange Pi PC+ Vanilla Kernel Image]

Yes, since the 4.8.x is completely broken under H3 (I still not understand why), I've switched to sun8i-emac-wip-v5 branch too.

Now, I'm struggling to make SPI work again, I've fixed the DT, but I get "SPI transfer failed" during tests. It was working fine in 4.7.6 ...

[Can't auto mount in fstab at Orange Pi PC]

Again, provide your /etc/fstab, otherwise we can't point you at the syntax error.

Also, tell us which Armbian version are you using.

[Refactoring for Dev 4.8.x broken]

I've decided to give a try by building new image with the refactoring of 4.8.x.

 

So the image I've done is Armbian_5.21_Orangepipcplus_Debian_jessie_4.8.3.img

I placed it on sdcard and look at the boot using serial debug.

 

Unfortunately, the 4.8.3 Kernel is broken and get stuck the this last line ...

 

 

 

 

U-Boot 2016.09-armbian (Oct 20 2016 - 12:18:44 -0400) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi PC
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   phy interface0
eth0: ethernet@1c30000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
1774 bytes read in 197 ms (8.8 KiB/s)
## Executing script at 43100000
114 bytes read in 167 ms (0 Bytes/s)
3983564 bytes read in 411 ms (9.2 MiB/s)
5888608 bytes read in 570 ms (9.9 MiB/s)
0 bytes read in 137 ms (0 Bytes/s)
23462 bytes read in 1126 ms (19.5 KiB/s)
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    3983500 Bytes = 3.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
   Loading Ramdisk to 49c33000, end 49fff88c ... OK
   Loading Device Tree to 49c2a000, end 49c32ba5 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Loading, please wait...
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.25.2
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: clean, 56600/81440 files, 229999/325632 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Debian GNU/Linux 8 (jessie)!

         Expecting device dev-ttyS0.device...
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Paths.
[  OK  ] Set up automount Arbitrary Executable File Formats F...utomount Point.
[  OK  ] Reached target Encrypted Volumes.
[  OK  ] Reached target Swap.
[  OK  ] Created slice Root Slice.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Listening on Delayed Shutdown Socket.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on udev Control Socket.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Listening on Journal Socket.
[  OK  ] Created slice System Slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Created slice system-getty.slice.
         Starting Increase datagram queue length...
         Starting Restore / save the current clock...
         Starting udev Coldplug all Devices...
         Starting Create list of required static device nodes...rrent kernel...
         Starting Load Kernel Modules...
         Mounting Debug File System...
         Mounting POSIX Message Queue File System...
         Starting LSB: Set keymap...
[  OK  ] Reached target Slices.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Debug File System.
[  OK  ] Started Increase datagram queue length.
[  OK  ] Started Restore / save the current clock.
[  OK  ] Started Create list of required static device nodes ...current kernel.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started LSB: Set keymap.
[  OK  ] Started udev Coldplug all Devices.
         Mounting FUSE Control File System...
         Mounting Configuration File System...
         Starting Apply Kernel Variables...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Listening on Syslog Socket.
         Starting Journal Service...
[  OK  ] Started Journal Service.
[  OK  ] Mounted Configuration File System.
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started Create Static Device Nodes in /dev.
         Starting udev Kernel Device Manager...
[  OK  ] Started udev Kernel Device Manager.
         Starting Copy rules generated while the root was ro...
         Starting LSB: Set preliminary keymap...
         Starting LSB: Tune IDE hard disks...
[  OK  ] Started Copy rules generated while the root was ro.

 

 

EDIT : Trying to boot it again, it produce sometimes core dumps just after the that last line, starting with :

Unable to handle kernel NULL pointer dereference at virtual address 00000001

EDIT 2 : Oh ? After several boots, it finally get thru ... Could it be DRAM settings ?

 

EDIT 3 : I've build also a Armbian_5.21_Orangepipc_Debian_jessie_4.8.3.img, and unfortunately, it is doing the same ...

[FEL mass storage or writing images directly to eMMC]

I've played a bit with MTD/UBIFS on my Olimex-Micro-A20, it works well.

But I didn't get chance to try building U-Boot with MTD/UBIFS yet ...

[General pointers for compatibility of Rpi code on Opi?]

The python library from https://github.com/duxingkei33/orangepi_PC_gpio_pyH3 is supporting I2C as well as SPI, along with plain GPIOs.