PaulStoffregen

Don't worry too much on the solder. Just avoid these 3 most common soldering problems 1: Cold solder - not applying heat long enough 2: Board mounted backwards - check the pin numbers match up! 3: Boards too close with parts on bottom of...

If you're able to water wash and bake dry your circuit board, using Kester 331 solder and Kester 2331-ZX liquid flux gives amazing results. I personally use that combo for PCB prototypes. Organic acid flux like Kester 2331-ZX is amazing stuff...

For these latest tests, did you monitor the 3.3V power with your multimeter? Do you have any way to monitor the USB current? If not, please buy (and use) one of these inexpensive USB power monitoring products.

Try change this sprintf(FileName, "%04d_%02d_%02d.csv", (RTC.getYear(), (RTC.getMonth(), (RTC.getDay()); to this sprintf(FileName, "%04d_%02d_%02d.csv", (RTC.getYear())...

First read the "Power Up Sequence" info on this page: https://www.pjrc.com/store/ic_mkl02_t4.html Hopefully the little javascript buttons can help by visualizing the power up steps for you on the schematic. If the sequence is getting to step...

Yes, custom USB interface combinations can be created by editing usb_desc.h. See the comments in that file for details. When editing any core library file, first confirm you have the right file by adding a simple syntax error. If clicking...

The newer SD socket (with 8 tiny holes where you can see the metal contacts) is the same push-pull type as the older SD socket (without tiny holes). SD sockets with push-push action have a spring inside. Usually they are at least 2mm wider to...

If using Arduino IDE 2.x.x, use Boards Manager and click the drop-down list to switch between any of the versions which support the newer IDE. If using old Arduino IDE 1.8.x, go to the download page, scroll down to the section for Arduino 1.8...

No, sadly GD32 and MKL02 have different pinout. You could restore your Teensy 4.0 by resoldering the chips it originally had when new. Normally I wouldn't even suggest this, but from your comments you do seem to have the ability to desolder and...

Please understand this is guesswork since I can't see the files on your PC, but I'm pretty you have copies of SD and SdFat different than the ones published in Teensyduino 1.59. Even if Arduino IDE is utterly unusable for you to go real...

So I just want let you know I haven't abandoned this project it's that I found out two weeks after getting my new Teensy's that I am moving again and have all my equipment in storage now. I hope this is the last time I have to move but I just...

Ok, I thought you were asking about the U2 chip because of "decipher the manufacture date of the bootloader". U2 is the bootloader chip. U1 is the main processor, MIMXRT1062DVJ6B. About the first 4 letters, "CTDA" in your photo, also a good...

I can add just a bit more info. That chip with code "AVNH" is probably 2019 to 2021 vintage. Here is a photo of a newer chip with "AAUY" sitting on the NXP packaging label with date code 2325 and lot code info. At the very least, hopefully...

I only know how to read the first line, where M2T5 identifies the part number as MKL02Z32 (the last character is number '5' not letter 'S'). On this chip, I have no idea how to interpret "AVNH". I suspect it is the date code and maybe more...

As requested, I've deleted the schematic and photos. Did you watch the voltage and current while working with the unresponsive hardware? Make any progress?

Try making a copy of your main project and delete portions until Serial2 starts working. Or if you don't find the problem, delete as much of your main project so you can show us a complete non-working code. If anyone can copy it into Arduino...

As explained earlier, simply delete the installed copy of PulsePosition which is overriding the known-good copy. This is the most important info: Multiple libraries were found for "PulsePosition.h" Used...

Did you monitor the voltages and USB current while working with those dead boards? If you don't have a voltmeter and you're not looking to spend a lot of money for a top-tier model, this pretty cheap one works quite well.

Just to repeat once more, while trying the 15 sec restore or anything else, please get into a practice of continuously monitoring the 3.3V voltage, VUSB voltage, and USB current. Also remember this restore process only works on not-yet-locked...

Probably not, but maybe... The bootloader chip is not involved in the software startup process. It does not function the same way as a traditional software-only bootloader, which runs first and then jumps to your program. When Teensy starts...

I'm just re-read this entire thread, looking for anything I missed and just generally trying to get a clear picture of this difficult situation. I still don't have a clear picture, so I'm hoping you might compose 1 good message to summarize all...

Maybe this is stating the overly obvious, but until this problem is fully resolved, please put sockets on any more PCBs you build so you can easily remove the Teensy.

Could you explain how the power supply works? Is all the board's power coming from the USB cable connected to Teensy? Or is external power connected (maybe not shown on this schematic)?

I don't know why that error is appearing. More info is needed to even begin to diagnose the issue. Before you go to the effort of collecting more info, please do the easiest thing first. Download and use a fresh copy of the 1.59 installer...

Which USB hub should I use when I try again?

Article posted on the website today https://www.pjrc.com/jawsfx-guitar-pedal-with-shark-proximity-looping/

SD card corruption is really unfortunate. Wish I had a better answer, but can't know why this happened. The only known issue (known to me... on my list of issues to fix) that seems close would be incompatibility with buffers in cached memory...

Your program configured pin 36 as INPUT. With nothing connected, the pin can randomly pick up all sorts of noise. Use INPUT_PULLUP. Or connect a real resistor to the pin. Do not leave high impedance input pins floating.

Please shot a screenshot or photo of the screen.

On 2nd though, perhaps my bandwidth estimation is off by a factor of 2. The narrow pulse would be half of a cycle of a square wave. Maybe. When you use only 8 bit PWM, the 255 / 256 = 99.6% duty cycle, which is a pulse 16X wider. So it needs...

I ran your program (the first on msg #11) on a Teensy 4.1. This is the waveform my scope sees on pin 29. Looks like a very stable 25 kHz waveform. My scope says the duty cycle is 99.97%. That's very close to 4095 / 4096 = 0.999756. I...

Please write more specific instructions to reproduce the problem. Which items are plugged at what time after upload? Or even better, give photos or short video with serial monitor visible.

I ran your program from msg #1. I made only 1 small modification to print "loop <number>" slowly because the note on/off messages scroll off screen too quickly (full code below). static elapsedMillis msec; // print at a reasonable pace if...

This is a really strange case. Normally when a board goes badly and consumes too much current for things to get really hot, either the 5V power or the 3.3V power measures low. But you said you measured 4.7V and 3.3V. Normally when a large...

Maybe this can help? https://forum.pjrc.com/index.php?threads/queued-triantaduows2811-a-32-channel-ws-library-for-teensy-4-0-using-flexio-dma.59023/

Try setting Tools > CPU Speed for slower, like 150 MHz or even 24 MHz. Quick and easy way to test if running too quickly for signals to stabilize.

Yes, you're right, something in these libraries is causing unused code to be compiled into the final binary. I've added this to my low priority bug list. Just to set expectations, this is a low priority if everything works properly and the only...

Sure. Teensy 4.0 has 7 serial ports. 5 of those are one the easy-to-access pins. Just connect the other modules to any of the other serial ports and then replicate your code for the other 2. Ok, maybe it won't be quite the simple. You'll...

I am not aware of any way, at least from code running on Teensy. I did try this by editing descriptors. For Serial it is possible to affect the name shown on MacOS and Linux, but not Windows (because it ignores the descriptor name and gets the...

You should probably run some tests with that Kingbright LED. The specs say brightness is 10 to 25 mcd with 10 mA current. Maybe a lower current will meet your needs, or maybe not. Only you can make that judgement call. If you need a...

Try the 15 sec restore. Hold the pushbutton for 13 to 17 seconds. At 13 sec, you'll see the red LED blink briefly to indicate you're at the beginning of the 4 sec window where releasing the button causes full memory wipe and restore of a...

On Teensy or pretty much any circuit board, if you have a large current flowing an unknown path, one thing you can do is measure voltage drop along the power and ground. You'll need a multimeter with sensitive mV scale. Then just touch any 2...

This is quite weird indeed. Is this Teensy actually working, like you can load new programs and they run correctly?

Try measuring the 3.3V voltage while the power is on the input parts are hot. Do not rely on ohms measurement. If the voltage is very low, only several mV, that's a sure sign the short is metal. Usually these problems can be fixed if you find...

I tried to look up the minimum pulse width needed for the GPIO interrupt hardware, but couldn't find it in NXP's documentation. But as a general rule of thumb, usually 2 clock cycles are needed because they almost always use a circuit that...

The ADC inside Teensy is far too slow for this type of narrow pulse. You will need to handle this as a 3V a digital signal. A voltage comparator is probably the best way, but TL714 is probably too slow. I'd recommend trying a faster chip, like...

I also have no understanding of the context here which makes answering difficult. (the reason I haven't replied to the latest questions) @rootwyrm - Have you actually connected the signals to your Teensy 4.0 or 4.1 and experimented yet? Maybe...

Try replacing all the wires carrying the USB signals with short lengths of real USB cable. Don't use ordinary hookup wire for D+ or D- anywhere, not even for short lengths. Even if all the wires are real USB cable, the use of non-USB connectors...

Well, this was just a guess. But it fits the facts you mentioned, that the code had worked on a previously used Teensy 4.1 but failed when you tried on a new Teensy 4.1. The uninitialized contents of emulated EEPROM would be a likely...

When you edit usb.c, first try adding any simple syntax error. Then click Verify. Arduino IDE should notice the file changed and recompile. Seeing the syntax error quickly confirms Arduino really is recompiling the code and you really are...