Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

awneil — Tue, 02 Jun 2020 11:49:26 GMT

Note that the last request was 9 months ago, and got no reply - so seems that blueshifting is no longer listening

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

Athan.Kok — Tue, 02 Jun 2020 11:18:58 GMT

Hi,I am interested in the SPI solution too if possible.

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

Mihal — Wed, 11 Sep 2019 14:37:31 GMT

hi. it would be nice. i'm interested in spi solution.

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

Sarp — Wed, 11 Sep 2019 10:38:50 GMT

I have implemented SPI functions but not QSPI, I can share my lib with you if you wish.
Now, I am at the start stage to implement FATFS to W25N01GV. Did you proceed a bit? Does anyone have a suggestion, sample guide or sth?

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

Nick — Tue, 23 Apr 2019 07:45:31 GMT

Using the basic QSPI examples to talk to the W25N01GV is never actually writing to backing flash, as you already determined (it wouldn't persist across power cycles). For one, the W25N01GV boots with all pages write-protected via the BP bits of the Protection Register (Status Register 1). This must be cleared before any persistent writes (technically, Page Program operations) can succeed. If you checked the P-FAIL bit of Status Register 3, you'd likely find it set high, if the write was truly attempted at all.

I've been able to drag the W25N01GV through most of its capability via extensive use of CINSTR, though I'm still only able to operate it via FASTREAD/PP 1x interfaces, and can only write 512 bytes to each 2048 byte NAND page. Look at the interfaces implemented by the nrRF52840 and the W25N01GV, and they quite clearly don't match up. Throw away the SDK's QSPI driver, save to use it as a map to QSPI HAL. You then must look at what the Winbond needs sent, see if there's anything that matches it in the nRF52840. There are few matches, so expect to implement most things with CINSTR.

Good luck!

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

blueshifting — Fri, 08 Feb 2019 23:26:57 GMT

@Mihal we can discuss our implementation of a driver on a Slack I've created. My intention was to make an unofficial slack for people working on nRF platforms to discuss topics that might not be significant enough to post here. You (and anyone else) should be able to join it at this slack invitation link.

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

Mihal — Fri, 08 Feb 2019 22:11:36 GMT

yeah, sure. it looks quite big and bothersome to make it alone.

i have also found some kind of winbond nand driver by the link. can't say that i understand anything though

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

blueshifting — Fri, 08 Feb 2019 21:58:04 GMT

Thanks, I’ll look for that. Perhaps this is a project we can tackle together?

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

Mihal — Fri, 08 Feb 2019 21:55:00 GMT

btw, i've just found an app note "Migration Guide from SPI NOR to SPI NAND" on official winbond page. i can't check it all right now but it must be helpful if you'll try modify some 3rd party driver.

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

Mihal — Fri, 08 Feb 2019 21:36:32 GMT

well, i think it's possible to make a kind of your own driver by encapsulating bunches of nrfx_qspi_cinstr_xfer(). But it's blocking as i can see, so there is another big problem. maybe it's possible to combine them somehow with standard read/write

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

blueshifting — Fri, 08 Feb 2019 21:17:36 GMT

I noticed the same thing: basic qspi write and validate read works, but the general state of the Nordic QSPI peripheral seems unsuited for NAND SPI flash. I will also admit not fully understanding how QSPI works - particularly when it comes to opcodes and write-enables, etc.

Currently I've been thinking about using SPI3 @ 32Mhz instead of QSPI and accessing the flash that way.

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

Mihal — Fri, 08 Feb 2019 21:12:59 GMT

Well. Actually i think my problem is in a different plane. Looks like i can't access memory properly.

Data is valid if i do a simple write/read test like in qspi example. But it does not stay the same after power down and addressing works weird. So i think that problem is in the different set of commands implemented in W25N01GV and in a chip used in PDK.

But the point is that i don't really understand how qspi driver works and whether i can fix it. Well, it's pretty clear that each function encapsulate a whole set of memory instructions but i guess there are no source in open access

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

Edvin — Fri, 01 Feb 2019 07:59:10 GMT

Hello,

At least in SDK15.2.0 the usbd_msc project uses QSPI. Although it only creates random files (random file names) instead of writing to the files, it is possible to use this project to write in the files as well.

If you replace fatfs_file_create() with this function:

static void fatfs_create_test_file(void)
{
    FRESULT ff_result;
    FIL file;
    uint32_t file_size = 0;

    ff_result = f_open(&file, "my_file.txt", FA_READ);
    if (ff_result != FR_OK)
    {
        NRF_LOG_ERROR("my_file.txt Does not exist\r\n");
        NRF_LOG_INFO("Creating my_file.txt");
        ff_result = f_open(&file, "my_file.txt", FA_CREATE_ALWAYS | FA_WRITE);
        if (ff_result != FR_OK)
        {
            if(!m_usb_connected)
                NRF_LOG_ERROR("Unable to open or create file: my_file.txt");
            NRF_LOG_FLUSH();
            return;
        }
    }

    ff_result = f_close(&file);
    if (ff_result != FR_OK)
    {
        NRF_LOG_ERROR("Unable to close file: %u \r\n", ff_result);
        NRF_LOG_FLUSH();
        return;
    }

    file_size = f_size(&file);
    NRF_LOG_INFO("my_file.txt create SUCCESSFUL; file size = %d\r\n", file_size);
}

To create a specific file, and then you can use a function similar to this to write data to the file:

static void write()
{
    int i = 0;
    char log_record[128] = {0};
    char log_record_r[128] = {0};

    FRESULT ff_result;
    FIL file;
    uint32_t fileSize;

    ff_result = f_open(&file, "my_file.txt", FA_OPEN_APPEND | FA_OPEN_ALWAYS | FA_WRITE | FA_READ);
    if (ff_result != FR_OK)
    {
        if(!m_usb_connected)
            NRF_LOG_INFO("Unable to open or create my_file.txt: %u", ff_result);
        NRF_LOG_FLUSH();
        return;
    }


    sprintf(log_record, "Helloworld!\r\n");


    FSIZE_t ptr = f_tell(&file);

    i = f_printf(&file, log_record);

    i = f_close(&file);
    if (i != 0)
    {
      NRF_LOG_INFO("f_close != 0, %d", i);
    }

    NRF_LOG_INFO("Wrote Data Record");
}

Best regards,

Edvin

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

blueshifting — Fri, 01 Feb 2019 00:51:24 GMT

I've not, though I've some ideas on how I'm going to do it. Just haven't gotten to that task yet.

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

Mihal — Fri, 01 Feb 2019 00:50:23 GMT

Hi, have you solved it? I have problems with this memory too

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

Edvin — Tue, 02 Oct 2018 12:42:03 GMT

Alternatively, you can check out the QSPI example.

Be aware that there is a current consumption bug in the QSPI. It is not very important when you just want to test this, but be aware of this before finishing your application.

It is the errata number 122 in this document.

I would suggest you check out the SDK\examples\peripheral\qspi example, since it looks like the W25N01GV supports QSPI.

You can easily test this example if you have the nRF52840DK, which uses QSPI on the flash storage chip on the DK.

If you want to change the pins that the QSPI uses, these are decided in sdk_config.h. Note that when they are defined as NRF_QSPI_PIN_NOT_CONNECTED, it will use the default pins that are defined in pca10056.h.

Also note that you may experience some weird behavior if you have long cables/PCB traces, and the QSPI_CONFIG_FREQUENCY is very high.

Best regards,

Edvin

RE: Help Wanted: nRF52840 QSPI + FatFS to Winbond W25N01GV

awneil — Tue, 02 Oct 2018 07:40:29 GMT

Have you looked at the FatFs documentaion?

That describes how to adapt the FatFs code to any target - basically, there is only one target-dependent file ...