Search results

Hello everyone! This is going to be a bit of a lengthy post, because I want to give as much background and information as possible, for a suitable discussion. My problems are regarding the SPI modules 0 and 1. At first, I thought about splitting it up, but now it seems, they share the same...

How about you make your own extension to micros()? I did something like that at some point. In the main loop, I would check, whether the current ellapsed Micros is below the one in the previous loop, if so, increment 'the upper byte' #define microMax ((1<<32)-1))/1000000.0 uint32_t...

Maybe I am missing a point here, but why do you use a voltage divider on the anode of the shunt reference? As far as I remember there should be resistor in series with the anode, where you also get the desired voltage. The resistor should be chosen to supply the required current to both the load...

Some of the functions you mentioned (like RX1, TX1) can be mapped to different pins. Every pin on the Teensy is a seperate pin on the MIMXRT1062. So no, pins 0 and pin 52 are not physically connected

16 MHz might be enough too, but I need to send >1.5 MByte/sec. I just tried something. Additional to your suggestion, of pulling the dis-/enable out of the single write call, I pulled "port->CTRL |= LPUART_CTRL_TIE;" out of there too. Its enough to enable the transmit interrupt once after all...

You are right, I have to see wether or not it is usefull. Like I said I could use it to start other communications while serial is busy. It might be a stupid question, but why is UART interrupt-driven in the first place?

That looks good! It sounds like thats about the idea I had in my head :D I will try that myself later. But for some real-talk now: does it really change anything? It seems the interrupts themself consume a lot of time, otherwise they would'nt all occur during the write() call, right? When I...

Try to measure on the Teensy pins directly. I recently had similiar issues that I could trace down to a very bad breadboard and relatively high contact resistances.

Thanks for your fast response! As you can see in my code, I already use availabeforwrite(), and it shows the whole buffer is empty prior calling write(), so thats no issue. I agree, that arduino is most likely not correct on that regard. It is clear to me, that write() gets interrupted by the...

Serial.write not working as expected (for me) I got an unusual problem with a seemingly blocking call to write() while using Serial2 with 20MHz I have put together a minimum working example to show my problem. Futher down are several results shown, 20MHz, 16MHz and a comparision between 6MHz...

Ah, okay, that makes sense! I did not think about the bootloader checking the flash memory first.

Thank you very much for all this information! The specific pins are exactly the part that made me doubt that it is going so easy. From what I have seen on the schematics of the Teensy 4.1, it uses the FlexSPI2 module to access the flash, is that right? The significant difference between RT1064...

As the title of this thread describes my question so well, I won't open another one with a similar title and just append this one. I was looking for information about the replacement of the RT1062 by an RT1064 on a Teensy project. From what I have seen in the migration documentation (and if I...