Jump to content

Recommended Posts

Posted

@balbes150, please check the fdisk -l output for Beelink GT1 / 16GB eMMC / 2GB RAM / AP 6255 (GT-T_V20.20160810)

root@amlogic-s905x:~# fdisk -l
Disk /dev/mmcblk0: 14.5 GiB, 15518924800 bytes, 30310400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk0rpmb: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk1: 14.9 GiB, 15931539456 bytes, 31116288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000d9380


Device         Boot  Start      End  Sectors  Size Id Type
/dev/mmcblk1p1        2048   133119   131072   64M  e W95 FAT16 (LBA)
/dev/mmcblk1p2      133120 30805119 30672000 14.6G 83 Linux
Posted

i was looking at those s912 boxes, including the GT1, and i'm curious, do they really have 802.11AC wifi or is it simply (a)/b/g/n 2.4GHz + 5GHz ??

 

if yes then how is it performing ?

thx

Posted

@mdel, don't know about the wifi hardware spec. GT1 has a seal antenna type, but it is working incredible well... I had bad, really bad experiences with this kind of antenna before, but it is working on mid-range (25m with walls) from AP.

Posted

i've ordered a Meecool bb2 (s912 2G 16G), so at some point i'll also do some tests with balbes150 images.

I really have no use for an s912 but i can play wit it a bit and see how it performs against s905 for my own use case.

 

@lvmc

yeah, i know those internal antennas are really weak but i was more interested in seeing AC performances, because my tests with xiaomi mini router in AC mode were quite impressive, although my wifi knowledge is quite thin as i tend to use it as little as possible.

 

I believe i saw an external antenna hack for the GT1 somewhere but it's really the same for any box, drill/screw an antenna mount on the case and solder it to the antenna pads on the board.

Posted

Hi, I'm new here.

I'm using LE on Mini MX, Mini M8S and Raspi3, I'm familiar with using USB Burning tool but not deeper knowledge of Android or Linux 

I would like to install armbian to an H96 Pro 3GB/16GB. 

I've downloaded Armbian_5.24_Amlogic-s905x_Ubuntu_xenial_3.14.29_20161125.img and write it to an sd card with win32diskimager.

I've renamed gxm_q200_2g.dtb to dtb.img and copied to the sd card's root folder.

With toothpick method I tried to boot from the card but it restart the boot logo over and over.

Could you give me a hint how can I go further?

How can I get the dtb from my box? 

 

After a single activation multi-boot, press and hold the reset button (with a toothpick) do NOT need. After the first reboot button to let go. Just try to include the TV box, WITHOUT using toothpicks.

Posted

Perhaps because of the 3GB RAM you need to use a dtb file from Your console. Or to analyze log files. The ideal solution is to connect the console UART. Then all at once it becomes clear where the mistake.

Posted

I thought to connect to UART but the box is glued together I don't want to destroy the top of it... :(

I tried from a different pc with debian on it and installed android-tools-adb, but no luck. 

Even lsusb cannot see any of the usb ports of the box.

 

Edit: 

I can see my android phone on both machine with adb.

 

Edit2:

I've found the fw of the box here: http://chinagadgetsreviews.com/firmware-r-box-pro.html

Is it worth trying to extract the dtb from that?

 

Yes, try to extract the firmware and get it from the dtb file. May need to rebuild this file with the kernel source.

Posted

Yes, You can try this file. If it doesn't work, I'll try to include the source code from this file in the next collection of images.

Posted

I tried to copy this file to the sd card's root folder and rename it to dtb.img 

After the boot logo ("H96 Pro") just black screen and no signal on HDMI.

Try this file. But I think it will not help. I think You pulled the wrong file, it will be necessary to unpack the firmware and see all dtb files in it.

 

https://yadi.sk/d/9cWeYdu333NagX

Posted

The process of testing and debugging installing to the internal memory. It is associated with a higher risk for potential users. I'm all need to repeatedly check. If make a mistake on an external drive - no problem, pulled out the media and TV box is working again. If make a mistake while recording on internal memory - get the brick. So I check a lot of different options, looking for one where the risk is minimal and there is a good result for the Linux.

Posted

@balbes150, yes. But if the device is bricked because of a previous failure on writing OS to eMMC why we can't just reboot and try to write again?

Posted

Thank you, I tried but nothing changed (boot logo, then no signal on HDMI). Is this file just a trimmed version of mine?

The file came from /dev/dtb

I've found another ones:

/sys/devices/virtual/dtb

/sys/devices/virtual/dtb/dtb

/sys/devices/virtual/dtb/dtb/dev

/sys/devices/virtual/dtb/dtb/power

/sys/devices/virtual/dtb/dtb/subsystem

/sys/devices/virtual/dtb/dtb/uevent

/sys/class/dtb

/sys/class/dtb/dtb

/sys/class/dtb/emmcdtb

 

Which one do you think is worth to check? 

 

Edit:

Checked all but they contain only version info: 243:0

 

How long are You waiting after trying to start the system from external media ? Depending on the carrier , you need to wait about 5-7 minutes. The message about no signal during startup - normally (I have not yet made support for savers the first stage of the system startup).

 

 

@balbes150, yes. But if the device is bricked because of a previous failure on writing OS to eMMC why we can't just reboot and try to write again?

 

Because if it's not right to change the bootloader (to run Linux), you NOT are able to boot neither from external media or from internal storage. Because of the peculiarities of the primary boot loader of the processor (not to be confused with the code of u-boot in the internal memory), the processor will first try to run the code u-boot from internal memory. And the code u-boot is ruined, the console hangs (becomes a brick). Will close the contacts on the chip eMMC, something to force the download first u-boot from SD card or via USB cable (the flasher with a PC). This is the main wealth Amlogic - start is only possible either when fully functional u-boot in eMMC, or in its full otsutsvie. And if it is, but tainted - the launch of TV box is not possible. EMMC how to develop cards that cannot be detachable from a TV box. So you need to be careful when working with u-boot.

Posted

If the system after the screen saver freezes and will not start, so multiupload was activated and working. Perhaps the reason is not a good start in the following cases : 1. or not appropriate dtb file 2. any problems with the media . TV box is VERY whimsical to quality and SD card settings. I have 15 different cards on different TV consoles from 5 to 12 cards do not allow you to start the system (there is a console where can I work only 3 out of 15 , and is where can work 12 of the 15 cards). ALL cards work perfectly and give no failure on PC and laptops. I think that's the problem with cheap scanners or a bad driver for a card reader for u-boot at higher speeds (maybe old drivers, computed on a slow card). Therefore, strongly suggest that in case of any problems with system start-up be SURE to check out the startup from a USB drive. Or use to check a USB card reader.

Posted

Hello I wrote ubuntu xenial desktop img on sdcard and booted it on beelink gt1. But no sound on hdmi how can I fix this? ( I can connect internet via my old s3 mini :) )

Edit: I don't know how to compile kernel or another need to use terminal. I can only repeat what you say here as I understand. I am sorry if my question is too silly.

Posted

HI,

 

 

I would like to report that  the images Ubuntu 16.04.1  amlogic-S905x (server and desktop 18.12.2016 from balbes150)) are working on  Bqeel T12 (S912 2G/16GB). The system is booted , networking is working , wifi is activated. Xwindows is started, Firefox is OK There is no Kodi yet.

 

However, docker is not working due to the fact that aufs is not compiled (modprobe aufs failed) in the kernel. The source from In the /lib/modules/3.14.29 does not include fs/aufs. Given the fact that dokcer is working well with  Odroid C2 based  Ubuntu  image ( for example MiniMx S905 with the same kernel 3.14.29) , i tried to compile the support for aufs based on the source of this one. Unhappily there were too many errors (missing modules,..)

 

I would be grateful if the support of aufs could be integrated in the Armbian S905x/S912 version.

 

Thanks in advance.

Posted

@balbes150, on your latest images for 905x / 5.24.

sudo modprobe cfg80211
sudo modprobe dhd
               dhd_bus_devreset: == WLAN ON ==
[  482.888058] F1 signature read @0x18000000=0x15264345
[  482.891391] F1 signature OK, socitype:0x1 chip:0x4345 rev:0x6 pkg:0x2
[  482.892072] DHD: dongle ram size is set to 819200(orig 819200) at 0x198000
[  482.892502] dhd_conf_read_nv_by_chip: nv_by_chip_count=1
[  482.892511] dhd_conf_read_nv_by_chip: chip=0xa962, chiprev=1, name=nvram_ap6210.txt
[  482.892760] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/brcm/fw_bcm43455c0_ag.bin
[  482.892768] dhdsdio_download_firmware: set use_rxchain 0
[  482.892773] dhdsdio_download_firmware: set txglomsize 40
[  482.892780] sdioh_set_mode: set txglom_mode to multi-desc
[  482.892785] Final fw_path=/lib/firmware/brcm/fw_bcm43455c0_ag.bin
[  482.892790] Final nv_path=/lib/firmware/brcm/
[  482.892795] Final conf_path=/lib/firmware/brcm/config.txt
[  482.893250] dhdsdio_download_code_file: Open firmware file failed /lib/firmware/brcm/fw_bcm43455c0_ag.bin
[  482.893256] _dhdsdio_download_firmware: dongle image file download failed
[  482.893290] dhd_net_bus_devreset: dhd_bus_devreset: -35
[  482.893299] dhd_prot_ioctl : bus is down. we have nothing to do
[  482.893306] dhd_net_bus_devreset: dhd_bus_devreset: -35
[  482.893358] wifi_platform_set_power = 0
[  482.893365] ======== PULL WL_REG_ON LOW! ========
[  482.893370] wl_android_wifi_on: Failed
[  482.893376] dhd_open : wl_android_wifi_on failed (-35)
[  482.893383] dhd_stop: Enter ffffffc060c55800
[  482.893389] wl_android_wifi_off in 1
[  482.893394] wl_android_wifi_off in 2: g_wifi_on=0
[  482.893399] wl_android_wifi_off out
[  482.893404] dhd_stop: Exit
[  482.893412] dhd_open: Exit ret=-1
[  482.894105] dhd_open: Enter ffffffc060c55800
[  482.894121]
               Dongle Host Driver, version 1.201.59.6 (r506368)
               Compiled in drivers/net/wireless/bcmdhd
[  482.894131] wl_android_wifi_on in 1
[  482.894137] wl_android_wifi_on in 2: g_wifi_on=0
[  482.894143] wifi_platform_set_power = 1
[  482.894148] ======== PULL WL_REG_ON HIGH! ========
[  482.894171] aml_wifi wifi.33: [extern_wifi_set_enable] WIFI  Disable! 240
[  483.094200] aml_wifi wifi.33: [extern_wifi_set_enable] WIFI  Enable! 240
[  483.594991] sdio_reset_comm():
[  483.623129] sdio: queuing unknown CIS tuple 0x80 (2 bytes)
[  483.625767] sdio: queuing unknown CIS tuple 0x80 (3 bytes)
[  483.628392] sdio: queuing unknown CIS tuple 0x80 (3 bytes)
[  483.633103] sdio: queuing unknown CIS tuple 0x80 (7 bytes)
[  483.726307] sdio: clk 200000000 SDR mode tuning start
[  483.726575] sdio: rx_tuning_result[0] = 10
[  483.726829] sdio: rx_tuning_result[1] = 10
[  483.727082] sdio: rx_tuning_result[2] = 10
[  483.727337] sdio: rx_tuning_result[3] = 10
[  483.727368] sdio: best_win_start =0, best_win_size =4
[  483.727376] sdio: sd_emmc_regs->gclock=0x1000245,sd_emmc_regs->gadjust=0x22000
[  483.727384] sdio: gclock =0x1000245, gdelay=0x0, gadjust=0x22000
[  483.727440] sdioh_start: set sd_f2_blocksize 128
[  483.727811]


               dhd_bus_devreset: == WLAN ON ==
[  483.728000] F1 signature read @0x18000000=0x15264345
[  483.731325] F1 signature OK, socitype:0x1 chip:0x4345 rev:0x6 pkg:0x2
[  483.732007] DHD: dongle ram size is set to 819200(orig 819200) at 0x198000
[  483.732443] dhd_conf_read_nv_by_chip: nv_by_chip_count=1
[  483.732452] dhd_conf_read_nv_by_chip: chip=0xa962, chiprev=1, name=nvram_ap6210.txt
[  483.732702] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/brcm/fw_bcm43455c0_ag.bin
[  483.732710] dhdsdio_download_firmware: set use_rxchain 0
[  483.732716] dhdsdio_download_firmware: set txglomsize 40
[  483.732722] sdioh_set_mode: set txglom_mode to multi-desc
[  483.732727] Final fw_path=/lib/firmware/brcm/fw_bcm43455c0_ag.bin
[  483.732732] Final nv_path=/lib/firmware/brcm/
[  483.732737] Final conf_path=/lib/firmware/brcm/config.txt
[  483.733191] dhdsdio_download_code_file: Open firmware file failed /lib/firmware/brcm/fw_bcm43455c0_ag.bin
[  483.733198] _dhdsdio_download_firmware: dongle image file download failed
[  483.733232] dhd_net_bus_devreset: dhd_bus_devreset: -35
[  483.733241] dhd_prot_ioctl : bus is down. we have nothing to do
[  483.733247] dhd_net_bus_devreset: dhd_bus_devreset: -35
[  483.733300] wifi_platform_set_power = 0
[  483.733306] ======== PULL WL_REG_ON LOW! ========
[  483.733312] wl_android_wifi_on: Failed
[  483.733319] dhd_open : wl_android_wifi_on failed (-35)
[  483.733327] dhd_stop: Enter ffffffc060c55800
[  483.733332] wl_android_wifi_off in 1
[  483.733337] wl_android_wifi_off in 2: g_wifi_on=0
[  483.733342] wl_android_wifi_off out
[  483.733347] dhd_stop: Exit
[  483.733355] dhd_open: Exit ret=-1
Posted
WiFi is now working on GT1.
 
1. Download & Copy AP6255 WiFi drivers extracted from Beelink's Android image:
 
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
Posted

The files listed in version images 20161218 (directory firmware/brcm). Loading the same modules already included. You tested version 20161218 ?

Posted

@balbes150,

 

Armbian_5.24_Amlogic-s905x_Ubuntu_xenial_3.14.29_20161218.img.xz, 19/12/2016.

 

nvram.txt is missing

Posted

 

@balbes : What's the next step for S912 ? Is there somethings we can do to help ?

I've run your last version successfully ( ubuntu desktop 161227), but I got poor performance in decoding video.  

Posted

@balbes150,

 

Your latest image is working on eMMC, but ethernet has stopped to work.

 

On install.sh I tried to set IMAGE_DTB to the .dtb file I extracted and published in this thread for GT1, it is not giving any more errors during the script run, but ethernet is not working anymore.

 

This dtb files are causing a general confusion on the users.

 

Best,

Luiz.

Posted

@balbes : What's the next step for S912 ? Is there somethings we can do to help ?

I've run your last version successfully ( ubuntu desktop 161227), but I got poor performance in decoding video.  

 

If You really want to help the project, it will be useful to build deb packages with the latest versions of KODI, codecs, modules for WiFi and BT Ubuntu\Debian.

 

 

@balbes150,

 

Your latest image is working on eMMC, but ethernet has stopped to work.

 

On install.sh I tried to set IMAGE_DTB to the .dtb file I extracted and published in this thread for GT1, it is not giving any more errors during the script run, but ethernet is not working anymore.

 

This dtb files are causing a general confusion on the users.

 

Best,

Luiz.

 

What version images network work ? What dtb was used ? Without a separate dtb files can not do, is features of this platform. It is impossible to make one universal file.

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines