First, wiltwong, let me congratulate you on your soldering skills. I can barely even see all those little wires, let alone attempt to solder them...
But second, my teensy 3.1 failed in exactly this same way, with a pop, point source glow + smoke, followed by a bump in that same place.
To help me figure out what I did wrong (and avoid it on the next teensy), does anyone know what type of error will result in the above behavior?
Summary of what I'm doing is below, if that helps, but not really asking anyone to solve this for me. I just need some more info to help me investigate more.
I had it plugged into an OctoWS2811 and was powering everything by supplying +5V and ground to those pins on the OctoWS2811.
I can't find a link to the power supply i'm using but it is a 5v 25A in ATX form factor and i was using the +5V "standby" line for power and had not yet pulled the power-on pin low to spin up the main 5V rails (there is no +12V so i don't think the "overvoltage when not powering +12V" applies and i measured the voltage at 5.2V)
I had connected it the exact same way several times before (and started the main +5V to power the LEDs, and ran a tweaked version of the Rainbow example).
This time I had loaded the Fire example, but i didn't (directly) change anything related to any pins. My changes were:
1. modify xy function for my 2-strand 10x10
2. set ledsPerPin to 50 instead of calculating by width*height, since i'm only using two strands
3. set width and height to 10.
I did have the LEDs connected, but not (yet) powered. And no code to wait until the power comes on to try to send them data. It's not possible to burn the chip by trying to send data + ground to WS2811/2 LEDs without the +5V on the LEDs is it?