defragster

And you soldered the connection, right?

I just got one of these (Thank's Ken) - I'm seeing the same results - and no solutions yet - but Found this: but strangely I can get only the zoom in and zoom out with my FT chip, In this 9 year old effort...

Is that Flash SD a 512MB device? That's small. That example uses SD.sdfs. Try it using one of the PJRC SD examples that don't use sdfs. Also Teensyduino ships with a specific version of SDFS - if there is another version in the libraries...

The println() has no expected affect - except blasting out 'CR+NL' 1999 times. Except noInterrupts() won't let that happen? So, if not that, then something unshown/unseen is causing trouble. 1Msamp/sec means this is happening 500 times/sec...

FINAL UPDATE: Changing the crystal to the correct 24 MHz fixed my problem and it is all working now!

Crosspost ... 'delay cycles' ... That explains why the DOCS and perf show write being 4X(?) faster. I wondered about the cache being undercut on return - that and the changes from configure. Can you post code for write?

Same here. p#18 was done looking to dual test the native access with the bitbang. Didn't find write_func(), but ran the test as posted, then found native access returning bad data just doing the fixed pattern write as coded in the PJRC example...

Can it write as well? After the PSRAM_Configure() - the normal access fails. Can it be undone to allow other code to use normally?

Great stuff

Lately been trying to consolidate/organize my IMU efforts and decided to grab a couple of new sensors that are used on the Nano Sense V2, the BMI270/BMM150 specifically. For reference Sparkfun has a BMI270 sensor and Waveshare has a BMM150...

Thx for (re)posting @mjs513. Just ran this (132.9 MHz) with the PJRC PSRAM test and times are faster: AFTER at 132: test ran for 25.52 seconds BEFORE at 88: test ran for 36.43 seconds 57 Write Read passes 8MB - where 44 need calc of next number...

Big thanks to @defragster for dogging this problem that had me stymied and to @KurtE for the quick fix!

Already did msg 17:)

Opps - I thought that was just a repeat of the github since I skipped before ... and skipped again Good work @KurtE <edit> Added a comment to PR that it was tested to work on T_4.1 board above, and two of the PCB's (with T_4.1)

Good to know @jmarsh @KurtE - are you going to do a PR? The pointer usage works - not sure about other changes No change in header or prototype - just referenced as a pointer now throughout the MANY uses in that file.

Yes... rewrite it because references don't work the way that code intends them. References can only be "bound" at creation, so static SPIClass& SPIPORT = SPI; mean SPIPORT will always refer to SPI. When the SerialFlashChip::begin() later tries...

POINTERS WORK! - skipped this for reading example code ... found and tested ... It is now back and working on the original board from @KenHahn Downloaded the ZIP and pulled JUST the SerialFlashChip.cpp file to this system and it works...

Opps - did not - read past that.

@PaulStoffregen or @jmarsh or other c++ nerd - is there a way to have this (p#12) properly resolved to specify alternate SPIClass& SPIPORT at runtime?

"Looks like" that shows the expected anticipated suggestion that the reference maps back to foo1 being the same thing? Seems easy test here is to do library hack: edit...

Yes, p#7 did show quote 'funny' I wasn't clear on the c++ there - but it works and passing in the requested info SerialFlash works without issue. Reading the code everything looked well ordered, with no hardcoded refs like to SPI or assumed...

Possible? Doesn't seem like that should be an issue. But these PJRC displays - as the only thing on an SPI bus just always work. Only the intro of a device on SPI1 - unique pins and software - creates this problem?

Thx @KurtE and @mjs513 SPI only has single device - PJRC ILI9341 with Touch. SPI1 has the SerialFlash on it - and nothing else. Display works in both cases. Touch works, unless SerialFlash is started. // LCD control pins defined by the...

Yeah, that's true. I haven't had any of the ones I've soldered short, but it's definitely close.

New observation: With SerFlash the Pin 13 LED is generally OFF and doesn't blink on at all! > Is something changing PinMode(13,OUTPUT) {or other SPI} for touch that Display write restores for the duration? Building "//THIS_GOOD" to disable...

Notes on the repro - with the setup done. Without setting it up the code compiled with 1.60Beta3 on IDE 2 using these libs: Using library ILI9341_t3 at version 1.0 in folder...

And it is faster if not bigger on the inside too. Congrats.

Got a board hosting a T_4.1 with SPI ILI9341 and a bunch of other stuff including 1Gb SerialFlash chip on SPI1 Removing everything but those thing from the DEMO sketch here...

@defragster Thank you. I didn't look closely. Thank you.

Yes, thank you for your reply. I really appreciate it. Have a nice day.

Glad it is showing working as expected. Asked about that in post #2

Does it look broken when run with a longer delay? Just to confirm the scope connects. What is the upper non-Green line showing Replace the WriteFast with ToggleFast after setting them out of sync like at the end of the If() Toggle works with...

Me too. Those pin numbers match what was found and marked to work on the prior page! p#6 What ESP32 variant is onboard?

Glad it is working

Thank you for your support :) I was using an old ILI9341_t3n lib from KurtE. The current lib ILI9341_t3n version 1.1.1 from KurtE it works very fine. Link: https://github.com/KurtE/ILI9341_t3n/commits/v1.1.1

I know this is a few years old, but in case anyone wants to do something like this going forward, I have something that may help. As I tried to do this while prototyping I ran into a few times where efforts to swap from one prototype board to...

That looks interesting and useful. Looking at Teensy it is scary how close VUSB pad is to that connector GND tab.

I'll be powering up a T_4.1 with ILI9341. Can you post a simple example program that shows the issue to repro test? When looking here in _T3N that code is not present and already fixed? ...

I solved my problem. I commented out the code lines in ILI9341_tn3.cpp Draw a character // Draw a character void ILI9341_t3n::drawChar(int16_t x, int16_t y, unsigned char c, uint16_t fgcolor, uint16_t bgcolor, uint8_t size_x, uint8_t...

It was c++\5.4.1. Changed it back and all is fine again. I'm not sure if it was me, the cat, a buggy OneDrive update, or something else. Thanks for the help guys. I was pulling my hair out yesterday.

Have seen OneDrive building noted as an issue before ... make sure all files are stored locally? Right Click 'local copy' - wait for SYNC to complete - haven't done it for a day so not sure of the text. And it was for somebody else as...

Misread it seems - but odd the code is perfectly filling the 32KB - it hasn't changed since p#6 - but odd the exact value was hit. So is PSTR() working as expected ? Any edits to example that would show other uses or value?

.....3h 35m later and still waiting.

Correct, I tried to recreate the issue in a short clear sketch that compiled without the Odd Error and allowed for with and without PSTR testing. Results below look to show improvement using PSTR when the three strings were edited with "One...

Just 25 more minutes to see the surprise ... Or so ....

Post #6 example code showed the same result! No change in RAM1 usage, but: data:5064 .vs. data:5508 and data:103360 .vs. data:103568 It looks like PSTR just places a Duplicate copy in Flash - but another copy also placed in the area...

The FLASHMEM and PROGMEM conflict ... Code in FLASH won't link with DATA in Flash giving the: "causes a section type conflict"? This works _ but only to change (duplicate?) DATA in FLASH? RAM1 DATA same in both?: void setup() { while...

Okay, we're definitely multitasking now. 20241123 03:32:07 connected to /dev/ttyACM0 press C-z q to exit DiscoBSD 2.3-current (TEENSY35) #109 576: Sat Nov 23 03:31:54 EET 2024 esp@tieteislaskin:/sys/mk64/teensy35 cpu: MK64FX512, 120...

That's great - if an 8 second auto restart occurs again the CrashReport may give a clue. That and the BreadCrumbs. Code above may be generally useful as follows. It will sit until SerMon connects - might be better if pin(13) were flashed...

Code to use Teensy as a USB PROXY is working here. But that expects computer to do the negotiation over USB and Teensy just passes it through after putting the ESP32 into program mode by UART. Not ever monitored the passing bits for content and...