Jump to content

Search the Community

Showing results for tags 'khadas-vim3l'.

  • 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

  • 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 2 results

  1. Hi, We're swapping the Khadas Fenix 4.9 and uboot v2015-01?? for the Armbian 5.10.y and corresponding mainline u-boot. In the "legacy" version we were able to use the u-boot script (then a dedicated boot.ini) for setting a gpio pin low like this gpio clear GPIOH_4 Unfortunately Armbian's mainline u-boot version does not recognize GPIOH_4 as a valid gpio pin name. Anyone able to help? Did the naming change? Gé
  2. Hi guys! Image from that link http://imola.armbian.com/dl/khadas-vim3l/archive/Armbian_22.05.1_Khadas-vim3l_jammy_edge_5.17.5_xfce_desktop.img.xz is about 352 Mb. When Im unzip it - 7zip give me error. http://imola.armbian.com/dl/khadas-vim3l/archive/Armbian_22.05.1_Khadas-vim3l_focal_current_5.10.110_xfce_desktop.img.xz - same problem. By the way I have some problem with building image by myself, some time it gives me complete with success, but image is broken too. I think so because first boot take loooooong time with no set root pwd, only rounding circle and second boot don't give me to set root pass and other credentials. So if it possible, could you test that images (in links) and if it's really problem - repair. May be problem there and build script repairing by itself when everything be ok. Much thanks! Update: If its need, I can share my Img.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines