Search results

What CAE software are you using?

The previous versions were also "Made in USA", right? But made by yourselves in your own workshop.

Why is there a header file named <avr/interrupt/h> if the design is based on Teensy 4 (ARM)? Is this a remnant of the porting to ARM?

Speak of the devil: Espressif has just released a RISC-V ESP32 version with MMU support! I haven't seen any pricing yet but hopefully it will force ARM to lower theirs. WCH also told me they would look into my suggestion to add a MMU to their offerings.

After more than 12 years I've finally gotten around to rewriting the software to work on the basis of interrupts. The display update seems much smoother and the key response is snappier. I am, however, somewhat disappointed that the power consumption only dropped from 4.4 Watts to 3.9 Watts...

The number of pages would be limited, of course, but you'd gain memory and process protection. An MCU would only have limited number of processes and the small OS running. It's certainly not meant for running Linux or Windows. Think of it as a more reliable MCU software stack.

BTW I sent an email to a company named WCH in China which makes RISC-V microcontrolers and suggested they add a MMU to their product. Their lowest offerings cost $0.20 (2K RAM and 16KB Flash) and their most expensive ones $2 (with 64K RAM and 256K Flash, somewhat comparable to a Teensy 4). If...

I'm not talking about Linux per se. There are many other smaller and simpler operating systems out there which would greatly benefit from paging and memory protection. Xous could be a candidate.

I read something about the "Linux Tax" ARM is levying for a MMU. How long before some Chinese company will release a RISC-V MCU with a MMU so we can run some half-decent operating system on a microcontroller?

First "production" version in use. The amplifier is a TPA3116 cheap thingie which sounds quite good.

First working version plus the breadboard prototype it's based on. Still need to finish up some small things (power connector, IR receiver window, rubber feet). The sound quality is exemplary. Those ESS SABRE DACs really shine.

Are all Teensies using Cortex-M cores (without MMU)? Are MMU's out of scope for Teensy?

Almost got the first one working.

Why don't Teensys have seperate "boot" and "reset" buttons like newer ESP32 products? I find that much more convenient than having to reset the device by the Teensy Loader.

Has any other Teensy flown in space?

A small clip of the breadboard prototype in use can be found here.

Bummer. That means I'll have to redesign the SD Audio Player PCB.

The first two assembled PCB's. I'll soon attempt to connect the SD card module, the D/A converter and the LCD

So is Teensy 4.0 pin compatible with Teensy 3.1 / 3.2? In that case, it wouldn't matter. Right?

Yep, thanks!

Does PJRC publish dimensional drawings of the various Teensy's to aid in development of footprints in CAE libraries? I'm looking for a LibrePCB Teensy component but can't seem to find it. I'm therefore contemplating contributing my own library but it would be nice to have dimensional drawings...

After some glacial development I'm now moving ahead with the production of a PCB.

The obligatory picture of the working setup with the IR receiver. I have to say: I'm very pleasantly surprised by the sound reproduction of the D/A converter. Probably one of the best I've heard, more so considering the dirt-cheap price.

Hi Paul, I'm using Teensyduino 1.54 I think (I'm using Visual Studio Code on Linux Mint with Platform.io and I'm not sure how to check). It was the first version that had long file name support. I'm not transmitting with IRremote, just receiving commands from a remote control. I'm using this...

After two hours of fiddling I finally got the IR remote receiver working as well. I still have to translate the codes into commands upon which the player will act, but that's certainly doable in a day's work.

Picture of the working setup with the new I2C LCD. I'm now going to work on integrating the infrared remote receiver. I've already prepared the software to handle the commands.

Oh and BTW, I'm also experimenting with Seeeduino XIAO which is a tiny form-factor Teensy doesn't have at the moment.

Thanks for this. I upgraded my Teensyduino in my SD Audio Player and it now supports long file names.:D

I'd like to add my $0.02. What I'd really like to see is a more integrated development experience with debugging through USB. If possible I'd also like to see being able to upload code without having to push a button on the Teensy. I'm also trying to get in contact with Eben Upton to urge him...

Paul will be pleased that I switched back to Teensy 3.0 for my Room Thermostat project after I started with the Raspberry Pi Pico. Maybe I'll get back to using it on some other project.

Just received the IR remote control and its accompanying IR receiver. Also ordered some additional 38Khz IR remote control receivers, just in case. I also got me a I2C LCD display even though I already have a regular LCD display (both 2 x 16 backlit). In addition, I also got me some NPN and...

If you want to play 24bit/96Khz I suggest you convert the file into FLAC and play that from the card since it needs to read less data. Another solution could be to increase the size of the SD card buffer in de SD code.

I recently updated the Teensy framework on my Platform.io installation and I suddenly got long file name support! I was looking in the source code and asking questions here and there but in the end it turned out to be as simple as pushing a button and recompiling and it works! I'll now be...

How do you use the SD drop in replacement? I want to use long filenames with the wave file player in the Audio library. Do I just add the new SD.h file? And what do I need to do with the SD.cpp file? Add it to my project and compile it?

You should power the DAC board with 5V, not 3.3V. At least that was the case with my DAC board (PCM5102 based).

I finally got the damn thing working! But only for WAV files at the moment. Stay tuned.

This last code contradicts what you're saying. It should be:        CORE_PIN3_CONFIG = PORT_PCR_MUX(4); // pin 3, PTA13, I2S0_TX_FS (LRCLK)

I couldn't get the software to work, but I now see the problem: I'm using the default SPI pins for the SD card, so the I2S doesn't work.

This board runs Linux. What's notable is that the article specifically refers to the "Teensy form factor."

I'm currently having the problem that the FLAC file plays for only a fraction of a second. I'm investigating what the problem is. As you can see the GetLastError() on the FLAC player object is 0 (no error), which makes it harder for me to identify the problem.

Are the Teensys (Teensies?) made in the USA or somewhere else?

Received the metal enclosure from China.

You're using KiCad, right?

Cool. I'll grab me a couple of those.

I'm planning to power the Audio Player through a USB mobile phone power adapter which can be purchased almost everywhere these days. For that I need a breakout board like this one (alternatively this one). I also need a 3.3V regulator like this one.

The idea behind the large display is that it should be easily read from a distance. The user will mostly be operating the unit from his / her remote control. That looks nice, I'll look into that. But I'm gonna stick with a 2 x 16 display for the first version.

I don't think I'll need it if I'm already using the SX1509 for the keys. i'm currently not planning to use keys on the front panel, merely an IR detector.

The LCD I was planning to use is here. I haven't found a similarly sized I2C or serial version.

I was planning to use a large 2 x 16 LCD with HD44780 controller in 4-bit configuration (so I'd need 7 I/O's).

Nice, I may use the SX1509 breakout board from SparkFun.