Shulou(Shulou.com)06/01 Report--

This article mainly introduces how to initialize VxBus Driver. It is very detailed and has a certain reference value. Interested friends must finish reading it!

The initialization of VxBus Driver is generally divided into three steps, and the entry function is usually in the form of xxxRegister (). If VxWorks starts up and then calls it-for example, in usrAppInit (), its loading process is relatively simple.

The Driver provided by WindRiver by default is loaded during the startup process of OS. Typically, xxxRegister () is registered in sysHwInit (), and the exact location is determined by the CDF file. Its first step of initialization (* devInstanceInit) is then called, such as the PCI Device of X86, which is called when registering the Driver of PCI Host Controller. So, all PCI Device Driver will be registered before this Controller

The registration process is roughly

$(BSP) / sysALib.s/sysInit ()-> $(prj) / prjConfig.c/usrInit ()-> $(BSP) / sysLib.c/sysHwInit ()-> $(prj) / prjConfig.c/hardWareInterFaceInit ()-> $(prj) / prjConfig.c/hardWareInterFaceBusInit ()-> $(driver) / xxxRegister () and the next two initialization steps are called in sysHwInit2 (). The difference is that the second step (* devInstanceInit2) is called directly, while the third step (* devInstanceConnect) is called in a new task, which leads to the fact that the real timing of its execution is likely to be the detailed invocation relationship after all the functions have been loaded by OS.

These are all the contents of the article "how to initialize VxBus Driver". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.