MMWCAS-DSP-EVM: Networking stack not working with built ti-sdk

Does MAC address match the value in the following register?

Good morning.

How would I go about reading those values from within the Linux distro? I do not have access to a debugger to attach to the MMWCAS-DSP-EVM, so I  don't think I will be able to read the register values through CCS.

How is the LAN MAC address setup in the Linux context / filesystem? Can you point me to the relevant code in the Vision SDK for Linux?

Using the omapconf dump command, I was able to get this output:

root@dra7xx-evm:/opt/vision_sdk# omapconf dump 0x4A002514 0x4A002518
|----------------------------|
| Address (hex) | Data (hex) |
|----------------------------|
| 0x4A002514 | 0x00B9039C |
| 0x4A002518 | 0x00E0FFF1 |
|----------------------------|

root@dra7xx-evm:/opt/vision_sdk# ifconfig
eth0 Link encap:Ethernet HWaddr E0:FF:F1:B9:03:9C
inet addr:192.168.14.33 Bcast:192.168.255.255 Mask:255.255.0.0
inet6 addr: fe80::e2ff:f1ff:feb9:39c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:563680 errors:0 dropped:4333 overruns:0 frame:0
TX packets:4886 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:49550676 (47.2 MiB) TX bytes:355436 (347.1 KiB)
Interrupt:87

eth1 Link encap:Ethernet HWaddr E0:FF:F1:B9:03:9D
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

It seems like the MAC address does correspond to what ifconfig reports.

I also saw today, that if I set a IP address of 192.168.14.33, the ARP requests originates from IP 192.136.14.33. 

Is it possible that there is a bug in network stack?

Yes, the ethernet driver has MAC address set correctly matching the values in register.

Did you try DHCP instead of static IP? Does it work?

For static IP, you have to make sure the source/destination are within the same subnet when you assign IP address.

Good morning. I tried to DHCP this morning, but as you can see, the MAC address issue is still present. 

As you can see from the Wireshark screen capture, the MAC address source is c0:ff:d1:99:03:9c, which is not the same as the E0:FF:F1:B9:03:9C address stored in memory.

This incorrect MAC address will mean that whatever responds to this packet will get filtered out by the layer 2 MAC filter. I believe this is the underlaying cause of the connection issues. 

Has this problem been seen before and is there a software patch that I can use?

Can you try to run "tcpdump" from the board?

This way we can check the packet content from SoC side.

I suspect maybe the packet is corrupted on PC side.

Can you also dump the value of below register? 

Regards,
Stanley

Hi Stanley

tcpdump is not an executable on that version of the Arago project (2016.12). I guess I can try cross compiling it, but that could take some time... Any other ways of inspecting the packets that would be installed by default?

Here is the address values from the working filesystem:

|----------------------------|
| Address (hex) | Data (hex) |
|----------------------------|
| 0x4A002534 | 0x06410000 |
| 0x4A002538 | 0x000002AF |
|----------------------------|

Here are the address values from the filesystem with the MAC issue:

|----------------------------|
| Address (hex) | Data (hex) |
|----------------------------|
| 0x4A002534 | 0x06410000 |
| 0x4A002538 | 0x000002AF |
|----------------------------|

The 3.07 SDK does not have this MAC issue.

Thanks for the feedback.