Forum Rule: Always post complete source code & details to reproduce any issue!
Tab Content
  • kallikak's Avatar
    06-25-2019, 11:46 AM
    Got it working. The defines are a bit broken, so it's not just a matter of removing the #if 0, but it's not much more than that. I can't be sure that there aren't any other side-effects, but it seemed ok.
    7 replies | 178 view(s)
  • kallikak's Avatar
    06-25-2019, 01:36 AM
    Well I'll certainly try re-enabling FTM3 this evening when I get home. Fingers crossed it was just commented out for testing... :-)
    7 replies | 178 view(s)
  • kallikak's Avatar
    06-25-2019, 12:45 AM
    That code snippet looks odd - seems to imply FTM3 is disabled? But the README says: "1 FTM with 4 channels (on teensy 3.6, only FTM0 and FTM3 are possible. on teensy 3.2, FTM0 only). All others channels will be...
    7 replies | 178 view(s)
  • kallikak's Avatar
    06-25-2019, 12:32 AM
    I believe pin 34 is E25, and from the library info: "The pair (hsync_ftm_num, hsync_ftm_channel_num) defines the pin generating Hsync signal. Look at teensyduino's teensy3/core_pins.h file, CORE_FTM*_CH*_PIN On...
    7 replies | 178 view(s)
  • kallikak's Avatar
    06-24-2019, 11:59 PM
    Hi, I am using the uVGA library with a Teensy 3.6, and all worked fine with the default settings. But for port-related reasons, instantiating the uVGA object using (hsync_ftm_num, hsync_ftm_channel_num) = (3,4) as...
    7 replies | 178 view(s)
No More Results
About kallikak

Basic Information

Statistics


Total Posts
Total Posts
5
Posts Per Day
0.17
Last Post
uVGA library with non-default pins 06-25-2019 11:46 AM
General Information
Last Activity
06-26-2019 04:55 AM
Join Date
06-24-2019