nRF52833-QDAA-B SoC chipset not detected during testing

[Jhakan]

Hello team,
We are currently working on a project that used nRF52833-QDAA-B as the MCU chipset. We have  followed the circuit configuration 5 for our test case. Our SoC is not getting detected when we have used this configuration. Whereas, when tried the same with nRF52833-QDAA-R/ nRF52833-QDAA-R7( same number of pins, package)  the chipset is being detected and we are able to build & flash the code. Kindly specify why this occurs and how to rectify this.

Also specify is we can work with  nRF52833-QDAA-R and build our entire project. If not what are the complications if used.

[Simonr]

Hi

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

[Jhakan]

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.

[Simonr]

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