Mar 03, 2020
01:58 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 03, 2020
01:58 AM
Hi all,
What happens when reading and flash operation (e.g. erasing/programming) conflict?
Best regards,
Lucas
#8042000 19449
What happens when reading and flash operation (e.g. erasing/programming) conflict?
Best regards,
Lucas
#8042000 19449
- Tags:
- IFX
1 Reply
Mar 04, 2020
04:16 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 04, 2020
04:16 AM
Hi Lucas,
This depends on whether the flash bank to be accessing the same bank or not. "Read from flash", would mean a read access is done via the SRI bus and "Flash Operation" means the flash bank is in "BUSY" state with a command.
Case 1) Same bank; Master 1 and 2 access to same bank (e.g. PF0) according to the following table:

1) During its execution the Flash bank reports BUSY in FSR. In this mode read accesses to this Flash bank are refused with a bus error or the ready is suppressed until BUSY clears.
This can be configured (see FCON.STALL). At the end of an operation the Flash bank returns to read mode and BUSY is cleared.
2) Bus error occurs for write access to DF0 address range when normal command interpreter is busy with a command. Bus error occurs for write access to DF1 address range when HSM command interpreter is busy with a command.
In case of flash commands conflict by the CPU and HSM, please see "Time Slice Control".
Case 2) Different bank; Master 1 and 2 access to different bank (e.g. PF0 and PF1) according to the following table:

Best regards,
Mr. AURIX™
This depends on whether the flash bank to be accessing the same bank or not. "Read from flash", would mean a read access is done via the SRI bus and "Flash Operation" means the flash bank is in "BUSY" state with a command.
Case 1) Same bank; Master 1 and 2 access to same bank (e.g. PF0) according to the following table:
1) During its execution the Flash bank reports BUSY in FSR. In this mode read accesses to this Flash bank are refused with a bus error or the ready is suppressed until BUSY clears.
This can be configured (see FCON.STALL). At the end of an operation the Flash bank returns to read mode and BUSY is cleared.
2) Bus error occurs for write access to DF0 address range when normal command interpreter is busy with a command. Bus error occurs for write access to DF1 address range when HSM command interpreter is busy with a command.
In case of flash commands conflict by the CPU and HSM, please see "Time Slice Control".
Case 2) Different bank; Master 1 and 2 access to different bank (e.g. PF0 and PF1) according to the following table:
Best regards,
Mr. AURIX™