Coap Client SED low power

RE: Coap Client SED low power

Mary — Wed, 15 Mar 2023 16:44:58 GMT

Found it.

This code puts the flash device in deep power down, then sets the CSn output high.

#if (CONFIG_SPI_NOR - 0) ||				\
	DT_NODE_HAS_STATUS(DT_INST(0, jedec_spi_nor), okay)
#define FLASH_DEVICE DT_LABEL(DT_INST(0, jedec_spi_nor))
#define FLASH_NAME "JEDEC SPI-NOR"
#elif (CONFIG_NORDIC_QSPI_NOR - 0) || \
	DT_NODE_HAS_STATUS(DT_INST(0, nordic_qspi_nor), okay)
#define FLASH_DEVICE DT_LABEL(DT_INST(0, nordic_qspi_nor))
#define FLASH_NAME "JEDEC QSPI-NOR"
#elif DT_NODE_HAS_STATUS(DT_INST(0, st_stm32_qspi_nor), okay)
#define FLASH_DEVICE DT_LABEL(DT_INST(0, st_stm32_qspi_nor))
#define FLASH_NAME "JEDEC QSPI-NOR"
#else
#error Unsupported flash driver
#endif

#define QSPI_CS_DEVICE		DT_GPIO_LABEL(DT_NODELABEL(qspics), gpios)		
#define QSPI_CS_PIN			DT_GPIO_PIN(DT_NODELABEL(qspics), gpios)


void flash_low_power()
{
	const struct device *flash_dev;
	const struct device *cs_dev;

	flash_dev = device_get_binding(FLASH_DEVICE);

	pm_device_action_run(flash_dev, PM_DEVICE_ACTION_SUSPEND);

	cs_dev = device_get_binding(QSPI_CS_DEVICE);
	if (cs_dev == NULL) {
		printk("Cannot bind gpio device\r\n");
		//return -ENODEV;
		return;
	}
	
	int err = gpio_pin_configure(cs_dev, QSPI_CS_PIN, GPIO_OUTPUT);
	gpio_pin_set(cs_dev, QSPI_CS_PIN, 1);

}

Mary

RE: Coap Client SED low power

Mary — Wed, 15 Mar 2023 13:56:36 GMT

I think most of the current is from the flash device, MX25R6435. From other posts, I saw that the CSn must be configured as gpio output and set high, but it doesn't come up that way. I will eventually be using MCUBOOT, with externa flash as slot1.

I created a "HelloWorld" but with this added to the prj.conf

CONFIG_SERIAL=n
CONFIG_PM=y
CONFIG_PM_DEVICE=y

I set the CSn as gpio output, and set it high. I am now down to 121 uA, which is still too high, but there are some other devices I need to look into.

About the QSPI flash...

I tried adding this code to configure the CSn line. Stepping into, then out of this function led to a odd place, where the call stack wasn't as expected. I ended up in nf_qspi_nor.c, in functions that I did not call. I noticed that there is support for "Anomaly 122" there. So, what is the proper way, using ncs, to put the flash in deep power down, then reawaken it when I need to use it? I will only use it for OTA updates.

void flash_low_power()
{
	struct device *dev;
	// eratum 122
	// https://infocenter.nordicsemi.com/index.jsp?topic=%2Ferrata_nRF52840_Rev2%2FERR%2FnRF52840%2FRev2%2Flatest%2Fanomaly_840_122.html
	*(volatile uint32_t *)0x40029010ul = 1ul;
    *(volatile uint32_t *)0x40029054ul = 1ul;
    nrfx_qspi_uninit();

	dev = device_get_binding(QSPI_CS_DEVICE);
	if (dev == NULL) {
		printk("Cannot bind gpio device\r\n");
		//return -ENODEV;
		return;
	}

	
	int err = gpio_pin_configure(dev, QSPI_CS_PIN, GPIO_OUTPUT);
	gpio_pin_set(dev, QSPI_CS_PIN, 1);

}

Here are the requested files.

devzone.nordicsemi.com/.../my_2E00_config devzone.nordicsemi.com/.../6320.zephyr.dts

Mary

RE: Coap Client SED low power

Sigurd — Wed, 15 Mar 2023 13:28:37 GMT

Hi,

Could you post the .config file and the zephyr.dts file that is generated in the build folder when you build the sample?