Latest activity

  • A
    Hallo, ich möchte mit einem T4.0 eine Schnittstelle für ein IPhone erhalten. Das Interface sollte 5x Audio Line in besitzen, 1x Stereo Output und 1x Midi Input. Kann ich so etwas realisieren???
  • TomChiron
    Is there a difference in the THD between sine and sine_hires?
  • KurtE
    Sorry been awhile since I played with the joystick stuff. Most of my playing has been done on the USB Host side. There are at least three things to do to see if it works. a) Update the HID descriptor. It may or may not be as easy as removing...
  • A
    audiofreak replied to the thread 48kHz 8i80 USB Audio.
    Hallo, ich möchte einen Aufbau mit Teensy 4.0 entwerfen der ein 4 Audio Line Input, Stereo Output und Midi Input besitzt. Das ganze sollte mit einem Iphone Funktionieren. Ist sowas möglich?
  • wwatson
    wwatson reacted to KurtE's post in the thread Call to arms | Teensy + SDRAM = true with Like Like.
    If you are building a specific board for a specific purpose, I say have at it! IF you like hard coding it like: IOMUXC_SW_MUX_CTL_PAD_GPIO_AD_B1_13 = 0x4U; IOMUXC_CSI_DATA04_SELECT_INPUT = 0; IOMUXC_SW_PAD_CTL_PAD_GPIO_AD_B1_13 = 0x0U, go for...
  • A
    aleglakov replied to the thread Teensy 3.2.
    Teensy 4.1 with heaters is 82+eur (taxes included) in our local shop...
  • R
    Rezo reacted to KurtE's post in the thread Call to arms | Teensy + SDRAM = true with Like Like.
    Note: that is simply a print to pdf of one of the pages in the excel document: https://github.com/KurtE/TeensyDocuments/blob/master/Teensy4x%20Pins.xlsx Note: @mjs513 did a modified version of this that I think is in @defragster github project...
  • KurtE
    Note: that is simply a print to pdf of one of the pages in the excel document: https://github.com/KurtE/TeensyDocuments/blob/master/Teensy4x%20Pins.xlsx Note: @mjs513 did a modified version of this that I think is in @defragster github project...
  • mjs513
    mjs513 reacted to KurtE's post in the thread Call to arms | Teensy + SDRAM = true with Like Like.
    If you are building a specific board for a specific purpose, I say have at it! IF you like hard coding it like: IOMUXC_SW_MUX_CTL_PAD_GPIO_AD_B1_13 = 0x4U; IOMUXC_CSI_DATA04_SELECT_INPUT = 0; IOMUXC_SW_PAD_CTL_PAD_GPIO_AD_B1_13 = 0x0U, go for...
  • mjs513
    mjs513 reacted to KurtE's post in the thread Call to arms | Teensy + SDRAM = true with Like Like.
    Yes you are right that B1_12-15 are already on the board. We should probably make a new version of the excel document which has all of these pins on it... As for mixing CSI and FlexIO. Not sure how... Probably need to read those sections in...
  • KurtE
    If you are building a specific board for a specific purpose, I say have at it! IF you like hard coding it like: IOMUXC_SW_MUX_CTL_PAD_GPIO_AD_B1_13 = 0x4U; IOMUXC_CSI_DATA04_SELECT_INPUT = 0; IOMUXC_SW_PAD_CTL_PAD_GPIO_AD_B1_13 = 0x0U, go for...
  • R
    Rezo reacted to jmarsh's post in the thread Call to arms | Teensy + SDRAM = true with Like Like.
    My main question would be, what do you even need the Teensy/Arduino pin numbers for when writing code for modules like CSI and FlexIO? You can use IOMUXC_SW_MUX_CTL_PAD_GPIO_x and IOMUXC_SW_PAD_CTL_PAD_GPIO_x to initialize them (which works...
  • R
    @KurtE can we get an original excel copy of this so that we can edit it? https://github.com/KurtE/TeensyDocuments/blob/master/Teensy4%20MicroMod%20Pins.pdf
  • ThirdEarthDesign
    I have a Teensy 4.1 that I'm using to build a button box with 32 buttons and 1 analog input using Teensy Joystick, but I'm wondering if it is possible to remove the unwanted axes. I would like to do away with the X, Y, Z Rotation and Slider...
  • J
    My main question would be, what do you even need the Teensy/Arduino pin numbers for when writing code for modules like CSI and FlexIO? You can use IOMUXC_SW_MUX_CTL_PAD_GPIO_x and IOMUXC_SW_PAD_CTL_PAD_GPIO_x to initialize them (which works...
  • KurtE
    Yes you are right that B1_12-15 are already on the board. We should probably make a new version of the excel document which has all of these pins on it... As for mixing CSI and FlexIO. Not sure how... Probably need to read those sections in...
    • 1713706462334.png
  • PaulStoffregen
    PaulStoffregen replied to the thread Teensy 3.2.
    Teensy 3.2 is discontinued. Some people still want them for old designs, where paying 3X or even 10X the original price might be less bad option than having to update or redesign. This is especially true for applications where the original...
  • KurtE
    KurtE reacted to jmarsh's post in the thread Call to arms | Teensy + SDRAM = true with Like Like.
    You have B1_12 and B1_15 available for pixclk and mclk. I would recommend using the pins shared with FlexIO2 wherever possible (for example hsync and vsync are on B1_14 and B1_13), since that's better at handling variable-length (compressed)...
  • PaulStoffregen
    I'm guessing you've already seen section "Power Up Sequence" on this page. https://www.pjrc.com/store/ic_mkl02_t4.html Difficult to guess what happened with your board. Perhaps pin 4 on the voltage regulator was the issue? Normally U4 is...
  • T
    I am responding to all of you guys. And most defiantly Ash..... I am a machine shop owner from Texas. I have never programmed, or played with electronics like you guys. Being in the maintenance and repair world "automotive and printing press" I...
  • PaulS
    PaulS replied to the thread Teensy 3.2.
    Most probably for replacement. Teensy 3.2 and Teensy 4.0 are not fully pin-compatible, e.g serial ports, CAN bus ports, etc. And don't forget the higher powerconsumption that comes with a Teensy 4.0. Besides that, a Teensy 4.0 puts out higher...
  • PaulS
    Agree. I would have pulled out the logic analyzer if I had the module laying around. Paul
  • M
    mi224 replied to the thread Teensy 3.2.
    A classic example...
  • BertG
    Hi, a logic/scope connected to CS, CLK, Data will tell you the truth -always helps (especially in discussion with a SW-engineer who believes in his code 😁). Setup- and Hold-times need to be respected as specified in the timing diagram above...
  • M
    mi224 posted the thread Teensy 3.2 in General Discussion.
    Does anyone know why the above goes for such obscene amounts? I've seen people bid £60 for a board that is way out of date! Seems like madness, but there must be a reason when you can get a 4.0 for a fraction of the price?
  • P
    I took the Waveforms Audio example, set the frequencies to 1000Hz, wave type to sine, and maxed the levels with sgtl5000_1.lineInLevel(0); sgtl5000_1.lineOutLevel(13); And looked at the line outputs with my QA403 audio analyzer: Which...
  • C
    got a real dx7 in the meantime, however blasphemously just using it as a MIDI input device :_)
  • PaulS
    Thought about again and I wonder if you are just not missing the highest bit (D11) due to improper timing. This piece of code from SPIencoder.cpp is possibly not correct: digitalWrite(_csPin, HIGH); digitalWrite(_clkPin, HIGH); delay(1)...
    • 1713679425483.png
  • A
    thanks for the reply, Paul, will check it out, I'm really enjoying using teensy and learning as much as I can... weird enough today I got back home and plugged it a couple of times and hasn't failed at all... it's going straight into executing my...
  • C
    Hi all, Had a weird situation that I am trying to better understand. One of our Teensy 4.0 units was not powering on: 5V input via micro USB 0V on 3V3 rail 0V on Pin 4 (EN) of TLV75733P No Short to GND on the 3V3 rail. Power cycling the 5V...
  • J
    You have B1_12 and B1_15 available for pixclk and mclk. I would recommend using the pins shared with FlexIO2 wherever possible (for example hsync and vsync are on B1_14 and B1_13), since that's better at handling variable-length (compressed)...
  • PaulStoffregen
    4 blinks usually means a problem with the crystal. Details here (scroll down to "Troubleshooting & Diagnostic Blink Codes") https://www.pjrc.com/store/ic_mkl02_t4.html
  • A
    my teensy 4.1 was working perfectly, I might have done something wrong as I was connecting and disconnecting some signal for diagnostics and changing some things around my breadboard. Bottom line is that it works but it keeps happening that on...
  • mjs513
    mjs513 reacted to KurtE's post in the thread Call to arms | Teensy + SDRAM = true with Like Like.
    @mjs513 did the one for the devboard that I am looking at. Looks like most of the pins are there. We are currently using AD_B1_04 through AD_B1_15 Mike does the below look correct to you as well? The T4.1 defines we were using.. The numbers...
  • D
    You need to pass -fdata-sections and -ffunction-sections to the GCC compiler when compiling ALL code and --gc-sections to the linker to eliminate unused data and functions in the ELF executable. Perhaps those aren't being used.
  • M
    I took the Waveforms Audio example, set the frequencies to 1000Hz, wave type to sine, and maxed the levels with sgtl5000_1.lineInLevel(0); sgtl5000_1.lineOutLevel(13); And looked at the line outputs with my QA403 audio analyzer: Which...
    • T4-sine-gen-1k.png
    • T4-pass-through-1k.png
    • T4-dist-v-level.png
  • KurtE
    KurtE reacted to mjs513's post in the thread Call to arms | Teensy + SDRAM = true with Like Like.
    Quick answer is yes. in one of the conversation posts I listed them as well: which is the same on your list.
  • C
    Thanks for the tip. PlayTunedNote is now working.
  • mjs513
    Quick answer is yes. in one of the conversation posts I listed them as well: which is the same on your list.
    • 1713648000067.png
  • M
    It probably sent part of the chip into CMOS latchup...
  • J
    Most of those pins are already there, iirc the only missing ones were some of the data pins around CSI 2 to 5.
  • PaulS
    Could be a library issue. What if you change the line Serial.println(myAS5045.EncDeg()); to Serial.println(myAS5045.EncRaw());? You should see values between 0 and 4095 for a full rotation of the magnet. Paul
  • D
    Dogbone06 reacted to KurtE's post in the thread Call to arms | Teensy + SDRAM = true with Like Like.
    @mjs513 did the one for the devboard that I am looking at. Looks like most of the pins are there. We are currently using AD_B1_04 through AD_B1_15 Mike does the below look correct to you as well? The T4.1 defines we were using.. The numbers...
  • D
    @KurtE I’ll add all the pins you want. As that will help the community. So go ahead and together with @mjs513 or anyone else, compile a table of the missing pins. Ideally you’d make a complete table of ALL pins, maybe some of the ones exposed...
  • KurtE
    @mjs513 did the one for the devboard that I am looking at. Looks like most of the pins are there. We are currently using AD_B1_04 through AD_B1_15 Mike does the below look correct to you as well? The T4.1 defines we were using.. The numbers...
    • 1713642796182.png
  • T
    Beauty! That totally does what I need it to. Thank you! -Tom
  • J
    Actually, the fact that I was getting true values led me to believe that the system was truly working. However, the values that I am getting are correct but only range from 180-360 degrees which is weird. Does anyone know why this might be the case?
  • J
    Try this: extern "C" const uint8_t usb_config_descriptor_480[]; extern "C" const uint8_t usb_config_descriptor_12[]; const uint8_t bMaxPower_480 = usb_config_descriptor_480[8]; const uint8_t bMaxPower_12 = usb_config_descriptor_12[8]; void...
  • PaulS
    PaulS replied to the thread External Power Supply Issues.
    So the basic arrangement worked on USB, good. Did you try to power the basic arrangement also by an external 5V using a 7805? If so, did that work? If not, how did you connect the external 5V exactly? Paul
  • T
    I am trying to figure out if there is a "simple" way at run-time for a Teensy 4 application to determine what specific values were held by a few private TeensyDuino constants at time of compilation. I have a custom circuit powered by a Teensy 4...
Back
Top