rafman Posted October 12 Posted October 12 your adapter is not powered. sudo bluetoothctl power on you receive (Changing power on succeeded) or error ? 0 Quote
MMorales Posted October 12 Posted October 12 (edited) root@transpeed-8k618-t:~# bluetoothctl power on [CHG] Controller 43:34:B0:00:1F:AC PowerState: off-enabling Changing power on succeeded root@transpeed-8k618-t:~# bluetoothctl Agent registered [CHG] Controller 43:34:B0:00:1F:AC Pairable: yes AdvertisementMonitor path registered [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# @rafman FYII: if i delete BCM4334B0.hcd there is no errors in dmesg. and all the commands works without erros in bluetoothctl. But i dont get any result when "scan" o "devices" so its the same. no works. like this when no "bcm4334b0.hcd": ^[[Aroot@transpeed-8k618-t:~# dmesg | grep -i bluetooth [ 5.610492] Bluetooth: Core ver 2.22 [ 5.610614] NET: Registered PF_BLUETOOTH protocol family [ 5.610619] Bluetooth: HCI device and connection manager initialized [ 5.610636] Bluetooth: HCI socket layer initialized [ 5.610644] Bluetooth: L2CAP socket layer initialized [ 5.610660] Bluetooth: SCO socket layer initialized [ 5.638749] Bluetooth: HCI UART driver ver 2.3 [ 5.638781] Bluetooth: HCI UART protocol H4 registered [ 5.638786] Bluetooth: HCI UART protocol BCSP registered [ 5.638893] Bluetooth: HCI UART protocol LL registered [ 5.638898] Bluetooth: HCI UART protocol ATH3K registered [ 5.638929] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 5.639088] Bluetooth: HCI UART protocol Intel registered [ 5.639183] Bluetooth: HCI UART protocol Broadcom registered [ 5.639213] Bluetooth: HCI UART protocol QCA registered [ 5.639218] Bluetooth: HCI UART protocol AG6XX registered [ 5.639243] Bluetooth: HCI UART protocol Marvell registered [ 5.997577] Bluetooth: hci0: BCM: chip id 68 [ 6.000063] Bluetooth: hci0: BCM: features 0x0f [ 6.023468] Bluetooth: hci0: BCM4334B0 [ 6.023498] Bluetooth: hci0: BCM4334B0 (002.001.013) build 0000 [ 6.023720] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [ 6.023727] Bluetooth: hci0: BCM: 'brcm/BCM4334B0.transpeed,8k618-t.hcd' [ 6.023733] Bluetooth: hci0: BCM: 'brcm/BCM4334B0.hcd' [ 6.023738] Bluetooth: hci0: BCM: 'brcm/BCM.transpeed,8k618-t.hcd' [ 6.023743] Bluetooth: hci0: BCM: 'brcm/BCM.hcd' [ 12.555772] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 12.555804] Bluetooth: BNEP filters: protocol multicast [ 12.555824] Bluetooth: BNEP socket layer initialized [ 12.562835] Bluetooth: MGMT ver 1.22 [ 12.824668] Bluetooth: RFCOMM TTY layer initialized [ 12.824718] Bluetooth: RFCOMM socket layer initialized [ 12.824739] Bluetooth: RFCOMM ver 1.11 root@transpeed-8k618-t:~# bluetoothctl Agent registered [CHG] Controller 36:E3:66:EB:FE:ED Pairable: yes AdvertisementMonitor path registered [bluetooth]# power on Changing power on succeeded [bluetooth]# show Controller 36:E3:66:EB:FE:ED (public) Name: transpeed-8k618-t Alias: transpeed-8k618-t Class: 0x00400000 Powered: yes PowerState: on Discoverable: no DiscoverableTimeout: 0x000000b4 Pairable: yes UUID: SIM Access (0000112d-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Volume Control (00001844-0000-1000-8000-00805f9b34fb) UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0542 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x05 (5) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedCapabilities Key: MaxAdvLen SupportedCapabilities Value: 0x1f (31) SupportedCapabilities Key: MaxScnRspLen SupportedCapabilities Value: 0x1f (31) Advertisement Monitor Features: SupportedMonitorTypes: or_patterns [bluetooth]# devices [bluetooth]# scan on Discovery started [CHG] Controller 36:E3:66:EB:FE:ED Discovering: yes [bluetooth]# discoverable on Changing discoverable on succeeded [CHG] Controller 36:E3:66:EB:FE:ED Discoverable: yes [bluetooth]# Edited October 12 by MMorales 0 Quote
rafman Posted October 12 Posted October 12 (edited) replace the BCM4334B0.hcd (don't delete it) / Reboot When is powered on --> (Changing power on succeeded) give : discoverable on USE your mobile phone, activate bluetooth, end discover for devices. can you see your TV-box from your mobile ? if yes then it work as mine. Edited October 12 by rafman 0 Quote
MMorales Posted October 12 Posted October 12 I tried all. No works on mine. I think is for the diff on kernel 0 Quote
rafman Posted October 12 Posted October 12 1 minute ago, MMorales said: I tried all. No works on mine. I think is for the diff on kernel your device is not descoverable give : [bluetooth]# discoverable on and retry with your phone. 0 Quote
MMorales Posted October 12 Posted October 12 I tried. All the ways. I tried too with 4 o 5 diferent fw taken from diferentes forums. Nothing. 0 Quote
rafman Posted October 12 Posted October 12 1 hour ago, MMorales said: FYII: if i delete BCM4334B0.hcd there is no errors in dmesg. and all the commands works without erros in bluetoothctl. But i dont get any result when "scan" o "devices" so its the same. no works. I do the same and the adapter seems to work fine now (better than before) rafman@orion-8k:~$ sudo hciconfig -a hci0: Type: Primary Bus: UART BD Address: 00:0E:42:C3:DC:50 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:1945 acl:0 sco:0 events:129 errors:0 TX bytes:4194 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: PERIPHERAL ACCEPT Name: 'orion-8k' Class: 0x6c0000 Service Classes: Rendering, Capturing, Audio, Telephony Device Class: Miscellaneous, HCI Version: 4.0 (0x6) Revision: 0x0 LMP Version: 4.0 (0x6) Subversion: 0x410d Manufacturer: Broadcom Corporation (15) but i have no discovery results. Something is problematic with BCM4334B0.hcd or with the driver / patch. 0 Quote
MMorales Posted October 12 Posted October 12 @rafman can you share your /etc/bluetooth/main.conf?. Please 0 Quote
rafman Posted October 12 Posted October 12 (edited) @Nick A After a lot of searching i found a thread with a similar problem (bug) on arch it started to happens (with 6.6.2 kernel) read here: https://bbs.archlinux.org/viewtopic.php?id=290578 my dmesg errors are same [ 27.873839] Bluetooth: hci0: command 0x0c24 tx timeout [ 27.873844] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 39.306413] Bluetooth: hci0: command 0x0c24 tx timeout [ 39.306412] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 41.322433] Bluetooth: hci0: Opcode 0x0c24 failed: -110 [ 41.322455] Bluetooth: hci0: command 0x0c24 tx timeout I don't know if it remains and affects us. Edited October 12 by rafman 0 Quote
Nick A Posted October 13 Posted October 13 (edited) Here are the Allwinner BSP kernel drivers if you want to dive deep into the rabbit hole. git clone https://github.com/AvaotaSBC/linux.git --depth=1 Have you tried a newer version of bluez? https://packages.debian.org/search?arch=arm64&keywords=bluez https://github.com/bluez/bluez/tree/master https://github.com/bluez/bluez/blob/bd7d49d54aa3aa490ebdd67b3dd2317d29213d45/monitor/bt.h#L1488 #define BT_HCI_CMD_WRITE_EXT_INQUIRY_RESPONSE 0x0c52 struct bt_hci_cmd_write_ext_inquiry_response { uint8_t fec; uint8_t data[240]; } __attribute__ ((packed)); https://github.com/bluez/bluez/blob/bd7d49d54aa3aa490ebdd67b3dd2317d29213d45/monitor/bt.h#L1271C1-L1274C28 #define BT_HCI_CMD_WRITE_CLASS_OF_DEV 0x0c24 struct bt_hci_cmd_write_class_of_dev { uint8_t dev_class[3]; } __attribute__ ((packed)); https://github.com/bluez/bluez/blob/bd7d49d54aa3aa490ebdd67b3dd2317d29213d45/monitor/packet.c#L5920 static void write_ext_inquiry_response_cmd(const void *data, uint8_t size) { const struct bt_hci_cmd_write_ext_inquiry_response *cmd = data; print_fec(cmd->fec); print_eir(cmd->data, sizeof(cmd->data), false); } https://kernel.googlesource.com/pub/scm/bluetooth/bluez/+/5.7/monitor/packet.c#4070 { 0x0c52, 137, "Write Extended Inquiry Response", write_ext_inquiry_response_cmd, 241, true, status_rsp, 1, true }, https://github.com/bluez/bluez/blob/bd7d49d54aa3aa490ebdd67b3dd2317d29213d45/monitor/packet.c#L5565 static void write_class_of_dev_cmd(uint16_t index, const void *data, uint8_t size) { const struct bt_hci_cmd_write_class_of_dev *cmd = data; print_dev_class(cmd->dev_class); } https://kernel.googlesource.com/pub/scm/bluetooth/bluez/+/5.7/monitor/packet.c#4015 { 0x0c24, 73, "Write Class of Device", write_class_of_dev_cmd, 3, true, status_rsp, 1, true }, You can ask the bluez developers for help. https://github.com/bluez/bluez/issues Edited October 13 by Nick A 0 Quote
rafman Posted October 13 Posted October 13 (edited) 13 hours ago, Nick A said: You can ask the bluez developers for help. i did it. https://github.com/bluez/bluez/issues/980 I returned my firmware to original (Armbian) firmware files. Edited October 13 by rafman 0 Quote
firepower Posted October 13 Posted October 13 (edited) regarding dts files, are the uboot and kernel dts files meant to be identical ? useful link about dts to/from dtb compiler. https://stackoverflow.com/questions/21670967/how-to-compile-dts-linux-device-tree-source-files-to-dtb Edited October 13 by firepower 0 Quote
afiftyp Posted October 13 Posted October 13 one important point on the BT module is that the frequency setting in the xxxxx-sdio.txt needs to match the speed of the oscillator sitting beside the BT module. There seem to be to common frequency's, 26 and 37.4 MHz. My transpeed uses "xtalfreq=26000". The corresponding link is: brcmfmac4330-sdio.transpeed,8k618-t.txt -> brcmfmac-ap6330-sdio.txt 0 Quote
rafman Posted October 13 Posted October 13 7 minutes ago, afiftyp said: My transpeed uses "xtalfreq=26000". The corresponding link is: brcmfmac4330-sdio.transpeed,8k618-t.txt -> brcmfmac-ap6330-sdio.txt My brcmfmac4330-sdio.transpeed,8k618-t.txt -> xtalfreq=37400 0 Quote
afiftyp Posted October 13 Posted October 13 The kernel people are not really happy with the patch to introduce the RTC auto calibration. The right way to go is using the existing code from the newer sunxi-ng source instead of adding the H616/H618 into the drivers/rtc/rtc-sun6i.c. I have to admit that I only partially understood the code in both places. Unfortunately the current code in drivers/clk/sunxi-ng/ccu-sun6i-rtc.c ends up with a completely unreliable box. Crashes and hangs during startup and only occasionally a successful boot. To get around that I have to patch ccu-sun6i-rtc.c the following way: Quote --- a/drivers/clk/sunxi-ng/ccu-sun6i-rtc.c +++ b/drivers/clk/sunxi-ng/ccu-sun6i-rtc.c @@ -202,7 +202,7 @@ static const struct clk_hw *osc32k_parents[] = { }; static struct clk_init_data osc32k_init_data = { - .name = "osc32k", + .name = "osc32k-out", .ops = &ccu_mux_ops, .parent_hws = osc32k_parents, .num_parents = ARRAY_SIZE(osc32k_parents), /* updated during probe */ @@ -271,13 +271,13 @@ static struct ccu_mux osc32k_fanout_clk = { }; My problem is that I have no idea why this change works Any idea is welcome. 0 Quote
Nick A Posted October 13 Posted October 13 (edited) Thanks for the update afiftyp. I'll give it a try. I thought maybe the issue was with my dts settings. Bluetooth only works when I boot into android and enable bluetooth. Then reboot back to Armbian. I don't use bluetooth much so I haven't looked into it. This code is from orange pi zero 2. https://github.com/NickAlilovic/build/blob/74d622f5b071acae4b61904e15f3da2f055c2167/patch/kernel/archive/sunxi-6.1/patches.armbian/arm64-dts-h616-add-wifi-support-for-orange-pi-zero-2.patch#L43 wifi_pwrseq: wifi-pwrseq { + compatible = "mmc-pwrseq-simple"; + clocks = <&rtc 1>; + clock-names = "osc32k-out"; + reset-gpios = <&pio 6 18 GPIO_ACTIVE_LOW>; /* PG18 */ + post-power-on-delay-ms = <200>; + }; My code is similar to orange pie. But I have a pinctrl-0 = <&x32clk_fanout_pin>; and no delay. https://github.com/NickAlilovic/build/blob/74d622f5b071acae4b61904e15f3da2f055c2167/patch/kernel/archive/sunxi-6.7/patches.armbian/arm64-dts-allwinner-h618-add-Transpeed-8K618-T-TV-box.patch#L121C1-L128C12 + wifi_pwrseq: wifi_pwrseq { + compatible = "mmc-pwrseq-simple"; + clocks = <&rtc CLK_OSC32K_FANOUT>; + clock-names = "ext_clock"; + pinctrl-0 = <&x32clk_fanout_pin>; + pinctrl-names = "default"; + reset-gpios = <&pio 6 18 GPIO_ACTIVE_LOW>; /* PG18 */ + }; This part confuses me.. clock-names = "osc32k-out"; I think it should be clock-names = "ext_clock"; Only the Armbian patches use "osc32k-out" for wifi_pwrseq clock names. I guess you can name it whatever you like it will always use &rtc 1 or &rtc CLK_OSC32K_FANOUT. https://github.com/torvalds/linux/blob/8e929cb546ee42c9a61d24fae60605e9e3192354/include/dt-bindings/clock/sun6i-rtc.h https://github.com/torvalds/linux/blob/8e929cb546ee42c9a61d24fae60605e9e3192354/drivers/mmc/core/pwrseq_simple.c#L120C20-L120C50 pwrseq->ext_clk = devm_clk_get(dev, "ext_clock"); if (IS_ERR(pwrseq->ext_clk) && PTR_ERR(pwrseq->ext_clk) != -ENOENT) return dev_err_probe(dev, PTR_ERR(pwrseq->ext_clk), "external clock not ready\n"); However, I did find the clock name "osc32k-out" in the RTC portion of h6.dtsi. The h616.dtsi doesn't have any clock-output-names. rtc: rtc@7000000 { compatible = "allwinner,sun50i-h6-rtc"; reg = <0x07000000 0x400>; interrupt-parent = <&r_intc>; interrupts = <GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>, <GIC_SPI 102 IRQ_TYPE_LEVEL_HIGH>; clock-output-names = "osc32k", "osc32k-out", "iosc"; #clock-cells = <1>; }; Also here. https://github.com/torvalds/linux/blob/6485cf5ea253d40d507cd71253c9568c5470cd27/drivers/rtc/rtc-sun6i.c#L232 static void __init sun6i_rtc_clk_init(struct device_node *node, const struct sun6i_rtc_clk_data *data) { struct clk_hw_onecell_data *clk_data; struct sun6i_rtc_dev *rtc; struct clk_init_data init = { .ops = &sun6i_rtc_osc_ops, .name = "losc", }; const char *iosc_name = "rtc-int-osc"; const char *clkout_name = "osc32k-out"; const char *parents[2]; u32 reg; of_property_read_string_index(node, "clock-output-names", 1, &clkout_name); rtc->ext_losc = clk_register_gate(NULL, clkout_name, init.name, 0, rtc->base + SUN6I_LOSC_OUT_GATING, SUN6I_LOSC_OUT_GATING_EN_OFFSET, 0, &rtc->lock); Because the there's no "clock-output-names" in the h616.dtsi.. char *clkout_name = "osc32k-out"; does not change. Maybe you accidentally used the rtc-sun6i.c clock. Edited October 14 by Nick A 0 Quote
afiftyp Posted October 14 Posted October 14 (edited) Nick, i can do a patch, but I really would like to understand why this change makes it work. In the end it would be less patching. Our sun50i-h618-transpeed-8k618-t.dtb does not have "osc32k" nor "osc32k-out" so i don't think it is dtb related. To try it, it is two additional changes: - change kernel config to CONFIG_SUN6I_RTC_CCU=y - remove the tree patches: patches.armbian/drv-rtc-sun6i-support-RTCs-without-external-LOSCs.patch patches.armbian/drv-rtc-sun6i-Add-Allwinner-H616-support.patch patches.armbian/Code-to-enable-Internal-OSC-Clock-Auto-Calibration.patch rtc-sun6i.c is still in place but it simply calls the new code in drivers/clk/sunxi-ng/ccu-sun6i-rtc.c as it no longer finds a usable RTC. Unfortunately I do not have a H616 to test how it behaves here. Edited October 15 by afiftyp Add info 0 Quote
rafman Posted October 14 Posted October 14 FYI: in the meantime of Expecting some answer from bluez guys, I download / compile and install the latest version (5.78) of bluez from their site. With the latest version i have no ( TX Errors 0x0c24) (using either android or debian firmware) But now i have --> Bluetooth: hci0: Opcode 0x0c03 failed: -110 (on both firmware) and no discoverable Device. rafman@orion-8k:~$ dmesg|grep -i blue [ 6.263046] Bluetooth: Core ver 2.22 [ 6.263152] NET: Registered PF_BLUETOOTH protocol family [ 6.263158] Bluetooth: HCI device and connection manager initialized [ 6.263178] Bluetooth: HCI socket layer initialized [ 6.263188] Bluetooth: L2CAP socket layer initialized [ 6.263204] Bluetooth: SCO socket layer initialized [ 6.440666] Bluetooth: HCI UART driver ver 2.3 [ 6.440696] Bluetooth: HCI UART protocol H4 registered [ 6.440701] Bluetooth: HCI UART protocol BCSP registered [ 6.440805] Bluetooth: HCI UART protocol LL registered [ 6.440810] Bluetooth: HCI UART protocol ATH3K registered [ 6.440840] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 6.441010] Bluetooth: HCI UART protocol Intel registered [ 6.441112] Bluetooth: HCI UART protocol Broadcom registered [ 6.441146] Bluetooth: HCI UART protocol QCA registered [ 6.441152] Bluetooth: HCI UART protocol AG6XX registered [ 6.441182] Bluetooth: HCI UART protocol Marvell registered [ 6.764123] systemd[1]: Reached target bluetooth.target - Bluetooth Support. [ 6.813233] Bluetooth: hci0: BCM: chip id 68 [ 6.819051] Bluetooth: hci0: BCM: features 0x0f [ 6.842499] Bluetooth: hci0: BCM4334B0 [ 6.842526] Bluetooth: hci0: BCM4334B0 (002.001.013) build 0000 [ 6.854934] Bluetooth: hci0: BCM4334B0 'brcm/BCM4334B0.hcd' Patch [ 12.833302] Bluetooth: hci0: BCM: features 0x0f [ 12.857635] Bluetooth: hci0: BCM4334B0 37.4MHz Class1.5 Samsung Note8-1675 [ 12.857665] Bluetooth: hci0: BCM4334B0 (002.001.013) build 1718 [ 78.123328] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 78.123353] Bluetooth: BNEP filters: protocol multicast [ 78.123371] Bluetooth: BNEP socket layer initialized [ 78.126292] Bluetooth: MGMT ver 1.22 [ 80.164838] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 201.031249] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 271.432754] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 277.992897] Bluetooth: hci0: Opcode 0x0c03 failed: -110 rafman@orion-8k:~$ bluetoothctl hci0 new_settings: bondable ssp br/edr le secure-conn [bluetooth]# Agent registered [bluetooth]# [CHG] Controller 43:34:B0:00:1F:AC Pairable: yes [bluetooth]# version Version 5.78 [bluetooth]# power on [bluetooth]# [CHG] Controller 43:34:B0:00:1F:AC PowerState: off-enabling [bluetooth]# Failed to set power on: org.bluez.Error.Failed [bluetooth]# [CHG] Controller 43:34:B0:00:1F:AC PowerState: on [bluetooth]# discoverable on [bluetooth]# Failed to set discoverable on: org.bluez.Error.Failed [bluetooth]# exit rafman@orion-8k:~$ So i am Returning to bluez 5.66 0 Quote
yi li Posted October 16 Posted October 16 @firepower hey ，I remember you had a T95ZPLUS where I made a firmware with wifi bt based on nick a's build, you can try it T95Z PLUS H618 - Allwinner CPU Boxes - Armbian Community Forums https://github.com/LYU4662/t95zplus-h618-build.git 0 Quote
firepower Posted October 16 Posted October 16 (edited) I have Tanix Tx6 and now a Vontar H618. which just arrived. I will check out your build. I cant even detect Bluetooth device. I need to dump my android DTS. looking at the AP6330 (SP6330) datasheet wifi/bt chip uses External Low Power Clock input (32.768KHz) and External Xtal Osc 26MHz. AP6330.pdf Edited October 16 by firepower 0 Quote
yi li Posted October 16 Posted October 16 That's my mistake, these two are not the same wifi model, my firmware should not work 0 Quote
L Jumadi Posted October 16 Posted October 16 @MMorales @Nick A Hi, I already success with Jefflessard version of openVfd with some minor error with my build, can check the forum if you try and have problem: Just in case you interested, I prefer it because it starting to display something when driver initialized so we early know the box starting and not hang up :) then can display timer or whatever you like after.. and setting just via bash scripting than writing other language code :) 0 Quote
firepower Posted October 16 Posted October 16 (edited) Vontar H618 PCB: FX-H618-D4_V10 23-03-21 Ram: 4GB (8 x K4B4G0446B HCK0) Rom: 64GB (KLMCG4JENB ) Wifi: HK6334Q Osc: 37.4MHz LED: FD650B-S PMIC: AXP313A Android 12 is much better than Android 9 on my Tanix Tx6, better ui and more responsive. I will test with default transpeed-8k618-t image. Edited October 16 by firepower 0 Quote
L Jumadi Posted October 16 Posted October 16 Just FYI @Nick A While working further with Jefflessard I found that all modules in your build not included in images created, Tough it compiles as module and already make the .ko file in the /sources/linux-kernel-worktree/devices. I dont know it is by design or not.. while Im afraid to update linux-kernel-image so I just copy (some modules).ko to /lib/modules/6.7.12-edge-sunxi64 run depmod and its ready to modprobe :) 0 Quote
MMorales Posted October 16 Posted October 16 thanks @L Jumadi i will give a try when i can. btw i attach a benchmark to the transpeed 4g-64 h618 for archive purpose Quote sbc-bench v0.9.67 Transpeed 8K618-T (Wed, 16 Oct 2024 11:40:59 +0200) Distributor ID: Debian Description: Armbian-unofficial 24.11.0-trunk bookworm Release: 12 Codename: bookworm Build system: https://github.com/NickAlilovic/build.git, 24.11.0-trunk, Transpeed 8k618-t, sun50iw9, sunxi64 /usr/bin/gcc (Debian 12.2.0-14) 12.2.0 Uptime: 11:40:59 up 9 min, 3 users, load average: 0.99, 0.97, 0.51, °C, 364239016 Linux 6.10.10-edge-sunxi64 (transpeed-8k618-t) 10/16/24 _aarch64_ (4 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 15.24 0.06 2.40 3.26 0.00 79.04 Device tps kB_read/s kB_wrtn/s kB_dscd/s kB_read kB_wrtn kB_dscd mmcblk1 21.95 641.63 422.69 0.00 368293 242624 0 mmcblk2 0.45 12.73 0.00 0.00 7308 0 0 zram0 0.09 2.08 0.01 0.00 1192 4 0 zram1 0.45 0.73 5.91 0.00 420 3392 0 total used free shared buff/cache available Mem: 3.8Gi 281Mi 3.6Gi 5.6Mi 75Mi 3.6Gi Swap: 1.9Gi 0B 1.9Gi Filename Type Size Used Priority /dev/zram0 partition 2012780 0 5 ########################################################################## Checking cpufreq OPP (Cortex-A53): Cpufreq OPP: 1416 Measured: 1413 (1414.040/1413.970/1413.740) Cpufreq OPP: 1320 Measured: 1318 (1318.178/1318.112/1318.046) Cpufreq OPP: 1200 Measured: 1197 (1198.000/1197.955/1197.940) Cpufreq OPP: 1104 Measured: 1101 (1101.979/1101.965/1101.937) Cpufreq OPP: 1008 Measured: 1005 (1006.017/1005.942/1005.514) Cpufreq OPP: 936 Measured: 933 (933.983/933.890/933.750) Cpufreq OPP: 720 Measured: 717 (717.999/717.990/717.819) Cpufreq OPP: 480 Measured: 477 (478.001/477.995/477.941) ########################################################################## Executing benchmark on cpu0 (Cortex-A53): tinymembench v0.4.9-nuumio (simple benchmark for memory throughput and latency) CFLAGS: bandwidth test min repeats (-b): 2 bandwidth test max repeats (-B): 3 bandwidth test mem realloc (-M): no (-m for realloc) latency test repeats (-l): 3 latency test count (-c): 1000000 ========================================================================== == Memory bandwidth tests == == == == Note 1: 1MB = 1000000 bytes == == Note 2: Test result is the best of repeated runs. Number of repeats == == is shown in brackets == == Note 3: Results for 'copy' tests show how many bytes can be == == copied per second (adding together read and writen == == bytes would have provided twice higher numbers) == == Note 4: 2-pass copy means that we are using a small temporary buffer == == to first fetch data into it, and only then write it to the == == destination (source -> L1 cache, L1 cache -> destination) == == Note 5: If sample standard deviation exceeds 0.1%, it is shown in == == brackets == ========================================================================== C copy backwards : 1225.1 MB/s (3, 8.7%) C copy backwards (32 byte blocks) : 1231.9 MB/s (3, 0.6%) C copy backwards (64 byte blocks) : 1223.8 MB/s (3, 0.1%) C copy : 1191.8 MB/s (3, 0.5%) C copy prefetched (32 bytes step) : 952.1 MB/s (3, 1.2%) C copy prefetched (64 bytes step) : 1036.7 MB/s (3) C 2-pass copy : 1115.5 MB/s (2) C 2-pass copy prefetched (32 bytes step) : 784.9 MB/s (2) C 2-pass copy prefetched (64 bytes step) : 733.4 MB/s (3, 0.2%) C scan 8 : 275.9 MB/s (2) C scan 16 : 539.6 MB/s (3, 0.3%) C scan 32 : 1007.9 MB/s (3, 0.2%) C scan 64 : 1501.3 MB/s (3, 0.3%) C fill : 3480.1 MB/s (3, 1.1%) C fill (shuffle within 16 byte blocks) : 3490.3 MB/s (3, 0.3%) C fill (shuffle within 32 byte blocks) : 3488.3 MB/s (2) C fill (shuffle within 64 byte blocks) : 3489.9 MB/s (2) --- libc memcpy copy : 1226.4 MB/s (2) libc memchr scan : 1445.5 MB/s (3, 0.5%) libc memset fill : 3482.6 MB/s (3, 1.1%) --- NEON LDP/STP copy : 1236.5 MB/s (3, 0.6%) NEON LDP/STP copy pldl2strm (32 bytes step) : 849.6 MB/s (3, 1.3%) NEON LDP/STP copy pldl2strm (64 bytes step) : 1063.3 MB/s (2) NEON LDP/STP copy pldl1keep (32 bytes step) : 1379.1 MB/s (3) NEON LDP/STP copy pldl1keep (64 bytes step) : 1377.2 MB/s (3, 0.8%) NEON LD1/ST1 copy : 1224.9 MB/s (3, 0.5%) NEON LDP load : 1979.7 MB/s (2) NEON LDNP load : 1567.4 MB/s (3, 0.1%) NEON STP fill : 3489.9 MB/s (3, 0.5%) NEON STNP fill : 2086.8 MB/s (3, 1.0%) ARM LDP/STP copy : 1236.5 MB/s (3, 0.3%) ARM LDP load : 1981.3 MB/s (2) ARM LDNP load : 1567.4 MB/s (3, 0.1%) ARM STP fill : 3490.1 MB/s (3, 0.6%) ARM STNP fill : 2093.3 MB/s (3, 1.5%) ========================================================================== == Framebuffer read tests. == == == == Many ARM devices use a part of the system memory as the framebuffer, == == typically mapped as uncached but with write-combining enabled. == == Writes to such framebuffers are quite fast, but reads are much == == slower and very sensitive to the alignment and the selection of == == CPU instructions which are used for accessing memory. == == == == Many x86 systems allocate the framebuffer in the GPU memory, == == accessible for the CPU via a relatively slow PCI-E bus. Moreover, == == PCI-E is asymmetric and handles reads a lot worse than writes. == == == == If uncached framebuffer reads are reasonably fast (at least 100 MB/s == == or preferably >300 MB/s), then using the shadow framebuffer layer == == is not necessary in Xorg DDX drivers, resulting in a nice overall == == performance improvement. For example, the xf86-video-fbturbo DDX == == uses this trick. == ========================================================================== NEON LDP/STP copy (from framebuffer) : 175.5 MB/s (2) NEON LDP/STP 2-pass copy (from framebuffer) : 168.3 MB/s (2) NEON LD1/ST1 copy (from framebuffer) : 45.2 MB/s (2) NEON LD1/ST1 2-pass copy (from framebuffer) : 44.7 MB/s (3, 0.2%) ARM LDP/STP copy (from framebuffer) : 89.6 MB/s (2) ARM LDP/STP 2-pass copy (from framebuffer) : 87.7 MB/s (2) ========================================================================== == Memory latency test == == == == Average time is measured for random memory accesses in the buffers == == of different sizes. The larger is the buffer, the more significant == == are relative contributions of TLB, L1/L2 cache misses and SDRAM == == accesses. For extremely large buffer sizes we are expecting to see == == page table walk with several requests to SDRAM for almost every == == memory access (though 64MiB is not nearly large enough to experience == == this effect to its fullest). == == == == Note 1: All the numbers are representing extra time, which needs to == == be added to L1 cache latency. The cycle timings for L1 cache == == latency can be usually found in the processor documentation. == == Note 2: Dual random read means that we are simultaneously performing == == two independent memory accesses at a time. In the case if == == the memory subsystem can't handle multiple outstanding == == requests, dual random read has the same timings as two == == single reads performed one after another. == ========================================================================== block size : single random read / dual random read, [MADV_NOHUGEPAGE] 1024 : 0.0 ns / 0.0 ns 2048 : 0.0 ns / 0.0 ns 4096 : 0.0 ns / 0.0 ns 8192 : 0.0 ns / 0.0 ns 16384 : 0.0 ns / 0.0 ns 32768 : 0.1 ns / 0.0 ns 65536 : 4.7 ns / 7.9 ns 131072 : 7.3 ns / 11.1 ns 262144 : 8.9 ns / 12.4 ns 524288 : 10.4 ns / 13.0 ns 1048576 : 29.0 ns / 45.4 ns 2097152 : 99.0 ns / 149.7 ns 4194304 : 147.4 ns / 196.7 ns 8388608 : 172.8 ns / 213.7 ns 16777216 : 186.6 ns / 222.0 ns 33554432 : 194.0 ns / 226.8 ns 67108864 : 198.0 ns / 229.7 ns block size : single random read / dual random read, [MADV_HUGEPAGE] 1024 : 0.0 ns / 0.0 ns 2048 : 0.0 ns / 0.0 ns 4096 : 0.0 ns / 0.0 ns 8192 : 0.0 ns / 0.0 ns 16384 : 0.0 ns / 0.0 ns 32768 : 0.1 ns / 0.0 ns 65536 : 4.7 ns / 7.9 ns 131072 : 7.3 ns / 11.1 ns 262144 : 8.9 ns / 12.4 ns 524288 : 10.4 ns / 13.1 ns 1048576 : 13.6 ns / 14.7 ns 2097152 : 98.3 ns / 148.2 ns 4194304 : 140.7 ns / 188.3 ns 8388608 : 162.3 ns / 200.7 ns 16777216 : 172.7 ns / 205.3 ns 33554432 : 177.9 ns / 207.3 ns 67108864 : 180.7 ns / 208.0 ns ########################################################################## Executing ramlat on cpu0 (Cortex-A53), results in ns: size: 1x32 2x32 1x64 2x64 1xPTR 2xPTR 4xPTR 8xPTR 4k: 2.842 2.865 2.134 2.126 2.122 2.123 2.918 5.924 8k: 2.830 2.830 2.123 2.122 2.122 2.122 2.918 5.927 16k: 2.833 2.831 2.130 2.123 2.125 2.123 2.920 5.928 32k: 11.27 13.89 11.65 13.44 11.64 13.53 17.51 30.19 64k: 16.75 17.23 16.01 17.04 16.01 17.20 23.18 45.06 128k: 17.37 18.54 16.97 17.94 16.94 17.91 27.23 54.16 256k: 20.16 20.90 19.78 20.25 19.76 20.29 27.57 54.24 512k: 23.20 23.75 22.66 23.36 22.65 23.78 27.87 54.62 1024k: 47.23 58.25 46.26 58.80 46.46 58.82 87.05 166.8 2048k: 180.3 186.3 177.5 181.4 177.1 181.0 256.7 508.6 4096k: 196.0 200.1 195.2 196.5 195.2 195.4 266.4 529.4 8192k: 195.9 197.2 194.8 195.9 195.2 195.1 269.5 529.1 16384k: 199.0 200.3 197.7 199.8 197.8 199.3 270.0 545.3 32768k: 205.6 205.9 202.1 205.8 202.0 205.9 276.5 555.2 65536k: 199.8 202.5 201.7 201.8 199.0 202.6 273.3 546.7 131072k: 200.5 202.4 199.4 202.3 206.6 202.2 273.1 545.0 ########################################################################## Executing benchmark twice on cluster 0 (Cortex-A53) OpenSSL 3.0.14, built on 4 Jun 2024 (Library: OpenSSL 3.0.14 4 Jun 2024) type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes aes-128-cbc 101502.19k 316819.37k 654948.69k 927581.18k 1054894.76k 1064763.39k aes-128-cbc 101662.68k 316789.91k 654933.59k 927563.09k 1054635.35k 1056593.24k aes-192-cbc 98116.06k 287014.10k 543429.97k 720182.27k 795118.25k 800156.33k aes-192-cbc 97691.46k 286572.69k 542621.61k 719602.35k 794946.22k 800751.62k aes-256-cbc 95031.92k 265476.91k 474354.01k 604318.38k 656566.95k 657462.61k aes-256-cbc 95338.91k 266504.66k 474870.61k 604666.20k 656610.65k 660373.50k ########################################################################## Executing benchmark single-threaded on cpu0 (Cortex-A53) 7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=C,Utf16=off,HugeFiles=on,64 bits,4 CPUs LE) LE CPU Freq: 64000000 - - - - - - - - RAM size: 3931 MB, # CPU hardware threads: 4 RAM usage: 435 MB, # Benchmark threads: 1 Compressing | Decompressing Dict Speed Usage R/U Rating | Speed Usage R/U Rating KiB/s % MIPS MIPS | KiB/s % MIPS MIPS 22: 866 100 844 843 | 15743 100 1345 1344 23: 828 100 844 844 | 15422 100 1336 1335 24: 797 100 858 857 | 15094 100 1326 1325 25: 755 100 863 862 | 14708 100 1310 1309 ---------------------------------- | ------------------------------ Avr: 100 852 851 | 100 1329 1328 Tot: 100 1091 1090 ########################################################################## Executing benchmark 3 times multi-threaded on CPUs 0-3 7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=C,Utf16=off,HugeFiles=on,64 bits,4 CPUs LE) LE CPU Freq: - - - - - - - - - RAM size: 3931 MB, # CPU hardware threads: 4 RAM usage: 882 MB, # Benchmark threads: 4 Compressing | Decompressing Dict Speed Usage R/U Rating | Speed Usage R/U Rating KiB/s % MIPS MIPS | KiB/s % MIPS MIPS 22: 2345 335 680 2282 | 60703 398 1300 5179 23: 2328 351 675 2373 | 59386 399 1288 5138 24: 2288 362 681 2461 | 57999 399 1277 5092 25: 2220 371 684 2536 | 56556 399 1262 5033 ---------------------------------- | ------------------------------ Avr: 355 680 2413 | 399 1282 5111 Tot: 377 981 3762 7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=C,Utf16=off,HugeFiles=on,64 bits,4 CPUs LE) LE CPU Freq: - 64000000 - - - 256000000 - - - RAM size: 3931 MB, # CPU hardware threads: 4 RAM usage: 882 MB, # Benchmark threads: 4 Compressing | Decompressing Dict Speed Usage R/U Rating | Speed Usage R/U Rating KiB/s % MIPS MIPS | KiB/s % MIPS MIPS 22: 2411 343 685 2346 | 60967 399 1303 5201 23: 2320 350 675 2364 | 59463 399 1290 5145 24: 2280 361 680 2452 | 58015 399 1277 5093 25: 2226 372 684 2542 | 56666 399 1264 5043 ---------------------------------- | ------------------------------ Avr: 356 681 2426 | 399 1283 5121 Tot: 378 982 3773 7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=C,Utf16=off,HugeFiles=on,64 bits,4 CPUs LE) LE CPU Freq: - - - - - - - - - RAM size: 3931 MB, # CPU hardware threads: 4 RAM usage: 882 MB, # Benchmark threads: 4 Compressing | Decompressing Dict Speed Usage R/U Rating | Speed Usage R/U Rating KiB/s % MIPS MIPS | KiB/s % MIPS MIPS 22: 2404 341 685 2339 | 60716 398 1301 5180 23: 2320 351 674 2364 | 59466 399 1289 5145 24: 2280 361 680 2452 | 58007 399 1277 5092 25: 2227 372 684 2543 | 56451 399 1260 5024 ---------------------------------- | ------------------------------ Avr: 356 681 2424 | 399 1282 5110 Tot: 377 981 3767 Compression: 2413,2426,2424 Decompression: 5111,5121,5110 Total: 3762,3773,3767 ########################################################################## ** cpuminer-multi 1.3.7 by tpruvot@github ** BTC donation address: 1FhDPLPpw18X4srecguG3MxJYe4a1JsZnd (tpruvot) [2024-10-16 11:53:47] 4 miner threads started, using 'scrypt' algorithm. [2024-10-16 11:53:47] CPU #0: 1.32 kH/s [2024-10-16 11:53:47] CPU #3: 1.26 kH/s [2024-10-16 11:53:47] CPU #1: 1.16 kH/s [2024-10-16 11:53:47] CPU #2: 0.98 kH/s [2024-10-16 11:53:52] Total: 5.24 kH/s [2024-10-16 11:53:57] CPU #3: 1.38 kH/s [2024-10-16 11:53:57] Total: 5.44 kH/s [2024-10-16 11:53:57] CPU #0: 1.38 kH/s [2024-10-16 11:53:57] CPU #2: 1.38 kH/s [2024-10-16 11:53:57] CPU #1: 1.38 kH/s [2024-10-16 11:54:02] Total: 5.50 kH/s [2024-10-16 11:54:07] CPU #3: 1.38 kH/s [2024-10-16 11:54:07] Total: 5.50 kH/s [2024-10-16 11:54:07] CPU #0: 1.38 kH/s [2024-10-16 11:54:07] CPU #2: 1.38 kH/s [2024-10-16 11:54:07] CPU #1: 1.38 kH/s [2024-10-16 11:54:12] Total: 5.50 kH/s [2024-10-16 11:54:17] CPU #3: 1.38 kH/s [2024-10-16 11:54:17] Total: 5.50 kH/s [2024-10-16 11:54:17] CPU #0: 1.38 kH/s [2024-10-16 11:54:17] CPU #2: 1.38 kH/s [2024-10-16 11:54:17] CPU #1: 1.38 kH/s [2024-10-16 11:54:22] Total: 5.50 kH/s [2024-10-16 11:54:27] CPU #3: 1.38 kH/s [2024-10-16 11:54:27] Total: 5.50 kH/s [2024-10-16 11:54:27] CPU #0: 1.38 kH/s [2024-10-16 11:54:27] CPU #2: 1.38 kH/s [2024-10-16 11:54:27] CPU #1: 1.38 kH/s [2024-10-16 11:54:32] Total: 5.50 kH/s [2024-10-16 11:54:37] CPU #3: 1.37 kH/s [2024-10-16 11:54:37] Total: 5.49 kH/s [2024-10-16 11:54:37] CPU #0: 1.38 kH/s [2024-10-16 11:54:37] CPU #2: 1.37 kH/s [2024-10-16 11:54:37] CPU #1: 1.38 kH/s [2024-10-16 11:54:42] Total: 5.50 kH/s [2024-10-16 11:54:47] CPU #3: 1.38 kH/s [2024-10-16 11:54:47] Total: 5.50 kH/s [2024-10-16 11:54:47] CPU #0: 1.38 kH/s [2024-10-16 11:54:47] CPU #2: 1.38 kH/s [2024-10-16 11:54:47] CPU #1: 1.38 kH/s [2024-10-16 11:54:52] Total: 5.50 kH/s [2024-10-16 11:54:57] CPU #3: 1.38 kH/s [2024-10-16 11:54:57] Total: 5.50 kH/s [2024-10-16 11:54:57] CPU #0: 1.38 kH/s [2024-10-16 11:54:57] CPU #2: 1.38 kH/s [2024-10-16 11:54:57] CPU #1: 1.38 kH/s [2024-10-16 11:55:02] Total: 5.50 kH/s [2024-10-16 11:55:07] CPU #3: 1.38 kH/s [2024-10-16 11:55:07] Total: 5.50 kH/s [2024-10-16 11:55:07] CPU #0: 1.38 kH/s [2024-10-16 11:55:07] CPU #2: 1.38 kH/s [2024-10-16 11:55:07] CPU #1: 1.38 kH/s [2024-10-16 11:55:12] Total: 5.50 kH/s [2024-10-16 11:55:17] CPU #3: 1.37 kH/s [2024-10-16 11:55:17] Total: 5.50 kH/s [2024-10-16 11:55:17] CPU #0: 1.37 kH/s [2024-10-16 11:55:17] CPU #2: 1.37 kH/s [2024-10-16 11:55:17] CPU #1: 1.37 kH/s [2024-10-16 11:55:22] Total: 5.49 kH/s [2024-10-16 11:55:27] CPU #3: 1.38 kH/s [2024-10-16 11:55:27] Total: 5.50 kH/s [2024-10-16 11:55:27] CPU #0: 1.38 kH/s [2024-10-16 11:55:27] CPU #2: 1.38 kH/s [2024-10-16 11:55:27] CPU #1: 1.37 kH/s [2024-10-16 11:55:32] Total: 5.50 kH/s [2024-10-16 11:55:37] CPU #3: 1.38 kH/s [2024-10-16 11:55:37] Total: 5.50 kH/s [2024-10-16 11:55:37] CPU #0: 1.37 kH/s [2024-10-16 11:55:37] CPU #2: 1.38 kH/s [2024-10-16 11:55:37] CPU #1: 1.38 kH/s [2024-10-16 11:55:42] Total: 5.50 kH/s [2024-10-16 11:55:47] CPU #3: 1.38 kH/s [2024-10-16 11:55:47] Total: 5.50 kH/s [2024-10-16 11:55:47] CPU #0: 1.37 kH/s [2024-10-16 11:55:47] CPU #2: 1.38 kH/s [2024-10-16 11:55:47] CPU #1: 1.38 kH/s [2024-10-16 11:55:52] Total: 5.50 kH/s [2024-10-16 11:55:57] CPU #3: 1.37 kH/s [2024-10-16 11:55:57] Total: 5.50 kH/s [2024-10-16 11:55:57] CPU #0: 1.37 kH/s [2024-10-16 11:55:57] CPU #2: 1.37 kH/s [2024-10-16 11:55:57] CPU #1: 1.37 kH/s [2024-10-16 11:56:02] Total: 5.49 kH/s [2024-10-16 11:56:07] CPU #3: 1.38 kH/s [2024-10-16 11:56:07] Total: 5.50 kH/s [2024-10-16 11:56:07] CPU #0: 1.38 kH/s [2024-10-16 11:56:07] CPU #2: 1.38 kH/s [2024-10-16 11:56:07] CPU #1: 1.38 kH/s [2024-10-16 11:56:12] Total: 5.50 kH/s [2024-10-16 11:56:17] CPU #3: 1.38 kH/s [2024-10-16 11:56:17] Total: 5.50 kH/s [2024-10-16 11:56:17] CPU #0: 1.38 kH/s [2024-10-16 11:56:17] CPU #2: 1.38 kH/s [2024-10-16 11:56:17] CPU #1: 1.38 kH/s [2024-10-16 11:56:22] Total: 5.50 kH/s [2024-10-16 11:56:27] CPU #3: 1.38 kH/s [2024-10-16 11:56:27] Total: 5.50 kH/s [2024-10-16 11:56:27] CPU #0: 1.38 kH/s [2024-10-16 11:56:27] CPU #2: 1.38 kH/s [2024-10-16 11:56:27] CPU #1: 1.38 kH/s [2024-10-16 11:56:32] Total: 5.50 kH/s [2024-10-16 11:56:37] CPU #3: 1.38 kH/s [2024-10-16 11:56:37] Total: 5.50 kH/s [2024-10-16 11:56:37] CPU #0: 1.38 kH/s [2024-10-16 11:56:37] CPU #2: 1.38 kH/s [2024-10-16 11:56:37] CPU #1: 1.37 kH/s [2024-10-16 11:56:42] Total: 5.50 kH/s [2024-10-16 11:56:47] CPU #3: 1.38 kH/s [2024-10-16 11:56:47] Total: 5.49 kH/s [2024-10-16 11:56:47] CPU #0: 1.38 kH/s [2024-10-16 11:56:47] CPU #2: 1.38 kH/s [2024-10-16 11:56:47] CPU #1: 1.38 kH/s [2024-10-16 11:56:52] Total: 5.50 kH/s [2024-10-16 11:56:56] CPU #3: 1.38 kH/s [2024-10-16 11:56:56] Total: 5.50 kH/s [2024-10-16 11:56:57] CPU #0: 1.38 kH/s [2024-10-16 11:56:57] CPU #2: 1.38 kH/s [2024-10-16 11:56:57] CPU #1: 1.38 kH/s [2024-10-16 11:56:57] Total: 5.50 kH/s [2024-10-16 11:57:03] CPU #3: 1.38 kH/s [2024-10-16 11:57:03] Total: 5.50 kH/s [2024-10-16 11:57:07] Total: 5.50 kH/s [2024-10-16 11:57:07] CPU #0: 1.38 kH/s [2024-10-16 11:57:07] CPU #2: 1.38 kH/s [2024-10-16 11:57:07] CPU #1: 1.38 kH/s [2024-10-16 11:57:12] CPU #3: 1.38 kH/s [2024-10-16 11:57:12] Total: 5.50 kH/s [2024-10-16 11:57:17] Total: 5.50 kH/s [2024-10-16 11:57:17] CPU #0: 1.38 kH/s [2024-10-16 11:57:17] CPU #2: 1.38 kH/s [2024-10-16 11:57:17] CPU #1: 1.38 kH/s [2024-10-16 11:57:22] CPU #3: 1.37 kH/s [2024-10-16 11:57:22] Total: 5.50 kH/s [2024-10-16 11:57:26] Total: 5.49 kH/s [2024-10-16 11:57:27] CPU #0: 1.38 kH/s [2024-10-16 11:57:27] CPU #2: 1.38 kH/s [2024-10-16 11:57:27] CPU #1: 1.38 kH/s [2024-10-16 11:57:27] Total: 5.50 kH/s [2024-10-16 11:57:32] CPU #3: 1.38 kH/s [2024-10-16 11:57:32] Total: 5.50 kH/s [2024-10-16 11:57:37] CPU #0: 1.38 kH/s [2024-10-16 11:57:37] CPU #2: 1.38 kH/s [2024-10-16 11:57:37] CPU #1: 1.37 kH/s [2024-10-16 11:57:37] Total: 5.50 kH/s [2024-10-16 11:57:42] CPU #3: 1.38 kH/s [2024-10-16 11:57:42] Total: 5.50 kH/s [2024-10-16 11:57:47] CPU #0: 1.38 kH/s [2024-10-16 11:57:47] CPU #2: 1.38 kH/s [2024-10-16 11:57:47] CPU #1: 1.38 kH/s [2024-10-16 11:57:47] Total: 5.50 kH/s [2024-10-16 11:57:52] CPU #3: 1.38 kH/s [2024-10-16 11:57:52] Total: 5.50 kH/s [2024-10-16 11:57:57] CPU #0: 1.38 kH/s [2024-10-16 11:57:57] CPU #2: 1.38 kH/s [2024-10-16 11:57:57] CPU #1: 1.38 kH/s [2024-10-16 11:57:57] Total: 5.50 kH/s [2024-10-16 11:58:02] CPU #3: 1.37 kH/s [2024-10-16 11:58:02] Total: 5.50 kH/s [2024-10-16 11:58:07] CPU #0: 1.37 kH/s [2024-10-16 11:58:07] CPU #2: 1.37 kH/s [2024-10-16 11:58:07] CPU #1: 1.37 kH/s [2024-10-16 11:58:08] CPU #3: 1.37 kH/s [2024-10-16 11:58:08] Total: 5.49 kH/s [2024-10-16 11:58:11] Total: 5.49 kH/s [2024-10-16 11:58:12] Total: 5.50 kH/s [2024-10-16 11:58:17] CPU #0: 1.38 kH/s [2024-10-16 11:58:17] CPU #2: 1.38 kH/s [2024-10-16 11:58:17] CPU #1: 1.38 kH/s [2024-10-16 11:58:17] CPU #3: 1.38 kH/s [2024-10-16 11:58:17] Total: 5.50 kH/s [2024-10-16 11:58:22] Total: 5.50 kH/s [2024-10-16 11:58:27] CPU #0: 1.38 kH/s [2024-10-16 11:58:27] CPU #2: 1.38 kH/s [2024-10-16 11:58:27] CPU #1: 1.38 kH/s [2024-10-16 11:58:27] CPU #3: 1.38 kH/s [2024-10-16 11:58:27] Total: 5.50 kH/s [2024-10-16 11:58:32] Total: 5.50 kH/s [2024-10-16 11:58:37] CPU #0: 1.38 kH/s [2024-10-16 11:58:37] CPU #2: 1.38 kH/s [2024-10-16 11:58:37] CPU #1: 1.38 kH/s [2024-10-16 11:58:37] CPU #3: 1.38 kH/s [2024-10-16 11:58:37] Total: 5.50 kH/s [2024-10-16 11:58:42] Total: 5.50 kH/s Total Scores: 5.50,5.49 ########################################################################## Testing maximum cpufreq again, still under full load. System health now: Time CPU load %cpu %sys %usr %nice %io %irq Temp 11:58:46: 1416MHz 4.01 100% 0% 99% 0% 0% 0% °C Checking cpufreq OPP (Cortex-A53): Cpufreq OPP: 1416 Measured: 1413 (1413.983/1413.877/1413.754) ########################################################################## System health while running tinymembench: Time CPU load %cpu %sys %usr %nice %io %irq Temp 11:41:37: 1416MHz 0.99 21% 2% 15% 0% 3% 0% °C 11:41:47: 1416MHz 1.00 25% 0% 25% 0% 0% 0% °C 11:41:57: 1416MHz 1.00 25% 0% 25% 0% 0% 0% °C 11:42:08: 1416MHz 1.00 25% 0% 25% 0% 0% 0% °C 11:42:18: 1416MHz 1.00 25% 0% 25% 0% 0% 0% °C 11:42:28: 1416MHz 1.00 25% 0% 25% 0% 0% 0% °C 11:42:38: 1416MHz 1.00 25% 0% 25% 0% 0% 0% °C 11:42:48: 1416MHz 1.00 25% 0% 25% 0% 0% 0% °C 11:42:58: 1416MHz 1.00 25% 0% 25% 0% 0% 0% °C 11:43:09: 1416MHz 1.00 25% 0% 24% 0% 0% 0% °C 11:43:19: 1416MHz 1.00 25% 0% 24% 0% 0% 0% °C System health while running ramlat: Time CPU load %cpu %sys %usr %nice %io %irq Temp 11:43:24: 1416MHz 1.00 21% 2% 17% 0% 2% 0% °C 11:43:27: 1416MHz 1.00 25% 0% 25% 0% 0% 0% °C 11:43:30: 1416MHz 1.00 25% 0% 25% 0% 0% 0% °C 11:43:33: 1416MHz 1.00 25% 0% 25% 0% 0% 0% °C 11:43:36: 1416MHz 1.00 25% 0% 24% 0% 0% 0% °C 11:43:39: 1416MHz 1.00 25% 0% 25% 0% 0% 0% °C 11:43:42: 1416MHz 1.00 25% 0% 25% 0% 0% 0% °C 11:43:46: 1416MHz 1.00 25% 0% 24% 0% 0% 0% °C 11:43:49: 1416MHz 1.00 25% 0% 24% 0% 0% 0% °C 11:43:52: 1416MHz 1.00 25% 0% 24% 0% 0% 0% °C 11:43:55: 1416MHz 1.00 25% 0% 24% 0% 0% 0% °C System health while running OpenSSL benchmark: Time CPU load %cpu %sys %usr %nice %io %irq Temp 11:43:57: 1416MHz 1.00 22% 1% 17% 0% 2% 0% °C 11:44:13: 1416MHz 1.00 25% 0% 24% 0% 0% 0% °C 11:44:29: 1416MHz 1.00 25% 0% 25% 0% 0% 0% °C 11:44:45: 1416MHz 1.00 25% 0% 24% 0% 0% 0% °C 11:45:01: 1416MHz 1.16 25% 0% 25% 0% 0% 0% °C 11:45:17: 1416MHz 1.12 25% 0% 25% 0% 0% 0% °C 11:45:34: 1416MHz 1.10 25% 0% 24% 0% 0% 0% °C System health while running 7-zip single core benchmark: Time CPU load %cpu %sys %usr %nice %io %irq Temp 11:45:45: 1416MHz 1.08 22% 1% 18% 0% 2% 0% °C 11:45:56: 1416MHz 1.06 25% 0% 24% 0% 0% 0% °C 11:46:07: 1416MHz 1.05 25% 0% 24% 0% 0% 0% °C 11:46:19: 1416MHz 1.04 25% 0% 24% 0% 0% 0% °C 11:46:30: 1416MHz 1.04 25% 0% 24% 0% 0% 0% °C 11:46:41: 1416MHz 1.03 25% 0% 24% 0% 0% 0% °C 11:46:52: 1416MHz 1.02 25% 0% 24% 0% 0% 0% °C 11:47:03: 1416MHz 1.02 25% 0% 24% 0% 0% 0% °C 11:47:14: 1416MHz 1.02 25% 0% 24% 0% 0% 0% °C 11:47:25: 1416MHz 1.01 25% 0% 24% 0% 0% 0% °C 11:47:36: 1416MHz 1.01 25% 0% 24% 0% 0% 0% °C 11:47:47: 1416MHz 1.01 25% 0% 24% 0% 0% 0% °C 11:47:58: 1416MHz 1.01 25% 0% 24% 0% 0% 0% °C System health while running 7-zip multi core benchmark: Time CPU load %cpu %sys %usr %nice %io %irq Temp 11:48:04: 1416MHz 1.00 22% 1% 19% 0% 1% 0% °C 11:48:27: 1416MHz 1.90 92% 0% 92% 0% 0% 0% °C 11:48:50: 1416MHz 2.44 92% 0% 91% 0% 0% 0% °C 11:49:15: 1416MHz 3.11 95% 1% 94% 0% 0% 0% °C 11:49:39: 1416MHz 3.26 88% 1% 86% 0% 0% 0% °C 11:50:02: 1416MHz 3.59 95% 1% 93% 0% 0% 0% °C 11:50:25: 1416MHz 3.65 92% 0% 92% 0% 0% 0% °C 11:50:48: 1416MHz 3.79 92% 0% 91% 0% 0% 0% °C 11:51:11: 1416MHz 3.96 93% 1% 91% 0% 0% 0% °C 11:51:35: 1416MHz 4.15 92% 2% 90% 0% 0% 0% °C 11:51:59: 1416MHz 4.15 94% 1% 93% 0% 0% 0% °C 11:52:22: 1416MHz 4.41 93% 0% 92% 0% 0% 0% °C 11:52:45: 1416MHz 4.21 92% 0% 91% 0% 0% 0% °C 11:53:08: 1416MHz 4.07 92% 1% 90% 0% 0% 0% °C 11:53:31: 1416MHz 4.00 94% 1% 92% 0% 0% 0% °C System health while running cpuminer: Time CPU load %cpu %sys %usr %nice %io %irq Temp 11:53:50: 1416MHz 4.19 41% 1% 38% 0% 1% 0% °C 11:54:32: 1416MHz 4.10 100% 0% 99% 0% 0% 0% °C 11:55:15: 1416MHz 4.08 100% 0% 99% 0% 0% 0% °C 11:55:57: 1416MHz 4.04 100% 0% 99% 0% 0% 0% °C 11:56:39: 1416MHz 4.10 100% 0% 99% 0% 0% 0% °C 11:57:21: 1416MHz 4.05 100% 0% 99% 0% 0% 0% °C 11:58:03: 1416MHz 4.02 100% 0% 99% 0% 0% 0% °C 11:58:46: 1416MHz 4.01 100% 0% 99% 0% 0% 0% °C ########################################################################## Linux 6.10.10-edge-sunxi64 (transpeed-8k618-t) 10/16/24 _aarch64_ (4 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 49.24 0.03 1.24 1.15 0.00 48.34 Device tps kB_read/s kB_wrtn/s kB_dscd/s kB_read kB_wrtn kB_dscd mmcblk1 7.92 228.69 147.90 0.00 376513 243508 0 mmcblk2 0.16 4.44 0.00 0.00 7308 0 0 zram0 0.03 0.72 0.00 0.00 1192 4 0 zram1 0.17 0.26 2.11 0.00 436 3480 0 total used free shared buff/cache available Mem: 3.8Gi 304Mi 3.6Gi 5.7Mi 84Mi 3.5Gi Swap: 1.9Gi 0B 1.9Gi Filename Type Size Used Priority /dev/zram0 partition 2012780 0 5 CPU sysfs topology (clusters, cpufreq members, clockspeeds) cpufreq min max CPU cluster policy speed speed core type 0 0 0 480 1416 Cortex-A53 / r0p4 1 0 0 480 1416 Cortex-A53 / r0p4 2 0 0 480 1416 Cortex-A53 / r0p4 3 0 0 480 1416 Cortex-A53 / r0p4 Architecture: aarch64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Vendor ID: ARM Model name: Cortex-A53 Model: 4 Thread(s) per core: 1 Core(s) per cluster: 4 Socket(s): - Cluster(s): 1 Stepping: r0p4 CPU(s) scaling MHz: 100% CPU max MHz: 1416.0000 CPU min MHz: 480.0000 BogoMIPS: 48.00 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid NUMA node(s): 1 NUMA node0 CPU(s): 0-3 Vulnerability Gather data sampling: Not affected Vulnerability Itlb multihit: Not affected Vulnerability L1tf: Not affected Vulnerability Mds: Not affected Vulnerability Meltdown: Not affected Vulnerability Mmio stale data: Not affected Vulnerability Reg file data sampling: Not affected Vulnerability Retbleed: Not affected Vulnerability Spec rstack overflow: Not affected Vulnerability Spec store bypass: Not affected Vulnerability Spectre v1: Mitigation; __user pointer sanitization Vulnerability Spectre v2: Not affected Vulnerability Srbds: Not affected Vulnerability Tsx async abort: Not affected SoC guess: Allwinner H618 (SID: 33802100) DT compat: transpeed,8k618-t allwinner,sun50i-h618 Compiler: /usr/bin/gcc (Debian 12.2.0-14) 12.2.0 / aarch64-linux-gnu Userland: arm64 Kernel: 6.10.10-edge-sunxi64/aarch64 CONFIG_HZ=250 CONFIG_HZ_250=y CONFIG_PREEMPT_NONE=y CONFIG_PREEMPT_NONE_BUILD=y ########################################################################## vdd-cpu: 1100 mV (1100 mV max) vdd-gpu-sys: 900 mV (990 mV max) opp-table-cpu: 480 MHz 900.0 mV (001f) 600 MHz 900.0 mV (0012) 720 MHz 900.0 mV (000d) 792 MHz - 936 MHz 900.0 mV (000d) 1008 MHz 950.0 mV 940.0 mV 950.0 mV 950.0 mV 1020.0 mV 1104 MHz 1000.0 mV 1000.0 mV 1000.0 mV 1200 MHz 1050.0 mV 1020.0 mV 1050.0 mV 1050.0 mV 1100.0 mV 1320 MHz 1100.0 mV (001d) 1416 MHz 1100.0 mV (000d) 1512 MHz - ########################################################################## Results validation: * Measured clockspeed not lower than advertised max CPU clockspeed * No swapping * Background activity (%system) OK * No throttling | Transpeed 8K618-T | 1416 MHz | 6.10 | Debian 12 (bookworm) tampered by Armbian-unofficial 24.11.0-trunk bookworm arm64 | 3770 | 1090 | 658920 | 1230 | 3480 | 5.49 | 0 Quote
firepower Posted October 16 Posted October 16 (edited) Vontar H618 working with transpeed,8k618-t image. wifi working with brcmfmac4334-sdio.transpeed,8k618-t.bin bluetooth does not work but icon appears in task bar Quote dmesg | grep -i bluetooth [ 9.796905] Bluetooth: Core ver 2.22 [ 9.797049] NET: Registered PF_BLUETOOTH protocol family [ 9.797056] Bluetooth: HCI device and connection manager initialized [ 9.797075] Bluetooth: HCI socket layer initialized [ 9.797083] Bluetooth: L2CAP socket layer initialized [ 9.797099] Bluetooth: SCO socket layer initialized [ 10.163407] Bluetooth: HCI UART driver ver 2.3 [ 10.163437] Bluetooth: HCI UART protocol H4 registered [ 10.163442] Bluetooth: HCI UART protocol BCSP registered [ 10.163538] Bluetooth: HCI UART protocol LL registered [ 10.163543] Bluetooth: HCI UART protocol ATH3K registered [ 10.163575] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 10.163735] Bluetooth: HCI UART protocol Intel registered [ 10.163822] Bluetooth: HCI UART protocol Broadcom registered [ 10.163855] Bluetooth: HCI UART protocol QCA registered [ 10.163860] Bluetooth: HCI UART protocol AG6XX registered [ 10.163890] Bluetooth: HCI UART protocol Marvell registered [ 10.525559] Bluetooth: hci0: BCM: chip id 68 [ 10.527984] Bluetooth: hci0: BCM: features 0x0f [ 10.551386] Bluetooth: hci0: BCM4334B0 [ 10.551413] Bluetooth: hci0: BCM4334B0 (002.001.013) build 0000 [ 10.559864] Bluetooth: hci0: BCM4334B0 'brcm/BCM4334B0.hcd' Patch [ 15.137586] Bluetooth: hci0: BCM: features 0x0f [ 15.161136] Bluetooth: hci0: BCM4334B1 37.4 MHz ExtLNA Murata VM [ 15.161165] Bluetooth: hci0: BCM4334B0 (002.001.013) build 1852 [ 18.854591] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 18.854622] Bluetooth: BNEP filters: protocol multicast [ 18.854645] Bluetooth: BNEP socket layer initialized [ 18.866766] Bluetooth: MGMT ver 1.22 [ 21.576450] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 39.679565] Bluetooth: RFCOMM TTY layer initialized [ 39.679606] Bluetooth: RFCOMM socket layer initialized [ 39.679633] Bluetooth: RFCOMM ver 1.11 [ 144.290000] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 4185.182614] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 4252.959629] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 4342.080999] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 4355.681223] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 4387.169641] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 4896.781723] Bluetooth: hci0: Opcode 0x0c03 failed: -110 ~$ bluetoothctl Waiting to connect to bluetoothd...[bluetooth]# Agent registered [bluetooth]# power on [bluetooth]# Failed to set power on: org.bluez.Error.Failed exit I had to install no internet apps for desktop as armbian mirror for firefox is broken as there is file size missmatch and it cancels the compile of image trying to instal firefox by apt or synaptic package manager gave same error. I had to install firefox nightly to get a working browser. Edited October 16 by firepower 0 Quote
rafman Posted October 16 Posted October 16 (edited) 8 hours ago, firepower said: Vontar H618 PCB: FX-H618-D4_V10 23-03-21 Ram: 4GB (8 x K4B4G0446B HCK0) Rom: 64GB (KLMCG4JENB ) Wifi: HK6334Q Osc: 37.4MHz LED: FD650B-S PMIC: AXP313A This Vontar hardware is identical, and the board also with my version of transpeed-8k Please let me know (or provide link) with your working/tested Android 12 firmware image for your Vontar H618. Edited October 16 by rafman 0 Quote
firepower Posted October 16 Posted October 16 (edited) Found this by searching vontar h618 firmware. https://androidpctv.com/vontar-h618-firmware-update/ And https://www.vontar.cn/pages/download Edited October 16 by firepower 0 Quote
firepower Posted October 16 Posted October 16 (edited) i like to make a bootable micro SDcard with the Vontar H618 Android 12 firmware and see if it would boot on the Tanix Tx6. Use Disks to make an image and restore to sdcard? Edited October 16 by firepower 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.