I have a project that I am working on using an MSP430F5510 that interfaces with a small brushed DC motor driver and 2.4GHz wireless transceiver. All components (including the battery) are housed within a small cylindrical plastic enclosure with plastic end caps, i.e. no external connections. The only metallic parts visible from outside the enclosure are some small fasteners used for mounting internal components.
The problem is that after applying ESD pulses to the assembled device (air discharge at 15kV according to IEC 61000-4-2 at various points on the enclosure), the MSP430 occasionally "resets". Fortunately, the device quickly recovers but inspection of the SYSRSTIV register immediately following each reset returns a value of 02h indicating BOR. This behavior is also consistent with what I've observed in practice using the wireless connection to query the cause of the previous device reset.
I understand that ESD related problems can induce a variety of system level upset conditions including device reset. However, the cause of each reset is very consistent and always points to the brownout circuity of the MSP430. With this in mind, I'm a bit lost of how next to proceed with diagnosing/correcting this issue. I've tried searching the web for resources on system level ESD robustness (including SLAA530) and found several design practices that may help alleviate the problem. However, I'm hesitant to redesign my PCB without fully understanding how or why a BOR is consistently caused by ESD.
Is a BOR reset even consistent with what one might expect during ESD testing or is it likely to indicate a problem elsewhere in the system (poor power supply, insufficient decoupling, etc.)? Is there something that I might have overlooked?
My apologies if additional information is needed. I'm happy to provide other materials if it may help.
Thanks in advance!