mjs513
Senior Member+

Ok just pushed the last update to plusNAND as well @Paul 's LittleFS library. I added support for Bad Block Management (BBM) for the M02. As I said before its not turned on (didn't send the command). Reason: Not...

@PaulStoffregen - @defragster - @KurtE In regards to BBM on the W25N02 I contacted Winbond to see if it was an error in the datasheet for the N02. Well, I got back an answer today and basically its not supported: ...

Afternoon now for me. So afternoon. Oh man - frustrating when internet is down - been there. Ok saw where the case statement was missing. Added it in to MTP.cpp and that seems to resolve the issue with copying and...

Morning @KurtE - had my coffee now. T3.5 and T3.6 both build with no errors. But unless I missed something I can not copy any files to the flash (n01 in this case). However, I can copy from the flash to the...

Ok think I am lost on what changes need to be made to the core - think I am behind on some things. Is your core files updated and which branch can I use to be even the MTP changes. EDIT: Never Mind figure it out. ...

@WMXZ I have been using @KurtE's branch of MTP for testing so I left the 'd' in to test events - as a debug tool as you said.

At from me the answer is not to both - I do have a Teensy LC someplace but have to find what I did with it.

@defragster - @KurtE - @Paul Just did a few more tests using the MPT-logger sketch just as a sanity check and see if I got any ECC errors well everything worked. The below is a table of chips tested and whether they...

Very cool Frank - thanks for adding Hardfaults was a nice feature

Just out of curiosity did you try it the way T3.x does it - probably should run a test to see if it works. Stay tuned EDIT: You probably know this but getting usb event errors on compile for the T3.5"...

@defragster - @KurtE Pretty much what Kurt said - there is some sort of conflict but didn't spend much time tracking it down specifically as I just rewrote to get rid of I2S/DMA and use the MPU-9250 to get real data. ...

Just as a heads up and by way of explanation of the libraries: teensy41_extram - only used for direct writing to the PSRAM and is a bit out dated and really doesn't need to be used anymore. Do a search on EXTMEM there...

Ok - reworked the mtp-logger example to just read data from MPU-9250 and store it on any of our flash chips, now it works no problem with the NAND on QSPI. Must be that conflict @KurtE mentioned. If you want to play:...

Ok just wrote a simple test case that seems to be working - probably do better on next update but wanted to see if this was going to work and it did - so probably a conflict as you identified: Logger Device ID:...

Morning - all mornings seem to be the same lately. Yep - made sure of that. Right now I am in the process of putting together a basic logger using similar functions for creating files/directories and writing data....

@KurtE - @defragster Still puzzling me about the problem with using the MTP logger. Wondering if there is some sort of issue with using DMA and/or I2S with QSPI NAND Flash? But funny thing is that it does work with...

@KurtE Of course it would be nice to have a file creation or file modified date but as you said not sure how LittleFS supports that. I was reading that LFS has custom attributes that you can set and doing a search...

@defragster - @KurtE Decided to try to modify the MTP_logger example to work with the selected device for logging data. I tested SD, SPI, QSPI, and SPI NAND which all worked without an issue. However, when I tried...

@KurtE = @defragster Just pushed an update to plusNAND to bring LittleFS even with what I have updated for NAND. In the READ_BCC test case I added a quick test of the addbblut function - I think I got it working...

Good Morning @KurtE I finally got to download your latest updates and they seem to be working. If I hit F5 on the PC they do show up. The other commands seem to working as well I tried the 'd' command and that...

@KurtE Thanks Kurt for the info Kurt. Think the stuff for keep reading the data actually helped. If I remember right when I was using it I was able to transfer the 5Mb file. Maybe its worth putting back in at some...

Yep that's the latest. I did the push yesterday for the BBLUT stuff so not sure if you have those changes in your version.

@KurtE Ok I did what I described in post #591. It recognized the N01 and N02 chips on the memory breakout board was able to create a directory and copy files up to 1.1Mb and the was able open/delete them. However if...

Morning @KurtE See you have been busy again :) Anyway so if I am reading your post right I should go ahead update the core with your changes: https://github.com/PaulStoffregen/cores/pull/532 and then use your...

Took your advice and issued a PR (Updated for NAND/FeRAM.Fram and tweaks) for what we have so far.

That looks like my breakout board C that I tested successfully with the SPI. Just for reference I am using the Bolderflight library with the 200 ns delays which is the PR that was referenced. However, the standalone...

Just as a quick update I reconfigured BreakoutBoard D to use SPI1: #define PIN_MISO1 1 #define PIN_MOSI1 26 #define PIN_SCK1 27 #define PIN_CS1 10 or 0 Again...

Ok just got back to this. Unfortunately I deleted my original message before hitting save so this is just a summary. Tested with 4 different breakout boards: Breakout Board A: DOA both for I2C and SPI. Scanner...

Don't think the problem is with Teensy as @WMXZ stated. Believe there is a problem with SPI implementation with the library. As a quick and dirty test for SPI with the MPU-9250 I updated an old test library I had...

Just tried a couple things moved it over to SPI and used CS = 10. See failure to correctly who I am register - getting 112 instead of 113/115. There is already a delaynanoseconds(200) with beginTransactions. This...

Great - another data point. Just hooked up my DFRobot BMP388 to a Teensy 4.0 and its working without a problem. Just got it last night but was distracted with LittleFS again. EDIT: Think I put back the delay(40)...

@KurtE - @defragster -@PaulStoffregen Just pushed a change up to the repository for W25N01G NAND flash to support Bad Block Management. I brought it to the point of actually writing the Table. A little reluctant to...

As you probably noticed LadyAda requested a PR for them to evaluate so I just sent them a PR: https://github.com/adafruit/Adafruit_BMP3XX/pull/14. EDIT: Quick up the Adafruit Library has been updated.

@KurtE Totally a loss at this point. Something definitely odd going on. For my Flash QSPI tests I used a kludged setup where I solder wires from the Flash pad to a set of headers for the flash chip and it seems to...

First the W25Q16JV-DTR is a NOR Flash chip, yes I know that the datasheet is silent on it but if you do a searching you will find that Mouser and Winbond shows it as a NOR flash. Second if you don't include the...

@KurtE Ok - I am at a loss now especially since neither pass the teensy41_psram_memtest sketch. That should have worked. Out of curiosity did you ever give it a try with our old (very old teensy41_extram library...

Yeah - know the feeling. Glad its working for you.

Saw that as well. Got lost after that as I couldn't visualize how sm_malloc was interfacing with PSRAM/FLEXSPI commands for read/write? Just didn't see the linkage between the two

Cool glad thats all it was.

Just as a quick follow up to yesterday's post I just tested the sketch on the Uno, Due, Mega and a Teensy 3.5 with the delay(40) removed and it seemed to work with an issue.

First you are not crazy. Received my BMP390 from Adafruit today and hooked it up to a Teensy 4.0 and got the same results that you showed in your post #13. Tried a couple of things but was failing but then I went to...

When I was looking at that yesterday it didn't make a lot of sense to me. Looked like in the configure function it tested the JEDEC (so that should be 2 reads) for each position of the ram. But then it just called off...

The pins look correct but as I mentioned are hooked up correctly to the Teensy 3.5 For SPI1: sck -> pin 32 cs -> pin 31 miso -> pin 1 mosi -> pin 0 then of course you have: #define RFM69_RST 24

Found my RF69HCW radio from Adafruit (https://www.adafruit.com/product/3070) and ran the sketch the modified rf69_tx_demo sketch that I mentioned but configured for SPI and I can't seem to duplicate your error about not...

@KurtE Looks like we cross posted :)

Just taking a quick look at the examples and the lib for the RH_RF69 looks like you can specify SPI1 or SPI1 (default is SPI). For instance, from the rf69_tx_demo.ino in the Teensy example folder: //For Teensy 3.x and...

Well, glad you found a potential issue but not good it a short on the castellated board. Hope you can get it fixed.

Morning @KurtE Was just going through the thread and you new message popped up. Why back when when we did PSRAM as a standalone library after Paul gave us the starting code and Frank B expanded on it we were using the...

@defragster - @KurtE Just pushed a minor change to the readECC function in the lib to correct an addressing issue that was bothering me. Yes I am feeling better now.

Just catching up as been a bit out of it for several days. But I just ordered one from Adafruit and should be Tuesday afternoon.

You as well Frank and all my other friends and forum members!! HAPPY NEW YEAR 2021 Stay safe and healthy :)

Great that is working and yep no more manual updates :)

You all sound like you are having way too much fun with MTP :)

Maybe not with Arduino 1.8.10 but definitely between Teensyduino versions. I just tested the sketch with 1.8.10 with TD 1.50 and didn't receive a compile error. So would recommend updating - besides a lot of things...

Right now ECC is enabled but BBM is not enforced :) Basically right now it lets me know when I messed something up with devel code - when I see ECC errors I go check what I did. Right now its pretty stable.

I just compiled the SimpleEncoder sketch on the T4.0 and the T4.1 and didn't receive any error messages from the library. Right now I am using Arduino 1.8.13 with the Teensyduino 1.53- beta5. So really need a bit...

thanks Kurt. Thats kind of what I was thinking as well but think its going to be Paul's call.

@defragster - @KurtE I think I figured out how ECC bad block management works for at least the W25N01 and probably the W25M02 (think I have to fix something with readBLUT function though - maybe). But makes it alot...

Oops = forgot to push the button. Just did it now - LFSIntegrity PlusNAND branch. Thanks :)

@defragster - @KurtE Pushed a update to the NAND lib to fix a couple of bugs I have in readECC function (SPI and QSPI). Going to see what happens if I add an error to the BBLUT table and enable BBM. Going to take a...

@defragster Runs look good - just about matches what I saw on the standalone versions. Thanks for adding :)

@KurtE = looking good. EF7020 - Winbond W25Q512JV*IM (DTR) from the list of FLASH chips :) Can't wait to see QSPI.

Ok. I was right SdFat allows you do cout stuff. Replace Streaming.h and #define cout with the following 2 lines: #include <sdios.h> // Serial output stream ArduinoOutStream cout(Serial); Now no need for...

Actually now that I am thinking about it doesn’t safari have a streaming class. The cout came from the original bench sketch

Oops see it now. Answered on the beta5 thread. https://www.arduinolibraries.info/libraries/streaming Haven’t tried this version yet and I may have made some changes to the orignal

Sorry didn’t see that yet. Comes from here http://arduiniana.org/libraries/streaming/. I can’t remember if I made changes to it... been awhile. But looks like someone else is maintaining it ...

Great you got it working this far. Think I read in another thread on MTP that support for events on T3.x wasn't implemented yet?

Did a modification of the Bench sketch but using LittleFS_Program, and added in a random read timing loop. Write/Read blocksizes are 2048bytes and I used random to jump around the file (16k) in 2048 byte increments:...

First thanks for the explanation. Really does help. Have one question what is your definition of "MANY", have a feeling my definition would be a lot less than yours :)

Out of curiosity I ran the same bench sketch on the N01, N02 and the W25Q512JV on the SPI memory board: SPINAND SEQ BENCH TESTS FILE_SIZE_MB = 5 BUF_SIZE = 2048 bytes --------------------------------------- N02...

@defragster I was reading Paul's post in the beta5 thread and remembered that I put together a benchmark sketch based off of the SDFat benchmark sketch. So decided to run in on the N01 chip: LittleFS Test Device...

@defragster Bad wording since I didn't really explain. Wondering why the M02 can only reliably work at 55Mhz when using SPI as opposed to 75Mhz say.

Just ran a quick test using a N01 Flash: Total time to erase to the 1Gbytes is: Done Formatting Low Level in 4240999 us. or 4.2 seconds from 1024 blocks of 128K. Looks like total wait time for each block erase is...

@KurtE Depending what sketch you are using you might have different speeds set up. If I remember right PSRAM/QPI is running at 88Mhz and if you are running SPI in from LittleFS its using 30Mhz. Are you testing the...

A couple of things. Both PSRAM and QPI use a mix of 2 pin IO (IO0 and IO1) and 4 pin (IO0, IO1, IO2 and IO3) commands. For instance JEDEC and read/writeregister only use IO0/IO1, READ/WRITES use IO0-4. So what you...

@KurtE Looks like it is working from what I can say for the JEDEC anyway. MOSI is showing the command 9F which is the read JEDEC command and then it reading 3 bytes from the MISO line which is 0xEF, 0x40 and 0x18. ...

@KurtE - @defragster Did just test the 512MB, 1GB(n01) and 2GB (n02) on the memory board with a T3.5. Running a couple of tests from LFSIntegrity received no errors and everything seemed operational. Just another...

Afternoon @KurtE Maybe a bad connection? I have been testing some of chips including the M02 on breakout I put together for QSPI. Curious. Which chip are using. M02? To be honest... would try the prebuilt version...

Tell me about - soldering those 0.10" pins are a challenge. About as small as I want to go with a soldering iron! But getting better at it :) @KurtE - @defragster - @Paul Getting ready to push an update to the...

That chip is going to be interesting. Looking at the data sheet I don't see the command to read the ID.

These are the only FRAM chips that are currently supported: {{0x03, 0x2E, 0xC2}, 24, 64, 128, 1048576, 250, 1200}, //Cypress 8Mb FRAM {{0xC2, 0x24, 0x00}, 24, 64, 128, 131072, 250, 1200}, //Cypress 1Mb FRAM...

that's correct for NAND I created a device erase function based on the D8h command which is a block erase of 128k at a shot. As you noticed deviceErase is alot faster especially for the larger chips over lowlevel...

Definitely doable but think you might want to check this post out as well: https://forum.pjrc.com/threads/58033-LittleFS-port-to-Teensy-SPIFlash?p=261313&viewfull=1#post261313. EDIT: Frank - don't use SerialFlash...

Thanks @KurtE - that's probably it, never really understood that syntax. Thanks for the explanation. Anyway changed to go the other way just because I wanted to get it working - which I did. Anyway, I just pushed...

I did get it working by doing the following but still would like to know what's wrong with the problem code: uint8_t die_select; cmd = 0xD8; //Block erase, 0xD8 if(pageAddr > pagesPerDie) { cmd = 1;...

@KurtE - @defragster Got something strange happening and I just can't seem to figure out what I am doing wrong. Probably something obvious but .... you know how that goes. First I soldered up a M02 so this is related...

Hi @Frank B. As far as I can tell the answer is no - there are no functions really to directly address the memory locations. LittleFS is file based so if you try writing directly to the chip you will probably mess up...

Short answer is especially for QSPI. At least for the W25Q128 and above. Not sure of the specs for the other Flash but I think 104Mhz for QSPI is a safe bet. For SPI 30Mhz seems good for FRAM which is a max of 40Mhz,...