ΣSigmaStudio Ask AI Русский Log in

Need Assistance with Testing OSPI Driver APIs on EV-SC594-SOM for ISSI IS25LX256 Flash.

Processors & DSP sohm Apr 2, 2024 00:00 3 replies Original on forum ↗
Subscribe
sohm Question
Apr 2, 2024 00:00

Dear ADI Engineering Zone Community,

I am currently working on testing the OSPI driver on the EV-SC594-SOM board to access the ISSI IS25LX256 flash memory. My goal is to read the flash ID, perform write and read operations on the flash memory. I have installed the EV-SC59x_EZ-KIT-Rel3.0.0 BSP and CrossCore Embedded Studio (CCES) for this purpose.

Here are the steps I followed to import the flash example project into CCES:

Open CCES and navigate to File -> Import -> General -> Existing project into Workspace -> Next.

Select the root directory and browse to the example location: C:\Analog Devices\EV-SC59x_EZ-KIT-Rel3.0.0\EV-SC59x_EZ-KIT\Examples\Device_Programmer\OSPI_ISSI_IS25LX256_Flash.

Click "Finish" to import the project.

My project explorer look like this

However, after importing the project, I encountered an issue where only the main function of is25lx256_dpia_SC594_Core0 is running, and none of the flash-related APIs are being called . The flash operation-related APIs are part of the is25lx256_dpia_SC594_Core1 project (is25lx256_dpia_SC594_Core1.c).

When I attempt to load and run only the is25lx256_dpia_SC594_Core1 project, I receive the following error message:

I would greatly appreciate any guidance or assistance on how to properly test the OSPI driver APIs for accessing the ISSI IS25LX256 flash on the EV-SC594-SOM board. Are there any specific configurations or steps that I may be missing in my setup or project settings?

Thank you in advance for your help and support.

EV-SC594-SOM

software

ADI_issue.png
ADI_issue.png
ADI_Issue_2.png
ADI_Issue_2.png
StuartS Reply
Apr 2, 2024 00:00

Hi,
That particular device programmer example and prebuilt executable is for use in conjunction with the cldp (Command Line Device Programmer) to write to the OSPI device memory. There should be some details in the accompanying readme in the projects you imported with those details.

More appropriate examples for accessing OSPI are provided in the BSP that might be better to review. From menu CCES Help > Browse examples, use a "ADSP-SC594" processor and "OSPI" keyword filter and you should get a summary of the available examples. You can then select an example(s) from that view to copy and import into your workspace. Each example should have a detailed readme file that describes how it is setup.

Regards,
StuartS.

sohm Reply
Apr 3, 2024 00:00

Hi ,

Thanks for the reply. I followed the method that you have mentioned and imported ospi_flashdirectaccess_octal example and here also I am facing the same issue that I have mentioned above . I am seeing ospi_flashdirectaccess_octal_SC594_SHARC_Core0, ospi_flashdirectaccess_octal_SC594_SHARC_Core1 and ospi_flashdirectaccess_octal_SC594_SHARC_Core2 as part of the project

Is there any example available to access the ISSI IS25LX256 flash memory in free RTOS environment . I could create a new project by adding free RTOS as add in and OSPI driver as well. Can you give me any example project to access the flash in free RTOS environment .

Thank You

StuartS Reply
Apr 3, 2024 00:00

Hi,

Did you find the readme file in the core1 project? One thing to note that for the multicore ADSP-SC594 parts the ARM Cortex-A5 core 0 needs to be run first as it does initializations and then releases the SHARC cores. The majority of the example is done in the SHARC core 1 for the SHARC example variants. Are you able to run core 1 once it hit main() and see the console output that gets printed, it should finish by printing "All done" to the console?

I'm not aware of any FreeRTOS specific examples for OSPI but I believe the driver as supplied in CCES will work without modification for FreeRTOS as the FreeRTOS port implements the OSAL abstraction layer replacing the baremetal noOS OSAL one used by default.

Regards,
StuartS.