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

Thread: PINOUT of the MK20DX256VLH7 on Teensy 3.2 and Eagle Library

  1. #1
    Junior Member
    Join Date
    Oct 2020
    Posts
    10

    PINOUT of the MK20DX256VLH7 on Teensy 3.2 and Eagle Library

    The pinouts of the microcontroller of the Teensy 3.2 on the pjrc's website and the Eagle library are different, is there any other library or something else?

  2. #2
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    13,132
    There may be bad ones - but there are good CAD images somewhere - seems a post yesterday where Paul noted the T_3.1 is the same as T_3.2 - that post had other links

  3. #3
    Junior Member
    Join Date
    Oct 2020
    Posts
    10
    Could you send em @defragster

  4. #4
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    13,132
    Just saw this is a new thread to the one you started :: pjrc.com/threads/63635-Eagle-Schematic-library-for-the-Teensy-3-2

    That is the one I was ferreing to I see now that I looked it up ... there are others

    Reading that thread - it has many links - one there has to work

  5. #5
    Junior Member
    Join Date
    Oct 2020
    Posts
    10
    Yes but the eagle libraries and the one that paul has posted on the pjrc website, the mk20dx256vlh7 microcontrollers pinout's are different

  6. #6
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    23,383
    All of those Eagle libs were contributed by people who use Teensy. Each one says who created it.

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

    I do not use Eagle. I have not created any Eagle libraries. None of those are my doing. I only made a page with links to the libraries other people have shared, so you can find them more easily.

    The best I can do is add a warning message on the website, or just remove the mention of libraries with errors. But since I do not use Eagle at all, I'm depending on reliable feedback from people like you. From only the messages on this thread, I have no way to know which specific library is claimed to have a defect, or specifically what the defect is, or whether the flaw is serious enough to completely remove the link or just add a warning to the page.

    Again, I personally do not use Eagle. I'm depending on clear feedback from Eagle users like you. Please be specific, and please understand the very best I can do is edit the web page. How exactly do you recommend I should edit that page?

  7. #7
    Senior Member+ KurtE's Avatar
    Join Date
    Jan 2014
    Posts
    8,183
    Might also help to know which eagle library you are trying, and was it the github one I mentioned in other thread?

    Also might help to know which ones are different and how they are different.... My guess is that maybe they converted a T3.0 to make it close enough to work for T3.1...
    The libraries were done something like 5 years ago and it does not look like the user has done anything up on github since 2017... So hopefully someone else has a more up to date version that they use.

    But as I mentioned I only used it to convert to Diptrace, and I was more interested in pin locations than names.

  8. #8
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    23,383
    @Constation - Please, tell me specifically which info you found has errors. At the very least, I would like to add a notice on the web page so others can be aware of the issue. But what can I do until you say exactly what is really wrong and specifically which file has the error?

    Ideally someone who uses Eagle might be able to contribute a fixed copy of the file. But again, without knowing exactly which file as the problem and what specific thing within the file needs to be checked and updated, how are we realistically going to improve this situation?

Posting Permissions

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