Create PacketBundle. Essentially the same data as PacketData, but easier to index and wire up the different signals because its a data aggregate
Wired up the router-modules to use PacketBundle instead of PacketData. The Input/Output ports is wired up with a Chisel.Queue instead of the dedicated router.Fifo
Rewritten router-tests to work with PacketBundles instead of PacketData
Temporarily commented out all code that has anything to do with the RamTile, in order to successfully run router-tests
Switched location of x and y coordinates and added writeReq-signal
Add ram-tile again, now wired up with a PacketBundle. There is probably some difficulties with the payload being a Vec and the ram expecting UInt of 128 bits. A solution might temporarily be to set payload to an UInt. The tests for RamTile still needs to be update for PacketBundle
Set payload in PacketBundle to Bits instead of a vector, allows for easier handling of data
Update RamTileTest to work with PacketBundle
Update RamTileSum for PacketBundle
Updated peek/expect of bundles with predefined arrays for the packets, instead of only poking/expecting certain fields of the bundle
Use Arrays to assign data for PacketBundle, instead of just assigning some fields in the test
Update DirectionRouterTest with better assignment of PacketBundle