Search results

Yes, that could be a problem. And no one knows how long Sparkfun will continue to produce Teensy. I fear that if difficulties arise—such as renewed delivery problems with certain parts (which don't even have to affect the CPU)—it will disappear from the market faster than you can say “oops.”...

Just for fun, Coremark Results for ESP32-C3 (160 MHZ, RISCV with FreeRTOS in background): 2K performance run parameters for coremark. CoreMark Size : 666 Total ticks : 14644 Total time (secs): 14.64 Iterations/Sec : 409.72 Iterations : 6000 Compiler version : GCC14.2.0 Compiler...

That's probably the main reason. Adafruit is competition for Sparkfun. Sparkfun isn't covering itself in glory in this matter either.

I'm not sure whether the umpteenth variant of the same hardware is really necessary (or the hundredth CAN/I2C/SPI/serial/Battery/audio interface extension). Something new would be refreshing and also attract new users.

Okay, it looks like two boards are needed :) One with high-speed ADC (as fast as reliably feasible). And the other with low-noise ADC, pre-amps, and > 16 bits. There's nothing like that on ALIExpress either—which is basically a good thing if PJRC wants to sell it. @WMXZ: Have you considered...

I've thought about it again, and I believe a really fast board with super-fast ADCs and DACs would open up new possibilities that are not really feasible with other run-of-the-mill microcontrollers. You could tinker with Doppler systems or other interesting physical effects. That would at least...

"Led 1 works but not 2,3 and 4.." All work, but you don't see it. You switch them on and - without delay - off. That's too fast to see it. You just have the delay() s on the wrong places. if (buttonState1 == LOW) { delay(200); // where is digitalWrite(ledPin1, LOW); ...

Yup, json is always heap. But you can use "static JsonDocument doc1" to have at least a bit static. All data, however is on the heap.

There are the UBLOX-GPS. They're pretty good (~1m resolution here) and just need a serial port...

Yes, I had already built something like that for the ESP8266 back then. However, I couldn't find any use cases for it. It's also tedious to develop for two controllers at the same time. It's easier to just use a fast ESP32, multi-core, without Teensy. But the C3 is also my favorite board at the...

I would say it has to be something that absolutely requires the speed of the Teensy. You can find pretty much everything you need in terms of boards on the market—but not necessarily for the Teensy. That's not so important, though. You can still use them. A useful board should take advantage...

Why do you need float for a display? Assuming it is an HDMI 8K display, 16 bits are still sufficient to exceed the resolution.

There are so many microcontroller boards out there. Somehow, each of them is probably Teensy-compatible, depending on which (more or less random) criteria you want to apply. It's just marketing. If it's going to be called “Freensy,” why not? Users will quickly discover that almost everything...

This board is interesting at first, and many long-time makers will jump on it. They will look at it, do some cool things with it, and then put it away, only taking it out to “play” with it every now and then. The thing is too expensive, too big, and too complex to be permanently integrated into...

If that's reason enough to kill a lib that is used by a few hundred users... and someone thinks that's good and right - I don't care. Then there will be no more MP3+AAC with Teensy. There are alternatives. Have fun ;)

Looks nice!

Which was first? ;)

I'm just looking to see if there are any new developments, hardware or software.

2 T4 needed for a line follower.. what's next? :)

Just try a lower rate, like 9600 - just to find out if it's a software or electrical problem.

Yes, and it is dual core and it's possible use the other core for simulantous tasks without performance impact, as long it's not using the FPU,too. I don't think there is an MCU with sufficient floating point performance. I'm not sure about Raspberry. What about those micro-ATX boards with...

You forgot to add the GND connection between both.

Yes then finally use google. Do you seriously think I'll do it for you? Or anyone else? I don't care what ADC speed the Raspi has, and if it has an ADC at all. LOL Not with this chip :) Have fun and keep dreamin :)

1) The titel of this thread said "Oscilloscope". 2) You should explain what you want to do. The answer is in the datasheet of that sensor - whatever you want to do with it (you did not even explain that) Don't expect someone to recommend a chip for you, without knowing any details. But what...

Link I'd recommend to buy a oscilloscope.

https://en.wikipedia.org/wiki/Nyquist%E2%80%93Shannon_sampling_theorem

The absolute minimum for sampling a digital signal at 1MHz is 2MHz. Better is 10 or 100 times the rate - depending on the need, (and whether the signal is analog or not). The Teensy 4.x CPU supports a maximum of 1msps (megasamples/sec), and is therefore not sufficient. Google will tell you if...

No, if there is no blink, and still has the factory blink program flashed, it's broken.

Not that many parts that one would need a BOM...

When it comes to this, and really fast signals, the layout on the board also plays a role. But i'm sure the lcd is well below 100MHz, more likely 30..60MHz max. Just try to keep the layout of faster signals short.

Almost. It is a bit more flexible - 150MHz maximum, and is calculated and set in clockspeed.c. (I played a bit with overclocking the IPG, but in the end it wasn't really stable, and you should refrain from doing so) The reference manual has a nice diagram of all clocks (a bunch), and shows how...

Hard to say, since half of it is missing, nobody can try it out and compile it. Just two general hints: "Register" has been obsolete for decades and is generally not used anymore. Simply because today's compilers decide much better than the programmer what should be in register and what not...

hm ok you're right :)

Try Platformio, it compiles faster.

You already had this information:) As I wrote in my first answer: Yes, IRQ_SOFTWARE is used by the audio libary. My (mp3,acc etc) Audio-codecs library uses IRQ_Reserved1 in additon.

It can be any of the interrupts. USB for example also uses interrupts. You just shouldn't do it in software. If you really want to do it in software without glitches, you have to disable all interrupts. You will lose a lot of functionality. There's a reason why all the hardware timers exist :)

The eventresponder is evil. It disables the interrupts (unnecessarily) and makes the timing of the system more unpredictable. Even if you don't use it at all.

Here is a (incomplete) list: https://github.com/TeensyUser/doc/wiki/Audio-Library-Hardware

That is far too little information. It can be anything. The forum cannot help you in this case.

Yes, that is the intention of these functions.... however you can't really rely on AudioProcessorUsage() because there are some things that are not taken into account. But for a rough estimation it is good enough (in most cases, at least...)

You can use almost any board that has I2S. Small boards are some with PCM 1802 (A/D) , boards with cs4344, max98257 etc etc etc...

There are some useful macros: #define NVIC_ENABLE_IRQ(n) (*(&NVIC_ISER0 + ((n) >> 5)) = (1 << ((n) & 31))) #define NVIC_DISABLE_IRQ(n) (*(&NVIC_ICER0 + ((n) >> 5)) = (1 << ((n) & 31))) #define NVIC_SET_PENDING(n) (*((volatile uint32_t *)0xE000E200 + ((n) >> 5)) = (1 << ((n) &...

You can use any. All are can be used as software interrupt, too. Just make sure they are not used otherwise. There are some unused.. IRQ_SOFTWARE is used by the audio library (yeah I don't like this name, as it says nothing about it's function. Tried to rename it, but, as usual, PRs got...

If you only want to output audio, you don't even need a board. T4 has MQS pins for audio.

I guess, yes. But I don't think PJRC is going to make this. They have other small boards like the PT8211 for audio and their SD shield. If you want to play MP3 only, from the SD only, yes. I doubt you can access the SD from the Teensy. Then, it has no I2S interface for audio.

I would simply use Platformio. A ready to use application. Some buttons (e.g. clean, compile, serial monitor, upload) are at the bottom of the window. Platformio has a really powerful editor, GIT integration without problems, you can easily restore old versions even without using Git, and the...

Try warm water and isopropyl. It must be clean. Don't bee too harsh with the toothbrush. It could easily tear off small SMDs. Be sure that it is really dry before re-connecting it. Even under the chips, where you do not see it.

Because write takes a byte (char or uint8_t) only. With a better IDE, you would have seen this while typing ;)

"USE_DSM_RX" ist not active: //#define USE_DSM_RX where? void getCommands() { ... #if defined USE_PPM_RX || defined USE_PWM_RX channel_1_pwm = getRadioPWM(1); channel_2_pwm = getRadioPWM(2); channel_3_pwm = getRadioPWM(3); channel_4_pwm = getRadioPWM(4); channel_5_pwm =...

Yup, this is due to the way the crash report is implemented. You can see now (again) which option does not work ;) A fix for the report would need a bit of effort, but is easy.