From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Fredrik Salomonsson <plattfot@posteo.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Question regarding qmk firmware
Date: Sun, 08 Oct 2023 10:28:43 +0000 [thread overview]
Message-ID: <fDW1GEWPl6kOciPrHcUcIVHkdwg4Jcc0UsuPK6md3lfp_ev9uoQOQW7eUTWH0jPS-WOQvwkcdA2TN_cBrcw1JJQQWL4ESy2h2o5ZlkBKlQ0=@elenq.tech> (raw)
In-Reply-To: <87r0m6xh3c.fsf@posteo.net>
------- Original Message -------
On Saturday, October 7th, 2023 at 21:23, Fredrik Salomonsson <plattfot@posteo.net> wrote:
> Hi,
>
> Today I was tweaking a keymap for one of my qmk based keyboards but some
> of the packages I used when building the firmware has been removed. My
> commad was as follows:
>
> `sh guix shell avr-toolchain dfu-programmer qmk -- qmk flash -kb ergodox_infinity -km plattfot -bl dfu-split-left`
>
> But `avr-toolchain` is gone. When I tried to just drop it and see if it
> worked I get
>
> `Ψ Compiling keymap with make --jobs=1 ergodox_infinity:plattfot:dfu-split-left QMK Firmware 0.14.19 Making ergodox_infinity with keymap plattfot and target dfu-split-left /gnu/store/rib9g2ig1xf3kclyl076w28parmncg4k-bash-minimal-5.1.16/bin/sh: line 1: arm-none-eabi-gcc: command not found`
>
> It seems `arm-none-eabi-toolchain` is also removed. Looking at the
> commit history for guix it looks like they got replaced by
> [proceduers][0] instead.
>
> [0] https://git.savannah.gnu.org/cgit/guix.git/commit/?id=35c1df5bd6317b1cd038c1a4aca1c7e4a52d4d93
>
> My question is how do I get access to the arm-none-eabi-toolchain from
> the commandline with guix shell?
>
> Thanks
Hi Fredrik,
Now what you need to do is call to the `make-avr-toolchain` function from `(gnu packages avr)` to get that.
Maybe the easiest way is to create a `manifest.scm` where you do something like this (i'm doing it by memory):
``` scheme
(use-modules (gnu packages avr)
(gnu packages flashing-tools)
(gnu packages firmware))
(packages->manifest (list (make-avr-toolchain) dfu-programmer qmk))
```
Then use `guix shell -m manifest.scm`.
There are other ways to do it, but I find this the easiest.
You can even make a package for your firmware and let guix compile it for you (and maybe flash it too?).
Cheers,
Ekaitz
next prev parent reply other threads:[~2023-10-08 10:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 21:23 Question regarding qmk firmware Fredrik Salomonsson
2023-10-08 10:28 ` Ekaitz Zarraga [this message]
2023-10-10 19:32 ` Fredrik Salomonsson
2023-10-08 10:34 ` Fw: " Ekaitz Zarraga
2023-10-09 1:30 ` John Kehayias
2023-10-10 19:46 ` Fredrik Salomonsson
2023-10-14 15:57 ` Maxim Cournoyer
[not found] <mailman.67.1696780842.10213.help-guix@gnu.org>
2023-10-10 14:20 ` Peter Polidoro
2023-10-10 17:43 ` Ekaitz Zarraga
2023-10-10 18:32 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='fDW1GEWPl6kOciPrHcUcIVHkdwg4Jcc0UsuPK6md3lfp_ev9uoQOQW7eUTWH0jPS-WOQvwkcdA2TN_cBrcw1JJQQWL4ESy2h2o5ZlkBKlQ0=@elenq.tech' \
--to=ekaitz@elenq.tech \
--cc=help-guix@gnu.org \
--cc=plattfot@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.