[olmoDalco]

Dear Neeraj Dantu,

I have reopen this thread because I am working again in this project and I am not able to bring up the Ethernet. After check the design files with Martin, it seems that there are not HW issue related because the Ethernet part is exactly the same that in the OSD red board. Lets me explain the current situation and the testing done.

As you know, I am using a custom board which is practically the same that the OSD3358 SM red board, but with some peripherals removed. The schematics, signal and layout related with the Ethernet part are exactly the same that the red board. This part has been checked with Octavo HW.

First of all, I have bypassed the eeprom ID check building a u-boot to do it. After that, I have write the ID in the EEPROM with the u-boot commands. You can see in this screenshot that they are correctly written.

After that I have used the reference image from octavo webpage (OSD3358-SM-RED-Custom-Debian-9.1-lxqt-09-19-2017-1.1.img). So that it means that the u-boot is not hard-coded to bypass the EEPROM. It boot correctly, but the Ethernet does not work.

Some points to take in mind:

• When I plug the Ethernet wire in the board connector and PC or router, it does not light.
• Although I have configured a static IP in the interfaces file, the board does not get it from the beginning. But when I do ifdown and ifup eth0, the IP is correctly assigned.
• With the DHCH and connected the board to a router, it does not get any IP.
• In my PC, every time I see the message that a device was disconnected and after that connected.
• The Atheros PHY driver is correctly detected. As you can see in the attached log, the board is able to get the MAC address.
• I have tested the Ethernet wire in others boards, and it works correctly. So the issue is not caused by the wire.

Could you please help me to answer the following questions?

1. My main guess about the root cause is that is caused because the Ethernet PHY mode is not correctly configured. As far as I know, the OSD red board should use the RGMII instead of the MII which is used for the Beaglebone. But in the u-boot log, I see that the eth0 mode is MII. Could you please confirm it?
2. After by pass the EEPROM and write the ID number in the u-boot, using the OSD3358 red board image that you provided me, the u-boot should detect the board as Beaglebone and model OSD3358 red board and it implies configure the PHY in RGMII mode?
3. Which is the correct ID for the OSD-red-board: “BNLT” or “BBNR”? I have try with both, with the same results (Ethernet does not work) but the u-boot detected different model of board.
4. Please lets me know a way to debug deeply the PHY Ethernet configuration
   • Are there some file descriptor to check the status?
   • Is possible check in the Linux which pins related with the PHY have been configured?

Attached you can find the EEPROM ID values, u-boot log and kernel log. As you can see, in this case the model is not detected correctly. But if I use the u-boot to by pass the EEPROM, the board is detected correctly.  The logs are related with these images, the same board and the same EEPROM ID:

1. u-boot.txt and kernel.txt. With the osd-red-board image (without uboot by pass).
2. u-boot_Bypassed.txt and kernel_Bypassed.txt: with the beaglebone image and the checked EEPROM ID hard-coded in the board.c file.

Thanks a lot.

Attachments:

1. kenel-1-.txt
2. u-boot-1.txt
3. u-boot_Bypassed.txt
4. kenel-log-uboot_bypaseed.txt

[olmoDalco]

Dear Neeraj Dantu,

Sorry for the delay in the replay, I have not being working in this project since last year and I have not sign in in the forum. Lets me explain the steps that I followed to bring up the OTG (I know that remove the boot scripts is not the best way, but I have to analyze these scripts in order to avoid the configuration which is causing the difficulty to use the OTG).

1. First of all, remove the triggering of these scripts. The fastest way is rename the autoconfigure_usb0.sh file (located in /opt/scripts/boot/), for example, “_autoconfigure_usb0.sh”.
2. Configure the g_mass_storage module in boot/config.txt and /etc/modules files.
3. Create and format the binary file to share for OTG:
   • sudo dd bs=1M if=/dev/zero of=/piusb.bin count=2048
   • sudo mkdosfs /piusb.bin -F 32 -I
4. Use the g_mass_storage module: sudo modprobe gmassstorage file=/piusb.bin stall=0 ro=1

I hope that these steps work for more people.

Thanks a lot,

Best regards.

[olmoDalco]

Neeraj Dantu

First of all, I want to thank you about your help and support. And sorry for the delay en the answer.
I dont want to flash de eMMC for MP, I only want configure and use the board as a mass storage device for debugging.

Lets me try to explain you a bit about my issue. I only wanted use the microusb port of this board as a pen drive in a PC computer. In order to configure the board to do it, I tried with the g_mass_storage module : I have configured the module in /boot/config.txt and /etc/modules files. I have created and format the binary file (with these commands: sudo dd bs=1M if=/dev/zero of=/piusb.bin count=2048 and sudo mkdosfs /piusb.bin -F 32 -I) and mounted the system (sudo mkdir /mnt/usb_share, sudo nano /etc/fstab, adding: “/piusb.bin /mnt/usb_share vfat users,umask=000 0 2”, sudo mount -a). Finally I tested the mass storage devide. Please execute the following commands:
sudo modprobe gmassstorage file=/piusb.bin stall=0 ro=1
But it was not correctly configured like a OTG, the dmesg log always showed some errors (I can send you the logs). After search about it, I found that there are some scripts which are executed after boot and are configuring the peripherals according to the OSD reference board , they are causing issues with our design. So that I removed the triggered of these scripts and configure the OTG manually (with the commands mentioned previously) and it works fine.

So that my recommendation if you find out problems related with OTG, is remove these scripts and after that configure the g_mass_storage module manually.

Please if you think that I can provide you some information like logs, video or something like that. Lets me know.

Thanks for the support.
Best regards.

Olmo.

[olmoDalco]

Dear Neeraj Dantu,

First of all, I want thank your support, don’t worry about the delay.

I have read the application note about the programming EMMC, and I have some questions. Really I don’t want programming the EMMC, I need only expose the system as a OPT client in a host computer (the same that a USB pen drive in a PC). My most important doubts are the following:

• I have followed the Digikey tutorial to setup the SD card to program my OSDboard (it is perfectly working) but I am not able to identify all specific images of the Linux system provided in the project download folder, which should be flashed in the SD card. I want avoid the programming EMMC process because I only need show the system like an OTG client, the most easy way as possible. Can I replace the following files for the showed one (in the Digikey tutorial) in order to flash the SD card with the correct Linux system and configure like as a mass storage system?:
  • u-boot-spl-restore.bin –> ./u-boot/MLO
  • u-boot-restore.img –> ./u-boot/u-boot.img
  • uImage –> 4.14.141-bone27.zImage
  • uinitramfs –> armhf-rootfs-debian-stretch.tar
  • uosd3358-bsm-refdesing.dtb –> 4.14.141-bone27-dtbs.tar.gz
• Is there any complete image (to write in a SD card) with the g_mass_storage and others necessary
  modules to configure the system like a USB OTG client?

Based on the above questions, I want mark that the most important point that I need do, is install a complete linux image which will be able to show a USB client OTG in any PC host computer, which use the g_mass_storage module.

Thanks a  lot Octavo team.
Regards.

• This reply was modified 5 years ago by olmoDalco.

[olmoDalco]

Hi Neeraj Dantu,

Thanks a lot for the contact with Martin, I have written him. I will share with you all information when we have in this post.

About your questions:

1. Yes, we are using the same pin interface than the OSD3358-SM-RED board in our design.
2. What do you mean with the same configuration for the PHY? You mean about the HW or interfaces configuration (etc/network/interface file). We are using the AR8035-AL1A ethernet PHY. And the HW configuration is the following:
   • PHY_ADDR0: SYS_VDD1_3P3V
   • PHY_ADDR1: GND
   • PHY_ADDR2: SYS_VDD1_3P3V
   • MODE[0]:GND
   • MODE[1]: SYS_VDD1_3P3V
   • MODE[2]: SYS_VDD1_3P3V
   • MODE[3]: SYS_VDD1_3P3V
   • IO_VOLT_SEL: SYS_VDD1_3P3V
3. About the connector, I think that we are using the same part number that the SM-RED board. Our RJ45 connector is RJMG2310228A0ER.

Thanks,

Regards.

• This reply was modified 5 years, 7 months ago by olmoDalco.

[olmoDalco]

Dear Neeraj Dantu,

I have done the test that you commented above, the interfaces file has been configured with <code class=”cpp plain”>iface eth0 inet dhcp and the results are as follow:

• With the DHCP configured:
  • The system take too much time to boot the kernel, and I have seen this debug log: “A start job is running for raise network interfaces (2 minutes of 5 mins 1 sec”.
  • The system is not able to get the IP, the ifconfig response is:

eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
ether 98:5d:ad:2b:3d:68  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 189

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10<host>
loop  txqueuelen 1  (Local Loopback)
RX packets 1760  bytes 124640 (121.7 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 1760  bytes 124640 (121.7 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet 192.168.6.2  netmask 255.255.255.252  broadcast 192.168.6.3
inet6 fe80::9a5d:adff:fe2b:3d6d  prefixlen 64  scopeid 0x20<link>
ether 98:5d:ad:2b:3d:6d  txqueuelen 1000  (Ethernet)
RX packets 40  bytes 5776 (5.6 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 61  bytes 10250 (10.0 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
root@beaglebone:~#

In order to start manually the eth interfaces, I have executed the ifdown/ifup commands and the results was the same, the system does not get the IP.

root@beaglebone:~# ifdown eth0
Killed old client process
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/98:5d:ad:2b:3d:68
Sending on   LPF/eth0/98:5d:ad:2b:3d:68
Sending on   Socket/fallback
grep: /etc/resolv.conf: No such file or directory

——————————————————

root@beaglebone:~# ifup eth0
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/98:5d:ad:2b:3d:68
Sending on   LPF/eth0/98:5d:ad:2b:3d:68
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
root@beaglebone:~#

The dmesg logs shows the following: [   53.377955] omap-aes 53500000.aes: will run requests pump with realtime priority
[  428.464150] net eth0: initializing cpsw version 1.12 (0)
[  428.464177] net eth0: initialized cpsw ale version 1.4
[  428.464189] net eth0: ALE Table size 1024
[  428.542375] Atheros 8035 ethernet 4a101000.mdio:04: attached PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=4a101000.mdio:04, irq=-1)
[  428.562132] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

I have tested it in two different computers and the results was the same, so that I think that it is not related with the PC network configuration.Attached you can find the  logs file.

Thanks a lot,

Best regards.

Thanks,

Best regards.

[olmoDalco]

UPDATE:

After a several reboots, it seems that the system was able to start correctly and get a IP. The dmesg in the boot show the following:

[ OK ] Started Raise network interfaces.
[ OK ] Reached target Network.
Starting dnsmasq – A lightweight DHCP and caching DNS server…
Starting Permit User Sessions…
Starting OpenBSD Secure Shell server…
[ OK ] Reached target Network is Online.
Starting LSB: Advanced IEEE 802.11 management daemon…
[ OK ] Started Daily apt download activities.
[ OK ] Started Daily apt upgrade and clean activities.
[ OK ] Reached target Timers.
[ OK ] Started Permit User Sessions.
[ OK ] Started LSB: Advanced IEEE 802.11 management daemon.
Starting Light Display Manager…
[ OK ] Started Serial Getty on ttyS0.
[ OK ] Started Getty on tty1.
[ OK ] Reached target Login Prompts.
[ OK ] Started OpenBSD Secure Shell server.
[ OK ] Started dnsmasq – A lightweight DHCP and caching DNS server.
[ OK ] Reached target Host and Network Name Lookups.
Starting The Apache HTTP Server…
[ OK ] Started Serial Getty on ttyGS0.
[ OK ] Started Light Display Manager.
[ OK ] Started Generic Board Startup.
Starting BB WL18xx Bluetooth Service…
[ OK ] Started BB WL18xx Bluetooth Service.
[ OK ] Started The Apache HTTP Server.
[ OK ] Reached target Multi-User System.
[ OK ] Reached target Graphical Interface.
Starting Update UTMP about System Runlevel Changes…
[ OK ] Started Update UTMP about System Runlevel Changes.

And the ifconfig response is:

root@beaglebone:~# ifconfig
eth0: flags=-28669<UP,BROADCAST,MULTICAST,DYNAMIC> mtu 1500
inet 192.168.6.33 netmask 255.255.255.0 broadcast 192.168.6.255
ether 98:5d:ad:2b:3d:68 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 189

Altought the error of the link is not ready still happening:

root@beaglebone:~# dmesg | grep -i -e eth -e phy -e ip
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.002275] Calibrating delay loop… 995.32 BogoMIPS (lpj=1990656)
[ 0.177207] SMP: Total of 1 processors activated (995.32 BogoMIPS).
[ 1.710300] NetLabel: protocols = UNLABELED CIPSOv4
[ 2.369529] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[ 2.417298] libphy: Fixed MDIO Bus: probed
[ 2.473760] davinci_mdio 4a101000.mdio: detected phy mask ffffffef
[ 2.474593] davinci_mdio: dt: updated phy_id[4] from phy_mask[ffffffef]
[ 2.488180] libphy: 4a101000.mdio: probed
[ 2.488211] davinci_mdio 4a101000.mdio: phy[4]: device 4a101000.mdio:04, driver Atheros 8035 ethernet
[ 2.489260] cpsw 4a100000.ethernet: Detected MACID = 98:5d:ad:2b:3d:68
[ 2.489411] cpsw 4a100000.ethernet: cpts: overflow check period 1250 (jiffies)
[ 2.498984] 47401300.usb-phy supply vcc not found, using dummy regulator
[ 2.505821] 47401b00.usb-phy supply vcc not found, using dummy regulator
[ 2.531612] cpuidle: enable-method property ‘ti,am3352’ found operations
[ 2.627910] mip6: Mobile IPv6
[ 2.640836] PM: Cannot get wkup_m3_ipc handle
[ 2.962875] wkup_m3_ipc 44e11324.wkup_m3_ipc: CM3 Firmware Version = 0x192
[ 18.110864] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 18.924888] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 26.730760] net eth0: initializing cpsw version 1.12 (0)
[ 26.730787] net eth0: initialized cpsw ale version 1.4
[ 26.730798] net eth0: ALE Table size 1024
[ 26.810288] Atheros 8035 ethernet 4a101000.mdio:04: attached PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=4a101000.mdio:04, irq=-1)
[ 26.848348] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 27.511932] using random self ethernet address
[ 27.511955] using random host ethernet address
[ 27.616774] using random self ethernet address
[ 27.616797] using random host ethernet address
[ 54.890427] Modules linked in: omap_sham(+) crypto_engine(+) pruss_soc_bus(+) omap_rng rng_core tieqep c_can_platform c_can can_dev snd_soc_davinci_mcasp snd_soc_omap snd_soc_edma snd_soc_core snd_pcm_dmaengine snd_pcm snd_timex
root@beaglebone:~#

With the static IP the ssh and ping are not working. I have attached the logs during the uBoot, where you can see the load dtb and the overlays. Our board follow the osd3358 sm red board but we have removed the HDMI. Do you think that it can be causing troubles?

Thanks,
Best regards.

Attachments:

1. uBootIP.txt
2. logsGetIP.zip

[olmoDalco]

Hello Neeraj Dantu,

I am doing some tests with the image that you sent me in order to find out the root cause of the issue. The following information I have get:

There is an error related with the PHU during the uBoot
Net: eth0: MII MODE
Could not get PHY for cpsw: addr 0
cpsw, usb_ether

The PHY ethernet is detected and it has a MAC ID.

[ 1.590754] libphy: 4a101000.mdio: probed
[ 1.594961] davinci_mdio 4a101000.mdio: phy[4]: device 4a101000.mdio:04, driver Atheros 8035 ethernet
[ 1.605312] cpsw 4a100000.ethernet: Detected MACID = 98:5d:ad:2b:3d:68
[ 1.612196] cpsw 4a100000.ethernet: initialized cpsw ale version 1.4
[ 1.618675] cpsw 4a100000.ethernet: ALE Table size 1024
[ 1.624020] cpsw 4a100000.ethernet: cpts: overflow check period 1250 (jiffies)

The eth0 link is not ready error still happening.

[ OK ] Started Flush Journal to Persistent Storage.
Starting Create Volatile Files and Directories…
[ OK ] Started Create Volatile Files and Directories.
Starting Update UTMP about System Boot/Shutdown…
Starting Network Time Synchronization…
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Started Network Time Synchronization.
[ OK ] Reached target System Time Synchronized.
[ 14.554797] net eth0: initializing cpsw version 1.12 (0)
[ 14.652485] Atheros 8035 ethernet 4a101000.mdio:04: attached PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=4a101000.mdio:04, irq=POLL)
[ 14.714184] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

The system does not get the static IP altought I have set it in interfaces.d

root@beaglebone:~# ifconfig
eth0: flags=-28669<UP,BROADCAST,MULTICAST,DYNAMIC> mtu 1500
ether 98:5d:ad:2b:3d:68 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 189

I am trying to turn down and turn on the eth0 interface but I have the following errors:

root@beaglebone:/etc/network# ifdown eth0
grep: /etc/resolv.conf: No such file or directory

root@beaglebone:/etc/network# ifup eth0
grep: /etc/resolv.conf: No such file or directory

[ 760.421581] net eth0: initializing cpsw version 1.12 (0)
[ 760.421732] net eth0: initialized cpsw ale version 1.4
[ 760.421745] net eth0: ALE Table size 1024
[ 760.494409] Atheros 8035 ethernet 4a101000.mdio:04: attached PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=4a101000.mdio:04, irq=-1)
[ 760.519726] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

Other thing that happened was that in the first boot with this image, the system took about 3 min to start and this error was showed: “A start job is running for raise network interfaces (2 minutes of 5 mins 1 sec”

Do you know why it only happen the first time?

Thanks.

[olmoDalco]

Sorry for write other message but I am not able lo load the complete log file, this error is happening “comlpeteLog: Sorry, this file type is not permitted for security reasons.” What can I do to send the file?

Thanks.

Regards.

• This reply was modified 5 years, 7 months ago by olmoDalco.

[olmoDalco]

Hi Neeraj Dantu,

Thank you very much for your help and support.

Yes, our dessign follow the OSD3358-SM RED board. I have installed the image that you said me but the ethernet is not working. I have configured a static IP, but the system does not get the IP. Attached you can find the log during the boot.

Could you please say me any way to debug this issue? Can I enable some logs in the kernel (building a new image)?

Thanks,

Best regards.

• This reply was modified 5 years, 7 months ago by olmoDalco.

Attachments:

1. uBootLog.txt
2. bootLog.txt

[Author]

Posts