MDBT42Q GPIO Pins Not Responding

RE: MDBT42Q GPIO Pins Not Responding

mosonu — Mon, 25 Nov 2024 09:08:26 GMT

Thanks, that solved my problem.

RE: MDBT42Q GPIO Pins Not Responding

Kenneth — Wed, 16 Oct 2024 11:07:12 GMT

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

RE: MDBT42Q GPIO Pins Not Responding

mosonu — Wed, 16 Oct 2024 04:59:22 GMT

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:

RE: MDBT42Q GPIO Pins Not Responding

Kenneth — Tue, 15 Oct 2024 10:54:52 GMT

Hello

[quote user=""]Sometimes, nRF Connect is able to detect the chip information, but other times it fails to do so.[/quote]

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