• State Not Answered
  • +1 person also asked this people also asked this
  • Replies 11 replies
  • Subscribers 65 subscribers
  • Views 7614 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

    Yes, I tried the qspi example without any modification and it works. I am aware that it is using READ4IO and PP4IO, that's why I am confused why the USB MSC example doesn't work with that. I did not mix the FATFS with the USB MSC, in the original example, the FATFS is uninitialied before the USB MSC is turned on. When I do the modification, I keep that part as well. In fact, I merely deleted the instantiation of the other block devices and the rest of the initialization and handlers and their contents remain the same. If it is possible, may be you could also try to adjust the setting in the USB MSC example? If the issues are really with the setting, changing it in the example without any other modification should be enough to trigger the error.

Reply
  • 0

    Yes, I tried the qspi example without any modification and it works. I am aware that it is using READ4IO and PP4IO, that's why I am confused why the USB MSC example doesn't work with that. I did not mix the FATFS with the USB MSC, in the original example, the FATFS is uninitialied before the USB MSC is turned on. When I do the modification, I keep that part as well. In fact, I merely deleted the instantiation of the other block devices and the rest of the initialization and handlers and their contents remain the same. If it is possible, may be you could also try to adjust the setting in the USB MSC example? If the issues are really with the setting, changing it in the example without any other modification should be enough to trigger the error.

Children
No Data
Related