Search results

Seems there is a 48 size font - not much fits on the screen [4"480x320] but bbig test against 10 for h*w stopped the broken text.

Ok, so twin 8's works by excluding FLASH, but a large 8+MB single PSRAM would collide with FLASH usage. And 32MB SDRAM test has a unique base address with it's coding.

Catch-22 on coding a project to limit coding? Left hand getting better at mouse - but keyboard gets both hands. Especially bopping around lines in the IDE. Micros takes over 35 clocks to read (not awful) - if the ARM_CYC_CNT could work it reads in 3 clocks - but that runs current CPU MHz. The...

This is about larger PSRAM chips and LittleFS_RAM right? The code for LittleFS_RAM gets a memory pointer - RAM2, PSRAM or SDRAM {seems that was tested?} when available - as long as the ?_malloc() works. It has no inside hardcoded ties to any specific memory - beyond a working malloc. p#8...

Yes, keyboard mouse to be minimized here. Did a quick KLUDGE adjustment that clears up the display and allows the audio compromise to function. Picked "100" as a guess for "H*W" (assuming fonts or other use small - and 10 rows of 240 were no problem) and it was enough for common text as shown...

Seems if the startup and global for size were accounted for and extmem code updated then having more PSRAM should work - may need linker update not sure of the boundaries set there to allow for stacking the FLASH after it? As posted the glance at LtilleFS RAM code just takes desired size and...

LittleFS takes the users specified size for the 'RAM drive: LittleFS_RAM() { } bool begin(uint32_t size) { Doesn't seem to be hardcoded there. Then the T_4.1 space for PSRAM is allocated as : return begin(extmem_malloc(size), size); Just the global : extern uint8_t external_psram_size...

p#31 added notes: Only diff is removing the End/Begin edit of the PR. This is the DEMO sketch that comes on the Mini device. And there is NO AUDIO playing during this text output. It is not just on this screen. For testing only the tutorial BarGraph sketch was observed to work with the added...

Bad Fix :: Someone noted that killing chip select CS terminates the transfer. Just looked at screen last night: you can tell which is which ...

Using this : https://github.com/newdigate/teensy-variable-playback/tree/master Saw it working: #define NUM_WAVS 4 // avoid silly mistakes const char *wav_31[NUM_WAVS] = { "F#4.WAV", "F#3.WAV", "C4.WAV", "C3.WAV"}; //, "F#2.WAV", "f#5.WAV", "C6.WAV"}; PSRAM fills quickly :)

yes, if not 'broken' then at 13-15 seconds of #1 the RED LED should give a flash sequence indicating to release the Button. If that does not occur after some tries, then there is a some failure.

Pics give a decent view - not seeing any missing components or obvious splatter or excess flux. Inspection there can confirm that and that any soldering contaminates are removed. Trying the 15 sec Restore is the best steps perhaps to repeat if there are no hot components. Continuous Button...

What was connected and how? Any soldering done? Any violations of the voltage limitations could do serious damage. How far did the 15 second restore get? The fast RED LED then release the button and then did it stay on for some 30 seconds or more doing the Restore to completion? If not then the...

Making the change pointed out there was a begin(_clock) argument in the reference code that did not have a variable for in the ST7796 lib - so it was left out, like in the begin() before the loop. Extending the transaction code would add more complexity. Did a quick search/scan of code that...

Did sketch edit to use long 480 for bar graph instead of 320 and audio play properly with PR#37. Also moved msecs=0 to end of update if() as the old update time 21/22ms was already over the 15ms entry time - and bigger bars now take 48/49ms Edited...

DONE: https://github.com/PaulStoffregen/ST7735_t3/pull/37

GOOD WORK KEN! That does it. Taking 21 & 22 msecs now with restored full BAR DRAW width. Audio plays good and proper! It just periodically does END and BEGIN SPI to free the bus. I'll do a PR ... just home from MRI and needs to ICE ...

Out of time - but have conjecture I just sent in email to Ken based on this quick test: Yes, Narrow bars sounds good! Showing 6ms update time now - where both were the same 21ms before. Even without the msecs=0 closing out the IF(){}! Maybe there is something the way the pixels pack for...

@KurtE - interesting notes - MBed going away and Zephyr may be the next Arduino pathway. Does, the variants work you did for the SDRAM/TMM have any value in abstracting the CORES to the Zephyr scheme? Or is that already part of the 1062 layer porting work done in Zephyr core?

May be a helpful clue. That was tested and noted to Ken in email but not shown in p#10, So rewriting the text numbers at the same rate not an issue - but the larger pixel volume of the bars triggers the issue: tft.setFont(Arial_14); tft.fillRect(60, 284, 40, 16, ST7735_BLACK)...

Alternate Info - as above ucing Audio Tutorial: Part_3_03_TFT_Display.ino. Seems the diff is: #include <ILI9341_t3.h> #include <font_Arial.h> // from ILI9341_t3 versus: #include <ST7796_t3.h> #include <st7735_t3_font_Arial.h> @KenHahn sent me a 'Beta' MINI PCB that then got some digital pin...

Had not seen that - as noted the menu area was messed up - maybe IDE adding that is why? It is fine after restarts. I see it shows KEY on left 'pane' edge when the options are brought out - if it could maybe just be placed on the Boards/Libraries edge bar all the time? > clicking the 'key'...

On the @KenHahn Mini board (with embedded PJRC Audio on PCB) modifying the Audio Tutorial to work with the ST7796_t3 and replace the ILI9341_t3 it works the display on the 320 direction! But the SOUND is broken audio. Perfect when the bar updates removed. Modified the timing entry to redraw and...

uint32_t operations are native 32 bit on T_3.x and T_4.x

... after update IDE 2.3.6 update seems to be messing with system? Installing 1.8.19 TeensyDuino 1.60.4 Reboot after Win Update - IDE 1.8.19 w/1.61.4 Similar build to IDE 2- libs all from right places, ST7796_t3 good and rotate(2) fixed. IDE 2 Full build 7 mins and IDE 1 full build under 1.5...

All Good. 0.60.4 on updated IDE2 - except the IDE UI x.6 update has lost app menu bar Building @KenHahn Demo sketch for https://protosupplies.com/product/mini-platform-teensy41/ Memory Usage on Teensy 4.1: FLASH: code:217808, data:26680, headers:8436 free for files:7873540 RAM1...

During printing no Position data will be buffered. After printing the bufferWriteIndex is not reset, so no more data will be collected. Setting up a second buffer might be enough to allow continued logging during prints, or a large enough circular buffer of some type.

Can Confirm. Using @KurtE github source Can't type much but this line: https://github.com/Defragster/AudioTutorialProtoMini/blob/main/ProtoSuppSD/Teensy_41_Demo_Mini_Platform/Teensy_41_Demo_Mini_Platform.ino#L182 Rotation 1,3,4 give BLUE screen background and 3 Buttons with RED background - all...

Future: Looking at the T_4.0 card you'll see a Program Pin hole. If that is held to GND the Teensy will enter the bootloader mode same as if the button was pushed.

Just seeing: Serial baud rate: 115200 No sure how that factors in as it seems a level shifter brings the encoder to the Teensy?

Glad the buffering showed the nature of the problem. Given that it is expected that during the printing as noted in p#4 that the encoder continues piling up changes that are unread. Not clear why the printing is needed? The more printing the more misses of the values. Also what the end result...

On the @Dogbone06 board I tried 6 (6.5?) up over 12 and the one board I had did better with 12 - but 10 was a good sweet spot on that layout for the other boards together all going a bit over 200 MHz - and some over the 220 as noted. Indeed, CAP location seems important - PJRC wanted them on...

Seems the computer is not recognizing it then as Teensy or other usb serial as it will work with other devices. Have not done it in some time - but there are ways to see and remove recognized USB devices. Perhaps do a simple sketch with Dual USB and see if TyCommander shows it then as that...

quick guess might be taking too long to print and report the data. By the time the IF() exits the next reading is ready so if falls behind showing missed readings? Perhaps the prints catch up then showing the record low short interval. Make an array of [100][3] for the reading values to print...

This: Your key.pem file is stored in your "sketchbook" folder, which by default is {Documents}/Arduino. If you change the sketchbook location from File > Preferences, the Arduino IDE may need to be restarted before your key.pem file is used from the new location. from ...

Not used Win 10 in a long time - Paul does have diagnostic scans to do in a CMD window that might show the associations the PJRC SerMon finds. This isn't a fix - but a possible workaround (that has been in use here forever) - download and use TyCommander to see if the Teensy is visible to this...

I have one on my desk now from @KenHahn and finding the @KurtE ST7796 Branch to work. Would be great to have it incorporated in next Beta. Viewing angle is great. Nice size and resolution. Just getting started but it is a big improvement in many ways - yet not too big - and touch is working.

Yes, that. Paul once noted IIRC that was to ID the PCB maker? ... I found three here and they all had the same hashes with 1062 dates: 2117, 2007 - the third recent from @KenHahn is screwed back under display. Another pair dated 2232 PJRC sent in Feb 2023 and have the same Hash code { sh LONG sh...

Post linked in #4 was T_4.0 so could test there as well as T_3.2 No resolution or test results or fix notes after this 2023: https://www.pjrc.com/teensy/td_uart.html Seems a simple test - probably more than can be done here with mostly just a left hand that is usable

Odd, linked post suggested old problem that should have gotten fixed - maybe it broke again since?

See here : https://forum.pjrc.com/index.php?threads/doubt-regarding-setrx-function-in-teensy-4-0.69293/post-319768 try: Serial2.begin(9600); Serial2.setRX(26); Serial2.setTX(31);

Wonder what they'll do with the PCB silkscreen bit hashes by the USB connector maybe?

A bit of overkill for sure :) - but watching the video one is handling the line steering and the other purposefully isolated for motor drivers as the goal was to measure current draw for the motors HI Frank!

Does a 15 second Restore press of the PGM Button until the USB end RED LED gives a flash to release do anything? That ideally would restore a factory Blink sketch.

Are there any hot components? Was it connected to anything before? In use for any good time before that?

Twin T_4.0's in action Treadmill vs. Real Hill: Which is harder to run

Using CrashReport()'ing in setup after Serial is established will give some info of the fault causing the restart that might be helpful https://www.pjrc.com/teensy/td_crashreport.html

My first check out attempt gave a long fail string as well - maybe like p#1 - clip gone now. Backed up and item in cart and worked on second attempt.

yield() is called each time before loop() re-enters. yield() can be called elsewhere to trigger the serialEvent#() functions. It has relatively efficient parsing of all the active UART Serial ports in use. delay() calls yield - but that would add wasted millis's. But, any tight or time abusive...

If it isn't down more than that after 6 months - the RTC is somehow not feeding off of it. That would explain it not holding time. Is the voltage being read from the Teensy vBat pin against GND? And there will be measurable uA of current used - some posts noted - not sure IIRC it was like 40...