Example of how to read QSPI NOR Flash Device ID

RE: Example of how to read QSPI NOR Flash Device ID

ovrebekk — Fri, 14 Jun 2024 09:18:08 GMT

Good to hear you found the issue, and thanks for sharing the solution 🙂

RE: Example of how to read QSPI NOR Flash Device ID

Josh — Thu, 13 Jun 2024 21:14:41 GMT

Ok looks like I got it working now. Here is the code for others to reference

/* get the manufacturer and device id of the qspi flash ic
   this flash ic has multiple variants (8 Mb, 16 or 32Mb) which have different device id
   it's up to the developer to know which one to look for after calling this function
   the manufacturer id should always be 0x1F
   the 8Mb dev id is 0x45 and the 32Mb version is 0x47 (for example)
*/

NVM_ERROR at25ffxxxx_get_id(at25ffxxxx_t *self, uint8_t *dev_id, uint8_t *manf_id)
{
    if(NULL == self || NULL == dev_id || NULL == manf_id)
    {
        return NVM_ERROR_INVALID_POINTER;
    }
    nrfx_err_t err_code;
    // Initialize QSPI peripheral
    uint8_t dummy_addr_bytes[8] = {0};
    uint8_t read_bytes[8] = {0};

    // Configure QSPI command
    nrf_qspi_cinstr_conf_t cinstr_cfg = {
        .opcode    = CMD_READ_MANUFACTURER_DEVICE_ID,
        .length    = 6, // cmd bytes + 3 addr bytes + 2 data bytes
        .io2_level = true,
        .io3_level = true,
        .wipwait   = true,
        .wren      = false
    };
    

    // Send command with dummy bytes
    err_code = nrfx_qspi_cinstr_xfer(&cinstr_cfg, &dummy_addr_bytes, read_bytes);

    
    // Output results
    if(NRFX_SUCCESS != err_code)
    {
        NRF_LOG_ERROR("nrfx_qspi_cinstr_xfer err: %d\n", err_code);
    }

    for(int i = 0; i<sizeof(read_bytes); i++)
    {
        NRF_LOG_ERROR("%d 0x%X\n", i, read_bytes[i]);
    }
    *manf_id = read_bytes[3];
    *dev_id = read_bytes[4];
    return err_code == NRFX_SUCCESS ? NVM_ERROR_NONE : NVM_ERROR_READ_DEVID_FAILED;
}

RE: Example of how to read QSPI NOR Flash Device ID

Josh — Thu, 13 Jun 2024 18:16:59 GMT

Also, I am able to write and read data from the flash IC

it's just the device id I can't read

RE: Example of how to read QSPI NOR Flash Device ID

Josh — Thu, 13 Jun 2024 17:33:18 GMT

That is one way to do it, reset then read the id

but we want to read the device id after a reset as well (sometime later).

I guess, my worry is I'm not using nrfx_qspi_cinstr_xfer function correctly.

If the datasheet says it needs us to send the 1 byte opcode and then 3 dummy (addr) bytes before it sends back the 2 databytes then am I using the nrf sdk function correctly?

RE: Example of how to read QSPI NOR Flash Device ID

ovrebekk — Thu, 13 Jun 2024 12:09:13 GMT

Often you need to send a reset command first, before reading out the Jedec ID. Have you checked the datasheet if this is necessary?

Have you tried to probe the QSPI lines with a scope or logic analyzer to see if the output is as you expect?

Just looking at the code I can't really spot the issue.

Best regards
Torbjørn