The error could be due to an issue with the Ethernet card on the target machine. The error 'EPROBEFAIL' could happen if xPC Target Kernel cannot access the Ethernet device when it boots up.
Follow the below mentioned diagnostics steps that should help resolve the issue at your end.
1. Check if you are using an unsupported Ethernet card on the target machine. Only cards that are supported on R2010b will work for xPC Target 4.4 (R2010b).
Please note that the host-to-target communication supported chipset list has been removed from the MathWorks website.
If you are using a Speedgoat hardware, the chipsets that we have tested and can ensure that they will work are inside Speedgoat target computers installed in properly configured Speedgoat motherboards.
If you have questions about any specific chipset, contact Technical Support with the Vendor ID and the Device ID.
2. Once you made sure that you have the right Ethernet driver installed on your Target PC, select the same Ethernet Driver when creating the boot disk.
3. If the Target PC has multiple Ethernet cards, it could be that the xPC Target kernel is picking up the wrong Ethernet card when booting up. Follow the instructions provided in the link below if multiple Ethernet Cards in the Target PC is causing communication issues
4. Once BIOS loads, the xPC kernel boot starts. During the boot sequence, a "BIOS search function" (provided by the hardware manufacturer) is used by the xPC kernel to scan for PCI devices in the system incrementally starting from bus 0. It stops scanning when it detects an unused bus, assuming the all the buses after the first unused bus are not used. It does this to shorten the boot-up time. Sometimes, in a target machine, most devices reside on lower buses, and the Ethernet controller might reside on a much higher bus. Buses in between would be unused. So the BIOS’ search function does not even detect the Ethernet controller. The Ethernet controller is totally invisible to the xPC kernel.
GETXPCPCI('all') command is a standalone utility, which bypasses the BIOS. This is why GETXPCPCI can still display the Ethernet cards and it is a good command to check if the above is the case.
If yes, certain versions of BIOS can scan from bus 0 to bus 255, no matter what is in the system. The system vendor generally knows more about the BIOS and if he can upgrade the BIOS, you can eliminate this problem.
Or, you can bump the Ethernet Card to Bus 0.
Best Answer