Seite 5 von 9 ErsteErste ... 34567 ... LetzteLetzte
Ergebnis 41 bis 50 von 81
  1. #41
    Anfänger
    Registriert seit
    01.01.2018
    Beiträge
    19
    Thanks (gegeben)
    9
    Thanks (bekommen)
    0
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Zitat Zitat von Captain Beitrag anzeigen
    please check

    e2 boot enable

    boot android

    start the tv app

    setup menu -> misc -> Preference -> use e2 Enable
    Thank you, but E2 boot are enabled. And the E2 image don't run. Enable WiFi kernel module

    •   Alt Advertising

       

  2. #42
    Avatar von Captain
    Registriert seit
    03.04.2013
    Beiträge
    13.380
    Thanks (gegeben)
    708
    Thanks (bekommen)
    18787
    Total Downloaded
    162,35 MB
    Total Downloaded
    162,35 MB
    ReceiverDankeAktivitäten
    create a serial log

    first flash again with green button


    openATV we are open Source

    Boykott GPL violator

  3. #43
    Avatar von Captain
    Registriert seit
    03.04.2013
    Beiträge
    13.380
    Thanks (gegeben)
    708
    Thanks (bekommen)
    18787
    Total Downloaded
    162,35 MB
    Total Downloaded
    162,35 MB
    ReceiverDankeAktivitäten
    Hier die Firmware und die config für den 6335 Adapter

    unter android wird folgenden treiber genommen

    U5ATVPLUS:/ $ lsmod

    Module Size Used by
    bcmdhd 780584 0
    cfg80211 389325 1 bcmdhd

    ahci_platform 2440 0
    libahci_platform 5529 1 ahci_platform
    libahci 22895 1 libahci_platform
    tntfs 538477 0
    xhci_plat_hcd 4372 0
    ohci_platform 4126 0
    ehci_platform 4590 0

    das ist die android Version vom Wifi adapter

    hier hatte ein user auch ein Problem das Power on fehlt bei sio version im Linux Kernel

    Re: Broadcom brcmfmac vs bcmdhd on Android (Linux Wireless)


    kernel log Android

    cfg80211: Calling CRDA to update world regulatory domain
    dhd_module_init: in
    ======== bcm_wlan_set_plat_data ========
    wifi:host_oob_irq: 228(36)
    dhd_wifi_platform_load: Enter
    Power-up adapter 'DHD generic adapter'
    wifi_platform_set_power = 1
    wifi:gpio(37) set{1}
    wifi_platform_bus_enumerate device present 1

    mmc2: new high speed SDIO card at address 0001
    bcmsdh_register: register client driver
    bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter
    bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter
    bus num (host idx)=2, slot num (rca)=1
    found adapter info 'DHD generic adapter'
    dhdsdio_probe : no mutex held. set lock
    F1 signature read @0x18000000=0x16224335
    F1 signature OK, socitype:0x1 chip:0x4339 rev:0x1 pkg:0x2
    DHD: dongle ram size is set to 786432(orig 786432) at 0x180000
    dhd_conf_set_chiprev: chip=0x4339, chiprev=1
    dhd_conf_set_conf_path_by_nv_path: config_path=/system/etc/firmware/ap6xxx/config.txt
    dhd_conf_read_config: Ignore config file /system/etc/firmware/ap6xxx/config.txt
    wl_create_event_handler(): thread:wl_event_handler:bc4 started
    tsk Enter, tsk = 0xce4c1468
    dhd_attach(): thread:dhd_watchdog_thread:bc7 started
    dhd_attach(): thread:dhd_dpc:bc8 started
    dhd_attach(): thread:dhd_rxf:bc9 started
    dhd_deferred_work_init: work queue initialized
    Dongle Host Driver, version 1.363.59.144.2 (r)
    Register interface [wlan0] MAC: e0:76:d0:fb:78:2e

    wl_event_handler: was terminated
    wl_destroy_event_handler(): thread:wl_event_handler:bc4 terminated OK
    dhd_wl_ioctl: returning as busstate=0
    bcmsdh_oob_intr_unregister: Enter
    bcmsdh_oob_intr_unregister: irq is not registered
    dhd_txglom_enable: enable 0
    dhd_conf_set_txglom_params: swtxglom=0, txglom_ext=0
    dhd_conf_set_txglom_params: txglom_bucket_size=0
    dhd_conf_set_txglom_params: txglomsize=0, deferred_tx_len=0, bus_txglom=-1
    dhd_conf_set_txglom_params: tx_in_rx=1, tx_max_offset=0
    dhd_bus_devreset: WLAN OFF DONE
    wifi_platform_set_power = 0
    wifi:gpio(37) set{0}
    ampak: off
    dhdsdio_probe : the lock is released.
    dhd_module_init: Exit err=0
    ampak: on
    dhd_open: Enter cee93000

    Dongle Host Driver, version 1.363.59.144.2 (r)
    wl_android_wifi_on in 1
    wl_android_wifi_on in 2: g_wifi_on=0
    wifi_platform_set_power = 1
    wifi:gpio(37) set{1}
    sdio_reset_comm():
    mmc2: queuing unknown CIS tuple 0x80 (2 bytes)
    mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
    mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
    mmc2: queuing unknown CIS tuple 0x80 (7 bytes)


    dhd_bus_devreset: == WLAN ON ==
    F1 signature read @0x18000000=0x16224335
    F1 signature OK, socitype:0x1 chip:0x4339 rev:0x1 pkg:0x2
    DHD: dongle ram size is set to 786432(orig 786432) at 0x180000
    dhd_conf_read_config: Ignore config file /system/etc/firmware/ap6xxx/config.txt
    dhd_conf_set_fw_name_by_chip: firmware_path=/system/etc/firmware/ap6xxx/fw_bcm4339a0_ag.bin
    dhd_conf_set_nv_name_by_chip: nvram_path=/system/etc/firmware/ap6xxx/nvram_ap6335.txt
    dhdsdio_download_firmware: set use_rxchain 0
    dhdsdio_download_firmware: set txglomsize 36
    Final fw_path=/system/etc/firmware/ap6xxx/fw_bcm4339a0_ag.bin
    Final nv_path=/system/etc/firmware/ap6xxx/nvram_ap6335.txt
    Final conf_path=/system/etc/firmware/ap6xxx/config.txt
    dhd_os_open_image: /system/etc/firmware/ap6xxx/fw_bcm4339a0_ag.bin (541314 bytes) open success
    dhd_os_open_image: /system/etc/firmware/ap6xxx/nvram_ap6335.txt (2494 bytes) open success
    NVRAM version: AP6335_NVRAM_V1.7_04102014
    dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
    Angehängte Dateien Angehängte Dateien


    openATV we are open Source

    Boykott GPL violator

  4. #44
    Avatar von Captain
    Registriert seit
    03.04.2013
    Beiträge
    13.380
    Thanks (gegeben)
    708
    Thanks (bekommen)
    18787
    Total Downloaded
    162,35 MB
    Total Downloaded
    162,35 MB
    ReceiverDankeAktivitäten


    openATV we are open Source

    Boykott GPL violator

  5. #45
    Mitglied
    Registriert seit
    02.12.2017
    Beiträge
    71
    Thanks (gegeben)
    3
    Thanks (bekommen)
    4
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Box 1:
    U5PVR Deluxe
     
     
    Thanks, that's very interesting.

    In your Android log, you see that the device Id is detected as 0x4339. This is also what is in the Linux driver for BCM4339. So I think the deviceId is really 0x4339. The brcmfmac driver supports this.

    But I also think you could be right with the power issue. I found a very interesting include file for brcmfmac in the 4.3.15 Kernel. It allows to make platform specific settings (Like power on the device before probing). See here:

    Linux source code: include/linux/platform_data/brcmfmac-sdio.h (v4.4.35) - Bootlin

    In the comment there's an example how this could be included e.g. in bcmsdh.c. Especially this is very interesting:

    power_on: This function is called by the brcmfmac when the module gets
    loaded. This can be particularly useful for low power devices. The platform
    spcific routine may for example decide to power up the complete device.
    If there is no use-case for this function then provide NULL.
    In your other link the guy uses exactly this way (for an older 3.x kernel - so it looks different). He adds the platform specific sections to the driver file.

    So I think, we need to patch /net/wireless/brcm80211/brcmfmac/bcmsdh.c and include the example code from brcmfmac-sdio.h. Of course the code must be adapted for the u5pvr platform. For example brcmfmac_power_on() must be implemented.

    The problem is: I don't know enough Linux driver C to power on the device. Maybe we could learn that from the Android kernel module bcmdhd. But not sure.

  6. #46
    Anfänger
    Registriert seit
    01.01.2018
    Beiträge
    19
    Thanks (gegeben)
    9
    Thanks (bekommen)
    0
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Zitat Zitat von Captain Beitrag anzeigen
    create a serial log

    first flash again with green button
    To enable the flash function with the green button, do I have to follow the guide with the rs232 cable? or was it introduced with the latest version of Android firmware?

  7. #47
    Mitglied
    Registriert seit
    02.12.2017
    Beiträge
    71
    Thanks (gegeben)
    3
    Thanks (bekommen)
    4
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Box 1:
    U5PVR Deluxe
     
     
    There is some guidline for Linux 3.x from Ampak, how to power on WiFi. Actually a certain pin on the AP module has to be pulled up. See page 10 here.

    I wonder if they also modified the Android kernel. They must have the same problem there. If it's a 4.x kernel, we could copy the respective code.

  8. #48
    Mitglied
    Registriert seit
    02.12.2017
    Beiträge
    71
    Thanks (gegeben)
    3
    Thanks (bekommen)
    4
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Box 1:
    U5PVR Deluxe
     
     
    More findings: The Ampag WL_REG_ON pin (12) is probably connected to an GPIO programmable I/O pin on the Hi3798. The problem is: We don't know which one. The chip comes with 13 groups of GPIO chips, each with 8 ports. On the Android log we clearly see, that they power on the AMPAK this way:

    wifi_platform_set_power = 1
    wifi:gpio(37) set{1}

    I assume that the 37 somehow indicates the GPIO port. If we know the Port we can activate the WiFi from command line with something like this:

    Code:
    # Make GPIO 37 available for us in /sys/class/gpio/gpio37
    echo 37 > /sys/class/gpio/export
    # Configure the port as output
    echo out > /sys/class/gpio/gpio37/direction
    # Set the output to 1
    echo 1 > /sys/class/gpio/gpio37/value
    Unfortunately this had no effect. So I think the port number is not correct.

    If we had a pinout of the Hi3798 chip we could check on the board which GPIO pin is used. But I could not find anything.

  9. #49
    Mitglied
    Registriert seit
    02.12.2017
    Beiträge
    71
    Thanks (gegeben)
    3
    Thanks (bekommen)
    4
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Box 1:
    U5PVR Deluxe
     
     
    @Captain I had no success. But I'm very sure that Android uses GPIO 36 (IRQ) and 37 (WiFi Power). Under Android I tried to init all available GPIO ports from 0 - 103 with /sys/class/gpio/export. It failed for ports 36, 37, 40, 41, 42, 60, 67 and 72 with "already in use" message. So these are the GPIO ports used on Android. And you see 36 and 37 in the Android log where WiFi is initialized.

    Meanwhile I've learned enough that I could even try to patch the brcmfmac kernel module. Some questions:

    1. Is the kernel source now available for everyone? I found the scripts under oe-alliance-core/meta-brands/meta-dinobot at 4.1 * oe-alliance/oe-alliance-core * GitHub
    2. Do you have a quickstart guide for where to start with oe-alliance-core compilation?
    3. Do you maybe have access to the Android Kernel source? I'd like to see if they patched the bcmdhd module. I'm pretty sure, they did. We could learn from that.

  10. #50
    Avatar von Captain
    Registriert seit
    03.04.2013
    Beiträge
    13.380
    Thanks (gegeben)
    708
    Thanks (bekommen)
    18787
    Total Downloaded
    162,35 MB
    Total Downloaded
    162,35 MB
    ReceiverDankeAktivitäten
    here last driver i have found and you can compile with linux too but detection now ready


    and i get this today from china

    this was the original u5pvr driver


    atv build read this for start : enigma2/README.md at 6.1 * openatv/enigma2 * GitHub

    build linux-dinobot

    bitbake -f linux-dinobot

    kernel all public : oe-alliance-core/linux-dinobot_4.4.35.bb at 4.1 * oe-alliance/oe-alliance-core * GitHub
    Angehängte Dateien Angehängte Dateien


    openATV we are open Source

    Boykott GPL violator


Seite 5 von 9 ErsteErste ... 34567 ... LetzteLetzte

Stichworte

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •  
Alle Zeitangaben in WEZ +1. Es ist jetzt 21:31 Uhr.
Powered by vBulletin® Version 4.2.5 (Deutsch)
Copyright ©2021 Adduco Digital e.K. und vBulletin Solutions, Inc. Alle Rechte vorbehalten.
Resources saved on this page: MySQL 5,88%
Parts of this site powered by vBulletin Mods & Addons from DragonByte Technologies Ltd. (Details)
vBulletin Skin By: PurevB.com