Just received the nRF9151 feather !!

Working through command line compile/flash.

What branch of the nrf9160-feather-examples-and-drivers repo should I use? v2.4.x is default, but v2.7.x seems to be where development is happening.

https://docs.circuitdojo.com/nrf9151-feather/building-and-programming.html#building has the following instructions:

west build -b circuitdojo_feather_nrf9161/nrf9161/ns -p -d build/circuitdojo_feather_nrf9161 –sysbuild

Should that be nrf9151 instead?

Assuming nrf9151, I could get the v2.7.x branch to build.

pyocd pack install nRF9160_xxAA

west flash –runner pyocd

Button and blinky samples seem to work – yay!

    I would suggest using nRF Connect SDK plugin rather than Circuit Dojo Tools. But if you already have them installed they should work as well.

    cbrake What branch of the nrf9160-feather-examples-and-drivers repo should I use? v2.4.x is default, but v2.7.x seems to be where development is happening.

    v2.7.x is the place to be for the nRF9151 design. I’ll be updating everything in the near future so it’s default.

    cbrake Should that be nrf9151 instead?

    Yes!

    cbrake west flash –runner pyocd

    Button and blinky samples seem to work – yay!

    Nice!! Glad it’s working otherwise. 😃

          Thanks – it is looking good!

          I’m somewhat experienced with Zephyr, so I prefer a straight command-line West flow 99% of the time. It may make sense to document that flow a little more prominently in the example repo README.md for people like me. I’d be glad to submit a PR at some point if that would be helpful.

          I have a template that I use for several other projects, and trying to figure out how to integrate the nRF feather into this:

          https://github.com/simpleiot/zephyr-siot

          Offhand, it seems I’ll need a separate top-level repo for my nRF and non-nRF projects as zephyr is pulled in through the nordic SDK. I could probably pull in zephyr-siot as a dependency to my nRF project repo, though, as most of the stuff I need is in the lib directory, so it seems it will function as a lib already.

            cbrake Offhand, it seems I’ll need a separate top-level repo for my nRF and non-nRF projects as zephyr is pulled in through the nordic SDK. I could probably pull in zephyr-siot as a dependency to my nRF project repo, though, as most of the stuff I need is in the lib directory, so it seems it will function as a lib already.

            Yea, it’s unfortunately the best way to ensure compatibility with the nRF chips that are not supported on vanilla Zephyr. I’ve seen projects in the past, like early iterations of Golioth’s SDK, use two manifest files.

              Yea you should be able to as long as the branch matches the version of NCS. I haven’t done it recently. Let me know if you run into any snags

              Just as alternative:

              https://github.com/boaks/zephyr-coaps-client/blob/main/west.yml

              https://github.com/boaks/zephyr-coaps-client/blob/ncs_2_9_x/west.yml

              That include the NCS directly. I mainly do this to support other nRF9160/61/51 based devices as well. It allows also to test newer NCS version as supported by NFED (on your own risk). For some boards, as long as the board-definitions are not in zephyr/boards itself, it requires to copy those definitions manually.

              Thanks, that looks like a good idea – may transition to that once I get a little further along …

              Terms and Conditions | Privacy Policy