As p#1 indicates - it is a weird process - but thought to see if breadcrumbs might show where the oddity came up.
First step seemed counting entry and exits - they were all balanced.
And wiping out factory weak...
regarding this: "However, after a few seconds, the code crashes."
> is that when there is or is not physical usable PSRAM chip? re: "run fine with or without PSRAM"
> will it crash in a few seconds when there is a...
Awesome - other posts link way farther back - so far back it didn't ring a bell until others found it - just linked to that one.
To work was pinMode used before and removed - or changed to using INPUT_DISABLE?
No code provided to confirm ...
This has come up before and again in past day - when pin hysteresis is enabled the midrange gets a sticky bias and that may be what is happening here.
If any pinMode() is used -...
There was a recent note regarding adding a capacitor - quick search found this older note: capacitors-best-option-for-removing-analog-sensor-noise
Not sure the recent post had more or better info - but it was in past...
Seems a new sketch for blinking was loaded to drop the speed to 24 MHz?
Any chance that sketch has something like:
while( !Serial ) {
//
}
That will cause this behavior where the program waits for USB to...
Understood - p#1 suggested USB and other things working and p#2 was to suggest USB isn't trivial code as Paul has noted it was a big dev task.
Pointing out there isn't a known boilerplate solution - unless the...
Looking at: ...\AppData\Local\Arduino15\packages\teensy\hardware\avr\1.58.1\boards.txt
It shows these lines that seem to match the indicated for compiling and linking commands in boards.txt (for all boards):
...
If programmed with simple BLINK (No USBHost activation) does anything still get hot? If no hot spots when no USBHost it might point to that switch chip being trashed - and self heating rather than working - and that...
Great news if the code builds/uploads and runs as expected. Until recent TeensyDuino update (1.59 Beta?) the use of LTO was not functional.
Seeing notes on results or modifications to the build line from that...
Followed that and see: #define LFS_VERSION 0x00020004
Here at line #25: github.com/lorol/LITTLEFS/blob/master/src/lfs.h
The integrated to ESP32 version of LittleFS seems to be using the same on media format/features...
Not sure about the chip and what could stress it beyond over voltage. AFAIK it is a switch that controls current flow on startup to conform to USB spec and prevent VIN from a surge that would brownout the Teensy host...
as for The Common Microcontroller Software Interface Standard (CMSIS) is a vendor-independent abstraction layer for microcontrollers that are based on Arm Cortex processors.
Web search shows:...
Install TeensyDuino in the IDE (paths below on Windows). This provides the gcc toolchain and all the needed header and processor startup code for void ResetHandler(void) that calls main().
See this path for IDE 1:...
LittleFS as included was customized to Teensy usage (hardware pin access interface to storage media) from a common source at some version ##.
Using the same source for one that supports ESP32 should find the storage...
Have used USB Host here direct and with powered hub - never on batteries and have not seen this on T_4.0 or T_4.1.
There is a chip onboard that switches the power pin on the USB Host and feeds directly from the...
Just did that to post and it gave build error so posted that ... Seems to have built and worked fine but some linkage to altered file location is missed and triggered 'error'.
So that should give info on sizes.
Run...
@PaulStoffregen - when build of sketch Export it seems the updated path may not be used at some point?
Did the Sketch/Export on Windows and got this that worked as expected - first time tried and it is in indicated...
Not saying mutex interaction can't cause trouble ... just that the by design Threads won't switch during normal interrupts that default to mid level PRI.
UART code is fed by interrupts which would be safe - but any...
Just looked - seems this is #ifndef __IMXRT1062__:
IntervalTimer context_timer;
...
/*
* Implementation strategy suggested by @tni in Teensy Forums; see
*...
Didn't check, but wondered what priority TeensyThreads uses for what is assumed an interrupt for task switching? If that were lower, then higher PRI interrupt code would be safe to complete and exit.
If not lower...
simple "int func()" here the other day was CrashReport'ing when it had no 'return intX;' - didn't see the build warning for far too long ...
Used the addr2line that was on the computer that used to work and it gave...
Either of these should work. From: ...\libraries\LittleFS\examples\Test_Integrity\QSPI\functions.ino
case 'F': // Low Level format
Serial.print( "\nFormatting Low Level:\n\t" );
lastTime = micros();...
Good to know. The Hack showed it wasn't as 'hoped' the same underlying buffer used for IP-based TCP.
Is there a solution to the p#12 lost/delayed TCP data? Or is that the nature of TCP that items need to be handled...
Seems like it should, Yes. Per the notes left above it might reduce overhead of TCP and quick testing shows no problem sending 28 bytes in 10us from one and received fine on another Teensy.
Seems the send might take...
Indeed forum search can be lame - when it doesn't work. Though with usable keywords - as in this case - it did find and narrow well enough.
I use BING and have the browser do site ref when it starts "PJRC" and it...
If the scanner was set up to use UDP? then using that would be an option. Seem that TCP messages still being used?
As for how to use the '.setReceiveQueueSize' - that just came up in a text search when I saw what the...
Using the UDP the default queueSize had to be increased that was with:
// UDP port.
EthernetUDP udp(32); // (##)-packet buffer allocate for incoming messages
Looking at:...
recalled and found this thread: pjrc.com/threads/68148-Teensy-4-x-RTC-battery-life?p=294269&viewfull=1#post294269
Search that worked was: RTC Battery Life
In IDE 2.1.0 w/TD 1.58.1 here Plugged a T_4.0 with a 64GB ADATA 'A2' card in the REV D Audio Card
Using unedited p#1 code it ran first time:
SD Card Test
------------
SD card is connected :-)
Card type is SDHC...
Quick guess: The passed pointer is saved at time of .addThread( ..., TEMP). So subsequent calls to blinkLed() are pointing to that space on the stack that was in use during setup().
Make " blinkParameters temp = {0,...
The out of the box Teens is running Blink code - assuming at default 600 MHz. Adding alternate code at 600 MHz not making any difference doesn't suggest the Teensy itself is the problem ... the next line says the PCB in...
Is it stalling because the ring buffer is full?
Is there a file write in another location needing?: !file_accel.isBusy()
Just with a quick glance maybe in logData() repeat on this while() there?
//If...
Lesson Learned: CHECK console output for WARNINGS!
- talked about UDP Chat example mod was failing ... called out to class member that expected 'int' return and func() had no return
>> Resulted in CrashReport !!!
And if the Flash were removed and the stored program area copied to a 'stored file' that would not be a complete solution.
The Teensy Loader wouldn't facilitate programming that to other Teensys? Unless that 'stored...
There were notes on a thread some time back about alternate extensions of the Single Button function. Not sure the suggestions touched on this.
If the Teensy is available to reach the prog Button, then the T_4.x...
Congratulations on getting a good build with that chip not seen tested yet. Good to know the bootloader chip can work with them and offer the extended temp range, or when needed fill in for the 600 MHz MCU with speed...
Yes, T_4.0 came out with 10x10 and Pin# silkscreen easy large type fit to the MCU. T_4.1's went 12x12 for extra I/O pins and those to on board PHY to MagJack and QSPI needed larger bga pitch to run the wires on Teensy...
Very cool they got tested to work. Not cheap - but perhaps available.
Those are smaller 10x10 size like on the T_4.0 instead of the 12x12 on the T_4.1?
Try this WDT @tonton81 designed/tested with the Teensy's 1062 in mind: github.com/tonton81/WDT_T4
Forum search should show development and use if the github examples are insufficient.
Never read much of the manual ... but there is a Low Power element to the MCU with some cute name. That element {in practice} is powered by the main power and runs RTC and maintains the On/Off state, as noted RTC...
bare T_4.1
105.5 mA : running some sketch
0.26 mA : seconds after holding On/Off to GND
Same T_4.1
135.5 mA : running a simple print time with busy calc'ing RND number between seconds after programming...
Desire is understood - not seen it called out as noted.
There is a low power section that controls the On/Off and it is AFAIK also related to the RTC section which is powered any time the unit has power.
The...
Not recalling having seen that as measured ... suppose it keeps the related RTC unit powered so will be some small current ... maybe my new cheap meter can measure that ...
Glad you are working again!
Got 91% isopropyl here - and after cleaning ... hairdryer there is used to help evaporate that and push out any fluid trapped under SD socket or other. Bake it in hand to the temp I can...
As long as power is maintained the prior CrashReport data is maintained in a small piece of RAM2/DMAMEM that is not cleared on Warm Restart.
You likely didn't add breadcrumbs either - but some 32 bit values are also...
Is there a check and Serial.print(CrashReport) in setup() with a wait for Serial when if(CrashReport) is found?
That is the first thing to check for a clue/guide.
Good eye Spencez - saw that too and wondered what was there. Other soldering looks nice on pins - not seeing any other odd splatter showing. But if it was working after soldering before then that shouldn't be trouble.
...
Check the indicated "PWM Resolution" section that lists the "Ideal" - that is where the math works best for adjustment for various bits of resolution. From that it was assumed the MAX would be that shown as suggested...
The table indicated in p#2 is best guess here, PaulStoffregen would know if otherwise.
The fastest expected for each device would seem to be that shown as ideal for the 2 bit resolution. Even that may not work for...
No doubt QNEthernet with @Shawn more active - been playing with parts here.
Since that was covered the next line was as far as I read. TeensyThreads is a very nice development - but with limited applications - or...
Seeing: #include <TeensyThreads.h>
Doesn't inspire confidence. Didn't read the code to understand usage - but interrupt task switching on a timer tick might be the problem if it affects code not designed for it and...
maybe 37500000 ?
See the section: PWM Resolution (Teensy LC, 3.0 - 3.6, 4.0, 4.1)
It seems to be dividing from a 150 MHz clock. The next MIN step above Zero will depend on the chosen resolution.
The Millis increment timer tick update works from an isr. When interrupts are disabled, or a same/higher priority interrupt prevents it from running then a timer tick can be missed and the clock will slip one ms at a...
Buffering from an _ISR() is not trivial - when there is another non _ISR() like loop() emptying the buffer.
This post by @PaulStoffregen points to one solution and the issues. That uses a circular buffer where the...
EEPROM READ and WRITE are uint8_t BYTE only:
uint8_t read( int idx ) { return EERef( idx ); }
void write( int idx, uint8_t val ) { (EERef( idx )) = val; }
Get and put are the alternate...
SD cards are not consistent in fast write and return times - low end is fast - but when the card gets data it may need to do housekeeping that can take over 100 ms.
An interrupt safe set of 'ping pong' buffers or...
So from a working display library example - adding only usage of the BUILTIN_SDCARD (none of the other devices) - the display stops working?
If sketch to that effect (starting with working Display example and...
Try a simple example from the 'ILI9488_t3' library perhaps? Make any needed adjustments for setup for the T_4.1.
Excluding all the other devices and libraries until the display works, confirming each wire if needed...
Yes, grass was getting ahead! Deck is 25 years old and parts half rusted away (note to self clean and repaint sooner than 25 years). Welder new to me and got the two needed brackets secured - one was off the other...
Noted in p#4 after skimming the manual that it shows either TCP or UDP. If you can accept/identify a missing scan packet, then that would be easier to see and test like the QNEthernet CHAT sample @shawn wrote. That's...
Common cause for this is in setup() some sort of: while( !Serial ){}
Not seeing the code or having any idea of what library or other is in use makes guessing beyond that tough ...
Very cool games you play @KurtE - reading when I get a chance. Finally got mower deck painted and running to finish that from 10 days ago and past time to start over ...
Was glad to see the found need and purpose...
Not clear if the issue is 1.58 or 1.59 as noted?
IDE 2 does not show LTO as an option for 1.58 so it was not corrected and incorporated. PIO may trigger it as an option - but not valid.
If this is just PIO and...
Ran into this again today?
@PaulStoffregen - is this an IDE 2 problem to report, or something specific to Teensy Serial Monitor holding the port open in IDE 2 even when the SerMon is clicked off?
IDE 1 does not do...
Missed this - there is a thread of a laser scanner sending 54,000 TCP distance reports a second - wondering if T_4.1 could capture them.
Using the QNEthernet library ... I measured under 10 us for the UDP chat...
@shawn of github.com/ssilverman/QNEthernet (or others) might have an idea of usable throughput speed for handling such a barrage of messages with a T_4.1.
There are three wired T_4.1's on the desk here - but not...
on phone I saw multipass unit? Couldn't read the details well ... phone said the download wasn't secure ... but read it anyhow.
Seems it gets an IP::PORT and just spews data UPD or TCP as selected?
150 Hz ... 150...
PJRC has a MASTER TEST jig that tests all that and more in some fashion - each Teensy visits it for a test and bootloader programming before it is allowed to sit in a PJRC package because it has to pass to get the...
Doesn't sound like a lot ... depends on the process and protocol - is the device just set to broadcast the data in how many messages or what type? Or it is queried some number of times per second to reply with the data?...
That is a significant difference! Does the code involved have any demand or measure for speed of execution? That is: is there any appearance the code has slowed or changed in any measurable way?
Looks like data grew 8K and code grew 15K with the change in Teensy toolset in the updated TD - that code growth caused use of another 32KB RAM1 chunk and the padding went from 8K to 25K bytes.
If the code shrunk 7K...
This post points to a manual probe test sketch:
https://forum.pjrc.com/threads/55735-ILI9488_t3-Support-for-the-ILI9488-on-T3-x-and-beyond?p=324323&viewfull=1#post324323
Puts pin pullup or pull down then carefully...
Fun stuff @KurtE! I keep watching - but still working on my mower deck as grass grows. Too much rust and too thin to weld beyond the reinforced important parts - now waiting for JB Weld to harden to paint.
Would be...
limited suggestions given it isn't English and not Windows ... the screenshots do show IDE 1.8.19 in use
On Windows downloading the IDE 1.8.## as a ZIP allows unzipping and using from a unique directory. It will...
The T_4.1 has a number of clocks independent of the main clock driving the CPU.
One was selected that gave the best overall range of needed values - but the granularity for fine tuning is determined by the clock...
Find latest posts