Search results

Thanks, Mark. I had read that page in a fair amount of detail, it didn't actually help me troubleshoot this problem. This comment seems to help: https://github.com/platformio/platformio-home/issues/1785#issuecomment-1141292058 Specifically, it talks about the ".platformio" directory in my...

I'm trying to get any project going in Visual Studio Code, because the Arduino IDE drives me crazy. Thus, I'm using (trying to use) platformio. I've previously successfully used platformio for direct AVR chip development (not teensy based.) I've upgraded to the latest version for platformio...

For those of use with hopelessly too short fingers (really, I'm way left on the bell curve here!,) there are other options these days ... (I've actually been considering something like a microKEY and a Teensy as a small portable instrument. Maybe in a hundred years when I retire?)

What I do in those cases is to get thin contact probes, and check for continuity along all the paths that should have it (and not among some that shouldn't.) Then I use those probes, and IDEALLY some test points on the board (if I remembered to put them in) to hook up a scope to make sure that...

So, in summary: It turns out higher quality equipment costs more to produce. Who would have thought?! :-D If you can afford a Tek, buy a Tek! but a Rigol is better than nothing.

Yeah, plugging this into one of my Jetson boxes detects it just fine, so this is a problem isolated to my Windows machine. Thanks for the encouragement :-)

When selecting only Audio, the loader can load it (at least when pushing the button.) When selecting Serial + MIDI + Audio, the loader can load it (when pushing the button) and the serial port shows up as COM9, but the audio device does not show up in the audio device list. I have had a variety...

Using Teensyduino 1.53, installed in IDE 1.8.13, btw. Connecting the Teensy both to a USB 3.0 hub that I have other USB Audio devices on, and directly to a USB port on the computer, makes no difference. Also: The I2S hardware/shield itself works fine in a sketch that just runs the I2S hardware...

I can't get Windows to see the USB Audio device of a recently purchased Teensy 4. I've set the board type to Audio: I'm running a simple passthrough sketch. (I have an Audio Shield attached using the double-decker pins): #include <Audio.h> #include <Wire.h> #include <SPI.h> #define LED_PIN...

Copying to the library folder should work fine. I don't know that there's necessarily a "single correct way." Btw, I highly recommend developing in very small increments. Compiling code, and putting it on the teensy is super cheap, and tells you a lot! So, start with a bare minimum sketch just...

Does this array need to be mutable, or is it static initialized data? If it doesn't have to be mutable, can you declare it as PROGMEM and keep it in flash?

Yes, he can. C and C++ totally allows that. The actual error is this: cannot convert 'Way_Pt' to 'float' for argument '1' to 'void Ev_GoTo_Pos(float, float, float, float, float, float, float, float)' He updated the code to pass a struct instead of a lot of floats, but he didn't update the...

I think ossi has explained the problem clearly, especially in post #7. The problem is: something wakes up, every now and then, and disables interrupts for some amount of time. The main question I have is: If you remove the Serial.print() call from the loop() function, does that still happen? As...

A big enough capacitor (220 uF or so) should clean up a too-noisy wall wart. If you hook up a scope or logic analyzer, do you see the random MIDI being sent by the Teensy? If so, it's likely you have some bug in your sketch, which overwrites some buffer or otherwise causes unpredictable...

The "teensy loader" software can load firmware into the Teensy without you pressing the button, and without you doing special things in your firmware. That being said -- the whole brilliance of the Teensy ecosystem, is that it uses a small, second, microcontroller, whose entire job is to push a...

The syntax highlighting is not semantic. It doesn't always work right, because it's extra decoration added by the text editor, not actual meaningful information extracted by the compiler. In the end, what the compiler does is what matters. If you #include <ADC_util.h> and then build the sketch...

The built-in ADCs on the microcontroller are not even 13 bits, unless your analog solution and buffering is quite excellent. Meanwhile, the ADCs built into the audio board (and other audio systems) are of a totally different class, and generally have very high resolution, as long as the rest of...

In my opinion, you absolutely want to use the audio library for this. 16 bits is going to be much more important than oversampling, assuming that you can get a low-noise electronics implementation to match. (microphones, wires, power supply, etc.) Some simple math: - distance: 450 mm between...

I think you mis-understand what "ground" means. Ground, in small-signal electronics, is simply the signal designated as a potential of 0 Volts compared to the other parts of the circuit. "Protective Earth," which is something you will found in grounded electrical outlets, and industrial...

To make that "tinny distorted AM radio sound," you need the following pieces in sequence: 1) The sound input. 2) A high pass filter to remove the rumble and microphone proximity bass. Set it at 12 dB/octave (2-pole) with the cut-off frequency at 300 Hz. 3) A compressor with a slow release...

I would want more waveforms, to get a better (longer) fit. I'd also want the trigger sound to be of higher frequency. You might be able to use a bandpass filter with a lower cut-off at 200 Hz, and a higher cut-off at something higher, like 2 kHz or more. Then sample with multiple cycles of the...

These don't affect what the Teensy sees at all. Well, theoretically, if your keyboard relied on the MacBook ground, and the Teensy relied on the USB connector to see MacBook ground, perhaps it would but ... that would be terrible design, and in that case, would immediately stop working when you...

That's not really feasible for the main inline DC blocking caps and bulk capacitance, though. Hence, the fall-back to film! Even there, a 4.7 uF capacitor is going to be 7.5x7.5 millimeter of board space, 20 mm+ tall, and cost you a buck fifty, each. High quality audio is expensive, compared to...

Oh, that's sweet! I was going by the old documentation that says SPDIF shares hardware with I2S.

Just play chip tunes using PWM. Turn off interrupts and control the PWM directly for each pin, manually. MUSIC ON ALL THE PINS! Also, I thought S/PDIF used the same hardware as IIS, so you couldn't actually use both at the same time?

The problem is with the SDCard FAT library. It is quite inefficient in how it reads blocks, and how it scans directories for files. If you can add a multi-threaded runtime into the Teensy runtime, and let it run at a lower priority than the main Teensy loop, then you could do this without more...

Those long loopy rails look like big inductors or antennas to me ... My experience is that high-quality audio benefits from four-layer boards, and may benefit from two-sided component mounts. Four-layers isn't that much more expensive than two-layer (I mean, the PCB is twice the cost, but the...

Long wires matter when you communicate at tens or hundreds of megahertz. Long wires also matter if they are very long, and VERY thin (like, thinner than 36 gauge) because they may have some resistance that may maybe matter. Maybe. Unlikely. Long wires may also matter if you have significant...

Very nice! I wish we could collect all of these into a single, descriptive page, and put it inside the Teensy documentation somehow. In general, the Teensy documentation links on the main store/product pages feels ... fragmented, to me. It's hard to find what you really need.

I love PlatformIO. Thanks!

It may be better to just run the sampling all the time, and when the noise crosses the threshold, wait for a small amount of time, and copy the data you need out of the buffer. That way, you get a copy of the data that happened before the threshold, and you don't need to wait for the ADC to spin...

A "register file" is generally the CPU registers, these come from the ARM cortex architecture specification. These are the registers where integers, floats, and pointers are manipulated by the CPU. The register file on ARM Cortex-M7 include registers r0-r15, as well as s0-s31 (or d0-d15, for...

I could have sworn I saw a 4244 description somewhere but I can't find it now. Waiting for confirmation seems fine, no need to add mention of un-confirmed chips.

The best I've found is this: https://www.pjrc.com/store/teensy40.html These symbol section decorators work much like PROGMEM does on old-school AVR Arduinos, so you may be able to get a description of how to actually use these in code by looking for tutorials on that. However, you have to...

You can debug the hardware by running a sketch that sets one column, and then checks each row input, waiting for a connection, and prints what it sees. Advance to the next column, check each row input. Something like this (may not compile, as I just typed it up) const byte ROWS = 8; //four...

With a de-coupling capacitor, the input impedance is much less of a problem. Also, linearity isn't a super bad problem -- you can either not worry about it at all (the effect is somewhat muted) or you can warp it in the software. For the AGND current, three things happen: 1) Teensy pins are...

The uploader needs to read the output hex file. I wonder how it does that? If you're on linux, you can use "top" and "strace" and "oprofile" to figure out where the time is spent. On Windows, you may be able to use procmon and VTune to do the same.

@PaulStoffregen for the tool: The list of compatible chips says: Compatible CODEC Chips: STGL5000 TLV320AIC3206 AK4558 Compatible DAC Chips: PCM5102A PCM1808 PCM5242 CS4344 The list of supported chips in the sources say: #include "control_sgtl5000.h" #include "control_wm8731.h" #include...

Connecting the pots to agnd is probably the right choice. However, you want to reduce the amount of current into agnd. With your current pots, you're sending 3.3/(2500/12) amps, or about 16 milliamps into agnd, constantly. That's pretty high. I would recommend using 10 kOhm sensors, or even 47...

Is it just me, or does it seem like using both JSON and XML on a microcontroller perhaps not the sweet spot of the Teensy microcontroller? If you need JSON and XML and maybe HTTPS then perhaps using a Raspberry Pi for those bits (maybe a Zero, even) and then using Ethernet or OSB or SPI or UART...

For what it's worth, a set of tabs, each with their own list of things, might be better than a pulldown menu. Or a popup menu to select a set of things, and then the list of things. You can get very close with the current "accordion" to automatically close other categories when one particular...

This means that you're doing too much with interrupts disabled. Copying a few global variables shouldn't take any appreciable time. However, if you try to copy large strings, or worse, do malloc() or use C++ objects with fancy constructors/destructors, you're doing it wrong. A mechanism I find...

The Teensy LC is specified at 5 mA for most pins, and some pins can do 20 mA output. The other Teensies are generally specified for 10 mA per pin. There's also often a "sum across all pins" specification for the microcontrollers on each Teensy boad, but those are not specified as part of the...

One theory: The code in the SD library has no caching. It will scan your entire root directory to find the "BA" directory, each time you open something. Then it will scan the "BA" directory it finds, to find each file. It does this by reading the disk, over and over again. You may be able to...

If you're making many of these devices, and you only need programmability for development, then you can use another programmer (such as a JTAG programmer) to program the production chips once you have a sketch you are satisfied with. In that situation, you will develop using a Teensy with the...

Thanks both of you!

I agree with the conclusion: wiring all that must have been maddening! There's a reason modern electronics largely use touch screens :-D

I see both pin 39 and pin 7 marked as OUT1A, with neither of them being dimmed (secondary.) Is it still pin 7, like on the Teensy 4.0, or did it move to pin 39 on the 4.1?

You shouldn't use comparators or interrupts at all. Just use the ADC input(s) and sample the audio. Hook the microphones to the sound-in circuitry and use the Audio library to sample it. You should know the exact distance between the microphones, because you can't get an accurate direction...

How do you set up the USB audio-in endpoint? Are you using the audio library / setup? I don't see code in the USB library to set up 11 kHz (it all sets up at 44 kHz) but maybe you changed something? What DAC are you using, and how do you set that up?