add MODECOM FreePC Z3735F/2GB/32GB to default generic

  • It's not impossible or particularly difficult, but we already have 4-5 different collections of brmfmac firmware and instead of tacking another on to the build system for the Generic x86_64 image it's about time we consolidated them and came up with a sensible build-time and userspace method for supporting device/board specific nvram configs; because we currently assume devices that use the same brcmfmac chip can use the same nvrman config and that's not the case (and I suspect this is why we have accumulated multiple firmware collections over time). That work gets a little easier once we have more devices on a common Linux 4.18/4.19 kernel codebase (as the kernel-firmware repo provides the latest or common firmware, but no nvram configs) so I wasn't planning to look at it until after LE9.0. If will probably be done for LE9.2 once we start to shift some of our Android-oriented hardware groups off legacy BSP kernels, which is always a good time for package spring cleaning.

    NB: in the Bluez move from hciattach to btattach the codebase is still fresh and I already found a number of cases where brcmfmac device ID's aren't mapped so devices either don't prompt for firmware or the filenames (as documented in all the howto guides you find in Google) need to be adjusted.

    In summary.. if you have a homebrew solution that's working please stick with it for a while, and we'll catch you up sometime later in the year.

  • I have exactly MODECOM FreePC / 32GB.

    but I don't know how to deal with adding drivers.

    I came across this video first: "

    External Content www.youtube.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
    "

    But if I try to add drivers according to the video instructions, they disappear after restarting.

    Is there a step-by-step instruction?

  • I found the solution for morons like me " instruction step by step":
    Create usb installer
    Now you have to partitions on usb: libreelec and storage
    in usb libreelec you have to file "SYSTEM"
    Copy on your computer and open terminal in this directory
    in terminal typing: unsquashfs SYSTEM

    this commend unpacing file to squashfs-root

    now go to /squashfs-root/usr/lib/kernel-overlays/base/lib/firmware/brcm
    copy the file :
    brcmfmac43430a0-sdio.bin brcmfmac43430a0-sdio.bin.7.10.1.244.ucode940.1020

    brcmfmac43430a0-sdio.txt brcmfmac43430a0-sdio.txt.jumper-ezpad-mini3

    or:
    http://jwrdegoede.danny.cz/brcm-firmware/…per-ezpad-mini3

    back to terminal and typ: mksquashfs squashfs-root/ SYSTEM -noappend -always-use-fragments

    this commend create a new "SYSTEM" file
    copy "SYSTEM" to usb libreelec

    now install libreelec on your device

  • Code
    mkdir -p /storage/.config/firmware/brcm

    ^ create and download correctly named files in that folder and reboot - no need to hack the SYSTEM file

    Your solution is better.
    Somebody know how fix bluetooth?

    Edited once, last by 13lenar: ap6212 is inside (March 28, 2021 at 1:18 PM).

  • I've used the capability to overlay firmware files for testing on a Cubox-i image within the last week, so I disagree. Pastebin directory listings to prove you did things correctly.

    I checked three times. Finally I installed v9.x and tried your solution, then upgraded to v10e.
    actually , I have no possibility to come back to the previous one, it has to stay as it is. Anyway thanks for replying!