zador.blood.stained

You can save the file system contents for offline access, but it's not possible to fully emulate this hardware.
 
Armbian -> Armbian dist-upgrade should work fine for new images, but it's always recommended to start from scratch to include new tweaks and configuration templates.

You have to change SD detection mode for the kernel (fex or DT) to avoid this issue.

If Lubuntu and Raspbian use legacy u-boot then most probably it ignores card detect switch (i.e. legacy u-boot on Pine64 still boots fine)
 
In u-boot and SPL for sunxi devices - no, in kernel - maybe, but card presence can still be detected by polling. But this is a question of describing hardware configuration regardless of its usefullness, so if there is a CD switch of "correct" polarity, it is assumed to work.

IMO OpenWRT is interesting if you use UCI driven configuration, i.e. for complicated firewall setup. It is a good choice or the only reasonable choice mostly if there is very little storage available - by throwing away unneeded options and heavyweight system libraries and combining read-only squashfs with overlayed jffs filesystems you can fit Linux based distribution in 4MiB onboard flash storage. DRAM at this point limits mostly what kind of heavyweight services you can use on the device.

Ok, found the issue. Apply this patch a top of previous: http://sprunge.us/KETE
 
It seems that H3 TV works without calibration, but H5 doesn't. Fortunatelly, it work with fixed value for calibration.

Hardware PWM can be enabled only on PA05 pin: https://github.com/igorpecovnik/lib/issues/498

Test results of de2_wip branch:
 
H3 / Orange Pi Plus 2e
HDMI output - works Composite output - works H5 / Orange Pi PC2
HDMI output - works Composite output - no signal, "Setting up a 720x576i composite-pal console (overscan 32x20)" is present in serial output, so the driver at least tries to enable it A64 / Pine64+
HDMI output - works, will try adding simplefb nodes to kernel DT later  
Edit: Tested simplefb on Pine64 dev - works for me. Note: On newer boards HDMI 5V power is controlled by "DC5V/BAT POWER" jumper.

MiQi added to Armbian. What I did:
 
- added kernel 4.4.50 ... took from https://github.com/mqmaker/linux-rockchip(4.4.16) ... and patch all the way up to 4.4.50. 
- added stock MiQi uboot. I tried too merge it with mainline but figured out soon that it's not going to be easy and abandoned that
- added boot scripts with environment file
- packaged kernel, u-boot, ...
- updated kernel config to meet Docker requirements 
- added proper serial console
- tested CLI and desktop build. Both runs smoothly.
Known bugs: random MAC, eMMC install script and boot script need some adjustments
 
Unknown: mali, video accleration librarires, ... etc. most likely those should go: https://github.com/mqmaker/rk-rootfs-build
 
From tomorrow morning, betas will be available here: https://dl.armbian.com/miqi/nightly/
 
armbianmonitor -u
http://sprunge.us/TWMF

Console log:
 
 

Hm. I was throwing away bags from things I have received recently and inside the bag from SoPine A64 (if I remember correctly) I found a piece of some kind of copper foil with black coating on one side (2cm x 6cm), so maybe I did get some kind of heat transferring option.

In the device tree. You need to add CPU regulator, operating points table and other DVFS and THS related entries with a patch to the DT.

Ok, but not today. I will report here when done.

Found it!!!
 
If I put this in composer init, it works!
 
u32* syscon_reg = (u32*) 0x01c00004;
clrbits_le32(syscon_reg, 1 << 24);

H3 does include RTC, but this board doesn't expose any option to use a backup battery for it. Additionally there may be a problem with RTC clock source configuration in the legacy kernel, but I don't think anybody is interested in investigating it (at least for the legacy kernel)

I think it has something to do with SMB access method and mounting of the shares. If you had some incorrect path errors, then the file manager passed raw smb:// file path to the player and not all players support that (i.e. vlc requires installing additional plugin and even with it will happily throw you an error if there are spaces in file/directory names).
 
And it was probably "fixed" when we added additional packages to desktop images - gvfs-backends and gvfs-fuse. In this case file managers that support GVFS will mount SMB share locally so any players will access the path like a local FS and will easily pick up the external subtitles.

Legacy with disabled display (for SD): u-boot-with-dtb.zip
 
Mainline with boot0 is more tricky (needs more time), will try to make it tomorrow.

Because it does't work in chroot during the build process since /run would be empty when reusing rootfs cache and services like resolvconf are not started to recreate the file.
We should alter the build process to recreate this symlink somewhere before copying files to the image.

I added experimental shutdown support for the PC2, numbers from power meter for the next nightly (12.02) are welcome.
Also please note that the only way to restart after power down is and will be the power cycle. This board doesn't have the PMIC, so it's either full shutdown or different kinds of suspend with "power button" support.

PA20 is not available on the header, it is used for controlling wireless chip power. It can only be used by soldering a wire to one of pads for resistor R69 (can be seen on the board between wireless chip and Ethernet transformer, resistor itself needs to be desoldered) and changing wireless driver configuration. 

I have pushed the fix upstream. It should be available in armbian, when new libvdpau-sunxi packages are built.
 
rellla

He means mainline u-boot SPI driver - to be able to store environment and use MTD partitions from u-boot proper.

Yes, looks like SoPine u-boot changes broke it, I'll try to fix it soon.
 
Edit: Added a workaround, removed broken files from the download server.

https://github.com/igorpecovnik/lib/blob/master/distributions.sh#L22-L29
https://github.com/igorpecovnik/lib/blob/master/config/boards/orangepizero.conf#L5

https://linux-sunxi.org/Bootable_SPI_flash
 
I don't think this needs any schematics, it's just an SPI flash with a bypass capacitor and a Write Protect jumper (optional) wired to the 2x4 2.54mm header. Wiki gives enough details on hardware implementation, and as for software - mainline u-boot can be loaded from the SPI flash, and if it fails to boot the system from SD it will try USB next (though if you have more than 1 USB storage devices attached it will need extra modifications). Armbian boot script in recent images can handle USB boot scenario well, so it works out of the box.

For the 78xx electrolytic cap should be on input and ceramic cap should be on output (as close to the regulator as possible). For all types of regulators looking at the datasheet is recommended before trying to apply a common sense - some require a ceramic cap on the output while others require electrolytic one for the stability.
In any case 78xx or any kind of linear regulator should not be used here - it will consume more power than the board itself at this voltage difference.

Will be done eventually. We already have a pretty big DT patch for this board.
 
Last time I edited the kernel config I enabled almost all Realtek wireless drivers that were available.