defragster

That page references the thread where development of the bootloader chip was discussed (you did read that thread, right ?!?!?). The definitive method of distinguishing between T4.0, T4.1, & TMM can be found in <Post #200>. Hope that helps . . ...

@ctadlock: I don't know what "that guy" is that you refer to. You asked a question (how does the bootloader chip distinguish ??), and the answer (by the FLASH size) is actually provided in several different forms & in several different places...

Interesting 2021 @defragster reference post @kd5rxt-mark :) I've been wondering what to add as post #2 made the note. PJRC presenting similar info - on the bootloader page would be good. But doing a non-Clone DIY board requires a great deal of...

Enjoy your vacation and can't wait for April :)

Yup, but I have other plans for next week. Real fun should begin in April. ;)

Not just a great SerMon program for one or more Teensy's connected or any Teensy with Dual or Triple USB Serial This: https://forum.pjrc.com/index.php?threads/teensy-qt.27825/ tycommander_TYQT also recognizes other online USB devices in various...

Paul can confirm - but this blinking says the Device is not finding a Host. It should go to Solid Red with a good cable connected to a ready Host. Can confirm that a GOOD cable can go BAD - works one minute then no longer working and a fresh...

Can the Teensy Loader see it? That looks like the bootloader USB ID. The RED LED by USB goes on with button push?

Size of the flash memory indeed. If you use a 16MB flash it will think it's a Teensy Micromod.

Interesting view for something out for years (and still true) from the SparkFun page: More speed and power than you ever thought possible in a microcontroller. Will be cool if/when they come out with the new generation of support boards for...

In graphical form Really would have liked more detail around 6-7.5 seconds, but it's telling me that I have basically synthesized the sigmoidal function. Now I have to make it stop sooner. Too slow! But it's a start, and a very good one at that.

A good reference for what the USB Device to Host Serial rate can be is this sketch. It starts fast and then at some point UI will get behind the buffers as long as they can even keep up...

It get significantly better, so they did do something that improved it.

@Dogbone06 was quite involved with Sparkfun around 2 years ago due to reliability issues with the NXP BGA joints coming undone from the thin, flexible PCB of the MM. They did some rework to the HW I believe to try an minimize that issue.

Sorry Brian - all I can say is that I have been using a couple of the early batch on and off with out issue - must have got luck. Never tried running for more than an hour or so.

Yes, that's my hope... especially coding time! I'm not ready to think about any new products until Sparkfun has been shipping Teensy 4.0 and Teensy 4.1 for a while. We've been pouring a lot of work into this transition for the last few months...

Sounds good to me, hopefully it will give PJRC time to concentrate on the things you do best, like innovation and support, and maybe even some website and repo maintenance ;)

Of course you can. Back in the day graphical adventure games used to run on 8mhz machines, sometimes taking well over 10 clock cycles per instruction. A teensy 4 runs at 600mhz! It can execute 2 instructions per clock cycles I love seeing...

Do tell ... ???

Indeed, Sparkfun has done well with MicroMod PJRC developed with them and SFun has been good to order from for years. Will be nice for PJRC to get to focus on things other than parts ordering, building and shipping.

This makes a lot of sense. A trusted partner who deals with supply and manufacturing means more focus on the all-important software and support side (which is the key differentiator from random Arm MCU boards that utterly lack a solid software...

Congrats! I wondered when something like this would happen. Makes a lot of sense, since they already are making the MicroMod. Should leave you with some coding time, and potentially new products.

Wow, sound like a great move for you and Robin. I look forward to you being able to spend more time on moving the software side. Best of luck.

Not sure whether to be sad or not but know it will take a heck of lot of pressure/stress off you and Robin having to deal with supplier and manufacturing issues. Definitely should free up a lot of time etc. So going to say congratulations and...

We are excited to announce the expansion of our partnership with SparkFun Electronics to include the manufacturing of all Teensy products. Teensy 4.0, Teensy 4.1 and related accessories will now be manufactured by SparkFun in Colorado, USA...

You’ve received a lot of useful help and have expressed little gratitude. Hope you find your solution and give something back.

Frank, if you look at file cores\Teensy4\CrashReport.cpp, you will find the code shown below, which reads and interprets the bits of register SRC_SRSR. Bits 0-8 indicate the cause of reset. You can copy and modify this code for your own use. The...

Good luck. I looked to find more ingo and joined the group.io ... missed the right spot? New ke2eky and lots of directions and distractions ...

Solved my problem. Reinstalled IDE after a clean uninstall and put the Teensy in boot-loader mode. Waited for the serial port to show and was able to down load program.

The sketch p#2 was edited and tested here ... was it used and tested there? With what results? With USB type Serial is should upload and shows a fast 100ms Blink until Serial connects. When/If there is no blinking then something has connected the...

Seems the cable is working to allow upload. The standard BLINK programs do not issue, or respond to, any USB Serial activity either send or receive? Not clear what ideas need to be addressed? Here is a quick edit of SerialPassthrough {with...

Yes 3X, that posted somewhere some few dozen or hundred(s) back in this long thread

Seems in like with the application notes

Yes, processor notes show that writes are a couple times faster than reads

with 2-3 devices the number of messages/sec the Host can receive should be <edit> tested/observed as it is using scheduled packets on a shared connection to and from host.

@samm_flynn Have tried the USB_Host Serial some - not sure and don't recall how extensively. For 'normal use' (or a test to be performed) use the 'master' would attach USB_Host to a powered USB Hub. Any desired 'devices' would plug the device...

That is odd - seems it never really talked to the T_4.1 much of the dialog below is missing, and added odd notes - and it never did a 'flash'. I just opened this NEW T_4.1 that had bootloader 1.05 and was updated on first programming to 1.07 -...

The DB5 here has one GND above B0_00 and 6 below B0_13 - though none mixed in the string of the B0 and B1 pins

This https://github.com/tonton81/SPI_MSTransfer_T4 was made for T_3.6 usage worked wonders in that case where it offloaded data to a second Teensy for processing and feeding to a PC. It seems to have been updated for T_4. Assuming the 4 T_4's...

On why T4 and RTC coin cell batteries (CR2032, CR2012 etc) give us months but not >>3 months: is this a software bug / omission after all? Reading the many many register settings in this NXP 2023 Application note, and not getting many hits when...

if (file_unix_time < last_file_unix_time) { last_file_unix_time = file_unix_time; file_to_delete = entry.name(); Serial.printf("\r\nFile name %s %s\r\n", entry.name(), file_to_delete); } I think that...

Change HardwareSerial to HardwareSerialIMXRT.

Check this code by Frank B : https://github.com/FrankBoesing/T4_PowerButton It allows capturing the On/Off press (when ON of course) - and the switch to OFF can be ignored IIRC. I'm not sure how the On/Off works when unpowered with only VBat...

@VictorFS With VBAT voltage, If the On/Off triggers an OFF it will stay OFF until the ON sequence is completed - or the VBAT voltage goes away. It seems like the floating pin may have been triggered?

Correct ... Opps Eyes open now - and reading 'wfi' just before the "IT" in p##7.

The "wfi" opcode/instruction, because systick is a function of the ARM CPU and by default wfi causes the CPU clock to stop. So the systick counter will never reach its threshold and trigger the interrupt, unless the extra code has configured the...

What is the 'it' here? This? " asm volatile("wfi"); " ? That would stop it, unless the code (you wrote once?) to enable the sys_tick interrupt as a normal interrupt. delay() counts on normal advance of micros()?

I reckon its on line 42 - its the answer to life, the universe and everything. Apparently...

Good using that, it is 12+ times faster to read - than micros() that is under 40 cycles. Should ' isr_stats t1_stats; ' also be volatile? Watching ' t1_stats.count ' should always be incrementing evenly. If the interrupt ends up consuming too...

Excellent catch by @defragster !!