Mass Sample for nRF5340

[paulb@figfi]

Hi,

I am attempting to make the Mass sample work on the nRF5340DK PCB.

I have found a patch -  RE: Log to nrf52 thingy internal flash which seems to improve things slightly, but I am still getting a fs mount error (-19)

I can get the nrfjprog --readqspi c:\test_24bit.hex -f nrf53 command suggested in another support ticket to do something, I can't find the output file - however it runs to end and if I scope the flash pins it seems to be doing something, so I assume the QSPI flash interface is working.

I also noticed there seemed to be some sort of clash on the storage_partition name so I changed it in several places to storage0 - however this made no difference either.

Any help appreciated.

Paul.

[Amanda Hsieh]

Hi, 

What version of NCS are you using?

I use that patch and enable CONFIG_APP_MSC_STORAGE_FLASH_FATFS to run Mass sample on the nRF5340DK, and get the following log:

*** Booting Zephyr OS build v3.1.99-ncs1-1  ***
Area 6 at 0x0 on mx25r6435f@0 for 131072 bytes
Mount /NAND:: 0
/NAND:: bsize = 512 ; frsize = 512 ; blocks = 216 ; bfree = 216
/NAND: opendir: 0
End of files
[00:00:06.374,481] <inf> main: The device is put in USB mass storage mode.
*** Booting Zephyr OS build v3.1.99-ncs1-1  ***
[00:00:00.492,187] <inf> main: No file system selected
[00:00:00.492,309] <inf> main: The device is put in USB mass storage mode.

The log from SPI_FLASH sample is:

*** Booting Zephyr OS build v3.1.99-ncs1-1  ***

mx25r6435f@0 SPI flash testing
==========================

Test 1: Flash erase
Flash erase succeeded!

Test 2: Flash write
Attempting to write 4 bytes
Data read matches data written. Good!!

 

I am attempting to make the Mass sample work on the nRF5340DK PCB.

What do you mean by "nRF5340DK PCB"? Are you using the custom board or nRF5340DK? Can you try on the nRF5340DK?

Maybe try to run the following commands before programming.

nrfjprog --recover --coprocessor CP_NETWORK
nrfjprog --recover

Regards,
Amanda H.

[paulb@figfi]

Hi, Thanks for the quick reply.

I am using the Nordic nRF5340DK PCA10095 2.0.0 2022.3 1050041259

I am building using NCS V2.1.1

PS C:\nRF\spi_flash2.1.1> nrfjprog --recover --coprocessor CP_NETWORK
[error] [ nRF53] - Application core access protection is enabled, can't enable coprocessor.
Recovering device. This operation might take 30s.
Erasing user code and UICR flash areas.
Writing image to disable ap protect.
PS C:\nRF\spi_flash2.1.1> nrfjprog --recover
Recovering device. This operation might take 30s.
Erasing user code and UICR flash areas.
Writing image to disable ap protect.
PS C:\nRF\spi_flash2.1.1>

*** Booting Zephyr OS build v3.1.99-ncs1 ***

mx25r6435f@0 SPI flash testing
==========================

Test 1: Flash erase
Flash erase succeeded!

Test 2: Flash write
Attempting to write 4 bytes
Data read does not match data written!!
000ff000 wrote 55 read 88 MISMATCH
000ff001 wrote aa read 88 MISMATCH
000ff002 wrote 66 read 88 MISMATCH
000ff003 wrote 99 read 88 MISMATCH

[Amanda Hsieh]

What is the HW version on the white sitcker of the nRF5340DK? 

[paulb@figfi]

nRF5340DK PCA10095 2.0.0 2022.3 1050041259

[paulb@figfi]

Perhaps I m suffering from this issue?

https://infocenter.nordicsemi.com/index.jsp?topic=%2Ferrata_nRF5340_Rev1%2FERR%2FnRF5340%2FRev1%2Flatest%2Fanomaly_340_136.html

I will investigate tomorrow.

[paulb@figfi]

So - the build code on my nRF5340 is QKA AD0 - which is slightly different to the errata code QKAA-D00, but I suspect they are a match?

I also found some code in the Zephyr SPI drivers 
https://github.com/nrfconnect/sdk-zephyr/blob/main/drivers/spi/spi_nrfx_spim.c#L168-L177

I have ordered another nRF5340DK, ut it is from the same supplier so I suspect it will have the same build code.

[paulb@figfi]

So - In desperation I pressed down on the mx25r6435f IC and the issue went away! So I guess there must be a dry joint on my PCB. New one ordered.

Thanks for your support in this. I am new to the nRF and it's SDK, so it is difficult to work out where issues might lay.