Works here too, after a bit of a 'mare updating Windows 11 on a sacrificial laptop 🐐. Tried on 1.8.19 and 2.3.10, failed before the workaround and worked after, for both IDEs.
I get the LISTENING status on my Windows 11 25H2 machine. I hadn't been experiencing problems, KB5127936 is not installed, and I've turned Windows updates off for the time being.
I’ll take your word for it - I have only a rudimentary understanding of the workings of USB, so “it can only handle one address” doesn’t render me much wiser. Then again, very little does, these days o_O
Isn’t that just re-inventing LittleFS? Or was that not ported over at the time? Obviously there’s some overhead with that which could be worth worrying about in some applications; as I say, not super-familiar with LittleFS…
True, I’d love to...
It did occur to me in an idle moment that a lot of flexibility is lost by only being able to use six endpoints on the RT1062. Would it make sense to present as a hub, using real endpoints, plus multiple virtual devices each “plugged into” (and...
I’m not going to waste my time tidying up a year-old PR in the vague hope that maybe it’ll get pulled before a real conflict appears. As far as I’m aware it works as-is, and if it’s a tad rough around the edges, so is quite a lot of the other...
If it’s that (quite possible), there was a thread on the subject, and I did that PR, but only a partial fix (created 2 months after my PR) made it into Teensyduino 1.60. And 1.61. And 1.62…
You may be best off using the Arduino-Teensy-Codec library. It’s been archived, but supports other filesystems and compressed formats, so could be used for short files in Teensy’s flash, or bigger ones if you put flash on a 4.1’s bottom pads...
When a button is pressed, store
which button it was
the difference between the relevant setting (timer or temperature) and the current encvalue
When the encoder changes
add its position value to the stored difference
put that value into...
I tell a lie - three programmers. I'd forgotten about the QL-specific GAL programmer, which allowed me to program the 16V8 for the Minerva mkII, implementing a bit-banged I²C interface by reading from the top few addresses of the OS memory. Happy...
Quite so. I still own a couple of EPROM / GAL programmers, though sadly no UV eraser (not that I'd have a use for it, really). First experience was (probably) trying to make a programmer so I could blow extension ROMs for my Acorn Atom; around...
I suspect it’s the only existing copy of some code, and the datasheet’s quoted >200-year data retention time has proven to be …. optimistic. If you build your own reader you can mess with timings and drive levels until you get the right data out...
Apart from the sheer entertainment value of
groping around
in a coal cellar
with no lights
and a blindfold on
looking for a black cat
being directed by someone else
who doesn’t know what a cat looks like
when the cat has long since escaped…
this...
@philipPJ
I think you are an AI bot and you do not understand a single word of what all the helpful people are posting here.
Please try to convince us humans that you are human and are willing to accept help.
I must confess I’ve never fully understood this approach. If the Teensy USB is damaged due to over-use or an inept user, it’s game over. Plus my use cases often need access to the SD slot.
On the rare occasions I enclose a Teensy, I’ll usually...
how do yo trouble shoot an intermittent? still cant get more that 11bits toggling and no code suggestions. looks like the Teency wont do 20 lines
clearly you don't know how the read timing diagram works.
It’s not only a lot of work, but would probably just compound the existing maintenance nightmare.
For the standard 16-bit audio library, there are 59 outstanding PRs, 82 issues, and the version number hasn’t changed in 10 years despite most...
Thanks Paul. I tried it again this morning, and now I can't reproduce it myself! In the mean time I'd pulled the most recent changes into an M1 Mac and that also fails to show the issue. If it occurs again I'll archive the sketch and associated...
It definitely makes sense to protect the Teensy pins, and an opamp gives you the opportunity to shift the levels if needed. I’m not familiar with Eurorack stuff so not sure what might be needed…
@PaulStoffregen, do / will you also have the hardware to test 8MB+Flash and 16MB+Flash, with LittleFS or similar? I'm not fully following all the register-bashing here, but it seems these are the other hardware options that could affect results...
That seems to be how it goes. You work on something for 5 months and 176 commits, then it throws a completely weird and spurious link error at you, which is "cured" by changing CPU speed o_O . Or in your case, to a different optimisation.
Here's a variant on the code, which switches between valid and invalid preloads
#include <Arduino.h>
elapsedMillis ticker;
void setup() {
pinMode(LED_BUILTIN, OUTPUT);
digitalWriteFast(LED_BUILTIN, LOW);
}
void loop() {
static int...
I just happened to have a Teensy 4.1 with 8+8MB fitted loafing about doing nothing, so I tried the above. It is as @jmarsh says: the LED flashes slower than 1Hz, but at 1Hz when the memory address is set to 0x70100000 (a valid address).
In cases where a user might do something stupid, I’d tend to go for an opto isolator. You should be able to find a fast enough one with several channels in surface mount, I’d’ve thought.
Unfortunately the above doesn’t work for me, for the issue I reported here. I have no idea why this has suddenly happened, or why changing CPU speed fixes it. It looks very like the sort of Heisenbug that will defy any effort to cut down my...
Funnily enough, I just did! Never seen it before... Weirdly, I could make it go away by compiling for 528MHz CPU speed, but I want the full 600MHz, darn it.
I found this thread which had a solution for Teensy 3.6; a similar solution for Teensy...
Just an idle thought while scanning the build hooks capability ... would it make sense to use a larger start value and increment, rather than 1 and 1? So the above becomes, say...
I've given this a quick test, and it fixes the problem for IDE 2.3.10 (presumably any 2.x).
As you might expect, just blindly pasting the same change into the platform.txt for IDE 1.x breaks it, because 1.x puts the "binary" output where the old...
Just to re-iterate post #17 above: I’m 100% convinced we know what causes the build error with IDE 2.x when doing an Export Binaries. I’ve given a full analysis and temporary workaround, it just needs confirmation by others…
Sure...
Open IDE 2.3.10 (probably any 2.x)
Open any sketch
Select Sketch / Export Compiled Binary
Observe the Compilation error: exit status 1
Well, a bit of investigation reveals the answer to this: you told it to! Here's a snippet from...
You MUST delete it! For IDE 2.x, the exported files are now in a sub-folder of the build sub-folder in the sketch. Any "exported" file in the sketch's root has a very high probability of not being the code you just built. You Have Been Warned...
OK, so I've just tried this (Arduino 2.3.10, Teensyduino 1.62). There's clearly a very bad bug that needs fixing...
As noted in the linked thread, the teensy_secure utility is looking for a suitably-named .HEX file, in a place where only a...
Just to add … IIRC, the Arduino 2.3.10 menu option Sketch / Export compiled binary, which should give you an accessible.EHEX file, failed to do so because it was looking in the wrong place for the .HEX file to convert. @Thundercat, you might want...
That's helpful already. I've definitely experienced issues when statically-constructed class instances worked OK, but dynamically-constructed ones failed in unpredictable ways. It would be relatively unusual to use the USB audio classes...
Well, we have this post. Of course, we were previously told 1.61, it didn’t make it to 1.62, and 1.63 hasn’t started yet. I’m definitely not holding my breath, but it is getting a reasonable amount of traffic here, and there’s a fair few people...
I’d like to think it would make better use of your time to check the new USB code - see thread starting here; everything before that is a previous incomplete attempt and a bunch of one post wonders offering to help and not following through.
The...
That sounds plausible. The target receiver latency in the Teensy code is set to 1.8ms; I can’t really follow all the code, but presumably there’s a similar or smaller transmit latency. The USB packets are at 125μs microframe intervals, which...
Over the years, the Teensy platform set the gold standard for microcontrollers, driven by both exceptional hardware and a vibrant community that actively shaped the core.
Looking at recent releases, however, updates seem heavily dominated by...
Please note, my intention for these improvements was solely to fix bugs, allow use of different audio block sizes, improve efficiency (slightly) and improve versatility (add 1024-point averaging), while retaining compatibility with the original...