FSL Read Data Out Problem

Hi,

The problem is that the Write signal is not a ready signal for MicroBlaze but it's a write signal into a FIFO. So what you have done is to write new values EVERY clock cycle into the FIFO which will get full very fast.

If you only want to write back the value that you read, then you should do this instead. FSL0_M_Write Hello Everybody.

Thanks for your help, I have updated the file as you said, but unfortunately I have still the same problem, I only get 0 values thats so strange...

Cheers Roger

Hi,

Sorry I didn't look careful enough on your C code. You are using the nonblocking version of the FSL macros but in this case you should do the blocking versions. use "microblaze_bread_datafsl" instead of the "microblaze_nbread_datafsl".

Could you also share the .mhs file so I could see that everything is connected correctly?

Göran

Roger Planger wrote:

Hi Goeren

Yeah finally, this was the mistake the non blocking Read Statement! Thanks a lot for this hint, now it works! So in the future when I wanna read out from FIFO I should use the blocking statement, shouldn't I?

Cheers Roger!

Sorry I didn't look careful enough on your C code. You are using the nonblocking version of the FSL macros but in this case you should do the blocking versions. use "microblaze_bread_datafsl" instead of the "microblaze_nbread_datafsl".

Could you also share the .mhs file so I could see that everything is connected correctly?

Göran

Roger Planger wrote:

Thanks for your help, I have updated the file as you said, but unfortunately I have still the same problem, I only get 0 values thats so strange...

Cheers Roger

Hi,

The problem is that the Write signal is not a ready signal for MicroBlaze but it's a write signal into a FIFO. So what you have done is to write new values EVERY clock cycle into the FIFO which will get full very fast.

If you only want to write back the value that you read, then you should do this instead. FSL0_M_Write

Hi Roger,

I'm glad that you got it working.

Depending on how long time it take to get the result. If the execution of the FSL modules take too many clock cycle and you want to do something else during that time or just enabling interrupts, you need to use the non blocking versions. But it that case you need to check if the execution of the FSL was successful or not.

But normally the execution of the FSL modules is not that many clock cycles and you can therefore in most cases use the blocking instructions. With the blocking instructions, you don't have to spend instructions and clock cycle to determine if the FSL instruction was successful or not.

Göran

Roger Planger wrote:

Hi Roger,

I'm glad that you got it working.

Depending on how long time it take to get the result. If the execution of the FSL modules take too many clock cycle and you want to do something else during that time or just enabling interrupts, you need to use the non blocking versions. But it that case you need to check if the execution of the FSL was successful or not.

But normally the execution of the FSL modules is not that many clock cycles and you can therefore in most cases use the blocking instructions. With the blocking instructions, you don't have to spend instructions and clock cycle to determine if the FSL instruction was successful or not.

Göran

Roger Planger wrote: