USB0 communication problem

This topic has 5 replies, 2 voices, and was last updated 4 years, 7 months ago by alvaro.

Viewing 5 reply threads

Author
Posts

March 24, 2020 at 3:47 pm #9948
alvaro
Participant
Hello,
I have developed a new design based on the OSD3358-512M-BAS, following the reference design tutorial series.
When the hardware was ready, I used the uart-usb interface cable for get the results from the execute of the MLO and u-boot. I also flashed the EEPROM with the magic number using the u-boot like the tutorial indicates. Finally, I tried and flashed the osd3358-sm-red-custom-debian-9-1 image. All the steps worked fine!
My problem is related with the ethernet communication over the usb0. When I connect a usb cable between the usb0 and the PC and try a ping to the board I don’t get response. I checked the file interfaces, located in /etc/network, but everything is correct. The next try was to flash another image. This time I used the bone-debian-8.10-seeed-iot and when I tried the ping it works correctly!
How can I solve the problem with the osd3358-sm-red-custom-debian-9-1 image?
Thanks in advance.
álvaro.
March 24, 2020 at 4:47 pm #9949
Neeraj Dantu
Moderator
Alvaro,
Try executing the following scripts on the RED image:
./opt/scripts/boot/am335x_evm.sh
./opt/scripts/boot/autoconfigure_usb0.sh

Best,
Neeraj

March 24, 2020 at 6:19 pm #9950

alvaro

Participant

Hi Deeraj,

First of all, thank you very much for your help!

I try executing the two scripts that indicated but the ping doesn’t work.

In case it can help you, here is the response:

root@beaglebone:/opt/scripts/boot# ./am335x_evm.sh
am335x_evm: usb_image_file=[/var/cache/doc-beaglebone-getting-started/beaglebone-getting-started-2017-05-25.img]
am335x_evm: cpsw_0_mac: [50:65:83:EB:CA:05]
am335x_evm: cpsw_1_mac: [50:65:83:EB:CA:07]
am335x_evm: cpsw_2_mac: [50:65:83:EB:CA:06]
am335x_evm: cpsw_3_mac: [50:65:83:EB:CA:08]
am335x_evm: cpsw_4_mac: [50:65:83:EB:CA:09]
am335x_evm: cpsw_5_mac: [50:65:83:EB:CA:0A]
am335x_evm: use_libcomposite
am335x_evm: modprobe libcomposite
am335x_evm: FIXME: need to bring down g_multi first, before running a second time.
am335x_evm: Starting serial-getty@ttyGS0.service
root@beaglebone:/opt/scripts/boot# ./autoconfigure_usb0.sh
root@beaglebone:/opt/scripts/boot#

root@beaglebone:/opt/scripts/boot# ./am335x_evm.sh

am335x_evm: usb_image_file=[/var/cache/doc-beaglebone-getting-started/beaglebone-getting-started-2017-05-25.img]

am335x_evm: cpsw_0_mac: [50:65:83:EB:CA:05]

am335x_evm: cpsw_1_mac: [50:65:83:EB:CA:07]

am335x_evm: cpsw_2_mac: [50:65:83:EB:CA:06]

am335x_evm: cpsw_3_mac: [50:65:83:EB:CA:08]

am335x_evm: cpsw_4_mac: [50:65:83:EB:CA:09]

am335x_evm: cpsw_5_mac: [50:65:83:EB:CA:0A]

am335x_evm: use_libcomposite

am335x_evm: modprobe libcomposite

am335x_evm: FIXME: need to bring down g_multi first, before running a second time.

am335x_evm: Starting serial-getty@ttyGS0.service

root@beaglebone:/opt/scripts/boot# ./autoconfigure_usb0.sh

root@beaglebone:/opt/scripts/boot#

March 26, 2020 at 3:43 pm #9958
alvaro
Participant
Hi Neeraj,
I have got a Beaglebone Black revC. I tried the same process with this board. Using the osd3358-sm-red-custom-debian-9-1 the ping to usb0 doesn’t work either (including the execution of the scripts that you told me).
When the kernel boots, shows the same error in both boards:
[ 23.516228] libphy: PHY 4a101000.mdio:04 not found [ 23.557868] net eth0: phy "4a101000.mdio:04" not found on slave 0, err -19
1
2
[ 23.516228] libphy: PHY 4a101000.mdio:04 not found
[ 23.557868] net eth0: phy "4a101000.mdio:04" not found on slave 0, err -19
For use the osd3358-sm-red-custom-debian-9-1, the only possibility is that the ethernet over usb0 works because I didn’t include the ethernet connector in my design.
Thanks.

álvaro.
March 27, 2020 at 11:21 am #9959
Neeraj Dantu
Moderator
Alvaro,
If you programmed the board ID with the one described in the application note(OS00), the board should boot and start a USB RNDIS (Ethernet over USB) interface. This interface should be named ‘usb0’ and should show up on the interfaces list.
If you use a USB cable to connect the micro USB port of the board to your computer, you should be able to ping the board via this RNDIS interface. If you are unable to, it may be because of the computer was not assigned the right IP address. You can set the IP address of your computer’s network adapter by modifying the IPV4 address settings in the properties of the Ethernet adapter created by the connection to the board.
The second error that you are referring to in your post shows that an Ethernet PHY has not been detected at the right address. This PHY corresponds to the Ethernet interface and is not related to the USB interface. So, if you don’t have an Ethernet interface on your board, you should disregard the error for now. Note that you will have to change your device tree later to reflect the hardware present on your board.
Please let us know if you have any more questions.
Best,
Neeraj
March 28, 2020 at 9:50 am #9967
alvaro
Participant
Hi Neeraj,
It’s true. The error was on the ip configuration of the network adapter 🙁
The ethernet communication over the usb0 is working correctly!
Thank you very much for the help!
Regards,
álvaro

Author
Posts

Viewing 5 reply threads

You must be logged in to reply to this topic.