Forum Rule: Always post complete source code & details to reproduce any issue!
Page 11 of 11 FirstFirst ... 9 10 11
Results 251 to 259 of 259

Thread: Teensy 4.0 Breakout Kit

  1. #251
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    9,695
    Sounds good Dan, looking forward to the next Beta to see how the feedback leads to any changes for clean assembly.


    I made some steps toward a menu for the expanded dynamic runtime "KurtE + 'xx=' multi test" to ring out pins during assembly steps.

  2. #252
    Senior Member+ mjs513's Avatar
    Join Date
    Jul 2014
    Location
    New York
    Posts
    4,101
    Welcome home Dan - looking forward to see the changes you make

  3. #253
    Senior Member
    Join Date
    Aug 2016
    Posts
    128
    so dan, any news? good or bad dont matter. can't wait to try the updated version. I have somewhat horrible vision and I didnt have a lot of issues soldering things. even that tiny cap and power chip. dont have the proper no clean flux, but some rubbing alcohol and a tooth brush just for this and it cleaned right up.

  4. #254
    Senior Member
    Join Date
    May 2016
    Posts
    219
    @loglow - Hi Dan. I haven't been very active on the thread because the breakout has continued to work well (except for pins 35&36). I have it running 24/7 on all sorts of software and peripheral chips and boards (music, SDR, scientific instruments). No problems, within the constraints of my tests, but I haven't tried USB because I don't trust my flex cable with the standard size headers.

    Do you expect to change the footprint on the next go-around? I'd love to start wiring a general prototyping board, and I'll get started as soon as I know what your plans are...
    Derek

  5. #255
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    9,695
    Question about the @KurtE pinsheet that @loglow turned into the nice Legal Print color table:

    The ALT5 Column references the GPIO[1,2,3,4] names of the pins.

    When the T_4.0's 1062 is powered up in startup.c the change is made to " // Use fast GPIO6, GPIO7, GPIO8, GPIO9 "

    Question: Should those column references be changed to reflect the GPIO[6,7,8,9] names of the pins?
    * Once this sheet is validated it seems such a good reference sheet that PJRC could post it with the T4 Card and/or other REF pages.
    ** One other suggestion - the lower right 'gray' corner might be a good place to put a "COLOR CODE to FUNCTION NAME" key for the REF colors as it appears on the TallDog pinout card.

    ALSO: Today I got a USB to wired Ethernet adapter for another thread - I first ran that downloaded library WIP and plugged that USB adapter into this TallDog breakout board and it ran well. I even unplugged the USB adapter off then back on and it resumed the IP test it does.

  6. #256
    Senior Member+ KurtE's Avatar
    Join Date
    Jan 2014
    Posts
    5,421
    Quote Originally Posted by defragster View Post
    Question about the @KurtE pinsheet that @loglow turned into the nice Legal Print color table:

    The ALT5 Column references the GPIO[1,2,3,4] names of the pins.

    When the T_4.0's 1062 is powered up in startup.c the change is made to " // Use fast GPIO6, GPIO7, GPIO8, GPIO9 "
    Interesting question: I sort of asked up on other thread, if there is more documentation, as I see very little describing GPIO6-9, other than there are some comments in code and a few places in manual that describe some registers, clocks, ...

    But so far my spreadsheet simply reflects that actual page data in manual. Like for our Pin 0, if you look at page 473:

    Code:
    MUX Mode Select Field.
    Select one of iomux modes to be used for pad: GPIO_AD_B0_03.
    000 ALT0 — Select mux mode: ALT0 mux port: FLEXCAN2_RX of instance: flexcan2
    001 ALT1 — Select mux mode: ALT1 mux port: XBAR1_INOUT17 of instance: xbar1
    010 ALT2 — Select mux mode: ALT2 mux port: LPUART6_RX of instance: lpuart6
    011 ALT3 — Select mux mode: ALT3 mux port: USB_OTG1_OC of instance: usb
    100 ALT4 — Select mux mode: ALT4 mux port: FLEXPWM1_PWMX01 of instance: flexpwm1
    101 ALT5 — Select mux mode: ALT5 mux port: GPIO1_IO03 of instance: gpio1
    110 ALT6 — Select mux mode: ALT6 mux port: REF_CLK_24M of instance: anatop
    111 ALT7 — Select mux mode: ALT7 mux port: LPSPI3_PCS0 of instance: lpspi3
    What is maybe sort of interesting to look at is what does this do for pin interrupt code? Comment in wondering, not sure how handled.
    For example: GPIO1 has IRQs (72-81), GPIO2 has (82, 83), GPIO3 (84-85), GPIO4 (86,87), GPI5(88,89)

    GPIO6-9 has only IRQ 157

    So I believe to process any IRQ handled by any IO pin, we have to scan that status of 31*4 status values to see what happened.

    Wonder if maybe at times fast IO is not necessary fast?

  7. #257
    Senior Member
    Join Date
    Jan 2013
    Posts
    121
    Hi all, Iím sorry for my silence this past week, Iíve been extraordinarily busy. Iíll try to catch up with everyone on here tonight.

  8. #258
    Senior Member
    Join Date
    Aug 2016
    Posts
    128
    It's okay take your time. M

  9. #259
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    9,695
    Yes, do it when you have time to make any needed changes come out as you can live with.

    I have been using the original pinned T4 for USB to wired Ethernet on other thread and it works fine with or without going through powered hub. Also tested on the MSC thread's code to access USB HDD's no problem - though a powered hub required then.

    I got some plastic M2 sized stand off's and they work well.

    Since I wrongly placed the first female short header on the bottom - then the second - my battery is trapped - so if you find a battery holder on the same spacing to drop in fit I'd like an extra to retrofit the original to have a replaceable battery.

Posting Permissions

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