Jump to content

Search the Community

Showing results for tags 'bigtreetech-cb1'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Product Groups

  • Misc
  • Support

Categories

  • Armbian
  • Armbian releases

Categories

  • Volunteering opportunities

Calendars

  • Community Calendar

Categories

  • Official giveaways
  • Community giveaways

Categories

  • Members

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

Found 6 results

  1. Hello. I am taking the task of organizing and performing the BTT Pi and CB1 support update. The plan is to use mainline kernel 6.6 and 6.8 (basically the default sunxi64 config) instead of the BTT fork and use patches to backport kernel patches for drivers and hardware support. The Jira issue is AR-2312, which is a collection of things that will need to be done for this initiative. @Gunjan Gupta @c0rnelius @ag123 @jernej @ALIGMSTEN I'm asking for your help on this, as Igor has said to me that you are more knowledgeable on the state of the board and what it needs. From what I've found, there has been a PR that upgraded the kernel used for BTT CB1 to 6.1.79 using patches, and there's a discussion on reconstructing or copying the BigTreeTech device tree for 6.6.y and up. The BTT's changes are mostly drivers, device tree and other hardware support and backporting. I think BTT's linux 6.2.y branch should be used as the starting point to determine what board-specific patches and changes are needed. Some of the drivers are already in the 6.6.y (CURRENT) and 6.8.y (EDGE) kernel versions, some are added by armbian, some are only in the vendor's fork.
  2. Hi everyone, I'm trying build armbian with legacy branch and I need apply patch to u-boot config. If I add my patch in userpatches, buid script ignoring it. If I build current branch, patches aplying
  3. I'm looking forward to buying a BIGTREETECH Pi v1.2 board to use as a slim home server to replace my Orange Pi PC. I've had pretty good experience with Armbian so far and I would like to make sure I can continue using it with the new board. I didn't find a specific image for BTT Pi v1.2, but I did find a "Desktop > ARM64" entry. I'm confused on what should I use and whether it's supported at all. Can someone clarify that for me?
  4. Hello, very now to Linux and Armbian and have a BIGTREETECH PAD 7 (a BIGTREETECH CB1 with built in screen https://github.com/bigtreetech/Pad7/blob/master/BIGTREETECH Pad 7 v1.0 User Manual.pdf ). I would really like to be able to run old-school Doom on it and was wondering if someone could tell me if it is possible, and then point me in the right direction of a noob-friendly tutorial if it is possible. Thank you for taking the time to read.
  5. Recent images don't boot on BigtreeTech PI V1.2 boards. These are the last log lines I get over the serial: Starting kernel ... Loading, please wait... Starting systemd-udevd version 255.3-1 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. <...repeated many times...> Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=0c02e3fa-3cf4-4e86-9829-edeabba5469c does not exist. Dropping to a shell! Image that did work for me: Armbian_23.11.1_Bigtreetech-cb1_bookworm_legacy_6.1.43_minimal.img.xz . I also updated kernel package to linux-image-edge-sun50iw9-btt (6.2.16-edge-sun50iw9-btt), and it works as well. Images that did NOT work: Armbian_24.2.1_Bigtreetech-cb1_bookworm_current_6.6.16_minimal.img.xz (current stable from the website), also I tried the latest nightly build Armbian_24.5.0-trunk.36_Bigtreetech-cb1_trixie_edge_6.7.5_minimal.img.xz I've looked around while in initramfs, and I don't see any /dev/mmcblk0* devices. Also, dmesg doesn't show anything about my SDHC card. For comparison, image that works has this in dmesg output: [ 1.925594] mmc1: host does not support reading read-only switch, assuming write-enable [ 1.928794] mmc1: new high speed SDHC card at address aaaa [ 1.929630] mmcblk1: mmc1:aaaa SK32G 29.7 GiB [ 1.931786] mmcblk1: p1 p2 p3 [ 2.094288] sunxi-mmc 4021000.mmc: initialized, max. request size: 16384 KB, uses new timings mode [ 2.095415] Freeing unused kernel memory: 2752K [ 2.095533] Run /init as init process [ 2.095540] with arguments: [ 2.095545] /init [ 2.095550] splash [ 2.095555] splash [ 2.095560] nofb [ 2.095565] with environment: [ 2.095569] HOME=/ [ 2.095573] TERM=linux [ 2.095578] ubootpart=5d175d74-01 [ 2.095583] cgroup_enable=memory [ 2.100579] sunxi-mmc 4021000.mmc: card claims to support voltages below defined range Image that does not work has this (note -- no logs regarding SDHC card): [ 1.605257] sunxi-mmc 4021000.mmc: initialized, max. request size: 16384 KB, uses new timings mode [ 1.611428] sunxi-mmc 4021000.mmc: card claims to support voltages below defined range [ 1.622065] mmc0: new high speed SDIO card at address 0001 [ 1.636956] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.07 [ 1.636974] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.636983] usb usb8: Product: Generic Platform OHCI controller [ 1.636990] usb usb8: Manufacturer: Linux 6.7.5-edge-sunxi64 ohci_hcd [ 1.636997] usb usb8: SerialNumber: 5101400.usb [ 1.637568] hub 8-0:1.0: USB hub found [ 1.637623] hub 8-0:1.0: 1 port detected [ 1.639238] Freeing unused kernel memory: 3072K [ 1.652717] Run /init as init process [ 1.652736] with arguments: [ 1.652741] /init [ 1.652746] with environment: [ 1.652751] HOME=/ [ 1.652755] TERM=linux [ 1.652760] splash=verbose [ 1.652765] ubootpart=6aa635ca-01 [ 1.652770] cgroup_enable=memory
  6. I couldn't find a topic with this device, although support is announced, so I'm posting here. To moderators: please create an appropriate section. How to unlock UART1 and UART2 on this device?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines