• State Not Answered
  • +1 person also asked this people also asked this
  • Replies 11 replies
  • Subscribers 64 subscribers
  • Views 7588 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 127105
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

External Flash and QSPI Settings

Fan Jiaming

I have tried to study the behavior of the QSPI and the external flash. I noticed that the QSPI_CONFIG_READOC and QSPI_CONFIG_WRITEOC settings in sdk_config.h cannot be set to use a higher data lines.

More specifically, the QSPI_CONFIG_READOC can only be set to Read2IO and QSPI_CONFIG_WRITEOC to PP. Anything above would cause the FATFS module to throw an error and the USB MSC to not recognize the drive (For some reasons, PP2O works on USB MSC but not FATFS).

I have set QSPI_CONFIG_SCK_DELAY to 255 and QSPI_CONFIG_FREQUENCY to 32MHz/16, so it might not be a clock issue.

Anyone succesfully use more data lines?

Parents
  • 0

    I tested it with the MX25R64 chip onboard, I trimmed off the excess code for the other block device and left only QSPI. But as soon as I use more data lines, the FATFS cannot mount the chip with FR_NO_FILESYSTEM as the return value and USB MSC unable to open the drive as well as do any write operations. Only after I return to use FASTREAD and PP, and reformat the chip then it becomes usable.

Reply
  • 0

    I tested it with the MX25R64 chip onboard, I trimmed off the excess code for the other block device and left only QSPI. But as soon as I use more data lines, the FATFS cannot mount the chip with FR_NO_FILESYSTEM as the return value and USB MSC unable to open the drive as well as do any write operations. Only after I return to use FASTREAD and PP, and reformat the chip then it becomes usable.

Children
No Data
Related