Prev: Peculiar system command problem on UNIX
Next: xPC Target Thermocouple DAQ
From: Nils on 22 Jul 2010 18:32
Hello,
I'm trying to boot my xPC target with a CD. It seems to start booting but after a few seconds it says the following:

Board: I82559, PCI-BUS: Error 4 134 0
Error: -->EPROBEFAIL

_____________________________

----> System halted
_____________________________

A quick search online suggests that EPROBEFAIL indicates an incompatible ethernet adapter. I have, however, installed an ethernet adapter that should be compatible with xPC Target, namely Intel Pro/100 M Desktop Adapter. The only thing I can think of is that there is a another ethernet adapter already installed, unfortunately part of the logic board, so I can't really remove it, and that the Kernel tries to recognize this first.

First of all, is anyone familiar with this error message and perhaps know how to deal with it?

Second of all, are the settings I do in the xPC explorer on the Host computer relevant to the boot disc I burn or is the contents of the boot disc independent of the xPC environment settings?

Thirdly, right now I have assumed that the index of the network adapter I'm trying to use actually is 1 and so I have set it with
setxpcenv('EthernetIndex','1')
but how do I actually know that this is the case?
From: Walter Roberson on 22 Jul 2010 18:31
Nils wrote:

> A quick search online suggests that EPROBEFAIL indicates an incompatible
> ethernet adapter. I have, however, installed an ethernet adapter that
> should be compatible with xPC Target, namely Intel Pro/100 M Desktop
> Adapter. The only thing I can think of is that there is a another
> ethernet adapter already installed, unfortunately part of the logic
> board, so I can't really remove it, and that the Kernel tries to
> recognize this first.

Sometimes BIOS will offer a mechanism to disable the onboard ethernet interface.
From: Nils on 22 Jul 2010 18:46
Walter Roberson <roberson(a)hushmail.com> wrote in message <i2ah3t$4b6$2(a)canopus.cc.umanitoba.ca>...
> Nils wrote:
>
> > A quick search online suggests that EPROBEFAIL indicates an incompatible
> > ethernet adapter. I have, however, installed an ethernet adapter that
> > should be compatible with xPC Target, namely Intel Pro/100 M Desktop
> > Adapter. The only thing I can think of is that there is a another
> > ethernet adapter already installed, unfortunately part of the logic
> > board, so I can't really remove it, and that the Kernel tries to
> > recognize this first.
>
> Sometimes BIOS will offer a mechanism to disable the onboard ethernet interface.

Yes, I discovered (thanks to you) that my BIOS also had this option. I disabled it, same result.
From: Gordon Weast on 23 Jul 2010 10:03
Nils,

The debugging path you can try is:

1. create a boot floppy that will use the serial port for host/target
communication. If your machine doesn't have a hard wired floppy
drive, then you can usually use a USB floppy to boot from to get
the following information. Even though real time performance may
suffer if USB is enabled in the BIOS, it is useful for debugging.

2. Once up with serial com, run 'getxpcpci all' and look to see
if the Ethernet board is found and where it is. The kernel uses
the PCI BIOS routines to search the PCI bus while getxpcpci has
it's own search and it may find the board when the BIOS didn't.
At least this can help us figure out why the probe is failing.

You may also be able to use the baseboard Ethernet if you reenable
it in the BIOS and just remove the second board. That does
depend on which version of MATLAB and xPC Target you're running.
Recent versions support more Ethernet boards and chips.

Gordon Weast
xPC Target Development
The MathWorks

Nils wrote:
> Walter Roberson <roberson(a)hushmail.com> wrote in message
> <i2ah3t$4b6$2(a)canopus.cc.umanitoba.ca>...
>> Nils wrote:
>>
>> > A quick search online suggests that EPROBEFAIL indicates an
>> incompatible > ethernet adapter. I have, however, installed an
>> ethernet adapter that > should be compatible with xPC Target, namely
>> Intel Pro/100 M Desktop > Adapter. The only thing I can think of is
>> that there is a another > ethernet adapter already installed,
>> unfortunately part of the logic > board, so I can't really remove it,
>> and that the Kernel tries to > recognize this first.
>>
>> Sometimes BIOS will offer a mechanism to disable the onboard ethernet
>> interface.
>
> Yes, I discovered (thanks to you) that my BIOS also had this option. I
> disabled it, same result.
From: Nils on 23 Jul 2010 10:38
Gordon Weast <gweast(a)mathworks.com> wrote in message <i2c7fs$rin$1(a)fred.mathworks.com>...
> Nils,
>
> The debugging path you can try is:
>
> 1. create a boot floppy that will use the serial port for host/target
> communication. If your machine doesn't have a hard wired floppy
> drive, then you can usually use a USB floppy to boot from to get
> the following information. Even though real time performance may
> suffer if USB is enabled in the BIOS, it is useful for debugging.
>
> 2. Once up with serial com, run 'getxpcpci all' and look to see
> if the Ethernet board is found and where it is. The kernel uses
> the PCI BIOS routines to search the PCI bus while getxpcpci has
> it's own search and it may find the board when the BIOS didn't.
> At least this can help us figure out why the probe is failing.
>
> You may also be able to use the baseboard Ethernet if you reenable
> it in the BIOS and just remove the second board. That does
> depend on which version of MATLAB and xPC Target you're running.
> Recent versions support more Ethernet boards and chips.
>
> Gordon Weast
> xPC Target Development
> The MathWorks
Thanks for your replies (Walter too, whom I forgot to thank last time)!

I didn't try your trouble-shooting but it seems to work now except for that it wont find a harddrive to write to (should be no problem as far as I can read).

The only thing I did was to change the environmental settings by changing the adapter index (see my first post) to 0 and THEN burning the boot-cd. So 2 things that seems plausible (and what perhaps most of you already know):
1. What is burned on the boot disc IS dependent on the environmental settings at the time you burn the disc.
2. The index of the ethernet-card might depend on what cards are activated and not on port number. I draw this conclusion since the default settings are index = 0 and that I believe the built-in card should have the lowest index. Here I of course might be completely off. Perhaps someone else can enlighten.

Thanks for your help though!
 |  Next  |  Last
Pages: 1 2
Prev: Peculiar system command problem on UNIX
Next: xPC Target Thermocouple DAQ