Search results

Let me clarify: The "PSRAM failure I originally noted." refers to a data corruption problem using the updated core code, not a hardware problem. In my project code I set up my array of structures and then initialise it to all zeros: The standard core code works perfectly, as expected, whilst...

Okay, so my MRAM has arrived and I have fitted one to an unused Teensy 4.1. Testing my project with the updated code fails with MRAM in a similar way to the PSRAM failure I originally noted. So, my conclusion is that either I am not configuring it correctly or there is something wrong in the...

I was referring to his posting notes on his work, not on the price of MRAM (which I bought 512k parts from Mouser ...).

He gives the GitHub project reference at the end of this thread ... Not too expensive so I ordered mine before Christmas, so they are due now (Monday as FedEx don't normally deliver at the weekend). As I said, I tried the updates with the standard PSRAM, which is supposed to work unaltered but...

Moving my queries to a more relevant thread since PROGMEM was not the problem ... I did a search and found this thread, which contains a link to a GitHub project. This project contains a number of updates to enable the use of MRAM and varying memory sizes on the extra memory pads. Has anybody...

The device I have ordered is a 3V one AS3004204 Yes, I have looked at the existing core code and see that there are many issues but Michael MacDonald has seemingly addressed them in his (untested?) GitHub project.

I realised, after posting, that I had gone somewhat off topic from my original enquiry so I did a search on PSRAM alternatives and found a 3 year old thread about using MRAM : by Michael MacDonald The MRAM he uses is of similar speed to the PSRAM (108 MHz clock). So I decided to give it a try...

I have taken another look at implementing LittleFS and it seems rather involved for what I want to do so I started to consider other possible? solutions. Battery backup for the QSPI_PSRAM and use EXTMEM for non-volatile storage ... Not a foolproof solution since the battery could discharge and...

Thanks Paul. I should have realised that there is a lot going on for storing in flash, I did it many years ago in a works project. Since this project is an upgrade to a previous version and a step towards a far more complex version, implementing LittleFS can be done now rather than later. I did...

Ha-ha-ha ... perhaps I should have checked that first ... Well, I haven't lost much time and I've learnt something ...

Yes. This is the current working version of the project with the array of structures in RAM. teensy_size: Memory Usage on Teensy 4.1: teensy_size: FLASH: code:97532, data:298632, headers:8312 free for files:7721988 teensy_size: RAM1: variables:381120, code:91304, padding:7000 free for...

Thank you. That would explain why I could not find anything defining the size of PROGMEM. I am using PlatformIO in VScode so the term 'sketch' does not apply, not that that has any effect. I shall recheck the error message I got on compile and also recalculate my expected flash usage, I may well...

Thanks for your reply. I was hoping that there would be something like a definition of PROGMEM somewhere within the core files which could be changed to allocate more flash but maybe this is not considered a wise move. I had looked at LittleFS_QSPIFlash but decided that creating a filesystem...

My project uses a large array of complex structures which I would like to retain in non-volatile memory. Rather than setting up a LittleFS Filesystem to load and save the data, is there a way in which the PROGMEM section could be remapped to use the LitttleFS area in main Flash, or even the...