The pin VUSB is power input from USB? So it’s possible to power the device via that pin, if no USB is connected?

    zpm1066 btw - I’ve been field testing nRF9131-EK for DECT NR+ and LTE-M/NB-IoT with GNSS. A very neat board, slightly longer than a Sparkfun Thing+ board, with nPM1300, nPM600, 256Mb external flash memory, and a Segger J-link OB. There are a few more enhancements coming down the line to make it even better.

    I believe the 9131 does require more certification testing in order to legal deploy devices that use it. Versus the 9160, 9161 and 9151.

    AchimKraus Is there an update on the pyocd issue?

    I have not made progress. I’ve been focusing elsewhere. I have been playing with using probe-rs instead as it has been added as a target recently for Zephyr. I ported the pyocd code that updates the modem firmware also to use probe-rs (and using it in production). So I’m leaning to use that.

    Just to mention: the nRF9161 prototype does a pretty well job on my side. Works since August without issues.
    That’s amazing to hear. Thank you for testing it @AchimKraus !

    AchimKraus The pin VUSB is power input from USB? So it’s possible to power the device via that pin, if no USB is connected?

    VUSB is connected direct to the headers so you could power the device through the pin:

    I have not tested if it plays well with USB. (it may work just fine) I typically recommend using VBAT pin for external power and turning the charger off. It depends on your application though.

            jaredwolff I believe the 9131 does require more certification testing in order to legal deploy devices that use it. Versus the 9160, 9161 and 9151.

            Agreed. The nRF9151 is the sanction proof nRF91 and what Nordic Semi recommends for all new cellular designs.

            The nRF9131-EK is a very goodcompact reference design for DECT NR+ and LTE with J-Link OB that can be used as a dev board if the additional expansion offered by nRF9151-DK is not required.

                zpm1066 The nRF9131-EK is a very goodcompact reference design for DECT NR+ and LTE with J-Link OB that can be used as a dev board if the additional expansion offered by nRF9151-DK is not required.

                Oh yea. Feather-ish formfactor. Didn’t realize they had something this small. Good on them.

                    Great! Do you currently have a schedule for the nRF9151 feather (beta-boards)?

                      5 days later

                      AchimKraus Great! Do you currently have a schedule for the nRF9151 feather (beta-boards)?

                      Pre-order is now available. I have a few in stock I can ration between you and @zpm1066. Full availability Q1 2025. 😃 (I’m aiming for sooner though)

                          Any discount code possible? Mainly to compensate the shipping costs ;-).

                          5 days later

                          Hi @AchimKraus

                          No discounts on the nRF9151 until it’s fully launched. These beta boards take a long time to assemble and test. Upshot is the tester is nearly complete. 😃

                          Keep an eye out for upcoming discounts on the nRF9160 though..

                          On another note:

                          I played around with the nRF9151 Feather using nRF Connect for VSCode. Works well for those who prefer Nordic’s tools. Only big addition is to installing probe-rs or pyocd. Update to the docs are here: https://docs.circuitdojo.com/nrf9151-feather/using-vscode.html

                          13 days later

                          jaredwolff

                          On the current nrf9160 Feather USB does NOT play well when powering the device over the VUSB pin.

                          It would be nice if the next feather did for debugging purposes. I currently have my feathers deployed in 12V LiFePo battery powered systems with a buck converter to give me 5V for the feather and other devices.

                          I probably should’ve used the VBAT pin to power the feather, but it would be nice to add small lithium battery to act as a backup so I can continue logging power issues in the larger system.

                              Voxorin On the current nrf9160 Feather USB does NOT play well when powering the device over the VUSB pin.

                              Voxorin which version do you have again? Can you explain in what way? I removed the diode on 5V a few revisions ago.

                              Voxorin It would be nice if the next feather did for debugging purposes. I currently have my feathers deployed in 12V LiFePo battery powered systems with a buck converter to give me 5V for the feather and other devices.

                              Right now i’m powering it via the 5V pin for testing. So, it should work out in the field the same way. The only detail is whether or not it will be happy when you plug in USB.

                              VBUS pin is directly connected to USB in both designs now:


                              Voxorin I probably should’ve used the VBAT pin to power the feather, but it would be nice to add small lithium battery to act as a backup so I can continue logging power issues in the larger system.

                              Gotcha!

                                        jaredwolff Voxorin which version do you have again? Can you explain in what way? I removed the diode on 5V a few revisions ago.

                                        I was wrong, this isn’t an issue with the current feather.

                                        It turns out the issue only occurs when I use a C to C cable with my thunderbolt dock, and of course that’s the port I always use for testing haha.

                                            Terms and Conditions | Privacy Policy