Search results

The emulated EEPROM uses a portion of the flash memory chip to store its data. You can find the W25Q64JV-DTR Datasheet on the Teensy 4.1 page tech info section. For the raw speed specs comparable to those raw SD specs, turn to pages 89-90. Those SD specs say "SPI, SDIO", but they can't...

Just to confirm, did cutting those pads apart make it work without requiring the extra power source? Or asking another way... now that Teensy 3.2 is discontinued and people will only use this adapter for Teensy 4.0, should we ask Adafruit to update their web page to recommend everyone using...

You have to implement Daylight Savings Time separately. It's not part of the Time library.

Thanks for the Eagle work! Looks like Adafruit meant for the Program pin to be able to disconnect by cutting these pads apart. Unless there's some specific need for the other connected boards to be able to put Teensy into programming mode, I'd recommend cutting these pads apart so activity...

Or if you have some idea of which signal might be connected to that pin, can you arrange to have it not connect? The idea is to prevent the Program pin from accidentally being pulled low, which puts Teensy into programming mode where the red LED would remain on.

Maybe something unexpected is happening with the Program pin? Looks like *something* connects to that pin on Adafruit's adapter board. Can anyone with Eagle CAD open the schematic and post a PDF copy?

Looks like Adafruit shipped my older on Wednesday (it was placed on their website over the weekend) and the tracking info says it's due to arrive early next week. Please understand if the lockup problem does turn out to be a bug in any of the code we publish for Teensy, whatever fix is made...

This error means the gcc toolchain doesn't work with MacOS older than 10.14 (Mojave). It definitely does *not* work with 10.13.6 (High Sierra). Teensyduino 1.57 and older had gcc 5.4 which worked on old MacOS all the way back to 10.7 (Lion). Teensyduino 1.58 was the first to use gcc 11.3...

Maybe in future software we should have attachInterrupt() just turn on hysteresis automatically?

Maybe you should ask for advise about Arduino's boards on Arduino's forum. Of course it's ok to talk about Arduino's products here, but as a practical matter of reaching people with knowledge and experience using those boards, asking in the proper place matters. Please understand you're...

Can you show us photos of the hardware connections? We could make a lot of blind guesses about the problem, but if the problem is a mistake or misunderstanding with the wiring, a couple quick photos are pretty much essential to really help solve it.

Without any info... here's a completely blind guess. Maybe you have Teensy 4.0 or 4.1, and maybe you also have it connected to other circuitry which has a separate power source, *and* maybe that separately powered circuitry drives one of Teensy's pins or has a pullup resistor which tries to...

Agreed, parallel mode is (probably) simpler. On Teensy 4.1 you can read all 16 bits with a single GPIO register if you connect the data pins to all the "AD_B1_xx" GPIO pins. I spent a few minutes reading (more like lightly skimming) the AD7606B datasheet. This chip has combinations of...

If "possible" means a nice library, then the answer becomes "no". It is only "possible" by diving into the low-level hardware register details.

Have you tried running it on a Teensy 4.0? Looks like this should probably just work, assuming the mcp_can library uses SPI to talk to that chip. SPI uses the same pins, and this code looks like I2C is used for the display, which also uses the same pins between Teensy 3.2 to Teensy 4.0...

Yes, it is possible (2 bits half duplex), but no there are not examples.

This general approach, where software on the PC sends a command to Teensy and software on Teensy replies to each command, usually (pretty much always) results in poor performance. The main problem is PC operating systems are not designed for hard real time tasks. Usually your program will run...

If you desolder the crystal and try connecting the output of an oscillator (rather than another simple crystal), this corner is the location to connect the oscillator output. You probably should use resistors to attenuate the oscillator output waveform to about 1 volt peak.

Yeah, probably. Those look physically smaller than the 3.2 x 2.5 mm part on Teensy 4.1. But yes, if you could get one in the correct physical size, a TCXO would likely give an improvement over the ordinary crystal you have now. Maybe an OCXO part would be better? Depending on the strength...

Thanks for confirming. I'll keep this thread on my list to watch, but sounds like no need to deep dive right now. If it is looking like Wire might have a problem, hopefully a clear test case can be made before I dive into the Wire library.

Before you disable other interrupts, perhaps first try NVIC_SET_PRIORITY(IRQ_PORTD, 0); 0 is the highest priority, 255 is the lowest. By default, various interrupts are assigned 32 to 128, so setting 0 will allow it interrupt any others and no other can interrupt it.

Quick followup, is there still reason to believe the Wire library may have a bug which I should investigate? I see we have a solution to use Sparkfun's library and connect RST and INT pins. Is there any reason to believe the problems without those 2 signals, or the problems with Adafruit's...

Most but not all Teensy 3.0 had black solder mask. Some of the earliest Teensy 3.1 were also black. The board in this photo is definitely Teensy 3.0. The lighting doesn't quite catch the main chip well, but it is readable "MK20DX128VLH5" with adjusting the brightness.

No, there isn't any such comprehensive library hardware usage documentation. While some libraries are fairly simple and use SPI, Wire or Arduino GPIO functions to do their hardware access (most of Adafruit's libraries for various chips do this), some libraries are much more complicated and...

Check out the "Memory" section of the Teensy 4.1 page for detailed documentation. https://www.pjrc.com/store/teensy41.html#memory Might also be worth mention, if you're used to the way NXP's SDK does things... well, we're a bit more creative with how things on done on Teensy. ;)

Something must be wrong with the way you're testing. If you show us what you're doing, maybe we could spot the problem. Recommend starting with a photo of your test setup. It could be a "simple" mistake or misunderstanding which you could look at over and over without seeing, but might be...

Yes, confirm, the flash writing functions depend on running from ITCM.

FWIW, with publishing 1.59-beta4, I changed the main package index to use ZST for all downloads. So far nobody has complained they can't download. In hindsight, we probably should have switched to ZST earlier. I knew the older versions of Arduino IDE wouldn't support it, but I somehow had...

Yes, speeding up the install time is the main goal. Reducing bandwidth cost on the PJRC server is icing on the cake, but not my main focus. We currently have 20TB monthly allocation and we're running between 1.6TB to 1.8TB each month. Eventually we'll use a lot more, as I hope to host videos...

I copied the PJRC icon from the main website. You might need to hold shift while clicking reload to get your browser to reload it.

I also ran the code from msg #1 on a Teensy 4.0, using Arduino IDE 2.2.1 with Teensyduino 1.59-beta4 (0.59.4 in Boards Manager). This is what my oscilloscope sees on pins 10, 11, 13:

Photos of the hardware are what's missing here. The problem is almost certainly poor soldering or a wiring mistake or misunderstanding. I can confirm 64GB cards definitely do work with the audio shield and Teensy 4.0. We can help you get the hardware connected properly, but to advise how to...

I ordered 3954 and 1611 from Adafruit.

After you install any of these libraries, click File > Examples and scroll down the long list to look for your freshly installed library's examples. Some of these libraries give multiple ways to access the hardware. You want "hardware SPI", which is usually the default way. Beware of...

You can find libraries in Arduino IDE, like this:

If I were to order parts to try reproducing this problem, which specific items from Adafruit do I need to buy?

I tried running older IDE versions. Looks like ZST works all the way back to IDE 2.0.4, at least on Linux. Assuming Windows and MacOS are the same. Looks like IDE 2.0.3 is the point where we lose compatibility with "extracting archive: Not a supported archive" by using ZST compression.

Fixed. https://github.com/PaulStoffregen/cores/commit/4d2b1660736b9e468a8175aeec04ca7efe39440a https://github.com/PaulStoffregen/SPI/commit/52f8402bb62c56a0d5fabea20c056f584a703c9a

Is NeoTrellis connected only by I2C? May be slow, but only I2C should not mess up the audio. Very mysterious...

The server hosting these files also has a 1 Gbit connection to the internet.

Quick followup to this old thread. For the next version of Teensyduino, I'm adding a check for the installed location if running on Windows. If Teensyduino appears to in a pathname installed by Boards Manager, but Arduino IDE doesn't give identifying info (which is only present in 2.0.0 and...

Did ZST work on Raspberry Pi? At least in theory it's supposed to be faster on CPU limited platforms.

In Arduino IDE, first make sure you have Teensy selected either from the drop-down list in the toolbar or from Tools > Board menu. The rest of Arduino's menus update depending on the selected board. Then look for the examples in File > Examples > Audio.

Please understand I'm guessing trying to figure out what's wrong over the internet without access to your hardware... so here's another blind guess. I see you have Adafruit_NeoPixel library in use. Looks like Adafruit_NeoTrellis might also have Adafruit_NeoPixel internally? I don't understand...

Anyone using MacOS care to give this a try? Is ZST also best for Macintosh?

You might also consider placing resistors in series with the Teensy pins. Even 1K will go a long way towards limiting current and protecting Teensy is something really bad happens to the transceiver chip, or anything else that has a GPIO pin connected.

Looking like ZST is the clear winner. And wow is XZ slow (as implemented by Arduino using Google Go) on Windows. It was slower when I tried on Linux, but nothing like that slow!

In this screenshot you can see a slightly different URL than the one recommended on the download and install page. It's from this forum thread where we're testing alternate compression for the next release. For long term use, you should use the normal URL rather than copy precisely from this...

Version 2.2.1 is the latest stable release. I downloaded the nightly build from Arduino's website just now. It says versions 2.2.2-nightly-20231130. That ought to be the very latest. Indeed it has the same "Additional boards manager URLs" in Preferences as all prior versions. Here's a...

Wow, I saw XZ was slower on Linux too, but that's a pretty incredible difference. Hopefully more people with Windows can give this a try and report on the overall speed....