Paul - this millis() issues on certain set_arm_clock transitions. See: pjrc.com/threads/58053-T4-set_arm_clock-and-micros()
Title says micros() but that is because it tracks on millis() clocking.
Type: Posts; User: defragster
Paul - this millis() issues on certain set_arm_clock transitions. See: pjrc.com/threads/58053-T4-set_arm_clock-and-micros()
Title says micros() but that is because it tracks on millis() clocking.
Paul - TeensyDuino 1.49 fixable? Certain passes through set_arm_clock() with clock speed transition depending on current settings leave the clocking for millis() not properly set.
Post #2 the...
That isn't part of std WIRE lib it seems - so adding may have complications.
Looking at : \hardware\teensy\avr\libraries\i2c_t3 included in TD it does note non-blocking version details.
For...
This came to mind: github.com/ftrias/TeensyThreads/pull/21
Also note :: This branch [ PaulStoffregen/TeensyThreads {Latest commit on Aug 22, 2017} ] is 19 commits behind ftrias:master.
I saw github CORES has first pass of T4 USB Keyboard checked in followed by mouse and joystick - likely out with Beta 2 when it is ready:
Add USB keyboard for Teensy 4.0
Add USB mouse &...
The T4 or T_3.6 SDIO interface to an SD card can write perhaps 10 MB per second - depending on the driver library used. Also 5-15 MB/sec writes to disk or flash drive are possible with USB Host...
The info on the part in use would be needed to give a complete answer.
The ones used by PJRC are on the website and are a Electret Condenser Microphone. Unless the MEMS mic in use presents the...
opps - that explains my thinking it wasn't compiling the right code - I saw the IMXRT file which was obvious - but ignored the WireKinetis file :(
at a glance it looks like that should prevent the compiler from saying that - assuming it is called with no (params)? - confirm in verbose console output it is building with the sources from that...
That sounds great Paul. Other simple test done here looked good and reliable - even if it was not built for speed - it was reliable. And as noted dumping some @luni_LATIN text quickly pushed to 10...
IDE 1.8.9 builds much faster AFAIK - 1.8.10 does mega rebuild on the tiniest change on Audio sketch.
I did use you inbuilt firmware upload - same speed 4.86? Seems to go to Panic flash after 1 iteration with send of 0.02MB?
It finds a single T4 nicely on hub or left front port - but not on right...
@luni - Nice. I took a quick look 'software' - 'firmware' - looks like usable files are there somewhere for both CPU's :) I grabbed the first line of the latin text 930+ bytes and threw that in the...
Indeed, sounds like a Win issue - the few cmdline t_sermon dumps were garbage free output to file - it was good to see that finally.
Security:: for sure some of the dumps of garbage could have...
Indeed Win CMD output is slow - that is why I was doing the 1,000 batches before printing even one buffer. Though doing 10K batches did not run any faster - likely the minimal code overhead to clean...
Doing this :: T:\arduino_1.8.10\hardware\tools>teensy_serialmon.exe usb:0/140000/0/1 > seeme.txt
The created file this way doesn't seem to show the printed corrupt messages in a couple of tries. ...
Odd things noted above - using sketch with no delays posted below.
Not sure if any of this is T4 related - but all make at this this Win_10 PC an unreliable test bed::
> I see garbage spew on...
@Paul - modified prior PC app to read 512 bytes in groups of 1,000 times - and sends each buffer back to the T4, but only prints the last buffer of the 1,000. One sign of trouble with that garbage...
Indeed it is that thread. That post preceded the notes on T4 memory pjrc.com/store/teensy40.html
And above was right > what speed is RAM2 that it needs to be cached?
There is a memory thread - search forum for imxrt-size - details there may be helpful, also that exe imxrt-size will spit out info on what is allocated where at compile time. I posted an output of...
OCRAM is all open in the TD 1.48 - for pending faster USB in TD 1.49 it looks like 12 KB is allocated to USB buffers for DMA access. When that is complete USB will be optional and turning it off...
The code in the link above :: pjrc.com/threads/48450-uNav-AHRS?p=168449&viewfull=1#post168449
Puts the : attachInterrupt(digitalPinToInterrupt(GPS_SRX), GPS_serialrx_isr, RISING); - Directly on...
Setting up the 'Rx' as a watch pin served the desired purpose of seeing the Start of data bits in that case, so no need for low level UART operation was needed in that code. And with only 5 or 10...
That is more than a simple blink ... so added details might be helpful. Also interesting if the same process using the standard IDE install with known TeensyDuino can reproduce - it may be T4 or...
Paul - minor update ... Interedted to hear if you try this sketch and see similar or different behavior.
I finally stopped the tSerMon - running fine - [ except no send after the first few seconds...
Cool. Seeing signs of good throughput as noted above - but requires the indicated delay()'s in some fashion to have my Win10 PC keep running.
Right now with the last posted 7000/700 I have two...
Modified the output to show a run time time measure in minutes:
Moved the two delay times to #define at the top - printed for ref in setup():
#define LONG_DELAY_SEC 7000 // in...
What sketch is running - does it do this with Simple Blink - or is this a full speed write to Serial sketch for SerMon message viewing?
What version of the IDE and TeensyDuino are in use?
Make this call in setup() and see if it completes any faster: analogReadAveraging(1);
IIRC by default the internal hardware averaging does 4 reads per returned sample.
Paul - revisiting : PaulStoffregen/USB-Serial-Print-Speed-Test
When you get back to USB testing - maybe PJRC's IDE SerMon will work better for you than on my Win10 box. In any case this is...
Looking at Post #14 code - it looks like nothing gets pasted - but the line
#define SDFAT_BETA 0 is removed
I've posted code that puts an interrupt on the Rx pin that triggers when the STOP bit goes to START - the interrupt records the time, and turns itself off so data bit transitions are not trapped. ...
This should be #ifdef ?_1062_? since it is MCU specific?
Also we know restart times under 2 are suspect or fail - it would be good perhaps to add:
if ( delay_secs <2 ) delay_secs=2;
...
No, that as .a doesn't work as I tried it.
Normal code as :: sketchbook\libraries\reboot holding the reboot.h and .cpp instead of .a does work with this sketch:
#include "reboot.h"
void...
+Not: Thread titles are set in stone as they are the root of any link I suppose … Sorry the 'o' stays :(
I wasn't sure about the _isr() - it fires immediately on/at EXIT? Maybe that is the MCU...
When I turned on the _isr() "Alarm" I was seeing it with prior code - but timing may have changed and USB may get lost on exit?
Good to see it pared down some and working - I wasn't sure how much...
Looking across the forum these notes came up in T4 Beta thread:
Paul - used Serial.peek() for the first time and it works.
No, to get SerMon to send it typically pushes what was typed follwed by "ASCII code 10 = LF ( Line feed )". So a single character...
@WMXZ - above I noted this { post #12 } with a 2 second turnaround could be a way to RESET/Restart the T4 - which I've not seen yet?
There is a thread pjrc.com/threads/29607-Over-the-air-updates...
The manual is a headache at best. That code was from @WMXZ and whatever it does works - the only oddity in that thread was that Power button shares the Low Power restart segment of the RTC - and...
Just triggered the overtemp detection and it seems to just halt. Other than this RTC restart that does an automated Power Off and Restart not recalling anything else worked.
It'll work for now if...
Good to know nothing 'tweaked' your T4 in the process! I usually have my speakers off too - especially when it sits there beeping over and over 4 times a minute :) - there are those times that...
Paul: Just notice triggering a 15 sec Restore on T4. Press button - Red LED dark - Red BLIPS at 15 seconds. I held it some time after that expecting it to bypass the RESTORE and when released it...
Yeah - it just needed a cast to stop the warning - it was working so was ignoring that :: setSyncProvider((getExternalTime) Teensy3Clock.get);
Odd the USB isn't good and right? That should...
Is that in ref to post #48 code? Came working from IDE 1.8.10 install with TD 1.49b1. Yes there is 'THAT' warning about a type I didn't clean up - but it runs to T4 - that is a warning and the...
Guessing the disconnect from interweb was a special/specific request so that the test package would run in ANY case as properly signed and approved. When it can see the interweb it will have a...
Opened the sample for that RTC_Sleep code, here is where I left it in loop() there is a normal 20 second cycle and sleep 10 secs. If during the 20 secs push over Serial 'Enter' it does a RESET and...
Round about way to Reset : issue-to-reporogram-T4-0
That code works to SLEEP the T4 with a timer to wake. When it wakes it enters setup() after fresh load from flash in ResetHandler(). Not seen...
this post 11/21 speaks to the issue:
Those tests are generic showing suspicious behavior, pins to check or evaluate. They may be influenced by soldering itself or what it may be soldered to.
Ideally a fresh Teensy would not find any...