Latest activity

The set up is: Teensy4.1 Adafruit bmp388 over I2C openSUSE Leap 15.3 Arduino 1.8.19 teensyduino 1.59 I got a interestring result with the function micros() in combination with one/two do while loops. The code with OneLoop measures and...

Looks like the method: int vprintf(const char *format, va_list ap) { return vdprintf((int)this, format, ap); } Was added last year (May 2023) Wonder if they should have not put the implementation of it within print.h but instead into print.cpp...

You're right... the mono code uses 9 blocks while the stereo one uses 10 (maximum). So I increased the audio memory to 11, and it works! Then, I started to become crazy because increasing the audio memory is the first thing I tried. So, I did a...

They're using LCDIF (and PXP) to output to the display... which is pretty tricky considering the amount of pins shared between CSI and LCDIF... but the main note is they're explicitly not using the eDMA module which is where the slowdown seems to...

Try using AudioMemoryUsage() to monitor how many of the 10 audio memory blocks are used up. Or use AudioMemoryUsageMax() to check whether you have at any point used up all the memory. My guess, admittedly from only a quick glace at your code, is...

I wonder if there are any hints on this on how they use SDRAM with CSI in the 1050 document https://www.nxp.com/docs/en/application-note/AN12110.pdf

I find it odd that SDRAM is not working well with FlexIO & DMA.. On the original version of the devboard, @Dogbone06 has just standard T4.1 PSRAM, and I was able to use a frame buffer in there with my Micromod 8080 library without any issues...

That was an interesting forum post especially if you read all the way through it. The fix they recommended was basically to change both BCMRX registers to 0x81...

LCDIF, CSI, and PXP all have their own masters. Their priorities (against each other) are controlled by the SIM_MAIN NIC registers. The documentation hints that LCDIF has a bunch of cache memory tucked away inside of it, that isn't directly...

That was an interesting forum post especially if you read all the way through it. The fix they recommended was basically to change both BCMRX registers to 0x81...

@mjs513, looks interesting. Wonder what the differences are from the DMA and non-dma? Other than the obvious. Like when we are not using DMA operation, the new data is written to the cache, and only later, when necessary, it flushes it out to...

I find it odd that SDRAM is not working well with FlexIO & DMA.. On the original version of the devboard, @Dogbone06 has just standard T4.1 PSRAM, and I was able to use a frame buffer in there with my Micromod 8080 library without any issues...

We finally have DMA working properly on the MicroMod and presumably the SDRAM Dev Board (not tested yet). My MicroMod quit while testing the 8080 mode for the ER-TFTM101-1 display. Had to reposition the MCU board in the connector. It's working...

Thanks for the quick response. I can see the code is now using the right (?) library, but the error is still the same: C:\Users\*****\AppData\Local\Arduino15\packages\teensy\hardware\avr\1.59.0\libraries\ShiftPWM\CShiftPWM.cpp: In destructor...

Hello Paul, thanks for taking the time to answer my question. I have reviewed all the libraries and their respective licenses. For those under the MIT license, everything seems straightforward. However, with libraries licensed under LGPL 2.1...

Here is the mnimal code (using the original i2s objects) reproducing the problem: #include <Audio.h> #include <arm_const_structs.h> #include <utility/imxrt_hw.h> #include <SD.h> #include <SPI.h> File dataFile; const int...

Switching back from platform teensy 5.0.0 to older platform with: platform = teensy@4.18.0 does the trick. But why does teensy 5.0.0 rise this problem?

Thanks for reminding me about that example. I had already looked at it could not work out what it actually did! I will go back to and rejig it for platformio.

TLDR: https://mongoose.ws/wizard/ This is more like a framework announcement rather than a question. Some explanation: this is a visual tool for building networking functionality with no experience in network and frontend programming. The tool...

I find it odd that SDRAM is not working well with FlexIO & DMA.. On the original version of the devboard, @Dogbone06 has just standard T4.1 PSRAM, and I was able to use a frame buffer in there with my Micromod 8080 library without any issues...

Hi, I get this message building my project under PlatformIO for Teensy3.6 after some package updates. Project worked before but now build shows: .platformio\packages\framework-arduinoteensy\cores\teensy3/Print.h:118:62: error: 'vdprintf' was not...

Update regarding this: Further review of the board showed some left over flux on pins 5 & 6 of the BAS40-05V. (Potentially shorting these pins out) Measuring the button cell battery attached it is dead (<1v but cannot sustain any load)...

We finally have DMA working properly on the MicroMod and presumably the SDRAM Dev Board (not tested yet). My MicroMod quit while testing the 8080 mode for the ER-TFTM101-1 display. Had to reposition the MCU board in the connector. It's working...

vice versa also I tried. but it is not working can anyone help me in this.

We finally have DMA working properly on the MicroMod and presumably the SDRAM Dev Board (not tested yet). My MicroMod quit while testing the 8080 mode for the ER-TFTM101-1 display. Had to reposition the MCU board in the connector. It's working...

We finally have DMA working properly on the MicroMod and presumably the SDRAM Dev Board (not tested yet). My MicroMod quit while testing the 8080 mode for the ER-TFTM101-1 display. Had to reposition the MCU board in the connector. It's working...

Sounds a bit like the same thing I saw when I tried using SDRAM with FlexIO VGA output, using DMA to feed the shifter registers - DMA was too slow to keep up with the higher pixel clocks. Yet somehow the eLCDIF module (which has its own bus...

@mjs513, looks interesting. Wonder what the differences are from the DMA and non-dma? Other than the obvious. Like when we are not using DMA operation, the new data is written to the cache, and only later, when necessary, it flushes it out to...

Once I figure out how to do all that in Arduino code, I'll be sure to keep that little gotcha in mind 😅 I might end up using both the GPTs and quad timers, ideally I'd like to have eight different trigger pulses, but with each GPT having only...

Ok folks got the SDRAM adapter board setup and running with a OV5640 @VGA with a few caveats. When I first hooked it up the camera clock is was set at 10Mhz which works nicely with a regular Micromod. However, with SDRAM and using SDRAM...

Ok folks got the SDRAM adapter board setup and running with a OV5640 @VGA with a few caveats. When I first hooked it up the camera clock is was set at 10Mhz which works nicely with a regular Micromod. However, with SDRAM and using SDRAM...

The quad timers can also run off an external signal, up to a frequency of bus clock / 2 (typically 75MHz). They're 16-bits, but multiple timers can be cascaded to get 32-bits.

Seems like its using the "wrong" library. (Temporarily?) get rid of C:\Users\*****\Documents\Arduino\libraries\ShiftPWM and retry the build

To configure the input pins, you'll need to write to the mux registers and also the select input registers. IOMUXC_SW_MUX_CTL_PAD_GPIO_AD_B1_02 IOMUXC_SW_MUX_CTL_PAD_GPIO_AD_B1_03 IOMUXC_SW_MUX_CTL_PAD_GPIO_AD_B1_04...

One small gotcha... before you access any of the GPT2 registers, enable its clocks by setting the CCM_CCGR0_GPT2_BUS and CCM_CCGR0_GPT2_SERIAL bits in the CCM registers.

It indeed appears that they will do exactly what I'm looking for. That is a tremendously helpful feature. I was just about to start searching for this information. Thank you for the quick, very helpful answer Paul. Now I need to do some...

Hi, it was the same issue as stated by others , i didnt know wich page was everyone reffering to Thanks for your reply! :)

Hi Paul , yes i figured out wich page where you referring , everything is functioning now Thanks

Some pin mapping info which might help: GPT2_CLK is on pin 14 (AD_B1_02 mux = ALT8) GPT2_CAPTURE1 is on pin 15 (AD_B1_03 mux = ALT8) GPT2_CAPTURE2 is on pin 40 (AD_B1_04 mux = ALT8) - Teensy 4.1 only

Quick answers I believe the GPT timers might able to do this. In the reference manual, see Figure 52-2 on page 3015, and section 52.3.1 on page 3016. The GPT timers are also 32 bits wide, which is much simpler than dealing with only 16 bits...

Thanks so much for the quick reply, Paul. I'm embarrassed by the first drawing I posted, so I made a new and accurate one below. Both power supplies are connected to mains earth, but I'll double check all the connections to make sure they're ok.

I don't see any connection in this diagram between Teensy and the dual motor driver. Assuming there is indeed a connection for Teensy to control the motors, check the GND wire. Perhaps GND is not properly connected between them? And maybe that...

Can any of the timers within the Teensy 4.1 be incremented using an external clock signal, rather than the internal oscillator clock? My goal is to have a timer running off an external 10MHz square wave signal. I could then have a pulse on a...

Hello! I've found this forum incredibly helpful in the past, but this is my first time reaching out with a question. I'm working on a project that seems like it should be simple, but I'm being deviled by a problem that I think is electrical...

I'm trying to use the ShiftPWM library to control 13 LEDs with 795 shift registers. I'm pretty sure I had this working a few months ago, so I suspect either I've done something wrong or an update to something has broken it. The compile error I...

I'm looking for suggests on how to proceed here: A few seconds after boot I may find an I2C device connected to the Teensy 4.0 and it would be great if I could add a new device to the USB descriptors. The device is a variant of a HID device - a...

Still looking for help with this ... perhaps if I re-word: To re-use my proven code with lots of "Wire." entries on Wire2 on my T3.6 I am using: #define Wire Wire2 but only in the RTC and EEPROM tabs, leaving the SSD1306 OLED on Wire0 This is...

I slightly updated @mjs513 copy of it he sent recently. In that I filled in more information about the newer pins I Hid most of the columns, which shows: The ones in Yellow are the ones we do not have. 3 are critical for CSI (D3-D5) The...

This example perhaps? Paul

Connecting a motor direct to pin 8 of the Teensy? That doesn't sound safe, back EMF, burn out the pin through overcurrent, ESD through handling the motor - several ways this could be bad news.