BriComp

The bootloader chip reads the MCU SN and locks itself to that MCU. If you get a new MCU you WILL need a NEW bootloader chip.

Hi @Turby, I see you use my Nextion library. Some time ago I updated it to version 2, called Nextion2. I am currently working on a version 3. The latest does not include many updates, just sorts out some potential problems. Edit: I should have...

I use nextion (Intelligent Series) with my own library.

The Teensy has TWO clocks. The Teensy clock and the RTC clock. These need to be synched. In your setup put setSyncProvider(getTeensy3Time); I believe that this links the two clocks together. To get the time when running use time_t...

Yes, that's why I always use RV-3928_C7. I've had one going for years on the original battery. Extremely accurate as well.

He says he has:- Teensy 4.0 connected to nothing except CR2032 connected to VBAT and GND

The support will develop. There are some talented groups starting to develop real products. Places like CERN, The European Laboratory for Particle Physics where the World Wide Web (WWW) was invented in 1989. I worked at CERN on ATLAS experiment...

I note the plan to have the aerial directly above (or below) the metal can of the SD Card reader. How will this affect the aerial performance?

Change // initialize USB serial port Serial.begin(115200); a = micros(); while(!Serial) { if ((micros() - a) > USBTimeout) { break; } } to // initialize USB serial port...

Here is a YouTube video showing the changes made to the TI part, highlighting potential problems using this part. Just as a snippet, the slew rate has almost HALVED!

Where are you?

Note that this ONLY applies to the Texas Instruments version of the part.

Given that this may be detrimental to the life the Teensy I would recommend that it is NOT part of a library ( that would make it too easy to apply ) but a method on how to achieve it should be CLEARLY documented. i.e. make it available but not...

BE AWARE. BitDefender does NOT like the links above!

From @Paul. Although it quotes Teensy 4.0, I believe the sequence/requirements are the same for Teensy 4.1.

When posting code, can you do it between code tags using the </> button. It makes your code so much more readable and therefore more likely to get a responce. I have posted your code below so you can see the improvement. #include <Arduino.h>...

Keep a log of filename(s) in EEPROM.

Thanks @Paul, over to you @bmwcyclist.

@PaulStoffregen this gentleman is trying to contact yourself, as requested, but is having problems. Could you investigate.

The server is currently down, and being rebuilt. I might be up later today.

Server has a new SSD installed. No software, just a clean Linux install. So far the only service I've restored is DNS, so browsers can resolve forum.pjrc.com to an IP number to access this forum. I'm uploading the backup files now, about 75GB...

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...

I am being the messenger here as the user doesn't spend much time on the forum. It appears that the changes fixed some units that previously demonstrated the issue, but on others it allowed them to get further along in the process but then still...

Still OK (PJRC) in the UK.

Having examined the audio library supplied with Teensyduino I cannot find the example you mention above. I do not believe that it is Paul's code.

@Paul You have the wrong address here "Arduino 1.8.x, Windows: https://www.pjrc.com/teensy/td_160-beta1/TeensyduinoInstall.exe" should be "Arduino 1.8.x, Windows: https://www.pjrc.com/teensy/td_161-beta1/TeensyduinoInstall.exe"

I might be wrong, but one advantage I see of using Serial between the Teensys is that you just do a Serial.print.... and it's all buffered and your code can go and get on with other things.

You might want to look at the Snooze library. It is included with Teensyduino.

For UART (RFx,Tx) level shifting, better to use ADUM1201.

When powering a Teensy project I invariably use a Raspberry Pi Power adaptor. They are usually well priced and I guess of sufficient quality.

USB isn't anything like serial, where both sides are essentially the same type of hardware. With different connector serial types you basically just have to worry about connecting TX to RX and vice versa. USB doesn't work anything like that...

I have no problem doing T4.0 on Arduino IDE 1.x.