Thought so - but had to ask if is was near done and might line up with TD 1.54 now it is incorporated for awesome improvement - those write rates in P#33 are better than the old SD read rates.
I've had the SdFat Beta...
Great news Paul - big difference supporting a known system with (fixed) BOM for in house builds - versus supporting a generic range of items like FLASH chips.
@Bill Greiman - is there a feel for the coincidence of the 2.0.5 b1 timeline being weeks away from release that might coincide with TD 1.54 for use as SD.h ? ... both of course being unknown? Or is the new sdFat beta...
Snippets are usually a distraction - better to have the whole code posted if it can't be cut down to a smaller sketch that effectively shows the problem - that's why this :: Forum Rule: Always post complete source code...
Not indicated how many RGB LED's are in use? A photo showing the connections might help.
Quick guess based on something observed here : that GND wire may be feeding large return current through Teensy to host USB...
Good luck, if you get a working example posting it may help others and show how to use this feature.
Had hope that AN would show the 'enable' KurtE mentions, even if for wrong processor - if it does it is not as...
My EE buddy did that for a high school science project in 1980. Put his TRS-80 on a wheeled robot platform he built - focused light on an open top chip and navigated based on the chip's view of the world.
First glance it should be easier on the 1062 with external flash? As long as all needed code for the Flash writes is RAM resident - which user code is by default. But again that is not how the Teensy bootloader or the...
As noted in p#6 - Frank personally wrote such a 'code from SD' - so that was based on experience doing that and a great understanding of the Teensy programming process, not a coin toss - or anything that should be taken...
Not seen this come up before - but did find this app note for a different freescale/NXP processor : nxp.com/docs/en/application-note/AN5245.pdf
If the 1062 can support it as desired those notes may help - or suggest...
not crushed, i.e. discarded without reason - just noting a few hurdles making it non-trivial. One of which is the bootloader has one function and limited connectivity only to processor and none to SD card - it can "on...
Tested to work - Using a T_4.0 with loglow/TallDog T_4.0 board PCB to present SDIO pins to an SD socket.
That does not have PSRAM - but with reduced BUFFER it will use processor memory instead when EXTRAM is...
Indeed - even if that were a supported way to upload - where today it only via USB upload - it would take some orchestration overhead to ONLY do it once and not reProgram every time if the SD card were not removed.
...
Indeed that change makes this work in setup():
while(runTest(1));
So this need changed and also the :: "#if defined(ARDUINO_TEENSY41) "
Should also include :: #if defined(ARDUINO_TEENSY40)
It won't have...
That is in the spot of code noted in p#14.
Those "#if defined(ARDUINO_TEENSY41) " in "static void enableGPIO(bool enable) {" would preclude that from working on Teensy 4.0 with SDIO soldered on - but should use...
Closest is the below in : ...\hardware\teensy\avr\libraries\SdFat\src\SdCard\SdioTeensy.cpp
#elif defined(__IMXRT1062__)
//------------------------------------------------------------------------------
static void...
Edited the code to work with TD 1.54 b5:
#include <SD.h>
#include <SPI.h>
// https://forum.pjrc.com/threads/65851-Problem-reading-from-SD-card-directly-into-PSRAM?p=266951&viewfull=1#post266951
#define BUFSIZE...
Also note - there have been posts like "tried Paul's PSRAM test and it passed" - but then other usage fails until solder joints are reflowed or cleaned.
Noted as: "large file named TESTFILE.BIN" - but not how large? ...
Have not seen this noted as done or tried or done it here.
The TeensyDuino 1.54 Beta 5 has integrated a release version ( not Beta ) of the Greiman SdFat to replace the standard SD library.
Not sure that will...
The T_4.1 uses 480 Mbps USB. As presented (if I read right) by @KD5RXT-mark there is less disturbance and rerouting of the USB 'D' signal lines where it seems they are uninterrupted from the original cable. Not soldered...
That's great. When the version to release is assembled I'll look to get back and test it out when the code to be included is known and in one place.
Having the 1062 bootloader chip ready for the test pass will be...
Anything that provides simple info logging would be cool. As noted your On_Restart T_4 display is an awesome extension for HardFaults.
That's where I got bogged down - tying to add generic debug stuff to HardFault...
Things like that seem like a good addition to take the mystery out of a Teensy that 'just stops' - it doesn't generally happen - but when such things do happen it is an opaque puzzle.
And future more complex Teensy...
Forum search on "SCB_AIRCR" will find it liberally noted back to T_3.0 days IIRC - one might have comforting details - again IIRC from reading it is the common ARM way to do it.
For an advanced view of 1062's DMA and GPIO see : (arduino)\hardware\teensy\avr\libraries\OctoWS2811\OctoWS2811_imxrt.cpp
There are some other comments - but this is the biggest one:
// Ordinary RGB data is...
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 ...
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...
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...
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...
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...
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...
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...
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.
Find latest posts