defragster
Senior Member+

Rushing out the door - back in a few hours to see ...

Parsing the output shows this: BUGBUG @110: F_CPU=110000000 50ms delay:: 1010 us and 1 ms System Clock: 120000000 IPG Clock: 120000000 Semc Clock: 40000000 RTC Clock: 32768 USB1pll Clock: 480000000

UPDATE - second thread started HERE :: https://forum.pjrc.com/threads/58688-Teensy-4-0-Clock-speed-influences-delay-and-SPI

Small Edit to code above. NOTE: As noted elsewhere Compile at 24 MHz and it starts broken as well. Code change above gives proper and clearer output: if ( foo < 47 ) { Serial.printf("\n...

Using p#13 ClocksT4.zip Replace the ClocksT4.ino sketch with this. It does the changes as in the October Post - with clock data printed by @mjs513 and shows this when the counts are wrong on millis(): "...

This is a secondary thread - missed my attention - Original issue 18 October - details and samples to repro there : forum.pjrc.com/threads/58053-T4-set_arm_clock-and-micros() Problem is clock feeding millis()...

Opps - missed the connection … and misread.

@loglow/Dan: 'same here as well' - "PCB Only" for the kits as nothing 'used'. ADD: 1 new Top Mount battery holder, And 1 { 2x5 short header and female socket set }

I don't have a Teensy 2 - but set IDE 1.8.10 to Teensy 2 and did Verify of example BLINK - On WINDOWS - with TD 1.49 beta 2 - it compiles and all is installed to build - not sure if it shows anything different as info:...

Found this: gcc.gnu.org/projects/cxx-status.html#cxx17 As far as Teensy ggc version - this was just posted:

@MichaelMeissner - was this aimed at this thread? :: forum.pjrc.com/threads/58695-c-17

@DerekR: The stand offs - I got a set of four on quick count - they are for the four corner mount holes so when assembled it can sit on a bench/desk without forcing/inviting parts/pins or soldered joints to...

Got logged CSV data files from ...\ADCL_t4\Examples\T4_analogReadMultiIntervalTimer\T4_analogReadMultiIntervalTimer.ino with: const uint8_t ADC0_pins = {16,17,20}; const uint8_t ADC1_pins = {21,26,27}; //... const...

Looks promising! Will get to it shortly and double check. Was using laptop at TV so just happy to get the twin sets of three reading fast and not bother yet with the SD. Will double check the libs here at desk.

I got as far as updating libraries and putting this in the ADC_Lite example by KurtE: const uint8_t ADC0_pins = {16,17,20}; const uint8_t ADC1_pins = {21,26,27}; #define COUNT_PINS_PER_ADC sizeof(ADC0_pins) const...

Glad you can see a way out - and have a note to avoid in future - good/painful lesson. Glad we had Derek's heads up trouble report to get a deeper look before any more parts got soldered away. Odd - I thought...

What //#include "SdFat.h" ?? Had to comment it out - got the latest https://github.com/greiman/SdFat-beta and compile grief

Where is the latest tree? github.com/KurtE/ADCL_t4/tree/Comapre-WIP Any other needed changes for it to run work? Current CORES?

Thx, I'll look to set value out and read them in groups with the 6 Analog/non-PWM {16,17,20,21, 26,27} pins and cycle value up and down when at some measurable freq with the ADCLite. If I read right {26,27} are only...

Wasn't trying to justify bad behavior 'just because' - only that as posted/tested it was erratic. ... TODO maybe came in handy? I can't say about other pins/cases - only tested the noted on the post/thread. If you...

My comment on #395 notes that behavior now is that without 'some' change the behavior is problematic at best - there is a cusp where what would be expected to be HIGH value results in 'zero'. That PULL used prior code...

Good info and plan - I stopped short of further testing - hoping the fix will be evident to @loglow - but now would be the time to ring it all out. Never did the same for the initial beta board - but there USB Host...

Just seeing if I paid enough attention to read the code right :) Maybe I'll get a chance to work with it. I'd say super … KISsS. If there are read not ready fails - mark them for spacing and read to blocks of 512KB...

Happy :) / Sad :( :: Glad I read the lines right - so small. If @Loglow can confirm and correct easily it seems all in that cable. I started on the PCB and #36 does connect the two DAT pads and likewise the pin #37...

That looks clean and easy. Should the setup() of ///// ADC0 really look redundant with 4 commands issued twice to same object? In the 'not complete' case would it make sense to flag 'no value read' and keep the...

Kits Look Awesome - Based on Derek's note looking before soldering …. Using DVM to ring out the Flex Cable:: CLK comes out on CMD? - then staring at it ... The PCB on connect end shows CLK between D+ and D- but...

As far as the GPL issue as Paul noted - "GPLv3 which means none of it can be used directly in the MIT licensed Teensy Audio library" That is just saying that unless an alternative licensed library set of code was...

Multi channel at high rates isn't something I recall as posted. It would take the person having done it or interested in working it out to login and see the post. It would take some special effort if possible given...

Best wishes for a long and happy T4 life on the new board.

Good to hear!

@MM - instructions will be handy - there was a recent note about those close pins to battery holder needing trimmed/attended to in some fashion. Interesting - you guys got one already - USPS says something to be here...

which Teensy is in use might be important.

There is an active thread looking into T4's analogRead() : pjrc.com/threads/58387-Teensy-4-0-which-pins-for-which-ADC That is a WIP you might try.

Cool - will have to give it a look.

Downloaded and installed TD 1.49b2 for some reason this time it gave this on first run - I did not pick "Run": Looked at properties and it offered 'UNBLOCK', I did not check that and re-ran the download and it...

re: post #27 above { fail at 24 and 150 MHz } - it may be a clock setting issue : pjrc.com/threads/58567-Teensyduino-1-49-Beta-1 Resolved perhaps in TD 1.49 by release.

Follow up to post #27. There is a problem at 24 MHz startup speed switching from power up reset speed - this may explain failed SDIO on SDFat Beta code? EDIT UPDATE: Building at 150 MHz start with millis() running...

Indeed it is likely a rare not 'generally' easy to hit problem - and easy to work around. In doing the work on MICROS() using the millis() + CycleCounter timing I never triggered it. If the clock drops/raises in steps...

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 code in code block #2...

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 T_3.2 it should support...

This came to mind: github.com/ftrias/TeensyThreads/pull/21 Also note :: This branch 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 & joystick for Teensy 4.0

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 device. How long does...

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 same signal levels...

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 edited folder (where...

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 MB Rx in...

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 front port - though...

@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 short send I was...

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 been who knows what for...

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 and check receive...

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. Also hitting ENTER...

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 GUI and TyCommander...

@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 buffer - though not...

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 that in the 1.49 beta...

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 should put that back to...

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 the Rx pin and it does...

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 messages per second...

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 PlatformIO interaction...

Paul - minor update ... Interedted to hear if you try this sketch and see similar or different behavior. I finally stopped the tSerMon - running fine - - at 348 minutes. TyComm dies at 19 minutes then 119 minutes -...

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 T4's on the same HUB...

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 delayMicroseconds #define...

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 something you might give a...

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. Then the receive code...

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; Indeed observed the _isr()...

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 setup() { ...

+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 giving an ACK that the...

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 of that was really...

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 send arrives as two...

@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 where such a reset...

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 they overlap - it seems...

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 not best solution -...

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 sound is useful though....

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 did the restore? Is...

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 work! No problem on...

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 right thing ends up...

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 chance to ask aPPle about...

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 is back online in 2...

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 another easy way to...

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 issues and test...

Check this post / Thread : Problem-with-Teensy-3-2-Serial1-and-HC-06 Legit quality HC05's seem to work - not sure of the source of ones in use.

void setup() { pinMode (outputA, INPUT_PULLUP); pinMode (outputB, INPUT_PULLUP); Serial.begin(9600); while( !Serial ); // Add this when seeing output is needed // or to wait 2 seconds // while( !Serial &&...