h4yn0nnym0u5e's latest activity

You might want something a bit bigger for a footswitch…

Hard to say without a bit more information about your application. Maybe something like this 0.49” 64x32 OLED?

Thanks @h4yn0nnym0u5e for keeping up the good fight! Received an update today that the chips are still expected to exit the factory on 9/30, so should be available in about 3 weeks.

Done some work on this, and it appears a limited version of the pre-fetch code could be used to get a 7% speed improvement even with the ISSI chip. The original PSRAM can get to 15% faster, so maybe detection at startup would be the way to go...

Ah, OK, paying proper attention now ... it's that board. You can find some information on how to set it up to work with the Teensy at this post - it's possibly worth skimming the whole thread. One thing that occurs to me is the clock wiring...

How have you connected the sig-gen output to the ADC inputs? Ideally, provide a schematic, not just a description in words...

Well if there’s no easy way, I’m afraid you’ll have to do it the hard way and uninstall it so you can post some pictures of your wiring. I‘m still concerned by your statement that you’re “using the 3.5mm jack” … if you’re referring to the jack...

Do you mean the headphone jack? If so, note this warning: The “ground” on the headphone jack is NOT the same as Teensy ground, and shorting it to ground usually results in no or poor output. The shield silkscreen is pretty much the only place...

This would appear not to be the case - C will not magically add a 0x for you, you'd just get a compilation error. A2 is defined in teensy4/pins_arduino.h: #define PIN_A2 (16) // ... followed a few lines later by: static const uint8_t A2 =...

Finding this thread convinced me to get my first Teensy. I have been well rewarded! I have tested on these machines, using the 2 channel USB setup, with a pair of i2S microphones, (ICS43434): - Mac OS 10.15 - iMac, 3.4 GHz Quad-Core Intel Core...

There are only 8 USB endpoints in the Teensy hardware (and endpoint 1 is reserved for some cryptic reason). So for USB_TRIPLE_SERIAL_AUDIO you’ve tried to use two more endpoints than actually exist, and hence it doesn’t work…

Post a clear image or diagram of the exact connections you’ve used, and a short piece of code (using the </> code tags to preserve formatting) which others can compile and try out. Otherwise we’re just guessing…

Yes - this is a problem when users fail to use the </> code button, and use a variable named i to index an array in their sketch. The BBcode misleadingly interprets the as an instruction to start italic text. [I]Every instance is swallowed...

One thing to watch out for is zipper noise if you just use a pot to set the gain of a mixer object. It’s better to use a fader object with a short fade time. Google will find you a few examples of this cropping up on this very forum…

That will draw more current than the Teensy is rated for. I’ve had good results using Toslink, either via a proper transmitter or a simple resistor+LED.

Back here you said but now Still, I’m sure you can figure out the right balance… :) I‘m not sure (we’ve never seen much real code) how tolerant the system is to loop execution, and the possibility of it blocking interrupts, but anything that...

I just took a look at the RingBuf source code (I haven't used it myself, so I could be reaching incorrect conclusions). The buffer is stored in Teensy's on-chip RAM, so can't be huge. And it relies on writing to a filesystem to empty the buffer...

Exactly. The EXTMEM at the start puts the 8192-element array in PSRAM. That’s probably not necessary, each struct only needs 9 bytes, though for speed the compiler probably makes it 12, so as written it’s only 96kB. But it’s also only big enough...

Looks like Paul’s schematic goes left to right, and the Molex one from right to left. So you do need to fit the capacitor…

Just the 16MB one, I believe from my testing. The datasheets are a bit coy on the subject, but I think the 8MB ones can do a burst read through a page boundary, provided the /CE is only held asserted (low) for <8μs.

Further to issues encountered with getting the AudioEffectDelayExternal object working, I've circled back to the PSRAM memory test, i.e. using the FlexPSI2 interface to give memory in the EXTMEM area. Long story short, all appears well with the...

Thanks @h4yn0nnym0u5e for continuing to evolve the software for supporting the new PSRAM. With any luck, we will eventually have the parts to run it on!

Well, it's "fairly easy" for those who are happy digging around in the guts of the libraries! An updated library can be found in my repo, which includes a version of the ScrollTest example which shows how to scroll both up and down, and also...

It would be a fairly easy change to the scrollText method to enable scrolling down as well as up, but of course you’d have to call it yourself, because text wrapping or newlines only cause upwards scrolling. The while(!Serial) ; feature is...

Accurate documentation … wouldn’t it be lovely?!

Pretty sure it’s needed for scrolling text to work. Some displays may not implement it [correctly], there’s a lot of variants out there…

Is the MISO signal connected and functional?

My improved AudioEffectDelayExternal object has now been updated to allow the use of the 16MB PSRAM on the Audio Adaptor, as well as the older SPI-based options, 8MB PSRAM, 8x8MB PSRAM, EXTMEM and heap. It is of course much slower than fitting it...

@KenHahn, I idly dropped by your website, and noticed you stock the 23LC1024T for use as audio delay memory. You may be interested to know that the standard PSRAM can just be dropped in as a replacement, and if my over-3-year-old PR ever gets...

If that’s how you connected the amplifier, you probably need to do more. Here’s the test circuit from a datasheet: the datasheet I found is at http://www.utc-ic.com/uploadfile/2012/0316/20120316040633653.pdf; you should check it’s close enough...

For "outlines", read "shows exactly". For "most helpful", read "vital". I've tried a very simple sketch based on the vague hints in post#1, using Arduino 1.8.19 and Teensyduino 1.60b5, and completely failed to observe any problem. I'm quite...