The T_4.0 also has USB_HOST pins/ability. If storage space is needed and speed provided can be acceptable, and a SMALL enough USB Flash drive could be connected that would give much larger storage space.
There is a...
The PCB and components are unchanged.
The LOCKED Teensy will ship with the white image of a 'LOCK' stamped on the MCU:
image from pjrc.com/store/teensy40.html#codesecurity
Based on the link the allocation is always dynamic as p#1 shows.
The link shows making an explicit memory allocation and passing the pointer to the library.
Otherwise it seems the reserved space is just a pair of...
guessing the Matrix is dynamically allocated?
Quick search suggests that is the case and you can make and provide 'local' memory as indicated in the reply a couple down from the top here:...
Not sure of the answer to the question - cool that it works except the feedback part.
Edited p#1 to include the ... tags using the # on toolbar.
That retains code formatting/indentation for readability.
If...
Has worked when tried here since Beta 4.0 and 4.1.
The button to GND must not be going low enough? 1 mV doesn't seem like much - but something is keeping it from seeing the needed 'drop' to GND it seems.
In that...
Not having built and followed the MTP recently - it was dynamic in dev ... maybe the best ships in TD 1.59 beta 3? forum.pjrc.com/threads/73342-Teensyduino-1-59-Beta-3
Wow that comes from a page series not seen - at least in some time : pjrc.com/teensy/loader.html
It shows link to that Vista as well as Linux and Mac OS links.
Those pages indeed frozen in time and ready for a...
Did the Wireshark capture collect data when the Teensy was connected?
Assuming Arduino IDE in use?
Open a Blink.ino and do a verify build for T_4.1 board selected with USB type Serial
With Verify build done the...
Found: patents.justia.com/patent/11302162 - 'US Patent for Multifunction terminals for alarm systems Patent (Patent # 11,302,162)'
It doesn't show the figures?
Is that using 8 wires like an ethernet cable for...
Not reading the zip to explore the wireshark data ...
safe to assume there was some traffic after the 15s Restore and blink? The Teensy will come online as a HID device IIRC.
At that point with a working USB port...
Not sure if it was a Mac in that case: Recent days another post indicated a T_4.x recognized as a T_3.2?
not sure if that ever got resolved ... don't recall seeing follow up post ...
Use of RAM2 doesn't require any special attention when just used normally like RAM1 would be.
1,2, or 4 byte boundaries are not an issue. And the Cache works as desired to buffer access when not used for DMA.
Excerpted with renames from ...\arduino-1.8.19\hardware\teensy\avr\cores\teensy4\pins_arduino.h
wrote a sketch to verify changes here - seems they match updated p#1
assuming T_MM linear the same based on the 'card...
Indeed, the SD 'bookkeeping' delays can exceed 100ms. Thought to mention that reading the '50ms' value as posted - but the max value can depend on SD card in use and possibly the software ordering (open/write/close).
...
See posts #2 and #3 - the 1062 has two halves on different clocks and busses in some fashion.
3 cycles is what this takes: start = ARM_DWT_CYCCNT;
That CYCCNT is an easy read. Putting them together they are always...
Have not worked with current Flasher code at all - but that 8MB limit on 16MB Flash may be to assure that at least HALF of the flash is reserved for the process? And to locate the start point for the load area?
Years...
I asked for and received one of the demo packs! I didn't give it the time it deserved - though I did connect it and try to set up the PPS heartbeat signal and found it to repeat - but not to the same ns - us or even ms...
Something is off - seems that should be working.
90 chars 100 times/sec when UART can transfer 11,520 chars/sec - that shouldn't be difficult. The T_4.1 hardware FIFO isn't big (4 bytes?) - as long as interrupts...
- on/off is cool
- other thread notes batt type and capacity ... bigger and smaller ... can be 1-2 years, depends on time off ... assuming no vBat drain when powered and On?
- batt replacement in field worthy...
Reserved EEPROM area is not changed or erased during normal programming.
The 15 sec Restore process on the T_4.x will wipe it - but that is by design and not related to normal programming.
See if reading p#2 again makes sense ... No SPI 1 or SPI 2 or any other pins or PRIMARY pin functions are shared with those bottom side pins.
There are 'light gray' optional alternate functions shown for other...
Is this PSRAM for use on a T_4.1?
If so the QSPI pads on the underside for PSRAM do not use any SPI pins - it maps to unique Quad SPI pins direct to the processor.
The link in p#7 starts:
Lightweight C++ callbacks
I'm considering changing all or most of Teensy callback APIs (IntervalTimer, attachInterrupt, usbMIDI, more to be added) to properly support C++ functions. But not...
The T1 and T2 baud rate must match and be set to the same value - either both 115200 or 230400.
Confirm both T1 and T2 share a common Ground pin as well as the Rx and Tx wires.
Not seeing updated code since p#1 -...
That image is confused for sure. The 'Teensy Ports' is right for T_4.0 and should be used.
Something else on the computer seems to have the port open preventing access to that COM4.
If a sketch is built for board...
Speed of PSRAM ? - Is there a T_4.1 at hand for testing?
If so a memset of the buffer to zero could be timed
then time setting some number of bytes across the buffer with values
Then timing the read the buffer to...
This was noted:
When not uploading and just building, the compiler says space free for local variables is a negative value.
If it shows NEG that should trigger ERROR and stop, but the note says build not upload. So...
When 'free for local' is <=0 this code github.com/PaulStoffregen/teensy_size/blob/main/teensy_size.c#L99
Should cause a build error to be displayed. At this point the build is complete and the HEX remains and could...
Something is off.
Try the button press and hold until the flash to release as noted.
This does not involve the computer in any way and works on a USB Battery bank for instance. As long as the cable provides 5V...
Not Paul - but quick look shows this (after rejected upload of T_3.2 hex):
21:14:45.479 (loader): elf file is for Teensy 4.1 (IMXRT1062)
21:14:45.479 (loader): using hex file
21:14:45.494 (loader): begin operation...
The "automatic when using PlatformIO/Arduino IDE" is by design where those apps trigger the upload.
The Teensy Loader App is 'passive' when active and 'pointed to a HEX' file it is ready.
The button or the IDE's...
Are the Serial ports READ only by any chance?
If so wondering if after serial#.begin() a pinMode( pin#_Tx ) could be used for the change interrupt?
NOTE: on the T_3.6 GPS_IMU system noted above the Rx goes to LOW...
On the T_3.6 putting an interrupt on the RX pin {as it seems the above does} worked to see when a GPS started its message.
That same code on the T_4.x did not work as it seems the UART control/config of the...
Chromebook is browser based to some degree - the Chrome browser has a way to connect to Serial USB devices to a webpage - this might be the tip of the iceberg: support.google.com/chrome/answer/12576972?hl=en
Seems...
Great if the p#2 makes a usable alternative.
Though been using TyCommander for years and it has a great feature set - fast performance (not perhaps as good as the latest PJRC SerMon, but close enough when not full...
Not seeing that if this is the right spot : github.com/PaulStoffregen/cores/blob/master/teensy4/interrupt.c#L31
FASTRUN static inline __attribute__((always_inline))
inline void irq_anyport(volatile uint32_t *gpio,...
Can you post the working sketch with the _ISR showing the expected? If reading right: Could be handy in some case (act like a parameter) if called from loop() {==0} or by normal _ISR process {==16+70} - or maybe by...
Confirm the addr2line being used is from the current Teensy tools install for IDE 2 on Windows. The chain changed and an older one on my system worked before - but stopped after 1.58 or 1.59 and the one from here was...
p#3 "DSB" was just a default guess for double/extra triggering - not seeing the missing brackets.
The two LOCAL function copies of timeSinceLastChange was noted in p#3 - also now seeing local copies of " bool newA,...
For: sparkfun.com/products/15845
Pictures don't show ... and ::
The two rows of 14x1 headers are not included to give you the freedom to choose how to connect your audio board with your Teensy.
That seems EVIL to send 13 pin header kit when 14 pins are needed. Even if you knew better (rather than expecting the kit parts to be complete) you would not then have the parts on hand to complete the kit.
Hopefully...
If I give a link can I say no? :)
stackoverflow.com/questions/15491751/real-life-use-cases-of-barriers-dsb-dmb-isb-in-arm
If you are mainly a device driver developer, then examples are fairly straightforward to...
All 14 pins end to end need to be in place on both boards.
It needs to connect GND on the USB end and then to both end corners pins #12 and #13 to be properly and fully connected.
Third pic p#3 shows added Teensy...
For short _ISR routines they can complete before the interrupt is marked as serviced.
Try with this added "DSB":
void encoder_shaft_moved() {
elapsedMillis timeSinceLastChange=0;
bool newA, newB;
// put...
Yes, that is what that shows. If wired and programmed like that used for the Audio adapter there must be "a PCB-design problem" as indicated in p#8.
Perhaps a 'breadboard', or other wiring test, using a 'spare' Micro...
CrashReport usage is from above is something like:
void setup(){
Serial.begin(115200); // If Serial connects in under 2 secs it will be present when this returns.
while (!Serial && millis() < 4000);
if (...
The T_4.0 can support the SDIO access bus - but that is the bottom side pads that are pins 34-35.
T_4.1 also SDIO uses same MCU 1062 pins - but diff sketch pin #'s - though not relevant to T_4.0.
For Standard SPI...
Not familar with this usage as WebServer but:
void setup(){
Serial.begin(115200);
while (!Serial && millis() < 200);
...
That while (!Serial && millis() < 200); won't pause at all as the Serial.begin()...
Edited p#1 for readability
It shows TD 1.58 in use.
TD 1.59 Beta 3 has been released with further changes - please try with that.
Assuming it was compiled as default "faster"?
+1 @AndyA ...
I was going to make a short note: back in T_3.6 days (2018) had a GPS with PPS and monitored that against MCU's "ARM_DWT_CYCCNT" that had to be enabled for T_3.x's and on the T_4.x's it is on from...
PJRC seems to prefer sticking to NXP product family where possible - bootloader used selected does all that is needed - mcu used has evolved over time as needed. As long as nxp delivers them those seem to be the chip of...
Saw the notice, very cool idea - but time doesn't allow.
Have seen a few posts on various methods - if anything develops hopefully it gets posted on forum.
PSUEDO fed by ENTROPY 'random':...
Quick test shows with vBat removed:: OFF state is maintained as long as USB power is present.
So vBat is optional as long as VIN is powered and there is retaining power sent from USB.
Great, glad that solves the problem with a cleaner and simpler solution.
I had not looked into the code presented - but seemed it must be in there, and there it was.
In OFF mode the consumed power will come from...
That solves going to OFF with a user Button.
Using the same button to go ON from Sleep likely to have the same problem.
Not sure there is a way around that - would need a button to GND the On/Off to wake the...
Went back to code by Frank==@mcu32 and made this:
// Software trigger Teensy 4.x OFF
// Power RTC vBat
// GND pin #14 : Instant OFF
// Wake to ON Restart with short of On/Off Pin
void setup()
{
...
Not sure - seems it evolved from NXP SDK and other limited sources.
Here is one post from Beta period with links to some others: pjrc.com/threads/60532-Teensy-4-1-Beta-Test
Nothing pops out there - Try other sketches or perhaps start setup with BLINK code and wait before enabling the LED strips - and start with only one.
Perhaps the power is dipping with the LED's starting up?
...
Teensy 4.x DIY boards use this pjrc.com/store/ic_mkl02_t4.html
In the case of T_4.x the bootloader chip is actively involved in power on of the 1062 MCU chip. Without the bootloader indeed startup process would need...
Assuming they work fine powered by USB?
Some external supplies don't deliver power at the right rate for proper startup.
There are posts relating to this ... somewhere and not real recently.
Can you put a 3V...
Hard to see if there is a difference between the two images?
What shows is a compiler parameter error that may have been unnoticed by the tool chain in 1.57 that was updated for 1.58. There is another toolchain...
Pinned and on a PCB adds heat sink area ... except when PCB is a heat source instead.
T_4.1's extra inch helps spread heat to dissipate over larger surface and run cooler than a 4.0 - soldering pins to a T_4.0 helps...
Bummer. It got testing on first Beta units for T_4.0 and 4.1 with PJRC Beta hardware breakout PCB's, so it is known to work.
And that linked Frank B library showed 2 years last github edit? So, it worked then and...
Can't say ... maybe connected 'under load' the voltage drops if the battery isn't fresh enough?
Put DVM inline and measure current - it draws more than a tiny bit.
At least it seems the right 'bell rang' here for hopefully finding the issue and needing proper vBat power to hold state and also go back on.
Good luck!
schematic wouldn't help me :)
Seems the battery wouldn't last long if it is being pulled down to 0.2V? Either is has no capacity, or it is being shorted in this state?
What voltage is on GPIO pin (16/A2)?
Does...
Don't recall seeing this ... for some reason wondering about putting 3V on the vBat pin?
That remembers the On/Off state and cutting VIN from VUSB using 'other' supply may be hitting the voltage flow on startup issue?
All of this is wrong for a T_4.1 with SDIO based SD socket - see examples noted in p#2
void Logging::setup_log() {
// Setup pinout
pinMode(PIN_SPI_MOSI, OUTPUT);
pinMode(PIN_SPI_MISO, INPUT);
...
Seems that was a recent T_4.x specific change where IRQ_SNVS_IRQ exists and is used for a new RTC based timer.
@luni will need to #ifdef that - going back a version of TTT will get rid of that conflict, unless that...
Find latest posts