Thanks for the suggestions. I’ll definitely keep them in mind.

16 days later

AchimKraus Thingy:91 is missing expandability and a DK is just to large in size.

Recently Nordic Semi has been making a few changes to the Thingy91:X devicetree files, e.g. added support for the expansion board and other misc changes. I don’t see an “edge_conenctor” defined in the "“thingy91x_nrf9151” devicetree yet like in nRF5340. Somewhat slow progress at the moment, perhaps there are delays in nRF9151 availability.

I expect the Thingy91:X Expansion Board will be the same spec as that in the Thingy:53 (nRF5340) or an enhanced version with backward compatibility. The nRF7002-EB WiFi 6 ( I use several with Thingy:53 and nRF52840 boards) should work with the Thingy:91X. With I2C (EB and I2C STEMMA), SPI and several GPIOs, the Thingy:91X should be pretty expandable for sensors and peripherals.

Originally, both the Thingy91:X and nRF9131-EK were planned for Q1 release. Hopefully we’ll see a Q3 release.

    Yea it will be cool to see. Who knows I may base a new board off of the 9151 😉 First thing is first, gotta finish the 9161 version!

      a month later

      Proto 2 has been on my desk for a few days now. I’m trying to figure out what’s drawing so much current with the programmer disabled. (Getting 1mA in active sleep whereas it should be < 10uA)

      I think it’s going to have to come to removing parts until I get the expected current. 😭 We’ll see!

        zpm1066 jaredwolff Looks great! What’s the beige connector? I2C STEMMA?

        Currently connected to the SWD lines for the RP2040 for programming with an external Picoprobe

          Now we’re talking!

          Average of 6uA in sleep mode at 3.6V. That includes the LIS2DH and the external flash in sleep/power down. Slightly better than the current nRF9160 Feather at ~10uA.

            One culprit is the UART console. That should be disabled when the device is operating in low current applications:

            int setup_uart()
{

	static const struct device *const console_dev =
		DEVICE_DT_GET(DT_CHOSEN(zephyr_console));

	/* Disable console UART */
	int err = pm_device_action_run(console_dev, PM_DEVICE_ACTION_SUSPEND);
	if (err < 0)
	{
		printk("Unable to suspend console UART. (err: %d)\n", err);
		return err;
	}

	/* Turn off to save power */
	NRF_CLOCK->TASKS_HFCLKSTOP = 1;

	return 0;
}

            I was having issues with NCS 2.5.x so when I switched to 2.6.1 I had much better luck configuring the nPM1300. I’m aiming to release the board synced with NCS 2.7.x.

              jaredwolff Nice! Makes sense that the UART be disabled for low current usage.

              I’m glad that the nRF9161 board will be released with NCS 2.7.x. Latter has some major changes in SoC / board names and definitions, plus Sysbuild for multi-image/multi-SoC support.

              I have NCS 2.7.0 (pre-release) installed but will wait for a “release Version” before moving a few of the multi-image builds to Sysbuild.

              Is the beige connector going to be for I2C STEMMA? Thanks.

                  zpm1066 Is the beige connector going to be for I2C STEMMA? Thanks.

                  Currently connected to the SWD lines for the RP2040 for programming with an external Picoprobe

                      jaredwolff
                      Is the plan to let it stay connected to SWD on board release or use it for I2C and program the board via USB? Thanks.

                        The RP2040 can be programmed with the built in bootloader. The nRF9161 is programmed with the RP2040 running CMSIS DAP.

                        I actually don’t necessarily need the extra connector for programming purposes. Something like Qwiic or STEMMA would be attractive for you @zpm1066?

                          jaredwolff Absolutely! An I2C STEMMA / Qwiic connector would be pretty useful for quick hookups to sensors, OLED display, etc. Most boards these days support this connector.

                            Also, just a thought - Not sure if it’s relevant for others, or if the cost is going to be higher, but a 16bit ADC instead of the 12bit one currently on would be great 🙂 I’m currently connecting adafruits ADS1115 to get that additional resolution 🙂

                            Get really more than 12 bits from a ADC isn’t easy in my experience.
                            And sometimes it requires an additional amplification. So I’m not sure, how many will then be happy with it.

                            Not sure if you guys have had this issue but modem traces don’t work well with non-Nordic devices since a while back. (The nRF9161 Feather will only have one USB-UART port)

                            Working on a PR for the Cellular Monitor so it can use any available port on your machine.

                            Great little tool especially to find out that these devices are no longer being pre-programmed with IMEIs! I will be pre-programming them here so no worries about that.

                            Nice thing is both the onboard LNA works for GPS. A single antenna is all that’s needed for the nRF9161 Feather!

                            Tracking:  5 Using:  5 Unhealthy: 0
-----------------------------------
Latitude:       41.XXX
Longitude:      -72.XXX
Altitude:       89.0 m
Accuracy:       10.0 m
Speed:          0.3 m/s
Speed accuracy: 1.2 m/s
Heading:        0.0 deg
Date:           2024-07-23
Time (UTC):     20:19:55.091
PDOP:           5.1
HDOP:           2.6
VDOP:           4.4
TDOP:           3.7
                            Terms and Conditions | Privacy Policy