Forum Rule: Always post complete source code & details to reproduce any issue!
Results 1 to 15 of 15

Thread: Teensy 4.0 Schematics/eagle files?

  1. #1
    Junior Member
    Join Date
    Aug 2019
    Posts
    3

    Teensy 4.0 Schematics/eagle files?

    When will these be available on the site or github?

  2. #2
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    9,012
    Paul posted recently to a similar post - they are on his list of things to be done ASAP. It has been noted that his Schematic creation is manually created for usable detail - not just spit out from other software.

    https://forum.pjrc.com/threads/57112...l=1#post211727

  3. #3
    Junior Member
    Join Date
    Aug 2019
    Posts
    3
    awesome, i'll keep on waiting

  4. #4
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    20,294
    I'm drawing the schematic now. It's going to take a while...

    But here's the GPIO part. Hopefully no big surprises?

    Click image for larger version. 

Name:	schematic40_gpio.png 
Views:	42 
Size:	27.9 KB 
ID:	17242

  5. #5
    Junior Member
    Join Date
    Aug 2019
    Posts
    5
    hello
    good news for the i/o map
    have you a idea if it is possible to interface hard Qei in this case
    do you now where find exemple of Qei parameters
    thank you
    fabient

  6. #6
    Junior Member
    Join Date
    Nov 2016
    Posts
    14
    Quote Originally Posted by PaulStoffregen View Post
    I'm drawing the schematic now. It's going to take a while...

    But here's the GPIO part. Hopefully no big surprises?

    Click image for larger version. 

Name:	schematic40_gpio.png 
Views:	42 
Size:	27.9 KB 
ID:	17242
    Paul, it looks like you've got a typo there. B1_00 is tied to 7 and 8 on your diagram.

  7. #7
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    20,294
    Opps, a typo indeed.

    Here's the completed schematic.



    Also on the schematics page:

    https://www.pjrc.com/teensy/schematic.html

  8. #8
    Senior Member
    Join Date
    May 2015
    Posts
    356
    Thanks! What’s the DMG2305UX’s function? I thought it might be to allow Ext Vin and the USB to power it at the same time but I it’s not set up that way.

  9. #9
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    9,012
    Is that lowly switch on the mkl02 the famous Teensy *TM* Brickproofing Button?

    Valid assumption that those many extra mkl02 pins {versus T_3.x's} are somehow related to what might be a debug avenue once noted?

  10. #10
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    20,294
    Quote Originally Posted by DaQue View Post
    What’s the DMG2305UX’s function?
    Reverse polarity protection

  11. #11
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    20,294
    Added minor fixes to the schematic, for the Program pin and 3.3V & GND (right side of the board between On/Off & VTAB). Also added 10 of the 11 test points which were overlooked earlier.

  12. #12
    Senior Member
    Join Date
    May 2015
    Posts
    356
    I should have known that. Thanks

  13. #13
    Junior Member
    Join Date
    Aug 2019
    Posts
    3
    N12? not used, left floating?

  14. #14
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    20,294
    Indeed, N12 (USB_OTG1_CHD_B) is floating. That open drain output pin would normally be used to integrate the USB charger detection to an external power management chip, presumably so it could know when to draw much more current. Sorry, Teensy 4.0 doesn't support that sort of external power management integration. The wakeup pin (L6) and standby request (L7) are also unconnected.

    PMIC_ON_REQ is connected to the 3.3V regulator enable, but that's the extent of Teensy 4.0's support for hardware power management. Trade offs had to be made to fit everything into the small size. Many other features (like native ethernet) that people wanted didn't make the cut either.

  15. #15
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    20,294
    Quote Originally Posted by defragster View Post
    Valid assumption that those many extra mkl02 pins {versus T_3.x's} are somehow related to what might be a debug avenue once noted?
    Nope, not really. This new chip has several complex features which required extra pins. That's all.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •