In our setup we use the SD 3.0 spec compatible bus driver, i.e. Catalog item "SD Bus Driver" (SYSGEN_SDBUS, IMGSDBUS2).
I have followed your steps and I am able to build the dll.
But none of my changes make it into the final image.
Looking into CE.Bib and COMMON.BIB I noticed that SDBUS.DLL can either be "SDBUS2.DLL" or "SDBUS.DLL" depending on IMGSDBUS2 being set or not.
My assumption is that my freshly build SDBUS.dll is excluded in favour of the SDBUS2.DLL.
Question: using your approach, do I have to select "Legacy SD BUS Driver" from the catalog to include my cloned version?
SDBus.dll versus SDBus2.dll
Hi,
thank you very much for that very good article.
However I do have some questions.
In our setup we use the SD 3.0 spec compatible bus driver, i.e. Catalog item "SD Bus Driver" (SYSGEN_SDBUS, IMGSDBUS2).
I have followed your steps and I am able to build the dll.
But none of my changes make it into the final image.
Looking into CE.Bib and COMMON.BIB I noticed that SDBUS.DLL can either be "SDBUS2.DLL" or "SDBUS.DLL" depending on IMGSDBUS2 being set or not.
My assumption is that my freshly build SDBUS.dll is excluded in favour of the SDBUS2.DLL.
Question: using your approach, do I have to select "Legacy SD BUS Driver" from the catalog to include my cloned version?
Maybe I am missing something here.
TIA,
Bjoern