MDBT42Q GPIO Pins Not Responding

Hello,

I'm trying to configure the GPIO pins on the MDBT42Q-P192KV2 module, but they are not responding as expected.

I'm using the nRF52840 Development Kit to flash the code. Sometimes, nRF Connect is able to detect the chip information, but other times it fails to do so. Even when it successfully detects the chip and flashes the code, I'm unable to measure 3V on the corresponding pin.

Any help or suggestions would be greatly appreciated!

Thank you.

Code :

#include <zephyr/kernel.h>
#include <zephyr/drivers/gpio.h>

/* 1000 msec = 1 sec */
#define SLEEP_TIME_MS   4000

/* The devicetree node identifier for the "led0" alias. */
#define LED1_NODE DT_ALIAS(led1)

/*
 * A build error on this line means your board is unsupported.
 * See the sample documentation for information on how to fix this.
 */
static const struct gpio_dt_spec led = GPIO_DT_SPEC_GET(LED1_NODE, gpios);

int main(void)
{
	int ret;

	if (!gpio_is_ready_dt(&led)) {
		return 0;
	}

	ret = gpio_pin_configure_dt(&led, GPIO_OUTPUT_INACTIVE);
	if (ret < 0) {
		return 0;
	}

	gpio_pin_set_dt(&led,1);

	return 0;
}


overlay and prj config files are attached.
8424.prj.conf1581.nrf52dk_nrf52810.overlay

Parents
  • Hello

    Sometimes, nRF Connect is able to detect the chip information, but other times it fails to do so.

    Assuming this the problem, can you show me a picture of your setup, e.g. what supply voltage is and what wires are connected between the DK and your module? Can you send me a screenshot when if fails? 

    Make sure to connect all 4 wires of gnd, vdd, swdio and swdclk to the module. Also try to pull up (to VDD) the reset pin of the nRF52810 in case it's enabled and possible low.

    Kenneth

  • When I can not see chip name (nrf52810) the error is :
    error] [ Client] - Encountered error -105: Command connect_to_emu_with_snr executed for 23560 milliseconds with result -105
    ERROR: Unable to connect to a debugger.
    [error] [ Worker] - JLinkARM.dll Open returned error 'Cannot connect to J-Link.'
    ERROR: The JLinkARM DLL timed out while communicating to the J-Link probe.
    ERROR: If the error condition persists, run the same command again with
    ERROR: argument -- log, contact Nordic Semiconductor and provide the generated
    ERROR: log.log file to them.
    NOTE: For additional output, try running again with logging enabled (--log).
    NOTE: Any generated log error messages will be displayed.
    FATAL ERROR: command exited with status 35: nrfjprog --program /home/test/nrf_ws/nrf52810_icm42670/build/zephyr/zephyr.hex --sectoranduicrerase --verify -f NRF52 --snr 1050206029

    Wiring: 



  • If you only get this intermittently it may indicate some bad connection, if you get this allways I would suggest try to pull nRESET (pin 0.21) directly to VDD.

    Kenneth

Reply Children
No Data
Related