data

Members
  • Content Count

    80
  • Joined

  • Last visited

About data

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    nürnberg
  • Interests
    Linux, embedded stuff, networking and ham radio

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So, does this mean the current nightly for the Lite2 may most likely work if I use a 'legacy' dtb?
  2. @dolphs Which image have you used?
  3. Probably you have to wait a little bit longer. The latest nightly is still from the 7th/8th at this moment...
  4. @Igor Thank you very much for your efforts! Will this be incorporated in the Lite2 image as well from tormorrow?
  5. Orange Pi Lite2 affected as well: After upgrading to the latest nightly (Jun-01), it does not boot anymore :(
  6. Great, thank you! Once I've tried it, I'll report back here.
  7. Lite2 has an AP6255 connected to UART1
  8. Do you know if these patches are included in the current lite2 built?
  9. @megi I noticed I already had the firmware for ap6255 at /lib/firmware on the lite2 but I am still not able to attach the device to uart1 How have you managed to configure uart1? Or are there some relevant differences in the kernel which haven't been ported to the lite2 built yet?
  10. So were you able to configure the device using hciattach?
  11. hciattach is what you are asking for. e.g. $ sudo hciattach /dev/ttyS1 bcm43xx 921600 noflow - Can you attach the firmware to this thread?
  12. 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?
  13. 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!!
  14. Perfect, thank you! So it'll be online in the coming nightly, right?! I'll try tomorrow and let you know!
  15. 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