Search results

Could noise on the USB line cause the fault on the teensy? I am getting USB port saying over voltage and turning the port off at the same time as this happens.

It powers: DAC (MCP47F) ~ 380uA Couple of LEDs ~ 3mA Half of a buffer (TXS0104EPWR) ~ 10uA RS485 RX (MAX3096CSE+) 2.4mA So lets say 15mA if we are super conservative? A decouple cap for each IC (I used 2x 10uF and 1x 1uF).

Thanks for the information previously. I replaced the part and it has since gone twice more. Any thoughts on what could be potentially causing this? My first idea was to use something like (https://uk.rs-online.com/web/p/voltage-regulators/1005939) to create the 3v3 rail. The idea that a bigger...

Mine is an 8 pin IC with "GDT". I thought it would be the NCV8186 but the datasheet says that is "GAX"? Or am I reading that wrong? Edit: After spending more than 5s looking and scrolling down I can see GDT is the 3v3 non-discharging variant. Now I know all this I am still looking for possible...

It’s the 3.3 V regulator on the teensy 4.1. I am not sure which specific part I have on mine, I believe they have been changed twice?

I am trying to trouble shoot an issue with U4 going short on a few teensy boards I have. The challenge is mostly that of the 30 boards I am using I have only had U4 go short on one setup. I want to think it is something to do with upstream of the USB cable. If this is the case what would I be...

Is it possible to setup an interrupt based on encoder value?

"reensid" TeensyID? https://github.com/sstaub/TeensyID it is the same code I am compilling for both systems. Just checked at the versions of TeensyID are 1.3.3 on both IDE's. Not sure why I didn't immediately try it but I rolled the teensy version back to the last non-beta in 2.0 and that...

1.8.16 and 1.57 works fine, same code on 2.0 boot loops, verbose output below. Using board 'teensy41' from platform in folder: C:\Users\C\AppData\Local\Arduino15\packages\teensy\hardware\avr\1.58.0-beta2 Using core 'teensy4' from platform in folder...

Just tried the new 2.0 IDE with my previous firmware and it seems to boot loop the Teensy now. Now firmware changes except for switching to the 2.0 IDE? (T4.1, 800mhz, fastest compilation)

Apologies for not being able to search very effectively! Looks promising.

I have some code that I am looking to optimise to reduce delays in interrupts and make sure some parts of the code runs as fast as possible. What I would like to do is compile my C code and interrogate the resulting ASM code to see what is going on and if I can change/increase the speed of...

Apologies tonton81, I can try that out but when I thought it was a hardware issue I snipped off the shifter and soldered on a 74HC541. I don't have the issue anymore, so my shifter was part to blame (like this https://www.sparkfun.com/products/12009 - for reference this is a terrible design for...

I haven't had any serial dropping or other issues that could identify the power being an issue?

Thanks for confirming. It seems to be the logic level shifters I had in my circuit caused the issue. But I don’t understand how hardware can change the teensy operation?

EDIT: It seems these issues are something to do with the hardware I am using. For some reason when plugged in the teensy only sends half the packets it needs to. Without changing the program and removing the hardware it send the full number of packets. This is true for MODE0 or MODE2. What...

Thanks KurtE, not sure why I didn't just test it out but you are right. This perfect I have all the pins I need now!

Title sums its up, I need one more pin and I have an SPi device that only needs to be commanded. Therefore my MISO pin is unused but I believe when I activate SPI it is overridden to be an input. With normal arduino this is a microcontroller level function but I wonder if it is different on the...

I actually had in mind a similar question, I would imagine a completely different industry but I have much your same questions specifically the legal side so interested in watching this thread.

Is there a way to debug the code running on the teensy 4.0 line by line, similar to STM Cube? I really like the teensy but I am leaning to STM for my next project mostly because of the IDE over Arduino.

I believe, and I am sure I will be corrected. They are the registers of the processors not related to teensyduino or arduino but just the architecture. You can find details of them in the hardware datasheet: https://www.pjrc.com/teensy/K66P144M180SF5RMV2.pdf Likely the code would only work for...

Thank you Paul, I just tested it out on my setup and it works exactly how I hoped it would! I admit I am disappointed I could not work it out for myself, but I am very grateful you took the time to help me! Really solves my timing issues, I can put off using a FPGA another few years!

So I am a little defeated by all this DMA PDB DAC stuff. I wanted to give it one more try before I give up and introduce new hardware. The chunk of code I was looking to replace with DMA is this: void jetNozzle() { //jets with the currently selected nozzle //should be called by all...

Thank you frank... but is that related to my question? If so I understand even less than I expected.

Thank you very much. Will look into those manuals and that example. I Knew I had seen a more extensive manual before but couldn’t find it.

I have been using the T3.6 in a project I created that runs a piezo device that responds to analog voltage. I have the teensy connected to a board that has amplification and shift registers to link the 2 DAC channels to 16 outputs. Until now the Teensy only had one time critical activity...