• State Verified Answer
  • Replies 23 replies
  • Subscribers 76 subscribers
  • Views 4848 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 276024
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Changing Flash parameters in overlay file

CktDesigner

My project is using nRF52840.   Early software development used an nRF52840-DK to develop most of the software.   Software is based on Zephyr using nRF Connect version 1.6.1.     I'm using the "littlefs" file system.   I got most things working using the nRF52840-DK.     I now have my custom board and it uses a slightly different (and larger) qspi-nor flash device.   

I'm still using the nRF52840-DK board file, but "modify" some of the parameters using an overlay file.    I know I need to change some of the parameters w.r.t. the flash.    I was able to modify the jedec-id for the new device, but am looking for some documentation that defines the parameters (keywords) in the board definition file (what some of them mean and format of values)   

Can you point me to these definitions (so I don't have to read through a lot of code :-))?

Thanks!

  • 0 in reply to Simonr

    Yes, I'm using the project you referenced.

    But in main.c at lines 20 through 32 it defines "PARTITION_MODE" which references /lfs1 which is defined in the overlay file.   There, the partition /lfs1_part is referenced which is defined in the &mx25r64, which is the Flash device connected via the qspi bus.   

    So by default, the example uses the external flash.    I think to use the SOC flash you have to comment out the definition of PARTITION_MODE on main.c line 20...

    I needed to add the jedec-id line to redefine the device id to the one I'm using on my custom board.   When it still didn't work I thought that some other parameter must need to be adjusted but didn't see any concise definitions for these parameters.

  • 0

    Hi again

    Yes, you seem to be right indeed. 

    I have looked at the Macronix and Cypress write procedures, and they seem very similar, so I've not been able to track down what exact changes are necessary to be done yet, but I have a few suggestions, and I'm also awaiting a reply from our FS/QSPI experts (I hoped they got back to me by today, but they have not). I will update you as soon as I hear from them.

    You can try setting the size in your overlay file to match the size of your Cypress chip. Since you're able to read the JEDEC ID correctly for instance, the flash chip seems to be set up correctly, but the file system procedure is what's not working as intended.

    Best regards,

    Simon

  • 0 in reply to Simonr

    OK, thanks.

    I updated the overlay to reflect the 128 Mbit size of the Cypress part, but it didn't make any difference.    Still fails during format with error code of -5.

    Thanks again...

  • 0

    Hi

    I have asked our development team to take a look at this, but I'm still waiting for a reply there. Hopefully I'll hear back either today or just over the weekend. Thank you for your patience.

    Best regards,

    Simon

  • 0 in reply to Simonr

    Hi Simon,

    I moved on to other issues (and other projects), but am now back to trying to solve this issue.

    I'm now using NCS 2.0.0 but having the same issues.     I'm actually using two LFS volumes.  One uses an on-chip storage partition (and works well), and the other attempts to mount the qspi-nor device (for larger data files) and is still having issues mounting...

    Any thoughts?

    Thanks!

Related
Terms of service