Why doesn't byteenable signal toggle between the two access addresses when a 32bit Avalon-MM Slave component is used to read over the PCIe 64bit Avalon Master in SOPC Builder? - Why doesn't byteenable signal toggle between the two access addresses when a 32bit Avalon-MM Slave component is used to read over the PCIe 64bit Avalon Master in SOPC Builder? Description Due to a bug in SOPC Builder, the byteenable doesn't change between the two read transaction when the PCIe ® master has a wider bus width than the slaves (i.e. 32/16/8 bits Avalon Slave). This problem exists in Quartus ® II software design using SOPC Builder. To work around this problem, you can add an Avalon ® -MM Pipeline Bridge between PCIe Master and the slave. This problem is fixed in Qsys. Custom Fields values: ['novalue'] Troubleshooting novalue False ['novalue'] ['novalue'] novalue novalue ['Programmable Logic Devices'] ['novalue'] ['novalue'] ['novalue']