defragster
Senior Member+

Nice work! >> and colon >> characters: ":/0123456789" and space.

Updated Post #1 - PJRC/Paul has indicated it is NOT planning to produce a public WIKI. There is a GROWING USER WIKI :: TeensyUser/doc/wiki > please look and participate there.

@Paul - possible to add a note for NativeEthernet on the T_4.1 hardware page? The hardware is discussed - but no link to the library to use for support ... recent user post made note of that ...

Here is that library thread :: T4-1-Ethernet-Library

There is a software reset function FrankB just noted in this post:

That need to send the 'address array' is where the Teensy's MAC will be written when the code shown above is executed. 'just supply' means allocate the needed 6 byte variable and pass to the function shown in p#2 and...

That is impressive and clean, nice looking hand work on the panel cover graphic!

There is overhead with the tests and I/O write/read, mask shift and test - I should have looked more at the code before guessing speed. Also it isn't using FAST versions ( given the pin isn't CONST ) of digitalWrite...

I had not seen that before - interesting - it might clock near or above 60 MHz for each byte? Did not look at the data sheet either to see how fast it can cycle - or the daisy chain setup - without sending a 'start'...

That code is 2013 and looks like it refers to bit banging the exchange in the second code snippet? If it can work manually and not using the SPI engine for the transfer then the bit bang code is in charge of the pins...

Okay, I had just glanced at the comments on the pin #'s (and saw i2s comments) before posting - then the 'red notes' on the FLEXIO mux set. So potential issue is not because the are mux'able to FLEXIO - but if the code...

Just to make sure at a glance what that is showing - the issue is using those pins 35,36,37 is in conflict because they have FLEXIO2 conflict with QSPI usage?

TD 1.54 Beta 6 will be out in some days and will have some stable version of LittleFS included - maybe by the time the chip arrives. That will have all the setup and operation commands needed to read and write that 64...

No, PSRAM is not needed to add FLASH. They are independent and either or both can be used. Hopefully the comments in this code snippet point to a chip that has been tested and used that can be acquired? Some of...

That looks to be the needed change in what looks to be the correct file. Unless there are multiple copies of TeensyDuino installed and the edit was not made in the location used? Or for some reason the file change...

There is this library that allows working with the On/Off :: github.com/FrankBoesing/T4_PowerButton The examples show usage - it was recently updated to catch and show FAULTS as well.

Good work @mjs513 - I typed on github asking about that ... but never hit post I saw today ... too many distractions ... Wish I had known about the 2Gb NAND digikey had with last order so I don't have one of any sort...

Indeed maybe not ... I think you'd have to hook the warn callback and make a note of that in the static RAM. Then if it went OVERTEMP and restarted - not sure if that is a reported FAULT? If it is reported then it is...

Pretty sure Panel mount for the ethernet was not considered. It was just a desktop test proof of concept/function that works in that situation. No those boards don't offer any good mounting options - just a minimal...

As long as there is a clean and easy way to include or enable it it sells itself - having a lib in the CORES would be awesome to just add #include 'something'. As noted I started working on it in T_3.6 beta I think -...

As noted in p#23 - if I'm reading the 'picture' right and the notes about no active components: I don't see that as an option - to use the ribbon without a magjack - or cabling punchdown wires direct to Teensy?

Interesting - well it is an otherwise empty function - may it gets optimized away :) ??? Could do a normal non-debug build and add a static var and use a stack var to get it and change it in some way it doesn't just...

Interesting that is failing to trigger on code over filling the stack? It is a 32 Byte(?) region? Maybe the recursive code isn't reading|writing to it to trigger but just stepping over it? Have not gotten to test...

@KurtE - just came back here to read the posting below - wonder if this is what is bugging the T_4.x remote memory PCB? The solder is there but 'iffy'? Odd the icon hover 'text' says "Thumbs Up" - but seeing the...

<edit>: I agree this should be provided in the core with a way to activate it for display on boot. Working on this in prior Beta's (with debug_tt) it seemed like it would be useful - but there were so few reports of...

Based on only the included image - that looks like just a way to panel mount a connector to take signals to a punch down block - or like a wall socket fixture - an alternative to in wall wiring - just a breakout...

Quite welcome. The comments in bold are not in the code - added for help with clarification - easier to read than 700 preceding posts as it all developed.

Look at the LFSintegrity sketch - it has #ifdef for all the known MEDIA types: //#define TEST_RAM // can be PSRAM or smaller in processor RAM1 or RAM2 //#define TEST_SPI // this is Propshield or other SPI based...

Internal temp can rise and fall quick at times esp with OC - but stable runs can take some time to heat the whole PCB metal sandwich - and anything soldered or attached. Wondering about junction temp and temp measure...

Paul's github has benchmark repository for T_4.0 test does as posted on the product page at 600 MHz - ( they may e linked there as well? ) - you could download the sketches and run them - coremark and another encrytion...

Use "wfi" with testing care - unlike the T_3.x's - there are no regular waking interrupts - so it can sleep until one comes along. The normal systick interrupt doesn't trigger to WAKE like on the 3.x's Monitoring...

Not sure where WDT_timings_t comde from - not a library included in TeensyDuino? More info needed on libraries and code in use - and version of TeensyDuino ...more complete code so a viewer could run it and observe?

Moving air is better - but a tape on heat sink is good for a couple of degrees - and both in combo best. More pins and soldered/plugged to something adds more ways to take heat out like moving air does from the whole of...

This post : Teensy-4-1-binary-from-alternate-toolchain Indicates it shows the fuses and that boot from serial is disabled.

Interesting to know the Serial is disabled - so even seeing the NXP bootloader appear won't allow access - that was a subject on another of these redundant threads. The Fuses are dangerous - and indeed once set (...

Well timed edges are critical - you only get one chance to read both sensors per 'trial'. An error if one sensor triggers without the other - and once both triggers those two points are the only available data? If...

LittleFS is NEW to TD 1.54 in beta as noted in p#771. Not sure if it works on TD 1.53 with the addition of the library also noted in p#771 or the current code on PJRC under LittleFS it is copied from before most recent...

The above Hackaday leads to an open source for Arduino port reading - GPL license - and it just sits in a while( !Sensor #1 ) then goes to While( !Sensor #2 ) for timing. As noted that uses trap on both sides rather...

p#19 test loop code works here for 8 MB repeatedly on T_4.1 with QSPI NAND and a PSRAM. Must be some wiring or connectivity oddity or the chip compromised? I can confirm the LEAKING: With this code edit: ...

Will be great having the T_4.1 card backside for ref - and better answering of the unmarked pins! Also nice if the stars are aligned to get the 1062's stand alone bootloader worked out now with latest info and...

Great you got it working! Looks like a nice clear display - not cheap enough to toss or have bad function from.

Getting/Setting up the sensors is the tricky part? Passing object can be 100 feet per sec or up to 3,500 fps - what range is intended use? Chrony commercial units used here have what seems a pair of single lens...

Expect there are examples for most if not all hardware elements on NXP. Indeed some folks have used SDK examples to understand chip functions as it compliments what is released as documentation. Integrating and...

So it is a soldering issue not a problem with the board itself - other than the close proximity of the metal bits? Good luck with the 'fix'

Starting with a Teensy 4.0 or 4.1 would likely be a great way to see working code and get a working prototype with all the power of the NXP 1062. But starting with Teensy will provide useful tools and support...

Not sure what version was downloaded? Also was it on TeensyDuino 1.54 Beta #5? As far as flash on underside access - those pins are designed for use with QSPI - QUAD not normal SPI. When setup for QSPI access the...

This means the enclosed waterproof container has an available USB port for programming? If the Teensy is properly running and has an active USB stack programming doesn't require a button press? The USB cable...

On prior Teensy the bootloader was only required to be online during programming - once programmed it could be removed. So there isn't any reason to think there is magic feedback from the bootloader tied into the...

The OT in OTP is 'One Time' - AFAIK once they are set as done by PJRC to function as desired for Teensy. based on Paul notes :: Indeed the bootloader MCU assists in timing and startup power distribution to the 1062...

If it works from powered with 3.3V that answers that - just reading the comments at code start suggested it might be powered at 5V and that change might be needed for best use at 3.3V. Mouser does show specs 2.8V,5V...

I liked the idea of showing the base address of the areas KurtE notes - but it got eliminated as TMI before when that page was created - still think having it there would be good reference. LittleFS still just a...

Good work! Looks very nice - good luck with the bootloader, nice the JTAG is there.

Also note that current TeensyDuino 1.54 Beta is changing the SD code to a more efficient alternate version. Would suggest working with that version to see functionality. Current Beta is #5 - but refresh to #6 may...

Another fun find by FrankB :) When I was looking at the fault handler code I wondered why that went 'ignored'. @mjs513 typed in the value check and "naming" for the Faults, that code as noted in startup.c I found at...

Looks like this at digikey : CKN10502CT-ND If the same as on Teensy LC from this old thread :: pjrc.com/threads/32866-Part-number-for-Button-on-Teensy-LC

The real Teensy 4.1 doc - shown above - is here : pjrc.com/store/teensy41.html The card backside was not finished when the T_4.1 was for first printing - or not quite yet - due to covid restrictions and other...

Those middle holes are USB Host arranged like on the T_3.6. See silkscreen on bottom of PCB.

Is the display running on 5V? Hopefully all I/O can work with 3.3V and not hurt the Teensy. This line in setup() just caught attention: Wondering if that should be 0x00 to interface to the 3.3V of the...

Does the output() function properly display the text strings? If so then try making string line 2 different to see if it still works. That will confirm the deivce is talking and displaying that data correctly.

A10 and A11 on T_3.5 are through hole pins - so top or bottom accessible - just not on the edge.

... the code is saying it isn't valid. Not sure if this helps :: github.com/KurtE/TeensyDocuments/blob/master/Teensy%20K66%20Beta%20Pinout.xlsx KurtE keeps that generally accurate. it may help understand -...

There is a set of HTML documentation in that repository. That error detail says :: WRONG_PIN A pin was selected that cannot be read by this ADC module. There are two ADC modules on the Teensy - each ADC unit can...

LFSintegrity show this - pretty near an EDGE case 64KB to 96 KB ITCM: RAM1: 22.79% of 512 kB used. Code (ITCM, 32 kB Blocks): 65.71 kB Variables (DTCM): 20.69 kB Available for Variables: ...

Top List of mid page Topic Anchor links all work - Very nice!

There have been some measurements posted in table form. I find a graph on this page that gives some idea : github.com/manitou48/teensy4/blob/master/coremarka.png A T_3.2 at 96 MHz looks to be under 40 mA. It can...

Version a) looks good - if that isn't clear at least it makes it easy to refer to if a problem is posted.

Can you wire an external PullUp to pin 13? Maybe the internal pullup is a bit short on power?

Several users have had T_3.6 ported code FAIL on T_4.x. And some T_4.x code fails to run right - either not compile or find the stack won't function. >> Too Much Info is easy to ignore or explain when it works, not...

NXP posted this 16 page doc Dec 29, 2020 :: Migration guide from i.MX RT1050/60 to i.MX RT1170

The First code wholly unbounced will likely show a ton of on/off cycles - put a delay(50) after the print perhaps to hide those and show 'reliable' output. Of course the Bounce2 library should have that if it is...

The '1170' is still marked as in 'Development'. While NDA folks may have gotten an EVK board that isn't even publicly available yet. 2 Distributors showing that EVK with the 1176 indicate 15 weeks lead time with no...

The first needs this line in setup() to provide pin 13 with LED power to go LOW on button press. > pinMode( 13, INPUT_PULLUP ); So does Bounce on PJRC.com and this forum post suggest Bounce2 does as well :...

reading the linked notes - two things pop out - of the not gonna help the actual problem nature? But may help understanding and help assure useful Serial output is seen. > Teensy 'Button' is Program - not a reset. ...

Suppose Paul will have a mind about that? Maybe non verbose emulate the IDE style? Verbose show both? I like the table as noted as it presents the info in a better to understand format without parsing the text.

Works as replacement here for prior version. Here is the result from LFSintegrity build: FlexRAM section ITCM+DTCM = 512 KB ITCM : 67288 B (68.45% of 96 KB) DTCM : 21184 B ( 4.97% of 416 KB) Available...

It is here :: github.com/KurtE/imxrt-size

Only seen it on Windows. And it was at first written to ONLY work on 1062's. Not sure what changes it would take for pre-1062's if expanded to work on them.

When memory questions arise seeing the map is helpful. Adding this ",--print-memory-usage" to any of the Teensy boards.txt ( or boards.local.txt ) gives a more detailed look at memory use like: ...

Happy New Year! Glad it is working for you. Indeed learned C in early 80's from "The C Programming Language by Brian W. Kernighan and Dennis M. Ritchie " outside my mainframe classes in a minicomputer lab. Then...

AFAIK :: Setting pinMode() is needed for DIGITAL usage. When used as an ANALOG the I/O functions prepare the pin as needed to function, and doing pinMode() on them only interferes. PaulS got the answer faster...

A year or so back a user asked about starting as one of two USB interfaces - IIRC. >> Thanks to SublimeTest - search of my sketches shows the EEPROM read testing done here 8/29/2018 - and putting forum thread link in...

Not sure this line is needed or helping :: pinMode(dacpin, OUTPUT); // DAC Try adding this line in setup() : analogReference(EXTERNAL);

Had not tried to compile - just seeing the plaintext there showed it would not. Also didn't look close enough at the code when I popped it open - did not see type String was in use - not a normal " 'c' string " They...

Not aware of anything inbuilt - note below about GDB debugger. It would be custom based on the code at hand. perhaps : Do a review of the code looking that all is correct as intended - making note of any...

Just seeing this as unanswered ... not that I have one ... Did you get it working? Not looked at this in some months, but saw it working when I did on Windows 10. What version of TeensyDuino is in use? Is the...

Hi all and HAPPY NEW YEAR 2021 Nice vid Frank - will share with the Mrs. - she loves ABBA :)

That 2 year old code was likely written using the early 1062 Reference Manual - perhaps the NXP evaluation board and software tools had examples for reference? Current version posted on PJRC.com - manual did suffer...

Check the T_4.0 card or PJRC.com info. These alternate pins looks to exist on a T_3.2, but they are not available on a T_4.0 because of processor internal design. #define TFT_MOSI 7 #define TFT_SCLK 14

He has posted recently to this effect - on another thread about this IIRC ... Yes - this related thread :: pjrc.com/threads/57173-Teensy-4-0-code-security That thread covers the needed feature of the 'bootloader...

This shows an example with some details if not seen before :: tutorialspoint.com/cprogramming/c_strings.htm There are probably better more informative links? NULL is Zero. A 'c' defined string is a series of...