This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF52810-CAAA SPI setting And current consumption.

I am developing the product using nRF52810-CAAA.
I have initialized it for SPI use as follows.

extern void mbprv151_spi_init(void)
{
	ret_code_t err_code;

	nrf_drv_spi_config_t spi_config = NRF_DRV_SPI_DEFAULT_CONFIG;

	spi_config.sck_pin		= MBPRV151_SCK_PIN;
	spi_config.miso_pin 	= MBPRV151_MISO_PIN;
	spi_config.mosi_pin 	= MBPRV151_MOSI_PIN;
	spi_config.ss_pin		= NRF_DRV_SPI_PIN_NOT_USED;
	spi_config.frequency 	= NRF_DRV_SPI_FREQ_500K;

	err_code = nrf_drv_spi_init(&m_spi_master, &spi_config, NULL, NULL);
	APP_ERROR_CHECK(err_code);
}


This will increase the current consumption by 3mA.
Why?
Is this normal?

Thanks,

I can not find a way to solve it.
I would appreciate your urgent reply.

Parents
  • You didn't mention which SDK you are using, but I think prior to 14 the drive did enable the pull up on Master In Serial Out (MISO) line which would cause some extra current draw if slave device drives that data line low. In 14 they introduced a define NRF_SPI_DRV_MISO_PULLUP_CFG which if set to 0 doesn't enable the pullup.

    But I don't think the pull would be 3mA

Reply
  • You didn't mention which SDK you are using, but I think prior to 14 the drive did enable the pull up on Master In Serial Out (MISO) line which would cause some extra current draw if slave device drives that data line low. In 14 they introduced a define NRF_SPI_DRV_MISO_PULLUP_CFG which if set to 0 doesn't enable the pullup.

    But I don't think the pull would be 3mA

Children
No Data
Related