Host target Communication lost once target PC is booted into the xPC environment

Hi all,

The communication between my host and target PC is lost everytime I boot the target PC into the xPC environment. I've tried 3 ways of booting - FDD, network, and CD boot - and all gave the same result. However, in the windows environment, the communication works well.

I purchased an EXPI9301CTBLK Intel Gigabit CT Desktop Adapter ) and plugged it into the PCIe slot. This card has Intel 82574L gigabit ethernet controller. I also checked 'Device Instance ID' for the device which are; vendor = 0x8086 and device ID = 0x10D3. Hence, I'm sure it's compatible. This card is properly installed and it works well in the windows environment (I used it for internet too).

I've also tried to adjust the BIOS setting for the target PC under Peripherals'>Onboard device>Onboard LAn boot Rom and disable it. I thought to disable the onboard ethernet. It still doesn't work.

I've seen this solution to a problem which is very similar to mine: http://www.mathworks.com/support/solutions/en/data/1-6JKGBJ/index.html but... it still doesn't work. =(

Any ideas anyone?

Here are some details of my comps.

Host:

Dell laptop - Intel core i7 CPU, Intel 82577LM gigabit network adapter, Windows 7.

Target PC:

Desktop Shuttle XPC - SG33G50 motherboard with built in Generic MArvell Yukon 88

Here are some info perhaps useful to you:

getxpcpci('all')
??? Error using ==> AutoConnect at 7
Message: A connection attempt failed because the connected
party did not properly respond after a period of time, or
established connection failed because connected host has failed
to respond 192.168.0.220:22223
Source: System
HelpLink:

Error in ==> getxpcpci>getInstalledPCI at 294
xpctarget.AutoConnect(clrObj);

Error in ==> getxpcpci at 123
pcii=getInstalledPCI(tg);

________________________________
>> getxpcenv

    xPC Target default environment

      Version                  : 5.0                           

      CCompiler                : VisualC                       
      CompilerPath             : C:\Program Files\Microsoft Visual Studio 10.0

      Name                     : TargetPC1                     

      TargetRAMSizeMB          : Auto                          
      MaxModelSize             : 1MB                           
      SecondaryIDE             : off                           
      NonPentiumSupport        : off                           
      MulticoreSupport         : off                           

      HostTargetComm           : TcpIp                         
      RS232HostPort            : COM1                          
      RS232Baudrate            : 115200                        
      TcpIpTargetAddress       : 192.168.0.220                 
      TcpIpTargetPort          : 22222                         
      TcpIpSubNetMask          : 255.255.255.0                 
      TcpIpGateway             : 255.255.255.255               
      TcpIpTargetDriver        : I8254x                        
      TcpIpTargetBusType       : PCI                           
      TcpIpTargetISAMemPort    : 0x300                         
      TcpIpTargetISAIRQ        : 5                             

      TargetScope              : Enabled                       

    xPC Target Embedded Option

      EmbeddedOption           : Enabled                       
      TargetBoot               : NetworkBoot                   
      TargetMACAddress         : 00:1b:21:ad:8e:70             
      BootFloppyLocation       :                               
      CDBootImageLocation      : C:\Users\ang.cs\Desktop       
      DOSLoaderLocation        :

Answer 1

[Sangyoon Lee]

I was having the same issue where the target machine will just black out after recognizing the boot image. It turns out, just unchecking the "USB support" option from the target settings was the magic key for my problem.

Answer 2

[Arnaud Miege]

Are the host and target connected directly or through a network? If directly, you need to use a cross-over cable.

Also, did you check that the gateway (255.255.255.255) is the same on both host and target computers? It seems to me that you've left the default value. It needs to match what's on your host computer.

Can you ping the target using the ping command in DOS when the target is booted with xPC Target? If not, then there's something wrong with the TCP/IP settings, and there's no point in trying to connect to the target from MATLAB.

HTH,

Arnaud

[James]

Hi, thanks for your reply,

The host and target is connected directly (from ethernet port on laptop to ethernet port on Intel card on desktop PC).

Oh.. the gateway has been specified to 192.168.0.1 for both host and target. Is this the problem? I'll check again.

No, I can't ping when it is booted with xPC target. But I can ping in windows environment for both computers. Here are some details. Please correct me if there's mistake.

Host:

IP - 192.168.0.219

Subnet mask - 255.255.255.0

Default gateway - 192.168.0.1

This is similar for Target PC just that the IP is 192.168.0.220.

[James]

Hi Arnaud,

I used a crossovercable for my connection.

In the GUI for xpcexplr I leave the gateway as 255.255.255.255. On the LAN properties, I only set values (above) for 'IP' and 'subnet mask', but leaving it empty for 'default gateway' , is this the right way? I'm sorry it's my first time in this. If this is right I still couldn't get it connected.

[Arnaud Miege]

If the gateway for your host is 192.168.0.1, then that's what you should enter in xPC Explorer. 255.255.255.255 on the target won't work if the host is set to 192.168.0.1. Try this, create new boot files/media, and try rebooting with the correct the gateway. Then try pinging the target (when booted to xPC) from DOS. Until that's successful, there's no point in going any further.

[Walter Roberson]

You should *never* use 255.255.255.255 as the gateway for IP! 255.255.255.255 is reserved for broadcast messages; some operating system requires that the process has privileges to send to such a destination, and sending to such a destination is required to use a hop-count of 1.

[James]

Thanks Arnaud and Walter for the answers. Will get back to you soon if this works.

[James]

Hi Arnaud,

Sorry for the late reply. Was away for a while.

I've changed the 'xpcexplr' gateway to 192.168.0.1, similar to that on the host PC. The target PC boots into the xPC environment but when I ping from the host PC (on DOS), it's not successful.

any ideas?

Could it be the bios setup?

Answer 3

[Reto Rüegg]

Hello all,

have someone solved this problem? It seems, that I'm stucking in the same situation...

Regards,

Reto