10

I've been designing a custom circuit around the Microchip ATSAMD21E MCU. I thought my circuit design was fine until I soldered it all together and discovered a short between 3.3V and GND. (Needless to say, this caused the voltage regulator to get hot and angry and smoke to appear, and nothing worked).

After several days of debugging, I realized the MCU itself is causing the short. Upon further inspection, it looks like the VDDANA pin (pin 9), which I connect to 3.3V, is shorted to the GND pin (28) internally to the chip. I even took a brand new MCU out of the tray and tested it without any PCB at all, and lo and behold it is shorting GND(28) to VDDANA(9).

Ok so now I don't understand how I'm supposed to power this MCU!

My schematic:

enter image description here

For reference, this is what the data sheet says I'm supposed to do:

enter image description here

Here's the pinout according to the Datasheet:

enter image description here

Joel Spolsky
  • 547
  • 1
  • 5
  • 17

1 Answers1

14

Ok, it turns out that the MCU's I purchased are ATSAMD21E17L -- notice the L, which have a different pinout.

SAMD21ExxL pinout

There was nothing about "L" variants in the older datasheet I have been reading, but the newest datasheet describes the -L variant as being "Pinout optimized for Analog and PWM" whatever that means.

Product part number showing new L variant

This probably explains how I was able to buy these chips in the first place, but CMON MICROCHIP WHY YOU GOTTA MAKE MY LIFE IMPOSSIBLE :( :(

Kudos and thanks to TQQQ and DKNguyen who set me on the right track

SamGibson
  • 17,231
  • 5
  • 37
  • 58
Joel Spolsky
  • 547
  • 1
  • 5
  • 17
  • 1
    Putting PA27 and PA28 (assuming these are analog pins given the name) right next to digital logic (VDDCORE, RESETN, main core GND pin) is rather suboptimal from a noise point of view. I can see why they have the variant, although the rearrangement is unfortunate. – TLW Feb 20 '22 at 07:52
  • 2
    It really never occurred to me that there might be a pinout-incompatible variant and that might be my problem. I guess, because I am too new at this, and just assumed if it wasn't working, it had to be my fault :) – Joel Spolsky Feb 20 '22 at 16:06
  • 1
    @JoelSpolsky Well, it was - you just assumed the fault was somewhere it wasn't ;) – J... Feb 20 '22 at 19:06