I’ve started transition a project I’ve been working on off of Photon breadboards and onto custom boards with a P1.
After a lot of trial and error, I’ve determined that I’m unable to DFU flash firmware to my custom boards, but cloud flashing works just fine. It doesn’t matter if I locally compile or download the binary, and it doesn’t matter which application I try flashing (I’ve tried both my code and Tinker and in both cases DFU doesn’t work and cloud flashing does)
Now I’m not 100% sure what’s going wrong as the LEDs we put on the boards have an opaque lenses and I’m not sure what color they’re supposed to be at any time. I believe that the devices are stuck trying to connect to the WiFi/cloud, but this seems odd as my application doesn’t utilize any cloud functions and works fine when not connected. So I really don’t know what’s wrong other than something goes wrong during DFU and I need to use Particle Doctor to recover the device.
And that brings me to the issue of my Bricked board. I’d been successfully “restoring” boards that weren’t working correctly most of the day and had taken one back to the office with me for further testing. After verifying again that DFU was causing the issue I went about restoring the device with Particle Doctor. I got to the first step after flashing the doctor app (Which seems to be the only thing I can successfully flash over DFU) of selecting DHCP type, when I encountered a BSOD with the error code of WDF_VIOLATION. After my computer had finished rebooting I went to put my board into DFU mode when the LED on the board went out and hasn’t come back on since. The only difference when I was in the office is that my laptop was hooked up to a docking station and thus the board was plugged into a USB hub vs directly into my laptop. Windows doesn’t recognize that anything is there when I plug it in and I’m out of ideas as to what to do next.