Teensy 4.0 DOA?

Status
Not open for further replies.

Burdalfis

Member
I just received my OSHpark edition Teensy 4.0 in the mail today, and unfortunately it seems DOA. The 5V rail is at 5.0V, the 3.3V rail is at 3.3V, the On/Off, Program, and Vbat rails are all at 3.3V as well. The Vbat rail is 3.238V, and the other pins and the 3.3V rail are at exactly 3.294V, I highly doubt that matters but I figured I'd mention it anyways. Both of the LEDs do not illuminate whatsoever, and the teensy draws 0.03a from the USB port. I'm thinking dead microcontroller? Is there anything else I can test or try?

Thanks!
 
New out of package with no pins soldered? Never programmed? Just the bare board plugged into USB with no button press and no orange LED flash?

Not sure what the 'rail' in ref to "other pins and the 3.3V rail are at exactly 3.294V" ?

The other pins on power up should be at GND - unless plugged into something or reprogrammed?

Gotten a couple OSH purple Teensy's - all fine - they go through the PJRC test and package process and are seen to work and left with the No_USB Blink sketch installed.
 
Ah sorry, I should have specified. The Vbat pin is down from the 3.3V rail and the On/Off & Program rail.

I have tried a different cable, 5 in fact.

Yeah, it's a brand new board, fresh out of the ESD bag, no headers soldered, never programmed, no blink program from the manufacturer, or at least it's not working, the program is probably there, on the flash. My PC does not recognize it at all. lsusb turns up nothing. I have tried my desktop and two laptops, one laptop running windows 10 with the latest arduino and teensyduino installed, the other laptop and desktop running linux, also latest software.
 
Out of ESD pack it will not by design present any USB connect, only blink given 5V/GND.

But when it gets GND and 5V to VIN from USB ( data or power only ) even from a battery pack - it should Orange LED Blink. Blink will stop in any case the Program Button is pressed - or if the PGM pin is set to GND.

If the On/Off pin gets GND it will sleep the Teensy until all power removed - or GND released and then pressed again - but that is not an initial test - just to say it could be set OFF and will hold that while vBat has power.

Assuming 'rail' just means that pin? Seeing rail gave the image of a breakout board with rails on.
 
Oh I should add, the programming button does nothing. I have tried pressing it, holding it down for 15 seconds, and holding it down while plugging the teensy in, all to no avail. No device detected in Arduino, no new devices listed in lsusb, no change in current draw from the usb port, no LEDs.
 
Ah yes, perhaps I am using an old term, sorry. I mean rail as in a common power supply connection, or common ground connection. I believe the term comes from when there were literal copper rails, or bus bars as they're known now, inside your device for a common point to get power from.
 
AHA! I may have found the issue. There are three tiny SMD components, broken off. Damn FedEx, fast shipping but at a cost. The ESD bag is in rough shape, holes and dents too. Anyone know what components they are? I have a rather expansive hoard of SMD components, I'll just solder in some new ones.
 

Attachments

  • IMG_20200602_010513.jpg
    IMG_20200602_010513.jpg
    135 KB · Views: 89
Those are these 3 parts on the schematic.

schematic40.png

The part closest to pins 7, 8 and pad 33 is the inductor. You can use a wire or any ferrite bead rated for 100 mA or higher. The other 2 do need to be X7R or X5R ceramic capacitors, since they are providing the input pulses of current for the 3.3V to 1.15V step down switcher.

The pads near pins 6 & 5 are meant to be empty.
 
Ah yes, perhaps I am using an old term, sorry. I mean rail as in a common power supply connection, or common ground connection. I believe the term comes from when there were literal copper rails, or bus bars as they're known now, inside your device for a common point to get power from.

Cool, my understanding similar - but as noted involves external rails of that would imply connection - versus the untouched pins.

Any signs it was damaged in transit? Photos?

Opps - time distracted - cross posted ...
 
Paul and Defragster, you guys are awesome. Thanks so much for helping me. If I may ask, which part is which? I could probably buzz out what goes where with a multimeter but asking is easier.

And yeah, definitely some signs. I'd attach a photo of the bag but I seemingly cannot. Rescaling the image, increasing JPG compression, and just taking a new photo altogether haven't worked, I've always had issues on my phone. If you really want to see I can just link it to my Google drive, I really don't mind.
 
Also no sign of the components in the ESD bag or the bag the boards and the ESD bag came in, but I'm not about to go really looking for something that's as small as dust particles. :p
 
Beautiful. Thanks again! Excited to give the new 4.0 a go, the benchmarks are insane. I'll update tomorrow after work on whether it worked or not.
 
Das Blinkenlights! It's alive! Turns out I didn't have a ~4.7uf cap big enough to fit the footprint, so a X7E low esr low L 10uf cap will do. And no ferrite bead. I wouldn't be surprised if it wasn't too stable, especially at higher clocks. But hey, it works!

Looks like a few pads lifted too. And by lifted I mean cratered the board, those OSHpark boards really are high quality. My guess is that a board edge in the bag caught and sheared off the components during packing or shipping, since it's just the ESD bag with the teensy tossed in with a bunch of loose boards in a bag.
 

Attachments

  • IMG_20200602_113729.jpg
    IMG_20200602_113729.jpg
    184.5 KB · Views: 79
  • IMG_20200602_113706_1_resize_60.jpg
    IMG_20200602_113706_1_resize_60.jpg
    364.6 KB · Views: 80
Status
Not open for further replies.
Back
Top