LAUNCHXL-CC1310: 15.4 Stack native OAD not working

Martin,
is the NVS driver trying to write more than 256 bytes in a row? There has been a bug discovered in the NVS driver last week. As a work-around, write operations need to be limited to 256 bytes chunks.

Hi Martin,

thank you for reporting. I confirm your observations and filed a bug report for the TIDRIVERS team. The NVSSPI examples do neither work on the CC1310 nor on the CC1350 launchpads. So it's actually the NVSSPI driver.

There's a bug in the nvs and nvsspi examples that shows up if the flash region being exercised was not in the erased state when the example first runs. A workaround is to change this code

 else {
    Display_printf(displayHandle, 0, 0, "Writing signature to flash...");

    /* Write signature to memory */
    NVS_write(nvsHandle, 0, (void *) signature, sizeof(signature),
    NVS_WRITE_PRE_VERIFY | NVS_WRITE_POST_VERIFY);
 }

to this:

 else {
    Display_printf(displayHandle, 0, 0, "Writing signature to flash...");

    /* Erase the entire flash region */
    NVS_erase(nvsHandle, 0, regionAttrs.regionSize);

    /* Write signature to memory */
    NVS_write(nvsHandle, 0, (void *) signature, sizeof(signature),
       NVS_WRITE_PRE_VERIFY | NVS_WRITE_POST_VERIFY);
 }

The examples will be fixed in 3.30.

There's another issue in the SPICC26XX driver that constrains SPI transfers to 1024 bytes or less. Consequently, attempts to read more than 1024 bytes from the SPI flash at a time will quietly fail. This issue can be worked around in user code by breaking the read into blocks of 1024 bytes or less.
Another solution is to include the NVSSPI25X.c file in your project and substitute the following implementation of NVSSPI25X_read():

/*
 *  ======== NVSSPI25X_read =======
 */
int_fast16_t NVSSPI25X_read(NVS_Handle handle, size_t offset, void *buffer,
        size_t bufferSize)
{
    NVSSPI25X_HWAttrs const *hwAttrs;
    size_t xferSize;
    uint8_t *dstBuf;
    int retval = NVS_STATUS_SUCCESS;

    hwAttrs = handle->hwAttrs;

    /* Validate offset and bufferSize */
    if (offset + bufferSize > hwAttrs->regionSize) {
        return (NVS_STATUS_INV_OFFSET);
    }

    dstBuf = buffer;
    /*
     *  Get exclusive access to the region.  We don't want someone
     *  else to erase the region while we are reading it.
     */
    SemaphoreP_pend(writeSem, SemaphoreP_WAIT_FOREVER);

    /*
     * break read down into 1024 byte pieces to workaround TIDRIVERS-1173
     */
    while (bufferSize) {
        if (bufferSize <= 1024) {
            xferSize = bufferSize;
        }
        else {
            xferSize = 1024;
        }

        retval = doRead(handle, offset, dstBuf, xferSize);

        if (retval != NVS_STATUS_SUCCESS) {
            break;
        }
        else {
            offset += xferSize;
            dstBuf += xferSize;
            bufferSize -= xferSize;
        }
    }

    SemaphoreP_post(writeSem);

    return (retval);
}

This fixes the NVS example. It does not solve the original problem with 15.4 stack native oad though. I'll have a look to see if it could be a similar problem but would apprechiate if someone took a look at it from your side.

Thanks,

Martin