Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why does the address input to slaves in my SOPC Builder system increment incorrectly during a burst transfer?

April 26, 2017address builder Burst incorrectly Increment input slaves sopc system transfer

0

Posted

Why does the address input to slaves in my SOPC Builder system increment incorrectly during a burst transfer?

1 Answer

0

Posted

Solution The Avalon® Switch Fabric may incorrectly increment the address input to slaves in an SOPC Builder system if a master changes the value of the burstcount signal in the middle of a burst. Figures 31 and 32 in the Avalon Memory Mapped Interface Specification (version 3.3 and lower)(PDF) incorrectly indicate that the burstcount signal can take on a don’t care value after the 1st beat of a burst. Instead Avalon masters should maintain the burst size value on the burstcount signal throughout the duration of the burst. Version 3.4 of the Avalon Memory Mapped Interface Specification has been modified to specify the correct behavior for burstcount signals.