OMAP-L138: Can't connect to the board through Ethernet

Silacko

Part Number: OMAP-L138
Other Parts Discussed in Thread: OMAPL138

Hi,

I have a MityDSP-L138F evaluation board, based on TI's Omap-L138 board.

I'm running Windows 7 on my host PC (which also contains an Ubuntu guest OS on it). I'm able to communicate with the board via UART, but I need to connect to it through Ethernet so that I can load executables via TFTP.

However, when I try pinging the device from the command line of Windows, I get an error saying: "Destination host unreachable".

On the device,

ipaddr=192.168.1.11
serverip=192.168.1.10

On the host PC (Windows),

C:\>ipconfig /all
...
Ethernet adapter Local Area Connection:
...
IPv4 Address. . . . . . . . . . . : 192.168.1.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
...

When I try pinging the board from my PC, I get the following:

C:\>ping 192.168.1.11
Pinging 192.168.1.11 with 32 bytes of data:
Reply from 192.168.1.10: Destination host unreachable.

From the board (serial port), I get:

U-Boot > ping 192.168.1.10
Using device
ping failed; host 192.168.1.10 is not alive

I also tried (from host) pinging 192.168.1.255 and typing "arp -a", but it didn't list the IP of the board as an entry. I checked the MAC address of the board, it's not listed there, either.

What do you think I'm doing wrong?

Thank you in advance.

Edit: I can now see the IP and MAC addresses of the board in the arp -a list, but I still can't ping it.

over 6 years ago

0 Cvetolin Shulev-XID over 6 years ago

TI__Guru 65405 points

Hi Silacko,

I've forwarded this to the SW experts. Their feedback should be posted here.

BR
Tsvetolin Shulev

0 Silacko over 6 years ago in reply to Cvetolin Shulev-XID

Prodigy 130 points

Thanks. Once I confirm the connection is done, I may need help to do that in the guest OS as well, because the TFTP server is installed on Ubuntu.

0 Mukul Bhatnagar over 6 years ago in reply to Silacko

TI__Guru* 78305 points

Hi
I am going to ping folks in Critical Link to see if they can help you directly on this.
We do not have the Mity DSP boards with us, so will likely not be able to support board level or the specific software base the board supports.
Regards
Mukul

0 Jonathan Cormier over 6 years ago in reply to Mukul Bhatnagar

Expert 2715 points

Hi Silacko,

Thanks for using our product. My first thought was to make sure you've allowed pings in the Windows firewall. By default Windows 7 and above block ping requests. https://kb.iu.edu/d/aopy

Please refer to our wiki page for this product support.criticallink.com/.../wiki and our forum support.criticallink.com/.../boards

Jonathan Cormier
CriticalLink

0 Silacko over 6 years ago in reply to Jonathan Cormier

Prodigy 130 points

Hi,
Sorry for the delay; I was away from work at the weekend.
I tried enabling the rule for the firewall, but unfortunately, it didn't make a difference.
I noticed something odd, though. If I ping the device from the host PC and ping the host PC from the device simultaneously, the ping will be successful on the host side (the device still claims the host is not alive). I'm not sure what the problem could be. Maybe I'm doing something wrong.
Silacko

0 Silacko over 6 years ago in reply to Silacko

Prodigy 130 points

Apparently, I can randomly ping the device. I managed to ping it a couple of times successfully, and the device could ping the host PC with a "host is alive" message. Now, it doesn't work again.

0 Silacko over 6 years ago in reply to Jonathan Cormier

Prodigy 130 points

The problem has been solved and I can use the tftp server to transfer binaries to the board. Thank you.

0 Mukul Bhatnagar over 6 years ago in reply to Silacko

TI__Guru* 78305 points

Good to know, thanks for updating and closing out the thread.

Jonathan @ Critical Link , thank you for your attention and support on this thread for the MityDSP OMAPL138 board.

0 Jonathan Cormier over 6 years ago in reply to Silacko

Expert 2715 points

Silacko said:
The problem has been solved and I can use the tftp server to transfer binaries to the board. Thank you.

Its helpful for the community if you explain what the solution was. Glad you got it figured out.

Just an FYI, playing around with ping in u-boot. U-boot appears to only bring up the network interface when its being used so if you ping the board you won't get a response unless like you tested while you ping out. This is complicated by the fact that uboot ping quits after it gets a response. So it appears that you get better results by pinging an address that doesn't exist which keeps the connection alive long enough to ping it from the host machine several times.

0 Silacko over 6 years ago in reply to Jonathan Cormier

Prodigy 130 points

I still don't know why the ping was not working, but I changed my TFTP server application, and it started working as expected.
I was using "OpenTFTP Server", which couldn't establisha connection. After switching to TFTP Util, it started to work.
Thank you.

Processors

Processors forum

OMAP-L138: Can't connect to the board through Ethernet