[EXT_EP-11338] Spi_AsyncTransmit taking longer than expected Created: 21/Jul/23 Updated: 21/Nov/23 |
|
| Status: | New |
| Project: | Embedded Software & Tools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | TI User | Assignee: | TI User |
| Resolution: | Unresolved | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Product: | MCAL |
| Internal ID: | MCAL-8514 |
| Found In Release: | MCUSW_J7_01.03.04 |
| Affected Platform/Device: | j721e-evm |
| Description |
|
Multiple reports of the Spi_AsyncTransmit() function taking longer than expected. From DesaySV: Do you have any comments about why the “Spi_AsyncTransmit” code execution be slower when DDR throughput higher? After change the code to MSRAM from DDR, the efficiency only improved 30%, is it reasonable? From Reachauto: And the time consuming part is Spi startSeqAsync,It check all the hardware queue and consume any pending job if the hardware is free. As i test,when i use one HardWare,it costs 40us .I'd like to know whether its time can be reduced by any operation, or it can not be optimized?
|