<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.arm.com/utility/feedstylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>How is AXI addressing scheme work for this problem?</title><link>https://community.arm.com/developer/ip-products/processors/f/cortex-a-forum/47663/how-is-axi-addressing-scheme-work-for-this-problem</link><description> Hi, I am not confident about my thinking so wanted to clear it. 
 Let&amp;#39;s say DATA_WIDTH= 64 bits 
 AWLEN=3 
 AWSIZE=1 ( 2 Bytes data transfer) 
 AWBURST= FIXED 
 According to me on every transfer data strobe will be in WSTRB= 00001000 (I.e. only address</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: How is AXI addressing scheme work for this problem?</title><link>https://community.arm.com/thread/167602?ContentTypeID=1</link><pubDate>Mon, 21 Sep 2020 14:07:30 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:795eeb3f-75b5-4d23-9255-3c635af6fbfe</guid><dc:creator>Colin Campbell</dc:creator><description>&lt;p&gt;AWSIZE tells you the maximum number of bytes that can be transferred in each AXI transfer; AWADDR (when not AWSIZE aligned) tells you within that AWSIZE range how many byte lanes can actually be used.&lt;/p&gt;
&lt;p&gt;So yes, each transfer in a FIXED transaction with AWSIZE=1 (2 bytes) and AWADDR signaling an unaligned address, means one byte per transfer maximum.&lt;/p&gt;
&lt;p&gt;If AWADDR=0x03 in your example this means that you can only use WSTRB=8&amp;#39;b00001000 or 8&amp;#39;b00000000 for each of the 4 transfers in the AWLEN=3 transaction, so a maximum of 4 bytes (and minimum of 0 bytes) can be transferred.&lt;/p&gt;
&lt;p&gt;Note that in FIXED bursts the unaligned address doesn&amp;#39;t change for each transfer (because it is &amp;quot;fixed&amp;quot;), so each transfer remains unaligned. But in INCR bursts it is only the first transfer that is unaligned, and all subsequent transfers in an INCR transaction can use the full number of AWSIZE indicated byte lanes. WRAP transaction types cannot have unaligned addresses.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>