Hi Ekaitz,
Ekaitz Zarraga <eka...@elenq.tech> writes: > 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. Thank you for pointing me in the right direction! This is what I ended up with: ```scheme (use-modules (gnu packages embedded) (gnu packages flashing-tools) (gnu packages firmware)) (packages->manifest (list (make-arm-none-eabi-nano-toolchain-6) dfu-util qmk)) ``` Then just simply run ```sh guix shell -m manifest.scm -- qmk flash -kb ergodox_infinity -km plattfot -bl dfu-util-split-left ``` And that worked like a charm. I had forgotten that my ergodox is using different tools than my kyria. Also the nano lib threw me for a loop. I was using the `make-arm-none-eabi-toolchain-6` at first. > You can even make a package for your firmware and let guix compile it > for you (and maybe flash it too?). Oh, that sounds that it might be useful. Especially if it can flash it too. As I have a few keyboards and not all keymaps are pushed upstream (yet). -- s/Fred[re]+i[ck]+/Fredrik/g