Latest activity

Many thanks to all of your replies. Now I think I got the full picture. 1) code to erase/program serial flash is stored in flash FASTRUN Code, but not executed from there 2) code to erase/program serial flash is copied at startup to FASTRUN Code...

Using SLA resin for 3D printing and potting the Teensy in the case can provide a nice finish and protection. Incorporating small pogo pins for connectivity is another creative solution. Regarding sharing the FreeCAD file, you can explore...

That works - thanks!

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.

The new 0.59.4 core seems to be messing with QNEthernetv0.25 and v0.26: ~/Documents/Arduino/libraries/QNEthernet/src/QNEthernet.cpp: In member function 'bool qindesign::network::EthernetClass::begin(const IPAddress&, const IPAddress&, const...

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

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

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

In short: no. The code is stored in the flash but at startup gets copied into the ITCM memory and runs from there. It's still possible to execute code directly from flash (functions tagged with the FLASHMEM attribute don't get copied to ITCM and...

Program flash writes resolve to this: https://github.com/PaulStoffregen/cores/blob/master/teensy4/eeprom.c#L246 // write bytes into flash memory (which is already erased to 0xFF) void eepromemu_flash_write(void *addr, const void *data, uint32_t...

Try adding asm volatile("dsb"); to the end of the ISR function. The Teensy 4 CPU is so fast that it can finish the ISR before external hardware register writes have finished, which causes the ISR to immediately re-trigger. The DSB instruction...

Thank you, It looks like I can put a dab of solder on them to bring it back to normal use.

There are two pads with a connection between them that you should cut if you're going to power the Teensy externally and use the USB connection at the same time. You can see it in this picture: In the bottom right picture (labelled USB Device)...

Hello Paul, I've been searching for the topic "writing to flash in XIP mode" and found your post above saying > Yes, it obviously must be possible because LittleFS does it on Teensy. > The details of how can be found in the LittleFS library...

That works - thanks!

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

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

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.

Bus keeper again? https://forum.pjrc.com/index.php?threads/teensy-4-0-4-1-web-pages-need-a-warning-about-input_disable-on-analog-inputs.69671/

So what do those pins (on/off, prog, vbat) do? How are they used?

Ok, will give this a shot. Yes the variables are all declared as volatile. Realizing I was also seeing similarly odd behavior for the analog current sensor readings, generally a steady value with sporadic fluctuations that are completely out of...

Hello, I made a circuit board that houses both a Teensey 4.1 and Raspberry Pi. The board also has power inputs for 5V and Ground. When I power up the circuit board, both devices switch on and work correctly. They should be able to talk to...

this gets lots indeed - whatever it is

Two quick suggestions, only read micros() once and use digitalReadFast() as shown below. Not sure what your calculation is doing, but are your variables accurlim, duration, plotttimer declared as "volatile"? void isrCP() { uint32_t us =...

Paul, I am assuming that you are doing this, to reduce the sizes of the downloads and speed up the installs. Wondering if it would also make sense to break up the install some. For example, I don't remember the last time I ever did anything...

Paul, I am assuming that you are doing this, to reduce the sizes of the downloads and speed up the installs. Wondering if it would also make sense to break up the install some. For example, I don't remember the last time I ever did anything...

I also verified I could download this to my older MAC: MacBook Pro 2013 variety running Catalina 10.15.7. Verified I could build the MTP TFT picture viewer for Micromod...

Two quick suggestions, only read micros() once and use digitalReadFast() as shown below. Not sure what your calculation is doing, but are your variables accurlim, duration, plotttimer declared as "volatile"? void isrCP() { uint32_t us =...

Hi, I doubt I won't get any feedback as this topic is quite old but ended up with an old set of Pro Pedals with gameport and I am in the process of converting them to USB using all the usefull information here. Getting the same problem with the...

I have a project originally written for the 3.2 that I'm trying to port to the 4.0. I have pretty much all functionality working exactly as original but I'm seeing strange behavior related to interrupts. Here is the attach interrupt in void...

I like that I'll give it a try and report back. Thanks!

I think the distorted sound is my codes fault, I think the sound is triggered over and over again while the pad is lit, instead of just playing it once

Can we have an icon again - its hard to locate the forum tab without it (I tend to keep many tabs open).

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:

This is what your code from message #1 shows on the logic analyzer: Agree with @thebigg that using SPI transactions around every transfer is the correct way. Also described here at paragraph Transactional SPI configuration. Paul

Technical specification NeoTrellis RGB Driver PCB Supply voltage: from 3.3 V / 5 V

Does the trace look any different if you arrange your code like this SPI.beginTransaction(SPISettings(2000000, MSBFIRST, SPI_MODE1)); digitalWrite(slaveSelectPin, LOW); // take the SS pin low to select the chip: stat = SPI.transfer(0x00)...

We use good BOURNS type PEC11L Series encoders. They have 100,000 cycles. The manufacturer recommends an external RC filter (see data sheet). The RC filter already has a pullup. Therefore internal pullup resistance is not necessary.

I've tested various configurations and haven't seen anything resembling 8 cycles.

1us/div means you're sampling at 1MHz, half the specified SPI clock rate of 2MHz...

Hey guys, I'm trying to use a teensy 4.0 for a SPI project. #include <Arduino.h> #include <SPI.h> // include the SPI library: const int slaveSelectPin = 10; void setup() { // set the slaveSelectPin as an output: pinMode (slaveSelectPin...

Using the instructions here (thanks @shawn) , I installed 1.59B4. All my projects compiled cleanly. Linux 6.6.3, pio 6.1.11.

thanks,I will have a try

thanks,I will have a try

Win 11 - Ctrl+P command didn't work? JSON string was right - closed IDE 2.1.1 and reopened and saw 0.59.4. It installed in under 30 seconds to update from 59.3 Had a sketch open and i built fine and uploaded to a locked T_4.1

Assuming the request processing doesn't take too long, you shouldn't need many sockets. I'd start with the default and see how the project behaves. What you describe is the client-side. I'm curious which server you're running on the Teensy?

Overall, I think you have a good chance of completing this project. You have the necessary technical skills and experience and are clearly passionate about this project. Here are some potential problems you may encounter: Hardware Limitations...

Neotrellis needs +5v for Vin. Onboard I2C level shifter is set for 3.3v by default.

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

I have written c++ code that reads from 4 x tf-minis: https://sourceforge.net/projects/benewake-tfmini/