Jump to content

data

Members
  • Posts

    94
  • Joined

  • Last visited

Posts posted by data

  1. With the boot-issue now resolved, the last nightly enables overlay-support for uart1.

    This is one more step towards working bluetooth on the lite2 and Orange Pi 3.

     

    Anyone interested is invited to do further testing.

    So far, I can enable the uart1 overlay either in armbianEnv.txt or via armbian-config.

    This gives us /dev/ttyS1 - at least it's there in dmesg and /dev/ttyS1 exists. Since the bluetooth module is connected via uart1, the

    next steps are to attach it. From my understanding, this needs the hci_uart module, which can be loaded via

    $ sudo modprobe hci_uart

     

    In addition, the btbcm module is required but this should be already loaded. So 'sudo modprobe btbcm' should not be necessary.

    You can verify if it is loaded via: $ lsmod | grep btbcm

    This in place, we should be able to attach the uart-port using hciattach. Now this is the point, where I am stuck.

     

    Typically, you do something along

    $ sudo hciattach /dev/ttyS1 bcm43xx 921600 noflow -

    However, I tried a couple of different baudrates as well as with and without flow-control without success.

    According to a couple of related posts, on success, one should see that the firmware is being loaded at this point.

     

    Any ideas or suggestions?

     

  2. Dear Martin,

     

    I am pleased to let you know, that the recent nightly from today works fine on the lite2!

    Thank you and all others here who contributed very much!

     

    Further, I can enable now uart1 and it shows up. I just was not able yet to set up bluetooth.

    Will post my results in the according thread.

     

    Keep up the good work!!

  3. Just tried the current nightly. Lite2 boots, however Wifi is not working. I can see some of the networks on 2.4GHz, no 5GHz. Connecting is not possible.

    System keeps spawning messages:

    [    8.812739] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
    [    9.040493] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
    [   24.287924] ieee80211 phy0: brcmf_escan_timeout: timer expired
    [   67.039923] ieee80211 phy0: brcmf_escan_timeout: timer expired
    [   69.599946] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
    [   69.605853] ieee80211 phy0: brcmf_notify_escan_complete: Scan abort failed
    [  102.623956] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
    [  102.629884] ieee80211 phy0: brcmf_run_escan: error (-110)
    [  102.635368] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
    [  155.615958] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
    [  155.621873] ieee80211 phy0: brcmf_run_escan: error (-110)
    [  155.627367] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
    [  218.591973] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
    [  218.597923] ieee80211 phy0: brcmf_run_escan: error (-110)
    [  218.603405] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
    [  281.567970] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
    [  281.573897] ieee80211 phy0: brcmf_run_escan: error (-110)
    [  281.579373] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
    [  324.831945] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
    [  324.837852] ieee80211 phy0: _brcmf_set_multicast_list: Setting mcast_list failed, -110

     

  4. Just in case nobody noticed yet: Current nightly as of May 2nd does not work on the lite2.

    Probably the issue exists since a few days. After my last apt upgrade on wednesday, my board

    did hang on boot. After a fresh install with the current nightly, it does not boot as well.

    These are the last lines from verbose boot output:

    Quote

    [    3.630355] sun6i-rtc 7000000.rtc: setting system clock to 2019-05-04T12:19:17 UTC (1556972357)
    [    3.639170] of_cfs_init
    [    3.641701] of_cfs_init: OK
    [    3.644699] vdd-gpu: disabling
    [    3.648404] Freeing unused kernel memory: 576K
    [    3.664016] Run /init as init process
    [    3.695698] random: systemd-udevd: uninitialized urandom read (16 bytes read)
    [    3.699727] random: udevadm: uninitialized urandom read (16 bytes read)
    [    3.703222] random: systemd-udevd: uninitialized urandom read (16 bytes read)
    [    5.032205] random: fast init done
    [    5.653993] random: crng init done
    [    5.657397] random: 7 urandom warning(s) missed due to ratelimiting
    [    5.726192] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null)
    [    6.314872] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD
     +IDN)
    [    6.333231] systemd[1]: Detected architecture arm64.
    [    6.339798] systemd[1]: Set hostname to <orangepilite2>.
    [    6.664121] systemd[1]: Listening on udev Control Socket.
    [    6.670242] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    [    6.677571] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    [    6.685582] systemd[1]: Listening on Journal Audit Socket.
    [    6.691363] systemd[1]: Listening on Syslog Socket.
    [    6.696533] systemd[1]: Listening on Journal Socket.
    [    6.701719] systemd[1]: Reached target Swap.
    [    6.810448] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro
    [    6.944233] systemd-journald[369]: Received request to flush runtime journal from PID 1
    [    7.300118] thermal thermal_zone0: failed to read out thermal zone (-16)
    [    7.300306] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 912000 KHz
    [    7.306963] thermal thermal_zone1: failed to read out thermal zone (-16)
    [    7.314324] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed to: 1080000 KHz

     

  5. In an effort to enable Bluetooth on the OrangePi (Lite2 | 3) I am stuck at enabling UART1 via overlay.

    According to the schematics, the AP6255 is connected via UART1 (PG6-PG9) to the H6 SoC but not defined in the dtb.

     

    Since there is a dtbo which looks promising at /boot/dtb/allwinner/overlay/sun50i-h6-uart1.dtbo I tried adding an

    overlay to /boot/armbianEnv.txt - manually and via armbian-config. Both did not work out.

     

    In addition,  I also tried adding uart1 to the dtb, without success.

     

    What am I missing?

     

     

  6. I tried a new approach on bringing bluetooth to life...

    With the current nightly, I noticed some complaints about a missing firmware:

    [   11.484843] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.xunlong,orangepi-lite2.txt failed with error -2

     

    Which was easily fixed by

    root@orangepilite2:~# cp /lib/firmware/rkwifi/nvram_ap6255.txt /lib/firmware/brcm/brcmfmac43455-sdio.xunlong,orangepi-lite2.txt

     

     

    But UART1,  connected to the ap6255 according to the official schematics is not defined in the dtb I found at

    /boot/dtb-5.0.9-sunxi64/allwinner/sun50i-h6-orangepi-lite2.dtb

     

     

    Now I am stuck with bringing UART1 aka /dev/ttyS1 to life. So far, I tried adding an overlay to /boot/armbianEnv.txt:

    There is one which looks promising at /boot/dtb/allwinner/overlay/sun50i-h6-uart1.dtbo

    So adding 'overlays=uart1' was the next step but I still don't get ttyS1 to work.

     

    Comparing the other dtbos, I noticed that some contain definitions for the RTS/CTS pins

    dtc -I dtb -O dts /boot/dtb/allwinner/overlay/sun50i-h6-uart2.dtbo

     

    What am I missing?

     

    [By the way, I also tried adding uart1 to the dtb, without success...]

     

    Schematics are at http://linux-sunxi.org/images/4/4c/OrangePi_Lite2_Schematics_v2.0.pdf

     

     

  7. Ok, I connected a TTL cable to the serial port but besides the line

    Quote

     

    orangepilite2 login: [  172.460867] reboot: Restarting system

     

    I get nothing else.

     

    Do I need a fresh install of the nightly version? Because I just did 'apt upgrade'...

    Or is there a way I can keep my existing setup?

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines