nRF52833-QDAA-B SoC chipset not detected during testing

RE: nRF52833-QDAA-B SoC chipset not detected during testing

Simonr — Thu, 03 Apr 2025 06:38:24 GMT

On the nRF54L15 DK we have a debug out that supports VDDIO voltages from 1.8V-3.6V, so if you need a debugger operating in 1.8V that could be worth a look. Alternatively using a dedicated J-Link programmer, as most of those also support 1.8V-3.6V.

Best regards,
Simon

RE: nRF52833-QDAA-B SoC chipset not detected during testing

Jhakan — Wed, 02 Apr 2025 04:06:22 GMT

Thanks for your response Simon. Yes will install 820 pF once again in the c8 pad and update you . Will check this first and if still not detected , we'll send a snippet of Visual studio where under connected device the chipset isn't displayed.

Regarding the debugging issue, will work initially by supplying 3.3 V to ournRF52833 chipset. However, we wanted to know if you use any debugger that operates in 1.8 V to check log. If so suggest what debugger do you use to view log files.

Additionally if you have enabled USB based flashing and debugging kindly share the configuration steps and supported files to avoid UART based debugging issues and as an alternate option.

RE: nRF52833-QDAA-B SoC chipset not detected during testing

Simonr — Tue, 01 Apr 2025 08:07:31 GMT

Can you try adding the 820pF onto the C8 pad to the QDAA-B boards as well? Please also specify what exactly is printed on the SoC that doesn't work correctly.

Regarding the debugging issues, this might be because the voltage on the nRF52833 doesn't match the debugger. You should also supply the nRF52833 with 3.3V if you have a debugger connected that runs on 3.3V.

Best regards,

Simon

RE: nRF52833-QDAA-B SoC chipset not detected during testing

Jhakan — Mon, 31 Mar 2025 09:57:28 GMT

Hello Simon,
Based on my understanding the only difference in hardware Configuration between nRF52833-QDAA & nRF52833-QDAA-B seems to be the C8 820 pF capacitor not to be installed. In our HW design we have a pad allocated for this capacitor however we haven't placed it in our pcb board.

In addition to this, we also observed some other things that we wanted to clarify with you guys. Currently we have started working with nRF52833-QDAA and flashed firmware build over JTag. The voltage input for the chipset and the other components installed is 1.8 V and it is constantly provided using a LDO . The Jtag used has voltage of 3.3 V and for debugging UART we use FTDI that also supplies 3.3 V. When debugging using FTDI our device undergoes continuous reset and the BLE advertising also stops. We want to know if this is because of the voltage difference between our board input voltage and the UART debugger.

RE: nRF52833-QDAA-B SoC chipset not detected during testing

Simonr — Mon, 31 Mar 2025 09:08:03 GMT

Thanks for the pointer Gaurav. Can you specify in this ticket what exactly is printed on the SoC that doesn't work correctly. N52833 should be the top line, but what are the other three? I think this SoC should be newer, and not require the C8 capacitor, but for clarity, do you have this capacitor included in your HW design Jhakan?

Best regards,

Simon

RE: nRF52833-QDAA-B SoC chipset not detected during testing

Gaurav Kapoor — Sat, 29 Mar 2025 05:14:16 GMT

Simon is it because of the design variation required for -B , Document AN149 , C8 capacitor thing ?

RE: nRF52833-QDAA-B SoC chipset not detected during testing

Jhakan — Fri, 28 Mar 2025 11:49:10 GMT

Hi Simon,
We use a JTag device to flash the SoC. When we tried with nRF52833-QDAA we were able to flash properly. But wheras in the case of nRF52833-QDAA-B the Soc was not visible under the connected devices drop down in Visual studio. Hence we weren't able to flash or debug with this chipset

RE: nRF52833-QDAA-B SoC chipset not detected during testing

Simonr — Fri, 28 Mar 2025 11:40:29 GMT

Can you explain what you mean by "not getting detected" exactly? The QDAA-B chipsets have readback protection enabled by default, so it might be this that's making you not be able to detect the board. Try running an nrfjprog --recover command to recover and recover the board where the readback protection is disabled.

Best regards,

Simon