NCS 2.0.0 hang in qspi_device_uninit

[denis]

I have an application that is working in NCS 1.8.0.  When I build with NCS 2.0.0 and run then there is a hang in qspi_device_uninit (called by fd_mount, ..., qspi_nor_read).  nrfx_qspi_mem_busy_check is getting 0xff for the status_value, which sounds incorrect.  Any ideas to help track this issue down?

Also, the "CORTEX PERIPHERALS" view in vscode says "SVD: No active debug sessions or no SVD files specified".  So I can't look at the QSPI peripheral registers.  Any ideas why that would be?

[Simonr]

Hi

There were some pretty big changes between versions 1.x.x and 2.x.x of the nRF Connect SDK. Have you gone through the migration and release note for the NCS v2.0.0? I'm not familiar with this issue in particular, but if you haven't done that, I'm guessing it can be resolved by following the migration notes closely for your application.

Best regards,

Simon

[denis]

Yes, I did review the release and migration notes.  I didn't notice anything related to QSPI.