RE: FATFS+QSPI+USBmsc bug

user13996 — Fri, 04 Jan 2019 14:02:50 GMT

Your response got deleted biaccidentally.

"Hi,Jeff

Not modified here, the p_erase_unit_buff inside the structure is already aligned with 4 bytes.

static ret_code_t block_dev_qspi_read_req(nrf_block_dev_t const * p_blk_dev,
nrf_block_req_t const * p_blk)

{

...

p_work->left_req = *p_blk;
p_work->req = *p_blk;
nrf_block_req_t * p_blk_left = &p_work->left_req;

p_work->state = NRF_BLOCK_DEV_QSPI_STATE_READ_EXEC;

ret = nrf_drv_qspi_read(p_blk_left->p_buff,
p_blk_left->blk_count * p_work->geometry.blk_size,
p_blk_left->blk_id * p_work->geometry.blk_size);

...

}

p_blk_left->p_buff , this buf's address maybe not aligned 4-bytes.

my project use freeRTOS, I don't use the example<nrf_block_dev_qspi.c>,I changed the code. Attach my code，you can refer to this."
test-devzone.nordicsemi.com/.../3173.my_5F00_block_5F00_dev_5F00_qspi.c test-devzone.nordicsemi.com/.../1512.QSPI_5F00_driver.c

RE: FATFS+QSPI+USBmsc bug

user9150 — Wed, 02 Jan 2019 02:57:06 GMT

I think it is the same problem, just modify the QSPI block driver code<nrf_block_dev_qspi.c>, let the write/read buf pointer address aligned 4bytes.

RE: FATFS+QSPI+USBmsc bug

user13996 — Wed, 26 Dec 2018 16:22:32 GMT

rc766437,

Does this appear to be a related issue to the problem I'm experiencing?
https://devzone.nordicsemi.com/f/nordic-q-a/39428/usb-msc-corruption

--Jeff