Do you have a data sheet for that TFT? Perhaps (still a blind guess) the 30MHz SPI clock are simply too much for it? You could try lowering it to 24MHz in the ILI9341_t3.cpp file on line 56. Or your wiring could be...
Thus, you should perhaps experiment a little with the delay(x) value. 100 was a blind guess, I don't know how much time this specific TFT needs to wake up, try increasing it until you don't see an amelioration. Then,...
Ouch... that issue was heavily discussed here and elsewhere several years ago. But I had thought that modern linux distributions would not longer come with this ugly Modem Manager.
Looks like the Teensy is just too quick for that TFT, seen that it is sold by Adafruit for the slower Arduino CPUs...
If you had respected the forum rule and you had posted your sketch, someone could have shown you...
Execution time is rather not predictable, since it is probably influenced by other (hidden, system) interrupts with higher priority, then there is the cache hit or miss problem with "if-then" or for-loops in the...
Since you feel like needing to press the button even twice, one to stop your running code and one to reprogram, it looks to me like your running code is messing up something. What about respecting the forum rule and...
No libraries needed. You might send the commands to setup the SGTL5000 (see its datasheet/reference manual) inputs directly over i2c after having designated a free GPIO pin on the Teensy to sense the slide switch...
Ah, good question. Up to now, I programmed first, then soldered the capacitor and assembled everything. I never tried to re-programm a board with capacitor.
On I2C, pull-up resistors are always needed. If there aren’t on your I2C adapter board, hook 4.7k from each SDA and SCL towards 5V. It won’t kill the Teensy.
In order to understand and to satisfy my scientific curiosity: what happens when you read the codes sent out with Serial1 back with Serial2 (kind of loopback test without external h/w involved) ?
And the wrong return...
You'll have to dive deeper in the audio library code to understand that there is always one audio "consumer" object, most times an output object, which acts as the heartbeat for the whole sauce. In a simplified way, on...
Up to now, and for many, many years, most people, starting by Paul himself, were able to write their code in a smart enough way to not need that debug functionality, but they have been ingenious enough to do everything...
There is a small round pad marked "RST" on the Teensy 3.2's bottom side which allows to solder a capacitor towards the nearby USB GND pad. As I'm somewhat 1980ies when it comes to circuit design, my Teensys all get pins...
If I read correctly, you didn't write which Teensyduino version you are currently using. V1.42beta3 introduced a reworked communication layer over USB to work around some buggy Arduino Java code. Did you give it a try? ...
Then, there is probably somewhere a little bug in your device renaming? I've done this several times using a custom xxxUSBconf.c and never ran into this issue on macOS High Sierra 10.13
It looks like FrankB defined somewhere a println function Macro which is intended to work without a preceding Stream object for debugging purposes. But that „somewhere“ seems not to be included.
Commenting out these...
Might be a typo in the source code of keyboard_usb.cpp since println() can never be used alone, it needs an object inherited from the Stream class, as for example in Serial.println().
If I read well from the beginning of this thread, the digital part works already, as Projectitis stated, and his questions were only about the analog post-DAC audio processing...
At the beginning, more than 50 years ago, I was neither a coder nor a circuit builder. I was just there, cried, and peed in my pants. Every competence might be acquired during a human's life :)
As we discussed previously, the TDA1308 module which you ordered has the DC blocking capacitors. It does not have filtering since it is not specially designed for use with DAC outputs but for general use. Thus, it's up...
This is most probably the best way to kill the DACs... Since these are unipolar, there is always a DC offset with the audio signal. Connecting whatever without decoupling capacitors will in the best case give an ugly...
The simple way is to launch your play requests synchronized with the packet clock, choosing entire multiples of 2.9ms as trigger intervals.
The more complicated way would be not using the audio library with its block...
What between VUSB and GND? If you find 5V there, you grilled the inductor between GND and AGND. If you can't find your 5V there, too, check the soldering of the USB connector. These may break when often...
T3.5 is probably too fast and starts Serial.println(whatever) before the other side is ready to receive data after just having been initialized with Serial.begin().
Add a delay(100) after Serial.begin() and check if...
Seems that you live in a country where electronic components are sold and shipped at whorehouse rates... :D
I’ll never again complain when the French customs require me to pay additional 20% of sales tax when I...
That's the problem when you buy cheapest Chinese stuff... On that Aliexpress product site, there are no schematics nor other important technical details. Thus, your first step should have been to avoid that seller and...
The LED lights up only if either your code drives the pin high via a GPIO command or an internal peripheral like the SPI or the I2S engines are multiplexed to pin 13 and send data over this pin.
By default, the LED is...
Before you think of dead-end and filtering in software after the signal acquisition - Did you make sure with an oscilloscope that the analog signals are really clean before you sample these? No hum, no noise, no supply...
IIRC, pin 13 is used by the audio shield and the audio library for data transfers, thus, it is normal that the LED starts lighting. A quick look into the audio shield‘s circuit diagram and/or a quick check of the signal...
Serial println converts automatically hex to dec, the latter being the default format. Thus, your code Uur = (now.hour(), DEC) makes no sense at all.
Uur = now.hour();
Serial.println(Uur);
should work.
On potential problem could be that the Teensy 3.2 is so much quicker than an Arduino UNO and that it may cause the OLED to hang if the first drawing commands arrive already before its internal reset and power up...
FSR means Full Scale Reading. In your case 1.2V. Worst case offset is thus 0.4*1.2V/4096 + 0.8*1.2V/100 = 0.1mV + 9.6mV = 9.7mV. Thus, your 2.8mV offset is already not too bad. If you need offset compensation, this is...
Looks like there exists a CurieTimerOne library which gives similar access as the TimerOne does for the AVR timers. Perhaps there are hints for capturing inputs.
But since this is not directly Teensy related, I'd...
You'll have to study the Intel 101 Curie processor reference manual to find out if this one has a similar timer hardware for input capture. Then, you'd have to add the corresponding code and the cpu related #ifdefs to...
The math suggestion comprised the idea (sorry if I haven’t been clear on that) that you write a new audio object which would sit in the middle between the usb input and the DAC output and perform just this math on every...
Simple Math: (virtual(0-10V) * 2) -10 gives (still virtual) -10 to + 10V which result in a 0-1.2V DAC output which can then be upscaled by factor 8.3333 to get 0-10V again.
I'd rather suspect the LP38691 voltage regulator. But whatever is broken, you might consider that a new Teensy 3.5 costs just 24$, and when you spend only one hour in diagnosing and trying to fix it, you most probably...
Background information: Handling over function pointers, i.e. as callback functions, has a little constraint. Non-static member functions don't allow the compiler to know from which instance of the object the member...
I was about to post the same...
The .ino :
#include "MidiController.h"
MidiController midicontroller;
void setup() {
// put your setup code here, to run once:
The problem does not only seem to be the include chaos, but also that you try to encapsulate the native Midi class in another class without friending it... <Midi.h> should be included in your header file as should the...
As it has been stated several times before, Arduino syntax is very limited. You'll have to use native C/C++ and learn register organisation, names, and their structure from the K66 reference manual or by studying the...
It's often a trade-off between RAM usage and speed, since 32bit aligned memory reads are faster. But in that special case, if I remember well, the 24 bit RGB data is packed to not to waste 8 bits.
Edit: You got...
Using AVR register conventions will give most times slow compiled code, since the ARM32 CPUs simply do not have identical registers and if you use these though, you pull the handbrake through emulation. Examples of...
When looking at your code, my first thought is that you should study the K66 processor reference manual and the Teensyduino core files. For example, the digitalWrite() command is by far not the quickest way to toggle a...
If you have room for external components, you might use 2 x 100uF electrolytic capacitors (or even smaller with higher load impedance) for the L and R headphone signals to remove the 1.7VDC offset and then use these...
This question has been discussed several times on these forums. All possible solutions need adding big components, be these 100uF electrolytic capacitors or transformers, to the small audio shield where there is...
If you have for example a good microphone which is very sensitive, would you blame it for picking up too much ambient noise, although it‘s not the microphone‘s but the noisy environment‘s fault?
Away from rhetoric...
The inductor between GND and AGND on the little Teensy PCB is already the required connection for the DC return path by blocking RF, noise, and spikes at the same time. That‘s why no other GND/AGND connection shall...
Compared to the simple and cheap but robust 10bit ADCs in old fashioned AVR hardware, the 16bit (13bit usable) SAR ADCs in the KINETIS CPUs allow a 4 to 8 times higher resolution and up to 50 times more speed but, due...
What I meant in 2) is elementary stuff seen during the first preparation year to engineering schools, question of limited signal transition rate with non zero inner resistance and external capacitive loads. Setting the...
Looks like you run into 2 issues:
1) inconsistent timing, there is no « heartbeat » making sure that your clock signal is at a stable frequency and limited, so that your LED driver can keep up with the incoming...
As long as you don‘t tell what you want to achieve, how can we know? I only can guess that you try to switch levels of GPIO pins at relatively high speed, but for what??? There are readily available shields and...
All these external modules can basically work with the Teensy 3.6. Success depends only on your capability to write appropriate protocol and driver code.
This is definitively not a copy and paste project with readily...
This code snippets are not revealing what you are trying to achieve. Normally, there is absolutely no need to touch at the core files, but your main code should use the exported functions „as is“. If you get compile...
These KINETIS defines are already in the Teensyduino core files and are automatically set, depending on which Teensy you selected in the Tools-Boards menu of the Teensyduino IDE. KINETISL is for the Teensy LC, KINETISK...
How horrible! :) 0.1% more than expected. All that without load and with a digital multimeter whose accuracy is normally between +/-0.5 and 1%...
Just don't care!
Explanations and code examples can be found on the corresponding PJRC reference website: https://www.pjrc.com/teensy/td_libs_TimerOne.html
Symbolic code would be in setup() initialize timer with a default value,...
You should perhaps describe first what you want exactly to do. The Push2 is not only a display but a full Midi controller, intended to work with a DAW. For the moment, impossible to see what a Teensy could or should do...
Although this has been answered multiple times on these forums: The Teensy core files and the Teensy libraries are under the open MIT license. The hardware (see schematics page on the PJRC website) is also available for...
The Push2 expects an USB host at the other end. No Teensy (besides the T3.6 on its secondary USB port) has USB host capabilities. You'd either go for the T3.6 or trickle with an external USB host shield and an adapted...
There is only one reliable way to diagnose such problems: Not asking for blind guessing in the forums, but first of all connecting a logic analyzer or an oscilloscope and checking the signals between the microphone and...
A while ago, I played around with touch.c and a Teensy LC and found it working as expected and described by the ref manual. I even traced the triangle waves at the corresponding TSI pins with an oscilloscope which was...
Or, perhaps I didn't get the question... In my eyes, the primary concern of a commercial product is to protect the firmware against being read out for copyright reasons. I've pointed you towards possible solutions. But...
Studying the Teensy's reference manual, you'd discover that most peripherals, among them the FTM modules, are not clocked with the CPU clock, but with the so called Bus clock. The latter is generated by integer division...
... and how do you want us to reproduce and diagnose the problem without your code (Forum rule!), schematics and pictures of your setup/wiring and perhaps a short video or more pictures of the erroneous display? You...
No... first, create a file "datafile.h" in your sketch directory in which you simply write:
static const uint8_t databytes={/*put here all the bytes you want, comma separated*/};
Second, in your sketch .ino file...
Find latest posts