Forum Rule: Always post complete source code & details to reproduce any issue!
Page 2 of 2 FirstFirst 1 2
Results 26 to 42 of 42

Thread: Teensy 3.6 256MHz

  1. #26
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    18,691
    I posted a quick shout-out on Twitter, linking to this thread.

    https://twitter.com/PaulStoffregen/s...66670760288257

    Click image for larger version. 

Name:	256Mhz.jpg 
Views:	8 
Size:	92.4 KB 
ID:	14989

  2. #27
    Senior Member+ Frank B's Avatar
    Join Date
    Apr 2014
    Location
    Germany NRW
    Posts
    4,774
    Quote Originally Posted by PaulStoffregen View Post
    I posted a quick shout-out on Twitter, linking to this thread.

    https://twitter.com/PaulStoffregen/s...66670760288257

    Click image for larger version. 

Name:	256Mhz.jpg 
Views:	8 
Size:	92.4 KB 
ID:	14989
    Wow... Good opportunity for a poll. As far as I know so far, it works on every Teensy 3.6 I know of. But are there some that may not run 256MHz sucessfully?

  3. #28
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    7,101
    I have 4+1 out on my desk - all connect and upload and work the same for Dhrystone.
    <edit>: Forgot the acrylic beta unit that works as well ( that uses the different pinned MCU - and olde USB connector )

    Compiled 'Fastest, pure-code, LTO' they do "int n = 111711;" iterations in 100,000 microseconds but use cycle counts between 25600053 and 25600188 for "Dhrystones per Second: 1117110.0"
    { 2 sometimes take 100,001 us and the cycle count isn't always the same - new high is 25600269 }

    They also run it Smallest code with LTO - more like :: Micros Run Time: 212208 ... CycleCount Run Time: 54325295 ... Dhrystones per Second: 526938.687500000000
    Last edited by defragster; 10-21-2018 at 08:00 AM.

  4. #29
    Senior Member+ manitou's Avatar
    Join Date
    Jan 2013
    Posts
    1,643
    Quote Originally Posted by Frank B View Post
    Wow... Good opportunity for a poll. As far as I know so far, it works on every Teensy 3.6 I know of. But are there some that may not run 256MHz sucessfully?
    All 3 of my T3.6 seem to work at 256mhz (including early acrylic beta unit). Running linpack 250x250 float with Fastest, getting 49.4 mflops.
    Last edited by manitou; 10-21-2018 at 01:04 PM.

  5. #30
    Junior Member
    Join Date
    Dec 2016
    Posts
    3
    Wow!

    With SPI-TFT´s like the FT81X works very stable!






    TFT: NHD 5" FT813

    Gameduino 2/3 library modified in order to get access directly to the SDIO reader of the teensy 3.6

    Another test in order to verify the stability of the SDIO reader@256MHz


  6. #31
    Senior Member
    Join Date
    Oct 2015
    Location
    Roma (IT, EU)
    Posts
    107
    At the new 256 MHz core clock, what about the various bus speeds (RAM etc.)? Standard or overclocked as well?

  7. #32
    Senior Member+ Frank B's Avatar
    Join Date
    Apr 2014
    Location
    Germany NRW
    Posts
    4,774
    See Post #1
    RAM is full speed 256MHz. USB is clocked by the 48MHz source (same as with 216MHz)

  8. #33
    Junior Member
    Join Date
    Nov 2018
    Posts
    6
    Nice work!
    Just did some testing with Audio library at 256 mhz and the Audio shield. Seems to work nicely!
    I did need to edit some files for it to compile.

    For output i2s F_CPU i did use:
    #elif F_CPU == 256000000
    #define MCLK_MULT 9
    #define MCLK_DIV 204
    #define MCLK_SRC 0

    And for other outputs i did just enter some "random", so i could compile (dont use other output objects, so can't try)

  9. #34
    Senior Member+ Frank B's Avatar
    Join Date
    Apr 2014
    Location
    Germany NRW
    Posts
    4,774
    Quote Originally Posted by Frassil View Post
    Nice work!
    Just did some testing with Audio library at 256 mhz and the Audio shield. Seems to work nicely!
    I did need to edit some files for it to compile.

    For output i2s F_CPU i did use:
    #elif F_CPU == 256000000
    #define MCLK_MULT 9
    #define MCLK_DIV 204
    #define MCLK_SRC 0

    And for other outputs i did just enter some "random", so i could compile (dont use other output objects, so can't try)
    That's pretty amazing. Are you sure? How did you test it?
    We always had problems with I2S >200MHz

  10. #35
    Senior Member+ Theremingenieur's Avatar
    Join Date
    Feb 2014
    Location
    Colmar, France
    Posts
    2,069
    I think that one important point is not using the PLL clock but the BUS clock with #define MCLK_SRC 0. That means that you have a lower frequency fed into the fractional divider which reduces potential overclocking problems.

  11. #36
    Senior Member+ Frank B's Avatar
    Join Date
    Apr 2014
    Location
    Germany NRW
    Posts
    4,774
    Ok, if this works, i'll make a pullrequest to make the AudioLibrary work.

  12. #37
    Junior Member
    Join Date
    Nov 2018
    Posts
    6
    Only tested with my ears
    180 and 192 mhz high pitch wave sounds good,
    216 is horror,
    240 got some random cracks and pops,
    256 mhz with my settings above works nicely (with my ears)

    Unfortunatly i only have a scope from 1960s that doesnt work so well.

    Have only done small testing with my synth project, and so far so good

  13. #38
    Senior Member+ Frank B's Avatar
    Join Date
    Apr 2014
    Location
    Germany NRW
    Posts
    4,774
    I've added some pullrequests for SD.h and Wire.

    With I2S, I had no luck so far - tested with PT8211

  14. #39
    Junior Member
    Join Date
    Nov 2018
    Posts
    6
    But now i did step on another problem, that is totally out of reach with my skills.
    As i said earlier, audio library did work nice at 256 mhz for me with audioshield, UNTIL i get above about 60% CPU usage by audio library interupts. Then i get total freeze.
    With 192Mhz it's stable and nice when i max it out at about 90% usage.

  15. #40
    Senior Member+ Frank B's Avatar
    Join Date
    Apr 2014
    Location
    Germany NRW
    Posts
    4,774
    Hm, I'm currently working with the audio library (without I2S, but high CPU load), and I have no problems.
    Your MCLK settings do not work for me.

    @Paul: The audio library still needs some updates, and I want to do it. What shall we do with the clock settings? Use Dummys ? Show errors? Use Frassil's values?

  16. #41
    Senior Member+ Theremingenieur's Avatar
    Join Date
    Feb 2014
    Location
    Colmar, France
    Posts
    2,069
    I'd strongly suggest rewriting the I2S clock generation part of the objects in the audio library, always using F_BUS as the clock source and the clocks MCLK=256*FS, BCLK=64*FS can be generated according to the other audio objects which use the PDB to generate the frame clock from the same F_BUS to prevent stuttering and incoherencies between the objects.

  17. #42
    Senior Member+ Frank B's Avatar
    Join Date
    Apr 2014
    Location
    Germany NRW
    Posts
    4,774
    Quote Originally Posted by Frank B View Post
    Hm, I'm currently working with the audio library (without I2S, but high CPU load), and I have no problems.
    Your MCLK settings do not work for me.

    @Paul: The audio library still needs some updates, and I want to do it. What shall we do with the clock settings? Use Dummys ? Show errors? Use Frassil's values?
    @Paul, (I hope you're reading this) - Can you just say what you think is best? - I can add it to the audio-lib, then, so it will - at least - compile and will be usable for the dacs/adcs.
    You don't need to invest time - I need your decision only

Posting Permissions

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