Ethernet Communication on C6A816x

Hi,

You can use standard way of setting IP addresses that is "ifconfig" on Linux console once it boots up.

Regards,

Hardik Shah

Hi,

As Hardik pointed out one option is to use "ifconfig" command from Linux console.

In case, you want static ip address before you get Linux console. You can use bootargs as mentioned below:

setenv bootargs 'console=ttyO2,115200n8 root=/dev/nfs nfsroot=10.100.3.192:/home/krunal/filesys,nolock rw mem=169M notifyk.vpssm3_sva=0xBF900000 ip=10.100.3.13:10.100.3.192:10.100.3.1:255.255.255.0:EIDLCPU2001:eth0:off'

Here, ip=${ipaddr}:${nfsserver}:${gatewayip}:${netmask}:${hostname}:eth0:off

Regards,

Krunal

Hi,

Once the EVM boots from SD card, from the terminal, I could assign a static IP address to the EVM using the following command:

ifconfig eth0 192.168.1.102 netmask 255.255.255.0 broadcast 192.168.1.255

After doing this, from the terminal, I could ping this IP using ping 192.168.1.102

However, while attempting to ping from a host PC, I get "Destination Host Unreachable" error and hence I am not able to establish communication between the EVM and the host PC through Ethernet.(I connect both the host PC and the EVM(J10) to the ethernet socket) 

 Kindly look into this and provide me the detailed steps(including the hardware connections) needed to establish this communication.

Regards,

Aravinda

Did you tried static IP from bootargs as mentioned in previous post?

Regards,

Krunal

Hi Kurnal,

Thanks for your response. Could you kindly provide the detailed steps for setting static IP from bootargs?

Regards,
Aravinda 

Please check my previous post. I have already explained there.

Let me know if you have any specific query on that.

Regards,

Krunal

Hi Krunal,

I have already looked into your previous post.

What I wanted to confirm was the steps that need to be done after modifying the bootargs, that is, needing to re build the uboot and the like.

Could you kindly eloborate these steps?

Thank you.

Aravinda 

Hi Aravinda,

Follow below steps:

1. Poweron the board
2. Stop at Autocount - U-Boot prompt
3. Set bootargs with static ip address as mentioned in my previous post
4. Use "saveenv" to save the bootargs - if you want to save them
5. Use - "boot" command to boot the board

Regards,

Krunal

Hi,

Case1: Directly connect host and EVM through an Ethernet  Cross Cable:

I could modify the bootargs and set the static IP address. That is, the following is being done:

setenv bootargs 'console=ttyO2,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=364M@0x80000000 324M@0x9F900000 notifyk.vpssm3_sva=0xBF900000 ip=192.168.1.10:192.168.1.5::255.255.255.0::eth0:off  noinitrd'

Using the above parameters, I created a new boot.scr. Now upon booting , I see that the IP address above(192.168.1.10) appears when invoking the ifconfig command. However,still pinging this IP from the host fails.(Destination Host Unreachable error). Why is this happening? Is anything wrong with the above?

Case2: Connect both the EVM and the host to a router

This then assigns an IP address to the Linux host automatically(DHCP). But the IP address is not assigned to the EVM. To do so, I modified the bootargs as: 

setenv bootargs 'console=ttyO2,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=364M@0x80000000 324M@0x9F900000 notifyk.vpssm3_sva=0xBF900000 ip=dhcp noinitrd'

Using the above parameters, I created a new boot.scr. Now, while the EVM boots up, it sends DHCP requests to the server. However these are timed out and so the IP address is not being set on the EVM. Below are the specific messages that appear on the console:

generic-usb 0003:15D9:0A4C.0001: input: USB HID v1.11 Mouse [ USB OPTICAL MOUSE] on usb-musb-hdrc.0-1/input0
davinci_mdio davinci_mdio.0: resetting idled controller
net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, id=282f014)
net eth1: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:02, id=282f014)
Sending DHCP requests .
PHY: 0:01 - Link is Up - 100/Full
..... timed out!
IP-Config: Reopening network devices...
davinci_mdio davinci_mdio.0: resetting idled controller
net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, id=282f014)
net eth1: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:02, id=282f014)
Sending DHCP requests .
PHY: 0:01 - Link is Up - 100/Full
..... timed out!
IP-Config: Auto-configuration of network failed.

Could you please look into this and see what is going wrong. Are there any specific settings that need to be made other than the above to enable DHCP.

  Regards,
Aravinda