Ultrasonic welding and nRF52

RE: Ultrasonic welding and nRF52

Kenneth — Thu, 28 Jun 2018 16:13:06 GMT

Hi Kari,

Have you tried some basic \blinky example to check if pins are operational? Have you tried debug the application to check for asserts? What about just using a simple BLE beacon example without any pins or debug output? Maybe there is a floating input (e.g. UART flow control or RXD) that is not connected.

Best regards,
Kenneth

RE: Ultrasonic welding and nRF52

kmalmiv16 — Wed, 13 Jun 2018 12:42:06 GMT

Hi Andreas,

Thanks for quick response!

OK, good you have not heard any issues with ultrasonic welding and bonding wires. Then there might be something else,

LF clock is running, voltages are ok in all pins, flashing is successfull (=>HF clock is running), but device's average (continuously) current consumption is about 4mA. Regularily there is 7mA current pulse, see figure.

I will continue studies...

Rgds,

-Kari-

RE: Ultrasonic welding and nRF52

Andreas — Wed, 13 Jun 2018 09:13:22 GMT

Hi Kari,

We know that quite a few of our customers do manufacture their enclosures, housings or parts of it using ultrasonic welding, at least to some extent. To date we have no reports that this has damaged our parts.

Still, I fail to see how a broken bonding wire would cause this issue. What is the reset reason? Do you measure stable voltages on all DEC pins (except perhaps when resetting)? Have you changing the LF clock source, or running a simple code that just initializes the oscillators, and reports the outcome e.g. by toggling a GPIO?

Best regards,

Andreas