M
mikcatta

  • Jan 17, 2021
  • Joined Nov 27, 2020
  • 0 best answers
  • @mikcatta so I spent some time playing around with compiling with the Toolchain Manager and had some success with the NFED repo.

    I used v1.4.1 and it work a-ok. Simply open a bash prompt or command prompt. This will pre-load your environment:

    You’ll have to copy your nrf9160-feather folder from nfed into whichever nRF Connect SDK you’re using. In my case I put my SDK install in C:\ncs\v1.4.1\

    Change directories and then compile as prescribed before: west build -b circuitdojo_feather_nrf9160ns -p

    • @mikcatta can you delete your build folder and try again with west build -b circuitdojo_feather_nrf9160ns

      • mikcatta Yes I believe all steps have been followed, the only thing I would mention is that I already had the SDK installed for compiling for the Thingy91, which was/is working.

        Sorry for the delay @mikcatta. I didn’t see the notification you replied!

        With the above being said, it’s difficult to add the NFED directory to an already existing NCS copy.

        Have you tried compiling this code for the nRF91 Thingy?
        How did you manage the install process of NCS?

        Things may not work as expected if you’re using the Nordic’s install wizard/Segger Studio. I recommend you pull a fresh repo using the instructions here.

        • Hey @mikcatta

          mikcatta Is it possible to implement a normally closed loop on this feather board (without it drastically using more current)?

          You’d have to use a GPIO interrupt which can run down to the (almost) lowest level of operation. I do have an example of how to set up GPIO interrupts in the nfed repository.

          mikcatta Also, what connectors are on the board for LTE? I Thingy91 uses a strange Muratta connector for the external LTE?

          The connectors for both the GPS and LTE are U.FL aka IPEX connectors. They’re pretty standard for devices across IoT. There’s even smaller variants like they use in phones but that wasn’t necessary here. 😀

        Terms and Conditions | Privacy Policy