Search results

MarkT, Aduen, if the +5 input is off, and only the RTC system is powered, do the pin states matter at all? Assumed the pin drivers get their power from a main supply, right?

Yes, posted on another thread, sorry I didn't realize this was left hanging. I had a bad socket for the teensy that was disconnecting the +5 input in a tricky way. Trick being, if I externally shut off the +5 and turned it back on, the pin was reconnected! (thermal latch effect at the bad...

Hi KurtE and friends, I've been using ILI9341_t3n library on T3.2's with no troubles for some years, thanks! Currently using it with T4.1's and it's fine and dandy. I've an odd but rare problem with it going blank white. One thing I do is periodically check of the LCD driver and controller...

Thanks,

I had an elusive problem show up after months of testing on three units in parallel. As luck would have it, only at a customer (Beta) test site. CPU halting, letting go of IO pins, and not resetting despite using watchdog timer(s). Power supplies were up. Log of power supplies (by Teensy...

Hardware issue found for my catatonic T4.1 problem: bad choice of IC sockets! The +5V power pin (highest current and corner pin) was just on the edge of disconnecting. Could be caused by pushing sideways on the Teensy, or low humidity. Interestingly, once the +5 input dropped enough to shut down...

Aah thanks.

It's actually 68 bytes max emulated EEPROM in one sector on T4.1 as I'm doing it, but I don't want to unleash a not-long-tested idea on anyone. So I'll give you only a little code. Basically (if I remember correctly), the T4 EEPROM emulation scatters write addresses around on FLASH to do...

Yes, sorry, did mention it elsewhere but got no answers, probably should have started it as a brand new thread. No apparent hardware damage, comes back all good after power cycling. In any event I'm convinced the external watchdog is easier than solving it in T4 setup - already working in 1...

It stops running software - not even a WDT interrupt routine with a fast pin write - and releases drive to all digital I/O pins, which go into keeper state. Teensy's 3.3V power output is still up. I suspect it's caused by weak ESD zaps to -> SPI port to LCD controller.

The problems with badly used WDT's are as old as microcontrollers, many folks have experience doing it well. This is a shift of subject, but I've got T4.1's going catatonic - possibly only when I use a lockable version in secure mode (SPI bus glitch=security violation?). I've exhausted every...

Nice! Thanks. This is helpful - just been turning on WDT's lately. I reduce the wait damage (for other reasons) by arranging to only do one flash sector erase in a single write. I do that by re-addressing all my EEPROM writes to keep them in a single actual sector at any one (small block of...

Paul, thanks, The similar question I'm trying to answer is, can the T4 perform the equivalent of a power-on reset from one of the IMXRT1060's built-in WDT's without running a wire out and back in, so to speak? I'm not asking if any outside circuitry gets reset, only the T4. Because a restart...

[followup] One thing I've learned, which wasn't clear from the docs, is that you can run multiple WDT's in parallel. Running WDT1 and WDT3 simultaneously hasn't brought it out of the zapped state though. Also, though the manual seems to say the EWM watchdog timer can reset the system...

Hi, Working with tonton81's Watchdog_t4 library. I have a system that can stop running when it gets mild ESD hits (this application actually generates ESD internally...) No hardware damage, just stops, restarts only with a power cycle. Before I fix the hardware protection I want to fix the...

Yes, that's exactly what I'd like to do, but there's no warning from the Arduino IDE. One could manually shut down your software, say through the serial terminal, but leaving the Teensy power on, every time you punch for a new build while developing code. But that would be slower and more...

Well, it's nothing to do with external circuitry, the output bit locks high (or probably low sometimes). This is for instance pin 37 on this T4.1. The pin was set to an output, const int PINAME = 37; pinMode(PINAME, OUTPUT); Then is subsequently updated often to a PWM value with ...

Aaah, thanks jmarsh, I'll hunt for that. Editing core teensyduino... shudder... Uncharted territory for me.

When rebuilding/reloading T4.1 software on the Arduino IDE, the CPU is locked, serial terminal shows greyed out, fine. But the PWM outputs stop PWMing, which causes an annoyance when they stop at 1 (full throttle! Damn the torpedoes!) I assumed these are hardware PWMs (using analogWrite(...))...

I stopped working on getting out of SNVS mode and settled for the 27 uA or so standby consumption. If I read the data BOOK correctly, the only way to wake up from SNVS is to use a timer. But I'd need that to be once or twice a second so as to not excessively delay power-on startup. Then first...

Yes, the processor never sees 3.6 V, there's >0.5V through the diode on the Teensy board.

Awesome. Works instantly, then just imported it as a header file and drew it the slow way (probably there's a faster image writer function somewhere) #include "logo250x46.h" void drawImage(int16_t x, int16_t y) { for (int16_t j = 0; j < 46; j++) { for (int16_t i = 0; i < 250; i++) {...

Thanks, so if I make sure that all code I'm using fits in (and is running from) RAM1, then I am safe to write a private version of the EEPROM write code? I'm pretty much only running things that are performance critical on this one. Of course it would get all the testingz, but preferably only...

Thanks Paul for the first answer. I've been testing and so far it's faster than the fast end of the spec, if I read the address scattering code right. I can get it to go away for a good chunk of a second for multiple sector erases, but nothing like the spec. But I shouldn't trust that for the...

The T4 and 4.1's EEPROM emulation using Flash ROM has to sometimes erase a sector. This takes 0.045 to 0.400 seconds to do and the code is completely blocking- interrupts are disabled during this time. (eeprom.c in \hardware\teensy\avr\cores\teensy4, code below.) I don't see what would...

From a couple of CR2032 battery data sheets, it looks like they run 3.0V or less most of their life, but for a bit at the beginning. Dropping voltage shouldn't be needed. You could measure the current consumption using a good multimeter in series with the battery. Maybe one diode drop might...

The processor manual has this temptation to try for wakeup on pin (state? change?): 11.4.1 SW_MUX_CTL_PAD_WAKEUP SW MUX Control Register (IOMUXC_SNVS_SW_MUX_CTL_PAD_WAKEUP) MUX_MODE : MUX Mode Select Field. Select 1 of 2 iomux modes to be used for pad: WAKEUP. Note: Some functions are...

Yep - just a thing to watch out for, and a solution. Rechargeable lithiums also go to 4V or so while charging, so that's something to regulate down for longest battery life. The big surprise is that the consumption goes UP when you turn the power on, if you supply at least close to 3.3V Batt...

Hi ChrisR, I've just started experimenting with SNVS mode also. See my piping up on https://forum.pjrc.com/index.php?threads/beware-t4x-rtc-power-consumption.64216/ for more infoz. Note my mention there that a battery much over 3V will be discharged also, even faster, when the power is ON (!)...

More on getting the standby (xtal RTC only) current down, and a question (anybody listening to this thread? :) Currently I'm using the same large 3.6V lithium (Tadrian TL-4902 non-rechargeable) battery, but with two silicon diode drops in series (MMBD4148SE dual diode). This drops the ON...

One thing I notice is that the T4.1 schematic shows two Shottkey diodes to supply the standby power, and if the 5V power in is on, this will pick up the current if the battery voltage is below ~3.1V. So, if I put a silicon diode voltage drop (1N4007) in series with my battery, what happens...

More on this problem, I'm running a T4.1 with a largish 3.6V lithium battery into the Vbat pin. I was surprised to see an immediate voltage drop on the battery when turning on the 5V power, and corresponding battery voltage increase with the power off. Current meter confirms this: Power on the...

Can do 17 Ch's ! Aah, so that sounds like you've written to SD on a T3.6, thanks. I'll take that for gospel until I learn otherwise, and I like the margin for error: about 3:1 bandwidth. I'll have to assume the SD card library and the audio library play well together interrupt/real-time wise...

Andre, Did you resolve this (T3.6 SD card/cs42448 potential conflict on SPI pins)? I'm spooling up to maybe build that combo. - Philip

OK, tried it, Audacity can do that! One detail is that you have to select Use Custom Mix in import/export preferences or it will mix down to stereo when exporting to multichannel RAW. Thanks. Now to answer the other questions (reliable raw write rate to SD on Teensy? Paul's Oshpark CS42448...

Thanks for the suggestion. The next question about that is, is a 5-channel RAW format understood by Audacity or some other free/cheap sound editor.

Requirement reduced to just five channels. Anybody?

Hi all. A search of the forum didn't turn up a clear answer to this: How many 44.1kHz 16b audio channels can one Teensy simultaneously record to SD card, *without dropouts*? Working on donating to an art project and need to record OR play back 6 channels simultaneously. (Not both...

Your first font choices are perfect ones to start with. I'm excited! Instant snaz upgrade!

Solved, thanks nox771. i2c_t3 works, no lockup. So I did more homework after seeing the related thread (https://forum.pjrc.com/threads/21680-New-I2C-library-for-Teensy3) from nox771. Loaded up i2c_t3 library from github, edited Adafruit ft6206 and mcp23008 libraries to include i2c_t3.h...

Not hardware problem. I'm not sure who you are replying to, headroom. Me, I'm not having a noise problem now, that was fixed long ago. But noise did test the driver and showed that it did not time out on an I2C comm fail. That's a software problem. I had the same issue recently due to a...

Wire I2C driver lockup reproduction procedure Allright, I ran into this I2C driver lockup-instead-of-timeout problem again in another context and I have a reproduction procedure for you to try. 1. Set up a program talking to an external I2C device, such as an MCP23008. Constantly looping...

We are doing an embedded control panel application to operate a Teensy 3.1 device over the USB serial port. It's built on Windows embedded. The windows 7 teensy driver does not install properly, with an error message saying that it's a problem with the .inf file. We don't need the loader...

OK thanks, I will see if I can make it happen by getting rid of pull-ups entirely in a low-noise situation, or by feeding a minor bit of noise in. Since raising the pull-up current fixed it I suspect it wasn't anything of damaging levels. But it's on me to find a way to reproduce it.

No need to test anything for me, I'm after the driver bug even though I have the hardware problem fixed. Really I'm hoping someone familiar with the Wire driver code itself knows how it could lock up and might pipe in. Thanks!

In a nasty EMI environment, I've found my T3.1 based gadget needed stronger pull-up resistors on its I2C bus. Turns out the I2C driver locked up regularly, resulting in the system being pulled out by the watch dog timer. The application has a 2kW switching power supply and a 1kW VHF RF source...

Thanks, Yeah, but, The pinout diagram never mentions the GPI/O functions of each pin. And I'm lost getting through the Freescale MK20DX256 documentation. I haz a need for execution speed on this bit, hence the analog sampling option is lame-ish. And I am sucessfully using A4 and A5 as an I2C...

Hi, I'd like to digitally read two of the inner pins on the T3.1 board, which I believe are on port C. I can read them as analog inputs (A10, A11), but not digitally. Is this not possible, or did I do something wrong, or are there more config bits to flip? -Phil const int K2A = 35; //I/O...

ILI9341_t3: YFY! It works. Speeding up the LCD text draws was my next task and Boom! It's done with no effort with Paul's library. Thanks, anyone who contributed. I'm using a T3 with the 2.3" color LCD over SPI. It was sad how slow it ran with the Adafruit driver, about 1/3 second to...