h4yn0nnym0u5e

From the start: Put a tiny blob of solder on one corner pad Using tweezers position the PSRAM as best you can Reflow just that corner pad Solder the opposite corner pad; you can make minor position adjustments with the tweezers, the legs are...

Completely forgot about that! If I remember right I use to get a message that I forgot to select MTP Serial. Its been awhile since I played. Been playing with the Arduino Uno Q. @PaulStoffregen - please dont ever make a board like that, its...

Also, it looks like you didn’t select an MTP-capable option in Tool/USB Type

…where it won’t get initialised. See here

Yes indeed! :) Sadly, with Mark's large program __verbose_terminate_handler() makes zero difference. I tried both gcc 11.3 and gcc 15.2, both Faster and Smallest Code optimization. No change on any test, not even 1 byte. However, with...

I recall wanting to remember stuff, too. Not sure what it was, though…

This thread, maybe? Or possibly this one? I’ve recently experienced the linking in of odd stuff I wasn’t using, as referred to in this post. Unfortunately it’s in an application which uses quite a few heavily modified libraries, and a modified...

The only library I can think of to add to the non-Teensyduino pool is TeensyTimerTool, and then only because I happen to be using it on a current project.

Because uint8_t useFrameBuffer(boolean b); // use the frame buffer? First call will allocate vs void setFrameBuffer(uint16_t *frame_buffer); Line 48 looks as if it's expecting a bool, and you've handed it a pointer, moreover a pointer which...

ST7735_t3_multiple.ino tested with two ST7735 displays on SPI and SPI1 of a Teensy 4.1. All good - a few minor tweaks in PR# 42.

I've done a very quick test on the ST7735_t3_multiple.ino example with a Teensy 4.1. Compiles OK with no warnings, and runs one screen on SPI with pins changed to suit my hardware. I'll add a second screen and check they both work together OK.

Can we take it you're determined to go it alone on all these fixes? Or is it worth trying to delegate at least a first pass to willing forum members?

That error happens when trying to link with a function that doesn't exist. If the function is never referenced the linker never has a reason to look for it.

I agree. Line 357 says // from Adafruit_GFX.h, at the start of a block of method declarations; if you then look at line 1374 of the Adafruit code, you see it does exactly what you said, duplicating the "magnification level". It seems to be a...

I deleted the copies added to the sketch and downloaded them afresh. Compiles fine now! Must have accidentally edited something on the sketch. False alarm. Apologies! Cheers for the reply (again!)

It ought to work OK. I’ve just checked back, and most of that was written in April 2021, so almost certainly using Teensyduino 1.55. Maybe posting the actual compiler output with verbose mode on, in code tags, would yield more clues? It looks a...

Yes, newly created .EHEX files in 1.61 work with all previously released bootloaders that support secure mode (1.07, 1.08, 1.09). Yes, exactly. This is why I've not yet updated the web page, beyond the brief mention in the update. I need to...

This all seems super-hard to explain in paragraphs of text. Maybe a table along these lines would be helpful? With the blank cells filled in with "OK" or "Fails - do X instead", of course :) I don't use any of the secure stuff so it's quite...

Tested with Win 11 / IDE 2.3.9 and the provided SPI library rather than the updated one from GitHub. All good. The project I'm working on uses TeensyTimerTool, which throws a warning with the new toolchain; it may have done so with the previous...

Updated to that and it's all working now :D - thanks Paul. Any chance you could increment the version number? The existing one is apparently 10 years old, and getting a bit tired...o_O

I did try 0.62b1 briefly (Win 11, IDE 2.3.9). It compiled my current project OK, in fact much smaller than 1.61, but the code crashed at line 1278 of SPI.begin() with a null pointer. A minimal program didn’t, but unfortunately I don’t have the...

That’s disappointing. I have two portable and one standard installations of 1.8.19 on one of my main dev machines. I prefer those greatly over 2.x, for which Arduino seem to have taken a Microsoft attitude of “let’s do the stuff we want, break a...

For what it’s worth, I think the structure you have looks about right. Very minimal changes to cores, which should make maintenance easier, then libraries on top which can be forked if needed, and will survive Teensyduino updates. I wasn’t sure...

Pull requests languish seasons turn and turn again who will hoe the weeds?

Very brief testing done, all seems to be working as advertised! I only tested the CCs, but given they're good I can see no reason why buttons / notes won't work too. I know it looks as if I'm using Teensyduino 1.59, but actually it's just a...

OK, found it - there's a second library it's dependent on, which you didn't mention in the example header comment. Compiles ... now to test ...

Just trying the control surface example, and it doesn't compile: Arduino: 1.8.19 (Windows 10), TD: 1.59, Board: "Teensy 4.1, Serial, 600 MHz, Faster, US English, 44.1kHz, 128 samples (normal), 2, Off" C:\Program Files...

Managed to resolve this after all! Instead of using tft.fillScreen, I saved every data point to a huge array and then redraw it all in the background colour. Wish I'd tried this weeks ago. No loss of timing or envelope oddities. Anyway - thanks...

This looks really interesting, and is relevant to my current interests :) I see that so far you’ve done some (all?) of the tricky low level stuff, but there don’t appear to be any simple examples of e.g. a keyboard or control surface sketch so...

Which FreeRTOS library are you using? I've just discovered an issue with the one by Timo Sandmann which was causing malloc() to allocate in RAM1 (for FreeRTOS or any other library). In my case that promptly ran out of space, leaving plenty of...

As of Teensyduino 1.61, FlexSPI pre-fetch isn’t enabled, so no issues will arise with any test. There’s a PR in to enable it, which gives a useful speed increase but can result in memory errors if a pre-fetch access occurs across a page...

Good luck! Do ask if you need help. Yes, one of my earlier and not-so-fine efforts, though with a bit of tape it gets the job done for now. The project as a whole has stalled for a while now. I got a bit stuck on the UI for loading SoundFont...

Note that this test isn’t probing enough if FlexSPI pre-fetch is enabled and 16MB parts are fitted. I have a PR in to fix this issue. Looks correct to me - 118, 59 and 29 seconds. :unsure: That’s the behaviour I saw which prompted this post...

The value is actually set in the cores part of Teensyduino, not in the Audio library itself - you can find it in the AudioStream.h file. The value can be changed without editing the file, by providing it in the compiler’s command line...

…is pretty much what was suggested in the post I linked to back in #18 above. I think they used a one bit DC offset.

I found this thread - maybe that technique would work for you?

Windows is notoriously poor when it comes to developing USB devices, though usually only if you've left the VID and PID the same but changed the descriptor contents - if your sketch always looks like the same USB device there ought not to be so...

I checked the boards.local.txt file in the PR and saw that it had already been fixed there. Otherwise, I would have let you know.

Wonderful. It works. I can now switch between linear and exponential envelopes. Thanks :love:

You probably need to import just the exponential envelope files. I merged in the most recent master Audio from Paul’s repo, but as he doesn’t see fit to use branches for development it’s polluted with Teensyduino 1.61 code, which also needs...

I've had a play, added some instrumentation pins and fixed a few bugs: the incremental screen clearing was wrong - you had increasing sizes of sub-area (N*LY/10), as well as changing positions. That resulted in longer clearing times than...

That's a good point against moving stuff from cores to Audio! All the "real" changes made have been in Teensy 4 cores, so will not impact Teensy 3, though of course Teensy 3 users won't be able to benefit, either. The only change within Audio is...

I assume that's a limitation of your Jeannie 1 project - with my code you could always set all of attack, decay and release to near-linear. However, you couldn't change the sustain level live; I've pushed up some changes to allow this, using...

I tend to be of the opinion that "if it ain't broke, don't fix it"! I agree it's messy as-is, but it conforms to the old structure so it looks as close as possible to a simple pull request rather than a re-structuring. The other major reason to...

With my code you can adjust the curvature of the attack, decay and release using a second optional parameter (target_factor). The usable range is 0.9999 to 0.5, defaulting to 0.95. If you set 0.5 it just uses the first half of the exponential...

@h4yn0nnym0u5e Thanks for submitting the pull request. Right, I added mute and volume controls. It is implemented in a similar way to the current usb audio interface. That means the volume and and mute signals are received by the usb interface...

Sure it is. It’s just a bit messy to get set up, but people have been doing it successfully over the couple of years it’s been in development. The instructions for doing it the old way are in the ReadMe over at...

Do you have anough space, power, and heat dissipation ability to consider using a Peltier device to cool a Teensy mounted in an insulated sub-enclosure? (300x92mm is a fair bit of space, but only 2-dimensional, which could be an issue :ROFLMAO...

Thank you for your suggestions - much appreciated. You've given me a lot of ideas to investigate. I'll do as you suggest and scope a spare pin to monitor the key points in the code.

So ... I don't have a piezo sensor, so I can't usefully compile and try your sketch. If you can simulate the piezo in a way that reproduces the issue, that would be helpful. I also don't happen to have the ILI9341_t3n library installed -...