https://devzone.nordicsemi.com/f/nordic-q-a/127446/nrf9160-s-rx-no-longer-receiving-dataWe&#39;ve designed our own board based on nRF9160 for main CPU w/ LTE and an nRF52 for BLE. Using BMP for debugging. I&#39;ve successfully run several boards through the production process: - update modem firmware to 1.3.6 - use nrfcredstore to generateen-USTelligent Community 13Mon, 16 Mar 2026 20:23:02 GMThttps://devzone.nordicsemi.com/thread/563373?ContentTypeID=1Mon, 16 Mar 2026 20:23:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:cc7cda18-85e9-4434-ad84-c6315bb548c3Mikael Jansson<p>Hello,</p> <p>It turns out I have the intelligence of a monkey! See, my nRF52 on the board is cross-wired on UART, and I&nbsp;<em>thought</em> I had loaded a blank nRF52 FW file, setting all pins to hi-z. Well, turns out that if your DTS file sets up UARTs and SPIs and whatnot, they most definitely won&#39;t be hi-z even though you have a main() {}. :-)&nbsp;</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/563352?ContentTypeID=1Mon, 16 Mar 2026 14:14:46 GMT137ad170-7792-4731-bb38-c0d22fbe4515:12201e13-b6f2-4bb1-94f9-ddc5ae2583d5Einar Thorsrud<p>Hi,</p> <p>If I read this correctly you have verified UART communication with other test firmware, but it fails with the AT client? Can you double check that you have built the AT client for your board with the correct UART pins?</p><div style="clear:both;"></div>