Open JohnHay opened 9 months ago
Yes, that's the idea but at the moment it's manual work and therefore the potential high to miss the update in the CoreList as well. It's fixed in a903680d5155aa2600549b9dd2f26e3a086021e7
Thank you. :-)
Currently my driver compare them in the attach routine and print a message to the console if there is a difference.
I have now loaded the version 9 LitePcie firmware and still see a version mismatch on the SMA Selector. It is not an issue for me, so you do not have to bring out a new version just for that. I just thought I'll mention it for when you next bring out a new version:
timecard0: CoreList 0x10000, register 0x10001, TC SMA Selector Inst0 Slave1
timecard0: CoreList 0x10000, register 0x10001, TC SMA Selector Inst0 Slave2
Should the version number in the CoreList match the number in the Version register of that core? There are some that are different.
I looks like TodSlave.vhd has a different version number (0x20003) from the above 2 ToD version numbers: