defragster
Senior Member+

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 &&...

Does the coding account for the amplitude limits on adding multiple sounds at once? If total signal combined hits over 1 you'll hear distortion. Seems there are notes in the Audio tool - or the Tutorial for details.

There is a sketch here to test for shorts: Possible-new-shields and this one that sets pins HIGH or LOW and then using a wire to PULL LOW or HIGH it will show the changes to Serial Monitor: Possible-new-shields ...

Installed 1.49b1 over github cores on 1.8.10 : All seems good and well. Improved USB Serial Receive code working fine. RAM report looks different and about right - showing cross ref of KurtE/'Frank B'...

I was wondering about readBytes - (and any other class parts?) - especially when the .available() didn't match the while(read) count. Seeing 600 makes me wonder about running at least this test at other speeds. ...

Paul - he did that before I posted the same about 'private lib' - from this thread he is using the newest by @mjs513 in post #7 :: C:\Users\USER\Documents\Arduino\Pipe\libraries\Teensy-4.x-Quad-Encoder-Library-master ...

That looks pretty much wonderful/good - using the now current updated github\cores - at least to above sketch - updated below. So the change updates the count on each 512 packet - which moves above sketch along its test...

See post #1 :: "NOTE: you will need to incorporate the Update imxrt.h for encoder structure #402 to make use of the library." That type define was added to that file.

It is MUCH better in the right direction. Assumed it was a WIP - if it was that easy you would have it done already. Saw the github update and wanted to see if the sketch was a decent test ... Did some edits on...

Paul - I saw github Update - it passes the above post #16 code test it seems? Just room for TWO large buffers so far? Though it doesn't seem to like it if the send is a large 2800 bytes? <EDIT>: Will change...

Paul Noted on other fixed thread about 'this' thread: With that other issue fixed based on post #12 by PaulI'll write something much better this weekend. Will need as much help as possible with testing! The...

That looks Very Cool! Useful extension of touch and well played on the drum line/stick/bar ... What is in the drum bar for sensors?

Keeping code formatted helps - doing it manually of course is suspect to seeing things like that. In the IDE a Ctrl+T will do formatting the their uniform standard. That is an easy way to find missing syntax...

512 bytes Also WORKING - with yesterday's github USB update: Multiple of the 64 byte line in a single Send up to and including 512 works as a single read group. Did CODE mod to show read count and string.length and...

Perhaps the "Github runs post #1 code " wasn't seen as CONFIRMATION that Github runs post #1 code - without problem or issue.

And this is 10,020 - the count goes on … fun to offer @wwatson help - especially when it helps get good stuff done. As far as Dev tools for Windows when the IDE gets tiresome using the SublimeText editor KurtE...

Everything is so in paranoid mode {justifiably} - download an office DOC and it can't run/edit/print without APPROVE. I opened the imxtr-size github VS SLN file - and had to APPROVE it to open to build! It does...

@KurtE : VS2019 installed - not built - but github debug imxrt-size.exe works now! And back in Sublimetext to compile and build. FlexRAM section ITCM+DTCM = 512 KB Config : aaaaaaab ITCM : 23200 B (70.80%...

Nice that worked as expected. The code wouldn't be hard to change - just some #ifdef stuff in the way and then testing the cases … It might even make sense to stop the timer anytime the queue goes empty - stop the...

Updated code from Github runs post #1 code with post #2 FAIL string :: "1234567890123456789012345678901234567890123456789 01234567890abc"

Paul - tested this code against T_3.6 to work as follows: > Run Sketch : It will wait to read any chars until Serial.available() gets three unique non-zero values - that will be increasing with new chars reported....

… cross posted … Understood … edit above … finally installing VStudio 2019 to replace 2017 I removed … me and my slow interWebs is distracted with a 2.6 GB download on a 650 KB/sec downlink :( … wanted to confirm is...

<edit> : Cross post - got back to this without refresh ... indeed looks like the K.I.S.S. of death here :) Paul - this one is not fixed with the USB Github update from earlier - the available count sticks at the...

@KurtE - I uninstalled VS2017 weeks back after 2019 released and you were using it - without install done - and just started - I can't run the imxrt-size.exe from github - your or my old one ... imxrt-size.exe -...

Cool. I see github updated 14 mins ago Will have to see if that reflects on this one too: Teensy-4-0-USB-serial-lockup And maybe this one : Teensy-4-0-Serial-available()-stops-incrementing

Not sure about that comment and p#14? On Teensy4 - Pin #14 isn't valid for alternate SCK like T_3.6 and others. The 1062 has so many pins that possible Alt funcs got distributed in wildly different ways it seems so...

Something seemed off for first post #2 comment :: Was that to upload to a T_4 and not a 3.6 or 3.5 ? Still odd that I got odd behavior from TyComm - not having any Valid print made it unsure when the code loaded to...

I just got the latest github.com/KurtE/imxrt-size - will need to get that back into my build so I can see such things. Good follow up KurtE … was in a rush to get back on task and have lunch ready :) Indeed it did...

Yes, on the T4 with original sketch watch the T4's pin #13 LED when the pinMode() is commented. The light is glowing as it is being used as SCK on T4 during SPI access. I picked an audio board with SPI Flash on it...

I got it to upload with TyCommander When code changed to this: PROGMEM const char buffer = {0}; void setup() { while(!Serial); Serial.println(micros()); }

Was that to upload to a T_4 and not a 3.6 or 3.5 ? Give a bit more console output ... SEE FOLLOWING POST Last code compiled for me - but did FAIL upload as follows with TyCommander:...

Opps - that wasn't a suggestion to try - it won't work on ARM Teensy at all. That is the AVR code - that was SIMPLE to add on the base Talkie. There are a couple more moving pieces where the Teensy version would...

That code github.com/idhanu/Talkie gives credit to the going-digital/Talkie fork by Peter made by PJRC - so the included sound set is the same. It does show the added public interfaces that extended that library...

Going back to the going-digital/Talkie fork source - not updated in 8 yrs - except a minor .H update 6 yrs back. That lib has these in .H as public: class Talkie { public: void say(uint8_t* address);...

I'm seeing the IDE 1.8.9 as re-building faster than 1.8.10 … it seems. The defragster\TSET on github is Windows only - and uses TyCommander for uploading. TyCommander has a GUI - with good SerMon and also a CLI...

That was ported back some time by PJRC - not sure what came of the .end() if it was there when it was forked - I don't see an end() or any effort to stop the timers after they are started - or deal with the pin - other...

exactly right.

Running this code on T4 Beta breakout with Audio Shield and I hear only left channel tone. So it isn't processing the right channel audibly. Indeed that pinMode() in setup() causes the left channel to go silent. ...

Good Suggestion - I tested that Beta lib yesterday on T4 - with onboard SDIO quad SPI. As noted it can do FAT32 or ExFAT. Write speed is near or over 10 MB/sec on a good formatted card. Average write times are 25-50...

Suggests internal wiring burned away from over current - like a fuse … as noted in first part of the post : "something burned up inside"

First thought was something in the constructor is being done too early - before other stuff is done as that has been an issue. Seeing "Using it in the main class worked fine" sort of suggests that may be the case? ...

Yes. Set in the IDE - edited to show F_CPU_ACTUAL in setup {also print __FILE__ so I know what the sketch will do when I type 'Any' char}: Use a freshly formatted SD for best performance. Sketch is...

Cool! Impressive numbers! Had not tested this yet. Just got the current and ran it on PJRC Beta T4 breakout and also the FRDM4236 board and see similar results: Type any character to start FreeStack: 474376...

In case related and to be sure you saw this Paul Post: Perhaps it needs a longer timeout? Though if a clock stretch by slave - it seems that would show on the LA?

Sounds like the sampling would be okay. Even a Teensy 3.6 should be able to do that. Not sure of the impact of the Audio sampling getting in the way as it should handle that. For sure the accelerometer sampling no...

@WMXZ - it isn't the PROGMEM on three func()'s. I put that on my func()'s and it is working past two iterations. Found it - adding the call to stopAlarm in the _isr() - causes prior code to now halt on the second...

That's odd - only easy to check thing would to be sure it has good GND and power - and the pullups are healthy/good.

Odd - I put your code on here an dit ran 3 cycles and is stopped? with power LED on : blink @ms=30030 :: 14:57:50 11/25/2019 End RTC has set the system time Start blink … blink End

Tried rtc_stopAlarm(); yesterday and that wasn't the ticket - not sure that rtc_resetAlarm(); doing the trick either to fully reset the Alarm system? I pulled RTC Cell and held buttons - repowered USB & Cell and on...

@WMXZ - is there an UNDO of the 'SNVS_LPCR |=(1<<6) ' change that would make the beta breakout Power button act like it seemed to before - turning off the 3v3 LED? The other beta breakouts didn't have RTC Cell holder.

That was my post #2 guess. The POWER and SNVS?/Timer share the LP unit. > Sleeping T4 wakes on Power GND'ing > Power on doesn't clear or reset the SNVS timeout so the next Power Off triggers it back on. @WMXZ -...

That is not something I have ever observed previously - unless there is bounce on the Power GND line - when there was no Wake timer set. This may be caused by a 'residual' active RTC Alarm Timer detected as expiring....

Yes, TyTools does it as needed. Following _reboot_Teensyduino_ in the sources will show the process: C:\arduino-1.8.9t4\hardware\teensy\avr\cores\usb_disk\usb.c: 1107 usb_send_in(); 1108 if (b1 ==...

The trick to getting Teensy into bootloader is sending the USB port to a unique baud rate - it is 134 bps. Looking in the USB code it monitors for that and then triggers control to the bootloader. like this what you...

Thanks for the share Jean-Marc … Did a fork and clone to test with.

Running the code - with the call to :: setWakeupCallandSleep(10); The GREEN power LED on the T4 Beta Breakout goes out for the 10 second Sleep Alarm wake cycle. Pressing the breakout POWER button a half second...

Running that code on the PJRC Beta final breakout with RTC Cell it seems to work - and hitting the POWER button does seem to override the RTC Sleep Alarm. @WMXZ - on your end running that sketch - can you see how it...