Search results

Thanks to Paul, Robin, and numerous posters here for their designs, coding, and support over the last 6 years. I have used Teensy 3.1, 3.2, 3.6, 4.0, and now 4.1 to successfully execute single-event effects testing of numerous digital devices in direct support of NASA flight programs and...

For anyone who stumbles across this thread, yes, it can be done. Not the right tool for the job necessarily, but it worked with the timing tweaked just right with nops.

This is going to sound crazy to anyone who knows enough to answer, but has anyone attempted to essentially bit-bang an NV-DDR3 interface or similar on a modern NAND device at the lowest speed modes? For background I have experience doing this with Teeny 3.x and 4.0 to older asynchronous flash...

I would be very curious in your results. I'll be at TAMU next week and might have a chance to run a Teensy in the K150 but TBD, it's low priority.

Small update since this thread got bumped. The T4.0 is my current controller for certain digital components that need radiation testing. I've been killing them off occasionally when used near, but not in, the beam line (at LBNL, not TAMU, but similar energies). I'm guessing the bootloader is...

It's been a couple years since I got everything working but you can definitely pull data into Python on Windows 10 at 10MB (yes bytes) per second from a T4. You'll need to scoop the data in large chunks and spend some time profiling your Python to find out where it slows down. Any real-time...

Great news about the USB. I'll check it out as soon as I can and see if the occasional stall has been fixed.

Just a followup note that the T4 ran great in a vacuum chamber at 600MHZ once it was installed on a PCB. The PCB had aluminum standoffs to mount on a large steel platform, and the holes for the standoffs were plated and tied to the PCB grouns. No thermal strap or active cooling, and it sat...

16 bits at once is going to suck, no doubt about it. For two 8-bit buses on T4 I made it work by reading a 32 bit register (GPIO6_PSR and GPIO7_PSR) and then scrambling it with a macro I can drop into my code that reorders the pins I'm using into a normal byte. This would never be fast if you...

I had to rewrite a lot of fast code that was using GPIOC_PDIR, GPIOD_PDOR etc from Teensy 3.6 when I moved to the 4.0. Using individual digitalreadfasts wasn't an option since I needed the fastest-possible reads in parallel. Unfortunately it's really a pain that there's not a full, in-orderbyte...

Understood. I have no complaints as it is right now. Certainly if I needed a fixed high-bandwidth solution an FPGA would be a more logical choice, with more headaches for me. I really appreciate the several-x increase in Teensy-to-PC throughput from 3.6 to 4.0. That pretty much matches my...

For many people it is, but even then, the program should still work without crashing. I, however, could easily generate 50MB/s of serial data to a PC, though I'm not able to get that on the USBHS implementation. I recall that I'm seeing around 7MB/s right now on T4. I use a Python GUI to log it...

How did I miss that? Apologies for the unnecessary question, but thanks to you and mjs513 for the very clear responses. I'll give it a test today.

Is there a straightforward way to adjust this at runtime rather than tinkering with startup.c?

To echo what Paul said, using either of those parts is not a trivial solder-at-home task. That .65mm pitch is going to be a pain in the butt to hand place, even if you have an oven. You'll never know for sure that you soldered it right even if it looks stuck in place, and without some electrical...

Essentially dumping binary data from an external device under test (a memory, ADC, etc) for post processing on a PC. I do a little bit of analysis in real time to check for errors but I need the full dataset recorded and don't have spare cycles for conpression.

I ran a Teensy 4 the other day with two 16' USB 2.0 active extension cables in series, along with a vacuum feedthru and a 5' micro-USB cable. No problem whatsoever. That said, using any device with multiple active USB extenders can be tricky since they act like a bunch of hubs in series. The...

There are USB Y-splitters for charging while also using data. For example, I have one to split my Amazon Fire Stick 4K's lone USB port, which is normally used for power only, so that it can also talk to a flash drive. You also find them on phones that use the lone USB port to, for example, drive...

You can always get a IMXRT eval board or any number of other Cortex-M boards if you want to play with the more traditional microcontroller dev environments and explore things like JTAG debugging. There are little Cortex-m4 boards with the bare essentials on a small breadboard footprint on Amazon...

I think the most adjacent parallel bits on any one port is six with this Teensy. You'll have to do some rearranging of your commands to send 7 or eight bit words, though it sounds like that should be doable for what your have in mind. The Teensy can also do parallel GPIO operations near thst...

FYI - In vacuum it took about five minutes for a Teensy 4 running a loop of floating point multiplication to reach 90C (per the internal tempmon) and shut itself down. It was straight of the box, without any headers installed, and hanging out in the open in a vacuum chamber, and running the...

Nope. Really wouldn't expect to with your heavy ion beam and its typical energies and ranges, and we keep the Teensy out of the beam line anyway. Some stray neutrons could maybe upset the Teensy but Ive never seen it. When we do proton testing it would be far more of an issue, but I haven't yet...

Thanks, defragster!

Ok, that would be ideal. I don't use the Arduino Serial Monitor except for occasional debugging, and I know the PC-side software can handle it. I collect data in one thread, process it in another, and run my GUI in a third, and right now it barely registers any CPU usage maxing out the 12mbps...

Paul, it looks like you've got a typo there. B1_00 is tied to 7 and 8 on your diagram.

Hi, I'm waiting for delivery of my first Teensy 4.0 as an eval. With prior models I've used USB Serial as my output stream to a host PC and accepted the ~10Mbps virtual COM port stream into a Python-based datalogging system. With the 4.0, I'd like to know what the best AND easiest way is to...

I'm sure I'm not the only one operating these in a vacuum chamber occasionally to control experiments, so the possibility of overheating is well-worth considering. With the 3.6 running OC'd at 240 MHz there was no issue, but I never checked the temperature, either. I wonder if 600 will be too...

Yes, especially with highly-scaled flash (planar flash from 2014 or 3D flash) it's pretty easy to do so. In fact they won't even operate error-free outside of the beam, so a heavy ion beam can easily turn a 0 into a 1. While we are characterizing all kinds of interesting effects in the error...

Funny I just came across this post -- we routinely use Teensy 3.2/3.6 (and soon 4) to operate devices being tested in the Texas A&M Cyclotron beamline (among several facilities we visit). They're convenient for us because they've got such a great combination of rapid development time, convenient...

Excellent! We do a lot of one-off prototyping and random digital component testing around here and the Teensy 3.1, 3.2, and 3.6 have been heavily used for these purposes. I am really looking forward to getting our 4's delivered. Question -- will I be able to do byte-sized GPIO operations with a...

THIS. Even if you can't write in an 8 or 16 bit mode and have to do some masking, I need the ability to write a whole port with a single GPIO register write (as in, a single bus cycle, so a custom function won't fly) if the 4.0 will replace my 3.2s and 3.6s at work. Realistically I want the...

I know this is an older post, but I may be able to help a bit. I have been doing what is basically high-speed bit-banging a parallel flash chip, with many of the same issues -- delayed input response necessitating NOPS that shouldn't theoretically be necessary between toggling RE# and reading...

Actually that's not a bad idea. Flip the headers and mount from below. Won't be able to see the led or reach the pushbutton easily but that's very minor. Thanks!

It's not that a tall object is in the way so much as we need line of sight from directly above the component that would be shadowed by the Teensy 3.6. I can't publicly post pictures of the board involved unfortunately.

Thank you both. I'll give it a shot then. It'd be nice to avoid re-spinning the boards I plug the Teensy into until our next planned revision.

I have some existing projects that use a Teensy 3.1/3.2, but could use the features (speed in particular) of the 3.6. Electrically I could drop in a 3.6 just fine I believe, but without redesigning the PCB it cannot physically fit without the SD slot overlapping another component (which I cannot...