Custom Teensy3.2 not getting flashed even with specific bootloader.

[npashine]

Hi I have developed the custom teensy 3.2 with my required extra module and its not getting flashed even with specific bootloader.
while burning what i saw is the programming windows just comes and goes like a flash.
Kindly find the PCB images in attachment.

U1 is bootloader.
U3 is MK20DX256VLH7.
Q2 is 16Mhz.
R2 and R3 are 33 ohm.

kindly let me know the placement and position of above components are correct or not.

Also find the video of flashing and verbose log in attachment.

Verbose log


12:39:38 IST: Teensy Loader 1.25, begin program
12:39:39 IST: File "Blink.cpp.hex". 12288 bytes, 5% used
12:39:39 IST: Listening for remote control on port 3149
12:39:39 IST: initialized, showing main window
12:39:39 IST: remote connection opened
12:39:39 IST: remote cmd: "comment: Teensyduino 1.25 - LINUX64"
12:39:39 IST: remote cmd: "dir:/tmp/build106311147377904526.tmp/"
12:39:39 IST: remote cmd: "file:Blink.cpp.hex"
12:39:39 IST: File "Blink.cpp.hex". 12288 bytes, 5% used
12:39:39 IST: remote cmd: "status"
12:39:39 IST: status data sent
12:39:39 IST: remote cmd: "auton"
12:39:39 IST: remote connection closed
12:39:39 IST: HID/linux: bus "001", device "002" vid=8087, pid=8000, ver=0004
12:39:39 IST: remote connection opened
12:39:39 IST: remote cmd: "status"
12:39:39 IST: status data sent
12:39:39 IST: remote cmd: "status"
12:39:39 IST: status data sent
12:39:39 IST: remote cmd: "status"
12:39:39 IST: status data sent
12:39:39 IST: remote cmd: "status"
12:39:39 IST: status data sent
12:39:39 IST: remote cmd: "status"
12:39:39 IST: status data sent
12:39:39 IST: remote cmd: "status"
12:39:39 IST: status data sent
12:39:40 IST: remote cmd: "status"
12:39:40 IST: status data sent
12:39:40 IST: remote cmd: "status"
12:39:40 IST: status data sent
12:39:40 IST: remote cmd: "status"
12:39:40 IST: status data sent
12:39:40 IST: remote cmd: "status"
12:39:40 IST: status data sent
12:39:40 IST: remote cmd: "status"
12:39:40 IST: status data sent
12:39:40 IST: remote cmd: "status"
12:39:40 IST: status data sent
12:39:40 IST: remote cmd: "status"
12:39:40 IST: status data sent
12:39:40 IST: remote cmd: "status"
12:39:40 IST: status data sent
12:39:40 IST: remote cmd: "status"
12:39:40 IST: status data sent
12:39:40 IST: remote cmd: "status"
12:39:40 IST: status data sent
12:39:41 IST: remote cmd: "status"
12:39:41 IST: status data sent
12:39:41 IST: remote cmd: "status"
12:39:41 IST: status data sent
12:39:41 IST: remote cmd: "status"
12:39:41 IST: status data sent
12:39:41 IST: remote cmd: "status"
12:39:41 IST: status data sent
12:39:41 IST: remote cmd: "status"
12:39:41 IST: status data sent
12:39:41 IST: remote cmd: "status"
12:39:41 IST: status data sent
12:39:41 IST: remote cmd: "status"
12:39:41 IST: status data sent
12:39:41 IST: remote cmd: "status"
12:39:41 IST: status data sent
12:39:41 IST: remote cmd: "status"
12:39:41 IST: status data sent
12:39:41 IST: remote cmd: "status"
12:39:41 IST: status data sent
12:39:42 IST: remote cmd: "status"
12:39:42 IST: status data sent
12:39:42 IST: remote cmd: "status"
12:39:42 IST: status data sent
12:39:42 IST: remote cmd: "status"
12:39:42 IST: status data sent
12:39:42 IST: remote cmd: "status"
12:39:42 IST: status data sent
12:39:42 IST: remote cmd: "status"
12:39:42 IST: status data sent
12:39:42 IST: remote cmd: "status"
12:39:42 IST: status data sent
12:39:42 IST: remote cmd: "status"
12:39:42 IST: status data sent
12:39:42 IST: remote cmd: "status"
12:39:42 IST: status data sent
12:39:42 IST: remote cmd: "status"
12:39:42 IST: status data sent
12:39:42 IST: Verbose Info event
12:39:43 IST: remote cmd: "status"
12:39:43 IST: status data sent
12:39:43 IST: remote cmd: "status"
12:39:43 IST: status data sent
12:39:43 IST: remote cmd: "status"
12:39:43 IST: status data sent
12:39:43 IST: remote cmd: "status"
12:39:43 IST: status data sent
12:39:43 IST: remote cmd: "status"
12:39:43 IST: status data sent
12:39:43 IST: remote cmd: "status"
12:39:43 IST: status data sent
12:39:43 IST: remote cmd: "status"
12:39:43 IST: status data sent
12:39:43 IST: remote cmd: "status"
12:39:43 IST: status data sent
12:39:43 IST: remote cmd: "status"
12:39:43 IST: status data sent
12:39:43 IST: remote cmd: "status"
12:39:43 IST: status data sent
12:39:44 IST: remote cmd: "status"
12:39:44 IST: status data sent
12:39:44 IST: remote cmd: "status"
12:39:44 IST: status data sent
12:39:44 IST: remote cmd: "status"
12:39:44 IST: status data sent
12:39:44 IST: remote cmd: "status"
12:39:44 IST: status data sent
12:39:44 IST: remote cmd: "status"
12:39:44 IST: status data sent
12:39:44 IST: remote cmd: "status"
12:39:44 IST: status data sent
12:39:44 IST: remote connection closed

 

[Epyon]

A schematic would be more useful than a PCB image .

Did you connect VOUT33, VREGIN and VBAT to 3.3V?

 

[npashine]

Attached is the schematic.
I Guess I only connected VOUT33 and VBAT to 3.3 v but not VREGIN.

How to attach pdf?

 

[PaulStoffregen]

Indeed, trying to follow the traces from these PCB images is a lot of extra work! I looked only briefly (not nearly long enough to reverse engineer the schematic), but I can see at least a couple problems.

First, there seems to be 5 traces routed underneath the crystal. This utterly disregards the advice about crystal placement:

The crystal should be located close to the MK20 chip. A ground plane should be placed underneath the crystal. If using a 2 layer PCB design, the ground plane for the crystal should NOT make any other connections to ground, other than the crystal case ground, capacitor grounds (if adding extra capacitance) and to the ground pin next to the crystal pins.

Never route any digital signal directly underneath the crystal (if disregarding the ground plane advice). PCB designs that violate these rules have experienced crashes or unreliable operation due to digital signals disrupting the crystal.

C16 and C17 appear to be capacitors associated with the crystal, which route the extremely sensitive crystal signals even farther with more exposure to other signals. Not good.

Also not good, at least from what I can see in these pictures, are the via pads. They appear to have almost no annular ring (much less than even the trace width used all over this board). They also appear to use a very small drill size. Even the very best PCB fab would probably be quite challenged to successfully manufacture this design. From only what you've shown us, I would suspect many of your board's vias are probably not conducting.

Perhaps these are the only mistakes? But with so little attention paid to following the crystal guidelines and via design, I would suspect this board may have other issues. Again, posting only these images (actual view, rather than transparent overlays on the same axes) and no schematic makes helping difficult... far more than the time I can put into this message. But hopefully this quick look helps at least a little?

 

[PaulStoffregen]

Oh, I see you just posted a schematic. But the image is unreadable.

To attach a PDF, click "Go Advanced". Then in the advanced editor, scroll down and look for the "Manage Attachments" button. In the window which appears, click "Add Files". After the files are uploaded and added to the "Attachments" portion of that window, click "Done".

 

[npashine]

View attachment ToneTag_Ver3.0_Rev1.14.pdf
Schematic PDF.

 

[PaulStoffregen]

Have you read the many other threads about troubleshooting custom PCBs? They are all linked at the end of the MLK02 chip page. Many are based on the older MINI54 chip, but the process is the same.

The first step is to check the voltage on Program and Reset, both with and without holding the button (SW1 on your design).

But giving the via design and crystal layout on this PCB, I would imagine you will need to redesign the entire board, no matter what the troubleshooting shows.

 

[HWGuy]

In the video it looks like there is a missing jumper for the supply selection.

 

[npashine]

hey, HWGuy Actually I was running out of jumper but I shorted the supply in the bottom.
Thanks for the keen observation.

 

[npashine]

Hey, guys I have attached a new design kindly let me know its okay or not?