How the avalon mm slave "address alignment" works?

--- Quote Start ---

Hi

thanks for ur help would be great if u can send me an example

i don t understand why i have to use 0x0, 0x4, 0x8, 0xC, etc...

but at all that i tried already and didn t worked aswell :/

i m using the offset adress only for intern adressfinding i don t access an RAM or something like that

i only want to write or read different things from my own HDL to the NIOS

i set the readlatency to 5 i ll try to set it to 1 maybe that helps

and the main question

i m using a 8 Bit Adress so i have HEX from 00 to FF

if i m using now 8'h00, 8'h04, 8'h08, 8'h0C ... in the HDL do i give the adress the same in the NIOS ? or do i need there 0x00 0x01 and so on? or 0x00 0x04 0x08 ???

dunno sometimes i get an adress access but sometimes i don t dunno why :(

--- Quote End ---

Hi, what you what to do is a little different from what we are doing, if you want use the IORW and IORD, i think you can use the "address" whatevery you prefer to use, but when you want the addressing space of the peripheral become a part of the CPU`s data or instruction addressing space, then you can not use the macro anymore, you can just use the memory-mapped bus.

To my problem, i am partly resovled, but not so satisfactory, i'd make a HDL to give more function to alignment the 16bits peripheral to a 32bits avalon master.