guidol

Mine DID boot without a dtb.img! (but didnt with the wrong .dtb)
But I think - that I did read - that the system does try to use the right dtb by itself

Mine DID boot without a dtb.img! (but didnt with the wrong .dtb)
But I think - that I did read - that the system does try to use the right dtb by itself

WiFi is now working on GT1.   1. Download & Copy AP6255 WiFi drivers extracted from Beelink's Android image: https://dl.dropboxusercontent.com/u/11164079/GT1/wifi.tar.gz   2. Load WiFi kernel modules   2.1. Manually modprobe cfg80211 modprobe dhd firmware_path=/lib/firmware/ap6255/fw_bcm43455c0_ag.bin nvram_path=/lib/firmware/ap6255/nvram.txt 2.2. On boot
# /etc/modules cfg80211 dhd # /etc/modprobe.d/options.conf options dhd firmware_path=/lib/firmware/ap6255/fw_bcm43455c0_ag.bin nvram_path=/lib/firmware/ap6255/nvram.txt SCAN
root@amlogic-s905x:~# iwlist wlan0 scan wlan0     Scan completed :           Cell 01 - Address: XX:54:XX:FA:C8:XX                     ESSID:"SSID_NAME"                     Mode:Managed Connect to SSID with nmcli
nmcli dev wifi connect NETWORK_SSID password NETWORK_PASSWD DMESG
              dhd_bus_devreset: == WLAN ON == [  149.800463] F1 signature read @0x18000000=0x15264345 [  149.806417] F1 signature OK, socitype:0x1 chip:0x4345 rev:0x6 pkg:0x2 [  149.807102] DHD: dongle ram size is set to 819200(orig 819200) at 0x198000 [  149.807543] dhd_conf_read_config: kso_enable = 0 [  149.807633] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/ap6255/fw_bcm43455c0_ag.bin [  149.807641] dhdsdio_download_firmware: set use_rxchain 0 [  149.807647] dhdsdio_download_firmware: set txglomsize 40 [  149.807653] sdioh_set_mode: set txglom_mode to multi-desc [  149.807659] Final fw_path=/lib/firmware/ap6255/fw_bcm43455c0_ag.bin [  149.807664] Final nv_path=/lib/firmware/ap6255/nvram.txt [  149.807669] Final conf_path=/lib/firmware/ap6255/config.txt [  149.861058] NVRAM version: AP6255_NVRAM_V1.0_29052015 [  149.861683] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded. [  149.939601] dhd_bus_init: enable 0x06, ready 0x06 (waited 0us) [  149.939765] bcmsdh_oob_intr_register: Enter [  149.939769] bcmsdh_oob_intr_register: HW_OOB enabled [  149.939773] bcmsdh_oob_intr_register OOB irq=100 flags=414 [  149.939802] bcmsdh_oob_intr_register: enable_irq_wake [  149.939808] bcmsdh_oob_intr_register: enable_irq_wake failed with -6 [  149.940733] dhd_conf_set_fw_int_cmd: set WLC_SET_BAND 142 0 [  149.941361] dhd_preinit_ioctls: Set tcpack_sup_mode 0 [  149.943237] Firmware up: op_mode=0x0005, MAC=44:2c:05:4b:5b:49 [  149.943243] dhd_conf_set_country: set country ALL, revision 38 [  149.943248] dhd_conf_set_fw_string_struct_cmd: set country [  149.943581] CONFIG-ERROR) dhd_conf_set_fw_string_struct_cmd: country setting failed -2 [  149.947523] Country code: US (US/0) [  149.947863] dhd_conf_set_fw_string_cmd: set roam_off 1 [  149.949492] dhd_conf_set_fw_string_cmd: set txbf 1 [  149.949947] CONFIG-ERROR) dhd_conf_set_fw_string_cmd: txbf setting failed -23 [  149.959389] Firmware version = wl0: Aug 25 2015 18:58:57 version 7.45.69 (r581703) FWID 01-24037f6e [  149.959398]   Driver: 1.201.59.6 (r506368)                  Firmware: wl0: Aug 25 2015 18:58:57 version 7.45.69 (r581703) FWID 01-24037f6e [  149.959611] dhd_txglom_enable: enable 1 [  149.959616] dhd_conf_set_txglom_params: swtxglom=0, txglom_ext=0 [  149.959620] dhd_conf_set_txglom_params: txglom_bucket_size=0 [  149.959624] dhd_conf_set_txglom_params: txglomsize=40, deferred_tx_len=40, bus_txglom=0 [  149.959628] dhd_conf_set_txglom_params: tx_in_rx=1, tx_max_offset=0 [  149.959632] dhd_conf_set_disable_proptx: set disable_proptx 0 [  149.960335] dhd_wlfc_hostreorder_init(): successful bdcv2 tlv signaling, 64 [  149.960826] wl_android_wifi_on: Success [  150.018061] dhd_open: Exit ret=0 [  150.140579] P2P interface registered [  150.153519] WLC_E_IF: NO_IF set, event Ignored [  150.154635] P2P interface started [  182.422348] dhd_module_cleanup: Enter [  182.422393] sdioh_remove: Enter [  182.422398] dhdsdio_disconnect : no mutex held. set lock [  182.430336] dhdsdio_dpc: Bus down, ret [  182.430350] bcmsdh_oob_intr_unregister: Enter [  182.430364] dhd_wlfc_deinit():3301, Already disabled! [  182.490019] dhd_stop: Enter ffffffc05119b000 [  182.490026] wl_android_wifi_off in 1 [  182.490030] wl_android_wifi_off in 2: g_wifi_on=1 [  182.490036] dhd_prot_ioctl : bus is down. we have nothing to do [  182.490118] bcmsdh_oob_intr_unregister: Enter [  182.490128] bcmsdh_oob_intr_unregister: irq is not registered [  182.490143] dhd_txglom_enable: enable 0 [  182.490150] dhd_conf_set_txglom_params: swtxglom=0, txglom_ext=0 [  182.490156] dhd_conf_set_txglom_params: txglom_bucket_size=0 [  182.490162] dhd_conf_set_txglom_params: txglomsize=0, deferred_tx_len=0, bus_txglom=0 [  182.490168] dhd_conf_set_txglom_params: tx_in_rx=1, tx_max_offset=0 [  182.490175] dhd_bus_devreset:  WLAN OFF DONE [  182.490240] wifi_platform_set_power = 0 [  182.490247] ======== PULL WL_REG_ON LOW! ======== [  182.490252] wl_android_wifi_off out [  182.490258] dhd_stop: Exit [  182.570103] dhd_detach(): thread:dhd_watchdog_thread:ee1 terminated OK [  182.570165] dhd_detach(): thread:dhd_rxf:ee3 terminated OK [  182.570188] dhd_dpc_thread: Unexpected up_cnt 0 [  182.570211] dhd_detach(): thread:dhd_dpc:ee2 terminated OK [  182.571711] P2P interface unregistered [  182.571746] wl_event_handler: was terminated [  182.571944] wl_destroy_event_handler(): thread:wl_event_handler:ee0 terminated OK [  182.799988] dhd_tcpack_suppress_set 376: already set to 0 [  182.800006] dhd_os_prealloc: failed to alloc memory, section: 7, size: 0bytes [  182.800031] dhdsdio_disconnect : the lock is released. [  182.800275] unregister wifi platform drivers [  182.800283] wifi_platform_bus_enumerate device present 0 [  182.800289] ======== Card detection to remove SDIO card! ======== [  182.800315] aml_wifi wifi.33: [extern_wifi_set_enable] WIFI  Disable! 240 [  183.000404] dhd_module_cleanup: Exit

normally a blinking led should show that the system has bootet (heartbeat led).
Maybe you could try to use etcher for Linux or Windows to create the bootable sd-card?
https://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-a-sd-card

before reboot /etc/network/interfaces will be active.
Configure via nmtui and set it active at boot, then save and reboot  - this wil activate the connection

Kernel for H3/H5 and A20/A10 has been updated and pushed to the repository. I made 24h severe burn-in testings with three boards: Cubietruck, Orangepi 2E and Orangepi Prime. I did nasty things to them and all are still running.

I did learn much here in the forum from "one to many" teaching or while reading problems and solutions of other boards/users.
Mostly I could solve my problems while reading other post, just because its all armbian and it all board are arm-style

The best for @jiapei100 will also to read a while in differnt threads and the armbian documentation - there are so many answers to questions.
You could learn much from many users here - and maybe later someone from you - if you could faster answer to more easy questions.

And if the armbian-forum isnt enough, then there are the forums of the board-manufacturers or the Facebook-Groups for this board

Yes - if you do not only compile a Kernel - you will get a full image which can be written to uSD,
BUT you need a 64Bit Ubuntu on your main computer and some disk space.
The image will be written to ./build/output/images - for me thats /home/guido/build/output/images/
 
Because I got it in a VirtualBox - I created only a 30GB Disk.
Before compiling I have 9GB free Disk-Space and the build-process does warn me.
But when I do compile for the R69 I have mostly ofer 6.7GB free (looking with df at the disks).
 
On my QuadCore AMD 3GHz the compile does run in the frist try 26 Minutes.... later if I compile another image with other kernel then it could run as fast as 16 minutes (less download?)
 

Good news but still odd: the legacy image's FEX file indicates a DRAM clock of 576MHz. Never mind, I created a pull request with an updated u-boot patch which should solve the issue for other users as well.
Thx for raising the issue and the extensive testing
 

I did build the image with this patch as Armbian_5.40_Sunvell-r69_Debian_stretch_next_4.14.17_RAM_408Mhz.img
and now all the others cards (8GB Ultra and 32GB Exteme) DO boot again in the first try
ARMBIAN 5.40 user-built Debian GNU/Linux 9 (stretch) 4.14.17-sunxi Linux sunvell-r69 4.14.17-sunxi #6 SMP Wed Feb 7 11:31:13 +03 2018 armv7l GNU/Linux I didnt want to copy the OS to eMMC, because for future purposes I want to leave the original Android there.
As I have the case closed I dont want to open these clips again - because Iam afraid they could break in a additional try

@guidol: Does the boot-stability improve, when you replace build/patch/u-boot/u-boot-sunxi/add-sunvell-r69.patch with the attached file (reduces DRAM clck to 408)?
If stability improves, could you copy the OS to eMMC via armbian-config and check boot-stability?
add-sunvell-r69.patch

First linux image for H6 Orange Pi boards available: http://www.orangepi.org/downloadresources/

Armbian images for R69 on Google Drive.

Mainline kernel vers. 4.14.17 also works quite well (supporting eth, wifi, both usb-ports, emmc, ir, audio, ...). You could build it yourself with the armbian build system (https://docs.armbian.com/Developer-Guide_Build-Preparation/)
# git clone --depth 1 https://github.com/armbian/build # cd build # ./compile.sh BOARD=sunvell-r69 for media stuff you better stay with the legacy kernel though ...

Founded. I like to bet for death horses!
And the First additional stretch goal is reached 22.943 € Monday, February 5.

Hi, 
You can use the OPi + image on the +2, thats what i do.
The only divrence between them are the ram and emmc size, 1GB/8GB vs 2GB/16GB.
After booting armbian wil display it has 2GB ram.

I've installed system with 4x kernel and now it works. 
 
Thank you! 

yea, I had that issues too, my audio is not working even tried both HDMI and 3.5mm port.
but I found out the solution that my sound is working using USB sound card. give it a try!

Hi again!
 
Problem solved!
I connected the SD card on my PC and tried to run fsck, but it bleats something about wrong partition size.
After a resize2fs fsck worked without any problem.
Now the BPI bootet with the new SD card.
 
Hope this help someone other!
Luca

My OPi one+ arrived. I burned the ubuntu image with etcher and it worked fine. I had to manually resize the fs but you expect a few rough edges with a new board.
 
The bare board runs on the hot side, idling at a reported (but unconfirmed) 48C. Benchmarks quickly push it into throttling at 70C, but even so it is faster (just) than any of my other 4 core boards. I'll add a heatsink and fan and see if I can get the temps under control. If so, and if the board remains reliable it seems like excellent value for money. The H6 looks very promising.

Ubuntu is Debian based, but the main difference is packages selection and their versions. Since we also define the package base, most of the packages are the same but they are certainly not the same version. This means certain application might not work out of the box and you need to solve dependencies on your own. This can be simple or a true nightmare. In this case, it's better to start with a proper base, whether Ubuntu or Debian. One good example is OMV - it does not work at all on Ubuntu - at least not out of the box. Stable version requires Debian Jessie, while current development is based on Stretch. For a board, which might be used as OMV (Helios4), we provide both, Jessie and Stretch and it's up to the user to decide which OMV version he will go for.
 
In the x86 world, a change between releases/distribution is usually also on a kernel branch, while here we don't have this luxury. We have to use what is available and since there is no better working kernel than 3.10.y for this board we simply can't provide Stretch. We could Jessie ... but since we provide a simple and easy to use build tools, this is not that urgent either.

uooohhhh!!!!!   What a tiny "big" CPD!!!!!  ;-) Thank you very much, guidol. It is a very good reference for me.  Now, I have moved my orange pi zero plus H5 to a very  open-space ( it was inside a very closed furniture before.... ). I have moved it behind my plasma TV ;-).  And now, almost idle, temperature is in normal values ( with 21C room temperature ):
 
root@zeus:~# armbianmonitor -m
Stop monitoring using [ctrl]-[c]
Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU  C.St.
22:02:28:  816MHz  0.36  10%   1%   1%   3%   3%   0% 47.2°C  0/2
22:02:33:  816MHz  0.33   4%   1%   2%   0%   0%   0% 44.4°C  0/2
22:02:38:  816MHz  0.31   2%   1%   1%   0%   0%   0% 45.0°C  0/2
22:02:43:  816MHz  0.28   2%   1%   1%   0%   0%   0% 42.2°C  0/2
22:02:49:  816MHz  0.34   2%   0%   1%   0%   0%   0% 44.3°C  0/2
22:02:54:  816MHz  0.31   3%   1%   2%   0%   0%   0% 45.3°C  0/2
22:02:59:  816MHz  0.29   2%   1%   1%   0%   0%   0% 46.2°C  0/2
22:03:04:  816MHz  0.34   2%   0%   1%   0%   0%   0% 43.0°C  0/2
22:03:09:  816MHz  0.32   6%   1%   5%   0%   0%   0% 47.2°C  0/2
22:03:14:  816MHz  0.29   2%   1%   1%   0%   0%   0% 44.5°C  0/2
22:03:19:  816MHz  0.27   3%   1%   1%   0%   0%   0% 43.9°C  0/2
22:03:24:  816MHz  0.25   3%   1%   1%   0%   0%   0% 45.4°C  0/2
22:03:29:  816MHz  0.23   2%   1%   1%   0%   0%   0% 44.9°C  0/2
22:03:34:  816MHz  0.21   5%   1%   3%   0%   0%   0% 45.4°C  0/2
Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU  C.St.
22:03:39:  816MHz  0.19   2%   1%   1%   0%   0%   0% 44.2°C  0/2
22:03:44:  816MHz  0.17   2%   1%   1%   0%   0%   0% 44.6°C  0/2
22:03:50:  816MHz  0.16   3%   1%   1%   0%   0%   0% 44.3°C  0/2
 
I use my OP Zero for NAS Server ( samba/nfs ) and for p2p downloads with mldonkey.
 
You can see my brico-project with an old celeron heatsink ( I am very worried with temperatures, perhaps I am a little friki... ):
 

Replacing bootloader on your eMMC
 
Boot from SD card.
mkdir tmp cd tmp # replace this URL with the one for your board! This is for Orange pi plus 2e wget http://apt.armbian.com/pool/main/l/linux-u-boot-orangepiplus2e-default/linux-u-boot-orangepiplus2e_5.39_armhf.deb dpkg -x *.deb .  root_uuid=$(sed -e 's/^.*root=//' -e 's/ .*$//' < /proc/cmdline) root_partition_device=$(blkid | tr -d '":' | grep ${root_uuid} | awk '{print $1}' | tr -d '"/dev') emmc="/dev/"$(cat /proc/partitions | grep -v ${root_partition::-2} | grep mmcblk | awk '{print $4}' | head -1) # adjust the path accordingly to your board - downloaded file dd if=usr/lib/linux-u-boot-orangepiplus2e_5.35_armhf/u-boot-sunxi-with-spl.bin of=$emmc bs=1024 seek=8 status=noxfer If you want to flash your SD card on external SD card reader:
sdcard=/dev/sda # make sure this is SD card and not your hard drive!! dd if=usr/lib/linux-u-boot-orangepiplus2e_5.35_armhf/u-boot-sunxi-with-spl.bin of=$sdcard bs=1024 seek=8 status=noxfer  

I think as OPi+ he means the https://www.armbian.com/orange-pi-plus/
The only "pi" with eMMC at my side is the NPi Neo Core2, but also with mainline (image of the NPi Neo Plus2 is working here with eMMC-support, but Iam running this from uSD).
 
My OPi One is using legacy kernel (as Pi-Hole Server) but hasnt a eMMC.
 
 

I dont think you could name it Nano pi Neo2 / Core, but you could name
Nano Pi Neo Air     -> Nano Pi Neo Core/Air (H3)
Nano Pi Neo Plus2 -> Nano Pi Neo Core2/Plus2 (H5)
because
Nano Pi Neo Core   is a Nano Pi Neo  (H3)  with eMMC = like a NanoPi Neo Air without BT/WiFi  and
Nano Pi Neo Core2 is a Nano Pi Neo2 (H5) with eMMC = like a NanoPi Neo Plus2 without BT/WiFi
 
Nano Pi Neo (H3) (without extension) and Neo2 (H5) (without extension) are without eMMC/BT/WiFi
 
PS: I didnt got a SSD on the Core2 - so armbian could read the size - I think