J721EXSOMXEVM: Fls Initialization

Hello Pradeep,

Good to hear back from you.

Pradeep R said:

Is SPI module mandatorily need to be initialized before we Initialize  Fls since Fls uses OSPI.

what do you mean by SPI module needs to be initialised ? Are you saying about McSPI? then no but ultimately OSPI is also an Octal SPI right.Can you point me what exactly are you referring to ?

Regards

Tarun Mukesh

Hello Tarun,

Thankyou. Same here

we were starting Flash operations with New MCAL package mentioned above.

During Fls_HwUnitInit, we see there is dependency  on SPI    (void)OSPI_init(((SPI_Handle)&(SPI_config[0])));

During Fls_Main_Function Invocation, we see there are few function calls to "NOR_spiPhyAvgVtmTemp". we are getting exception from here.

So we want to confirm whether SPI , yes McSPI is mandatorily need to be initialized  for Fls.

If we dont configure McSpi, we will get exception during Fls Init.

Can you please confirm this.

Regards,

Pradeep R

Pradeep,

The Flash driver module needs to use SPI protocol to perform the data transfers between system and Flash device. Specifically, this Flash driver requires OSPI interface and driver.

This answers your query i believe .It directly doesn't use MCAL SPI driver but the required initialisation are added into FLS driver itself

Regards

Tarun MUkesh

Hello Tarun, 

Thankyou for the reply.

we will remove SPI module and try to initialize Fls again.

Also one more Is any ISRs and interrupt is mandatory for Fls operations.? Do we need to Configure any ISRs in our Os.?

Regards,

Pradeep R

Pradeep,

Let me check.

Regards

Tarun Mukesh 

Hello Tarun,

we have one more issue, we are getting exception from NOR_spiPhyAvgVtmTemp function because of ARM instruction vmov s0,r2

Is there any floating point precision compiler option we need to use.

Regards,

Pradeep R

Hi pradeep,

sorry occupies with other high priority task and couldn't get much time.I will try to reply in couple of days. 

Regards

Tarun Mukesh

Hello Tarun,

Sure Thankyou

Now we resolved the NOR_spiPhyAvgVtmTemp issue but still Fls Erase , read and write not successful.

Regards,

Pradeep R

Hello,

i will check this  first thing next week.

Regards

Tarun  Mukesh

Hello Tarun,

Sure Thankyou

Regards,

Pradeep R

Hello Tarun,

Any feedback on this query?

Regards,

Pradeep R

Hey pradeep,

sorry.I couldn't check this, i will check and reply by tomorrow.

Regards

Tarun

Hello Tarun,

Sure Thankyou

Regards,

Pradeep R

Hello Pradeep,

I have gone through your query,TO use FLS we need to initialize SPI , since underlying it is using OSPI flash which needs SPI Initialization but this is not McSPI intialization.We have ospi_init() calls which you can see in mcusw/mcal_drv/mcal/board/flash folder

RegardS

Tarun Mukesh 

Hello Tarun,

Thankyou for the feedback.

Can you please provide feedback for other queries as well.

1 Is any ISRs and interrupt is mandatory for Fls operations.? Do we need to Configure any ISRs in our Os.?

2 What is the start address of OSPI Flash area, can we physically see this address in our trace32 IDE?

Regards,

Pradeep R

Hello Tarun,

Any feedback on above queries.

Also we have one more query in continuation to above queries

3  Can we reinitialize FLS module twice eg : after performing Fls_Init , we call Fls_Write and then again can we call Fls_init and then invoke Fls_read?

will there be any impact of OSPI flash area if we call Fls_Init twice without resetting the CPU?

Regards,

Pradeep R

Hello Pradeep,

Pradeep R said:

1 Is any ISRs and interrupt is mandatory for Fls operations.? Do we need to Configure any ISRs in our Os.?

2 What is the start address of OSPI Flash area, can we physically see this address in our trace32 IDE?

Yes If you are using this in interrupt mode.

Pradeep R said:

Can we reinitialize FLS module twice eg : after performing Fls_Init , we call Fls_Write and then again can we call Fls_init and then invoke Fls_read?

will there be any impact of OSPI flash area if we call Fls_Init twice without resetting the CPU?

I dont think this will be correct to re intialize without ressetting the CPU.