TMDXSK437X: Request technical advice to set up Network Boot via USB0 of AM437x STARTER KIT

Sung Hwan Kim80

Part Number: TMDXSK437X

I followed "6.1.9 Ubuntu 14.04 Set Up to Network Boot an AM335x/AM437x Based Platform" of SDK 06_03_00_106 Linux Software Developer's Guide.

After restart service network manager on Ubuntu 18.04 host PC, I found the BOOTP requests coming from the AM437x starter kit board using Wireshark. But the Ubuntu box was not set up to host the boot process via USB0 for an AM437x starter kit board.

So, I would like to know whether AM437x starter kit could not be working via USB0. If it could be working, what process is more required to use USB0 to boot AM437x starter kit.

over 3 years ago

0 Bin Liu over 3 years ago

TI__Guru*** 125116 points

Hi,

Yes, AM437x starter kit USB0 port should work with USB Network boot. The fact that you have found the BOOTP requests coming from AM437x also proves it.

0 Sung Hwan Kim80 over 3 years ago in reply to Bin Liu

Prodigy 160 points

Thank you for your comment.

I will try to get the result.

0 Sung Hwan Kim80 over 3 years ago in reply to Sung Hwan Kim80

Prodigy 160 points

I tried to set up Network Boot via USB0 of AM437x STARTER KIT as per 6.1.9. Ubuntu 14.04 Set Up to Network Boot an AM335x/AM437x Based Platform.

USB0(enp9s0f4u1 in my PC Ubuntu 18.04) configured with step 9 instead of step 8. The processing was paused from TI AM437x starter kit board reply ,which may be assigned 192.168.2.2 by isc-dhcp-server.

I found the USB0(enp9s0f4u1) was assigned 192.168.2.1 which was found from ifconfig.

I restart isc-dhcp-server, atftpd and network manager as per 6.1.9. Ubuntu 14.04 Set Up to Network Boot an AM335x/AM437x Based Platform.

If wireshark capture file is needed for your reference, I would like to send it. I tried to attached it, but this post was not allowed.

Anyway, Could I have your advice to resolve paused processing from AM437x starter kit board reply as attached wireshark capture picture? ?

Thank you in advance.

0 Bin Liu over 3 years ago in reply to Sung Hwan Kim80

TI__Guru*** 125116 points

Hi,

Sung Hwan Kim80 said:
If wireshark capture file is needed for your reference, I would like to send it. I tried to attached it, but this post was not allowed.

certain types of files are not allowed to attach to the posts. Can you please try to compress (zip) the file or rename it to *.txt, then upload it again?

0 Sung Hwan Kim80 over 3 years ago in reply to Bin Liu

Prodigy 160 points

Hi,

Please refer the next post and attached files,which was sent at Dec. 29 2020, for USB0 disconnection problem.

Thanks.wireshark_enp9s0f4u1_20201223154453_Hjjq4l.zip

0 Sung Hwan Kim80 over 3 years ago in reply to Bin Liu

Prodigy 160 points

Hi,

I attached the wireshark capture and /var/log/syslog for the USB0 disconnection problem of AM437x starter kit.

Could I know why the USB0 was disconnected and how to solve it?

Thank you in advance.wireshark_capture_USB0_disconnection_20201229.zip syslog for USB0 disconnection.docx

0 Bin Liu over 3 years ago in reply to Sung Hwan Kim80

TI__Guru*** 125116 points

Hi,

Sorry for the delay, I am currently out of office for the holidays. I will review the logs once I am back after the New Year.

0 Sung Hwan Kim80 over 3 years ago in reply to Bin Liu

Prodigy 160 points

Hello,

Thank you for your reply.

I will wait your advice for wireshark capture & syslog which were attached at last reply.

0 Bin Liu over 3 years ago in reply to Sung Hwan Kim80

TI__Guru*** 125116 points

Hi,

The syslog syslog for USB0 disconnection.docx you provided doesn't tell the full story.

- the log begins with BOOTREQUEST and BOOTREPLY and transfer u-boot-restore.img to the board.

This tells the network communication is working. But the log misses the information of EVM USB enumeration before network transfer.

- the log shows after u-boot-restore.img is transferred, the board rebooted and the ROM USB is enumerated again on the host. The host then assigned ip address 192.168.2.1. to the EVM USB ethernet port again. Then the log doesn't show any further message. Is the syslog complete?

0 Sung Hwan Kim80 over 3 years ago in reply to Bin Liu

Prodigy 160 points

Hello,

I attached the further message of syslog and wireshark capture.

In my view, the current problem is the USB0 disconnection repeatdly.

So, would you advice it from the attached files?

Thank you in advance.

syslog for usb0 disconnection_20210111.txt

Jan 11 14:11:29 shkim-A320MH sh[8789]: For info, please visit https://www.isc.org/software/dhcp/
Jan 11 14:11:29 shkim-A320MH dhcpd[8789]: Copyright 2004-2016 Internet Systems Consortium.
Jan 11 14:11:29 shkim-A320MH dhcpd[8789]: All rights reserved.
Jan 11 14:11:29 shkim-A320MH dhcpd[8789]: For info, please visit https://www.isc.org/software/dhcp/
Jan 11 14:11:29 shkim-A320MH dhcpd[8789]: Config file: /etc/dhcp/dhcpd.conf
Jan 11 14:11:29 shkim-A320MH sh[8789]: Config file: /etc/dhcp/dhcpd.conf
Jan 11 14:11:29 shkim-A320MH sh[8789]: Database file: /var/lib/dhcp/dhcpd.leases
Jan 11 14:11:29 shkim-A320MH sh[8789]: PID file: /run/dhcp-server/dhcpd.pid
Jan 11 14:11:29 shkim-A320MH dhcpd[8789]: Database file: /var/lib/dhcp/dhcpd.leases
Jan 11 14:11:29 shkim-A320MH dhcpd[8789]: PID file: /run/dhcp-server/dhcpd.pid
Jan 11 14:11:29 shkim-A320MH dhcpd[8789]: Internet Systems Consortium DHCP Server 4.3.5
Jan 11 14:11:29 shkim-A320MH dhcpd[8789]: Copyright 2004-2016 Internet Systems Consortium.
Jan 11 14:11:29 shkim-A320MH dhcpd[8789]: All rights reserved.
Jan 11 14:11:29 shkim-A320MH sh[8789]: Wrote 1 leases to leases file.
Jan 11 14:11:29 shkim-A320MH dhcpd[8789]: For info, please visit https://www.isc.org/software/dhcp/
Jan 11 14:11:29 shkim-A320MH dhcpd[8789]: Wrote 1 leases to leases file.
Jan 11 14:11:29 shkim-A320MH dhcpd[8789]: Listening on LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:29 shkim-A320MH sh[8789]: Listening on LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:29 shkim-A320MH sh[8789]: Sending on   LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:29 shkim-A320MH sh[8789]: Sending on   Socket/fallback/fallback-net
Jan 11 14:11:29 shkim-A320MH dhcpd[8789]: Sending on   LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:29 shkim-A320MH dhcpd[8789]: Sending on   Socket/fallback/fallback-net
Jan 11 14:11:29 shkim-A320MH dhcpd[8789]: Server starting service.
Jan 11 14:11:30 shkim-A320MH avahi-daemon[612]: Joining mDNS multicast group on interface enp9s0f4u1.IPv6 with address fe80::a888:39ff:fef6:ffed.
Jan 11 14:11:30 shkim-A320MH avahi-daemon[612]: New relevant interface enp9s0f4u1.IPv6 for mDNS.
Jan 11 14:11:30 shkim-A320MH avahi-daemon[612]: Registering new address record for fe80::a888:39ff:fef6:ffed on enp9s0f4u1.*.
Jan 11 14:11:31 shkim-A320MH ModemManager[611]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1': not supported by any plugin
Jan 11 14:11:33 shkim-A320MH atftpd[3194]: timeout: retrying...
Jan 11 14:11:34 shkim-A320MH dhcpd[8789]: reuse_lease: lease age 1741411 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.2.2
Jan 11 14:11:34 shkim-A320MH dhcpd[8789]: BOOTREQUEST from c4:be:84:cc:86:6b via enp9s0f4u1
Jan 11 14:11:34 shkim-A320MH dhcpd[8789]: BOOTREPLY on 192.168.2.2 to c4:be:84:cc:86:6b via enp9s0f4u1
Jan 11 14:11:35 shkim-A320MH kernel: [  560.730617] usb 5-1: USB disconnect, device number 18
Jan 11 14:11:35 shkim-A320MH kernel: [  560.730719] rndis_host 5-1:1.0 enp9s0f4u1: unregister 'rndis_host' usb-0000:09:00.4-1, RNDIS device
Jan 11 14:11:35 shkim-A320MH dhcpd[8789]: receive_packet failed on enp9s0f4u1: Network is down
Jan 11 14:11:35 shkim-A320MH avahi-daemon[612]: Interface enp9s0f4u1.IPv6 no longer relevant for mDNS.
Jan 11 14:11:35 shkim-A320MH avahi-daemon[612]: Leaving mDNS multicast group on interface enp9s0f4u1.IPv6 with address fe80::a888:39ff:fef6:ffed.
Jan 11 14:11:35 shkim-A320MH avahi-daemon[612]: Interface enp9s0f4u1.IPv4 no longer relevant for mDNS.
Jan 11 14:11:35 shkim-A320MH avahi-daemon[612]: Leaving mDNS multicast group on interface enp9s0f4u1.IPv4 with address 192.168.2.1.
Jan 11 14:11:35 shkim-A320MH avahi-daemon[612]: Withdrawing address record for fe80::a888:39ff:fef6:ffed on enp9s0f4u1.
Jan 11 14:11:35 shkim-A320MH avahi-daemon[612]: Withdrawing address record for 192.168.2.1 on enp9s0f4u1.
Jan 11 14:11:35 shkim-A320MH NetworkManager[3218]: <info>  [1610341895.1072] devices removed (path: /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1/5-1:1.0/net/enp9s0f4u1, iface: enp9s0f4u1)
Jan 11 14:11:35 shkim-A320MH NetworkManager[3218]: <info>  [1610341895.1073] get unmanaged devices count: 1
Jan 11 14:11:35 shkim-A320MH systemd[1]: Stopping ifup for enp9s0f4u1...
Jan 11 14:11:35 shkim-A320MH upowerd[1547]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1/5-1:1.1
Jan 11 14:11:35 shkim-A320MH upowerd[1547]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1/5-1:1.0
Jan 11 14:11:35 shkim-A320MH upowerd[1547]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1
Jan 11 14:11:35 shkim-A320MH ifdown[8875]: Cannot find device "enp9s0f4u1"
Jan 11 14:11:35 shkim-A320MH ifdown[8875]: Cannot find device "enp9s0f4u1"
Jan 11 14:11:35 shkim-A320MH systemd[1]: Stopped ifup for enp9s0f4u1.
Jan 11 14:11:35 shkim-A320MH kernel: [  561.032330] usb 5-1: new full-speed USB device number 19 using xhci_hcd
Jan 11 14:11:35 shkim-A320MH kernel: [  561.186433] usb 5-1: not running at top speed; connect to a high speed hub
Jan 11 14:11:35 shkim-A320MH kernel: [  561.206496] usb 5-1: New USB device found, idVendor=0451, idProduct=6142, bcdDevice= 0.00
Jan 11 14:11:35 shkim-A320MH kernel: [  561.206500] usb 5-1: New USB device strings: Mfr=33, Product=37, SerialNumber=0
Jan 11 14:11:35 shkim-A320MH kernel: [  561.206503] usb 5-1: Product: AM43xx1.2
Jan 11 14:11:35 shkim-A320MH kernel: [  561.206505] usb 5-1: Manufacturer: Texas Instruments
Jan 11 14:11:35 shkim-A320MH NetworkManager[3218]: <info>  [1610341895.6231] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/26)
Jan 11 14:11:35 shkim-A320MH kernel: [  561.256739] rndis_host 5-1:1.0 usb0: register 'rndis_host' at usb-0000:09:00.4-1, RNDIS device, 8a:9a:b0:90:cc:67
Jan 11 14:11:35 shkim-A320MH mtp-probe: checking bus 5, device 19: "/sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1"
Jan 11 14:11:35 shkim-A320MH mtp-probe: bus: 5, device: 19 was not an MTP device
Jan 11 14:11:35 shkim-A320MH systemd-udevd[8969]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 11 14:11:35 shkim-A320MH kernel: [  561.280381] rndis_host 5-1:1.0 enp9s0f4u1: renamed from usb0
Jan 11 14:11:35 shkim-A320MH upowerd[1547]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1/5-1:1.1
Jan 11 14:11:35 shkim-A320MH NetworkManager[3218]: <info>  [1610341895.6805] devices added (path: /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1/5-1:1.0/net/enp9s0f4u1, iface: enp9s0f4u1)
Jan 11 14:11:35 shkim-A320MH NetworkManager[3218]: <info>  [1610341895.6805] locking wired connection setting
Jan 11 14:11:35 shkim-A320MH NetworkManager[3218]: <info>  [1610341895.6806] settings-connection[0x555cd8ba2c40,e257b6d7-196c-67ad-7e60-c1bb5fb9aa2a]: write: failure to update connection: writing settings not supported
Jan 11 14:11:35 shkim-A320MH NetworkManager[3218]: <info>  [1610341895.6806] get unmanaged devices count: 2
Jan 11 14:11:35 shkim-A320MH systemd[1]: Found device AM43xx1.2.
Jan 11 14:11:35 shkim-A320MH systemd[1]: Started ifup for enp9s0f4u1.
Jan 11 14:11:35 shkim-A320MH upowerd[1547]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1/5-1:1.0
Jan 11 14:11:35 shkim-A320MH upowerd[1547]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1
Jan 11 14:11:35 shkim-A320MH NetworkManager[3218]: <info>  [1610341895.7080] device (enp9s0f4u1): carrier: link connected
Jan 11 14:11:35 shkim-A320MH avahi-daemon[612]: Joining mDNS multicast group on interface enp9s0f4u1.IPv4 with address 192.168.2.1.
Jan 11 14:11:35 shkim-A320MH avahi-daemon[612]: New relevant interface enp9s0f4u1.IPv4 for mDNS.
Jan 11 14:11:35 shkim-A320MH avahi-daemon[612]: Registering new address record for 192.168.2.1 on enp9s0f4u1.IPv4.
Jan 11 14:11:35 shkim-A320MH systemd[1]: Stopping ISC DHCP IPv4 server...
Jan 11 14:11:35 shkim-A320MH systemd[1]: Stopped ISC DHCP IPv4 server.
Jan 11 14:11:35 shkim-A320MH systemd[1]: Started ISC DHCP IPv4 server.
Jan 11 14:11:35 shkim-A320MH dhcpd[9025]: Internet Systems Consortium DHCP Server 4.3.5
Jan 11 14:11:35 shkim-A320MH dhcpd[9025]: Copyright 2004-2016 Internet Systems Consortium.
Jan 11 14:11:35 shkim-A320MH sh[9025]: Internet Systems Consortium DHCP Server 4.3.5
Jan 11 14:11:35 shkim-A320MH sh[9025]: Copyright 2004-2016 Internet Systems Consortium.
Jan 11 14:11:35 shkim-A320MH sh[9025]: All rights reserved.
Jan 11 14:11:35 shkim-A320MH sh[9025]: For info, please visit https://www.isc.org/software/dhcp/
Jan 11 14:11:35 shkim-A320MH dhcpd[9025]: All rights reserved.
Jan 11 14:11:35 shkim-A320MH dhcpd[9025]: For info, please visit https://www.isc.org/software/dhcp/
Jan 11 14:11:35 shkim-A320MH dhcpd[9025]: Config file: /etc/dhcp/dhcpd.conf
Jan 11 14:11:35 shkim-A320MH sh[9025]: Config file: /etc/dhcp/dhcpd.conf
Jan 11 14:11:35 shkim-A320MH sh[9025]: Database file: /var/lib/dhcp/dhcpd.leases
Jan 11 14:11:35 shkim-A320MH sh[9025]: PID file: /run/dhcp-server/dhcpd.pid
Jan 11 14:11:35 shkim-A320MH dhcpd[9025]: Database file: /var/lib/dhcp/dhcpd.leases
Jan 11 14:11:35 shkim-A320MH dhcpd[9025]: PID file: /run/dhcp-server/dhcpd.pid
Jan 11 14:11:35 shkim-A320MH dhcpd[9025]: Internet Systems Consortium DHCP Server 4.3.5
Jan 11 14:11:35 shkim-A320MH dhcpd[9025]: Copyright 2004-2016 Internet Systems Consortium.
Jan 11 14:11:35 shkim-A320MH dhcpd[9025]: All rights reserved.
Jan 11 14:11:35 shkim-A320MH dhcpd[9025]: For info, please visit https://www.isc.org/software/dhcp/
Jan 11 14:11:35 shkim-A320MH dhcpd[9025]: Wrote 1 leases to leases file.
Jan 11 14:11:35 shkim-A320MH sh[9025]: Wrote 1 leases to leases file.
Jan 11 14:11:35 shkim-A320MH dhcpd[9025]: Listening on LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:35 shkim-A320MH sh[9025]: Listening on LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:35 shkim-A320MH sh[9025]: Sending on   LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:35 shkim-A320MH sh[9025]: Sending on   Socket/fallback/fallback-net
Jan 11 14:11:35 shkim-A320MH dhcpd[9025]: Sending on   LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:35 shkim-A320MH dhcpd[9025]: Sending on   Socket/fallback/fallback-net
Jan 11 14:11:35 shkim-A320MH dhcpd[9025]: Server starting service.
Jan 11 14:11:35 shkim-A320MH systemd[1]: Stopping ISC DHCP IPv4 server...
Jan 11 14:11:35 shkim-A320MH systemd[1]: Stopped ISC DHCP IPv4 server.
Jan 11 14:11:35 shkim-A320MH systemd[1]: Started ISC DHCP IPv4 server.
Jan 11 14:11:35 shkim-A320MH dhcpd[9104]: Internet Systems Consortium DHCP Server 4.3.5
Jan 11 14:11:35 shkim-A320MH dhcpd[9104]: Copyright 2004-2016 Internet Systems Consortium.
Jan 11 14:11:35 shkim-A320MH sh[9104]: Internet Systems Consortium DHCP Server 4.3.5
Jan 11 14:11:35 shkim-A320MH sh[9104]: Copyright 2004-2016 Internet Systems Consortium.
Jan 11 14:11:35 shkim-A320MH sh[9104]: All rights reserved.
Jan 11 14:11:35 shkim-A320MH sh[9104]: For info, please visit https://www.isc.org/software/dhcp/
Jan 11 14:11:35 shkim-A320MH dhcpd[9104]: All rights reserved.
Jan 11 14:11:35 shkim-A320MH dhcpd[9104]: For info, please visit https://www.isc.org/software/dhcp/
Jan 11 14:11:35 shkim-A320MH dhcpd[9104]: Config file: /etc/dhcp/dhcpd.conf
Jan 11 14:11:35 shkim-A320MH sh[9104]: Config file: /etc/dhcp/dhcpd.conf
Jan 11 14:11:35 shkim-A320MH sh[9104]: Database file: /var/lib/dhcp/dhcpd.leases
Jan 11 14:11:35 shkim-A320MH sh[9104]: PID file: /run/dhcp-server/dhcpd.pid
Jan 11 14:11:35 shkim-A320MH dhcpd[9104]: Database file: /var/lib/dhcp/dhcpd.leases
Jan 11 14:11:35 shkim-A320MH dhcpd[9104]: PID file: /run/dhcp-server/dhcpd.pid
Jan 11 14:11:35 shkim-A320MH dhcpd[9104]: Internet Systems Consortium DHCP Server 4.3.5
Jan 11 14:11:35 shkim-A320MH dhcpd[9104]: Copyright 2004-2016 Internet Systems Consortium.
Jan 11 14:11:35 shkim-A320MH dhcpd[9104]: All rights reserved.
Jan 11 14:11:35 shkim-A320MH dhcpd[9104]: For info, please visit https://www.isc.org/software/dhcp/
Jan 11 14:11:35 shkim-A320MH dhcpd[9104]: Wrote 1 leases to leases file.
Jan 11 14:11:35 shkim-A320MH sh[9104]: Wrote 1 leases to leases file.
Jan 11 14:11:35 shkim-A320MH dhcpd[9104]: Listening on LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:35 shkim-A320MH sh[9104]: Listening on LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:35 shkim-A320MH sh[9104]: Sending on   LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:35 shkim-A320MH sh[9104]: Sending on   Socket/fallback/fallback-net
Jan 11 14:11:35 shkim-A320MH dhcpd[9104]: Sending on   LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:35 shkim-A320MH dhcpd[9104]: Sending on   Socket/fallback/fallback-net
Jan 11 14:11:35 shkim-A320MH dhcpd[9104]: Server starting service.
Jan 11 14:11:37 shkim-A320MH avahi-daemon[612]: Joining mDNS multicast group on interface enp9s0f4u1.IPv6 with address fe80::a888:39ff:fef6:ffed.
Jan 11 14:11:37 shkim-A320MH avahi-daemon[612]: New relevant interface enp9s0f4u1.IPv6 for mDNS.
Jan 11 14:11:37 shkim-A320MH avahi-daemon[612]: Registering new address record for fe80::a888:39ff:fef6:ffed on enp9s0f4u1.*.
Jan 11 14:11:38 shkim-A320MH ModemManager[611]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1': not supported by any plugin
Jan 11 14:11:40 shkim-A320MH atftpd[3194]: timeout: retrying...
Jan 11 14:11:41 shkim-A320MH dhcpd[9104]: reuse_lease: lease age 1741417 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.2.2
Jan 11 14:11:41 shkim-A320MH dhcpd[9104]: BOOTREQUEST from c4:be:84:cc:86:6b via enp9s0f4u1
Jan 11 14:11:41 shkim-A320MH dhcpd[9104]: BOOTREPLY on 192.168.2.2 to c4:be:84:cc:86:6b via enp9s0f4u1
Jan 11 14:11:41 shkim-A320MH kernel: [  567.434453] usb 5-1: USB disconnect, device number 19
Jan 11 14:11:41 shkim-A320MH kernel: [  567.435475] rndis_host 5-1:1.0 enp9s0f4u1: unregister 'rndis_host' usb-0000:09:00.4-1, RNDIS device
Jan 11 14:11:41 shkim-A320MH dhcpd[9104]: receive_packet failed on enp9s0f4u1: Network is down
Jan 11 14:11:41 shkim-A320MH avahi-daemon[612]: Interface enp9s0f4u1.IPv6 no longer relevant for mDNS.
Jan 11 14:11:41 shkim-A320MH avahi-daemon[612]: Leaving mDNS multicast group on interface enp9s0f4u1.IPv6 with address fe80::a888:39ff:fef6:ffed.
Jan 11 14:11:41 shkim-A320MH avahi-daemon[612]: Interface enp9s0f4u1.IPv4 no longer relevant for mDNS.
Jan 11 14:11:41 shkim-A320MH avahi-daemon[612]: Leaving mDNS multicast group on interface enp9s0f4u1.IPv4 with address 192.168.2.1.
Jan 11 14:11:41 shkim-A320MH avahi-daemon[612]: Withdrawing address record for fe80::a888:39ff:fef6:ffed on enp9s0f4u1.
Jan 11 14:11:41 shkim-A320MH avahi-daemon[612]: Withdrawing address record for 192.168.2.1 on enp9s0f4u1.
Jan 11 14:11:41 shkim-A320MH NetworkManager[3218]: <info>  [1610341901.8122] devices removed (path: /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1/5-1:1.0/net/enp9s0f4u1, iface: enp9s0f4u1)
Jan 11 14:11:41 shkim-A320MH NetworkManager[3218]: <info>  [1610341901.8123] get unmanaged devices count: 1
Jan 11 14:11:41 shkim-A320MH systemd[1]: Stopping ifup for enp9s0f4u1...
Jan 11 14:11:41 shkim-A320MH ifdown[9197]: Cannot find device "enp9s0f4u1"
Jan 11 14:11:41 shkim-A320MH upowerd[1547]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1/5-1:1.1
Jan 11 14:11:41 shkim-A320MH upowerd[1547]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1/5-1:1.0
Jan 11 14:11:41 shkim-A320MH upowerd[1547]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1
Jan 11 14:11:41 shkim-A320MH ifdown[9197]: Cannot find device "enp9s0f4u1"
Jan 11 14:11:41 shkim-A320MH systemd[1]: Stopped ifup for enp9s0f4u1.
Jan 11 14:11:42 shkim-A320MH kernel: [  567.736332] usb 5-1: new full-speed USB device number 20 using xhci_hcd
Jan 11 14:11:42 shkim-A320MH kernel: [  567.892493] usb 5-1: not running at top speed; connect to a high speed hub
Jan 11 14:11:42 shkim-A320MH kernel: [  567.917485] usb 5-1: New USB device found, idVendor=0451, idProduct=6142, bcdDevice= 0.00
Jan 11 14:11:42 shkim-A320MH kernel: [  567.917490] usb 5-1: New USB device strings: Mfr=33, Product=37, SerialNumber=0
Jan 11 14:11:42 shkim-A320MH kernel: [  567.917493] usb 5-1: Product: AM43xx1.2
Jan 11 14:11:42 shkim-A320MH kernel: [  567.917495] usb 5-1: Manufacturer: Texas Instruments
Jan 11 14:11:42 shkim-A320MH NetworkManager[3218]: <info>  [1610341902.3353] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/27)
Jan 11 14:11:42 shkim-A320MH kernel: [  567.968838] rndis_host 5-1:1.0 usb0: register 'rndis_host' at usb-0000:09:00.4-1, RNDIS device, 0e:63:17:6c:f4:83
Jan 11 14:11:42 shkim-A320MH mtp-probe: checking bus 5, device 20: "/sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1"
Jan 11 14:11:42 shkim-A320MH mtp-probe: bus: 5, device: 20 was not an MTP device
Jan 11 14:11:42 shkim-A320MH systemd-udevd[9283]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 11 14:11:42 shkim-A320MH kernel: [  567.987423] rndis_host 5-1:1.0 enp9s0f4u1: renamed from usb0
Jan 11 14:11:42 shkim-A320MH upowerd[1547]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1/5-1:1.1
Jan 11 14:11:42 shkim-A320MH NetworkManager[3218]: <info>  [1610341902.3940] devices added (path: /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1/5-1:1.0/net/enp9s0f4u1, iface: enp9s0f4u1)
Jan 11 14:11:42 shkim-A320MH NetworkManager[3218]: <info>  [1610341902.3941] locking wired connection setting
Jan 11 14:11:42 shkim-A320MH NetworkManager[3218]: <info>  [1610341902.3941] settings-connection[0x555cd8ba2c40,e257b6d7-196c-67ad-7e60-c1bb5fb9aa2a]: write: failure to update connection: writing settings not supported
Jan 11 14:11:42 shkim-A320MH NetworkManager[3218]: <info>  [1610341902.3941] get unmanaged devices count: 2
Jan 11 14:11:42 shkim-A320MH systemd[1]: Found device AM43xx1.2.
Jan 11 14:11:42 shkim-A320MH systemd[1]: Started ifup for enp9s0f4u1.
Jan 11 14:11:42 shkim-A320MH upowerd[1547]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1/5-1:1.0
Jan 11 14:11:42 shkim-A320MH upowerd[1547]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1
Jan 11 14:11:42 shkim-A320MH avahi-daemon[612]: Joining mDNS multicast group on interface enp9s0f4u1.IPv4 with address 192.168.2.1.
Jan 11 14:11:42 shkim-A320MH NetworkManager[3218]: <info>  [1610341902.4198] device (enp9s0f4u1): carrier: link connected
Jan 11 14:11:42 shkim-A320MH avahi-daemon[612]: New relevant interface enp9s0f4u1.IPv4 for mDNS.
Jan 11 14:11:42 shkim-A320MH avahi-daemon[612]: Registering new address record for 192.168.2.1 on enp9s0f4u1.IPv4.
Jan 11 14:11:42 shkim-A320MH systemd[1]: Stopping ISC DHCP IPv4 server...
Jan 11 14:11:42 shkim-A320MH systemd[1]: Stopped ISC DHCP IPv4 server.
Jan 11 14:11:42 shkim-A320MH systemd[1]: Started ISC DHCP IPv4 server.
Jan 11 14:11:42 shkim-A320MH dhcpd[9336]: Internet Systems Consortium DHCP Server 4.3.5
Jan 11 14:11:42 shkim-A320MH sh[9336]: Internet Systems Consortium DHCP Server 4.3.5
Jan 11 14:11:42 shkim-A320MH sh[9336]: Copyright 2004-2016 Internet Systems Consortium.
Jan 11 14:11:42 shkim-A320MH sh[9336]: All rights reserved.
Jan 11 14:11:42 shkim-A320MH sh[9336]: For info, please visit https://www.isc.org/software/dhcp/
Jan 11 14:11:42 shkim-A320MH dhcpd[9336]: Copyright 2004-2016 Internet Systems Consortium.
Jan 11 14:11:42 shkim-A320MH dhcpd[9336]: All rights reserved.
Jan 11 14:11:42 shkim-A320MH dhcpd[9336]: For info, please visit https://www.isc.org/software/dhcp/
Jan 11 14:11:42 shkim-A320MH dhcpd[9336]: Config file: /etc/dhcp/dhcpd.conf
Jan 11 14:11:42 shkim-A320MH sh[9336]: Config file: /etc/dhcp/dhcpd.conf
Jan 11 14:11:42 shkim-A320MH sh[9336]: Database file: /var/lib/dhcp/dhcpd.leases
Jan 11 14:11:42 shkim-A320MH sh[9336]: PID file: /run/dhcp-server/dhcpd.pid
Jan 11 14:11:42 shkim-A320MH dhcpd[9336]: Database file: /var/lib/dhcp/dhcpd.leases
Jan 11 14:11:42 shkim-A320MH dhcpd[9336]: PID file: /run/dhcp-server/dhcpd.pid
Jan 11 14:11:42 shkim-A320MH dhcpd[9336]: Internet Systems Consortium DHCP Server 4.3.5
Jan 11 14:11:42 shkim-A320MH dhcpd[9336]: Copyright 2004-2016 Internet Systems Consortium.
Jan 11 14:11:42 shkim-A320MH dhcpd[9336]: All rights reserved.
Jan 11 14:11:42 shkim-A320MH dhcpd[9336]: For info, please visit https://www.isc.org/software/dhcp/
Jan 11 14:11:42 shkim-A320MH dhcpd[9336]: Wrote 1 leases to leases file.
Jan 11 14:11:42 shkim-A320MH sh[9336]: Wrote 1 leases to leases file.
Jan 11 14:11:42 shkim-A320MH dhcpd[9336]: Listening on LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:42 shkim-A320MH sh[9336]: Listening on LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:42 shkim-A320MH sh[9336]: Sending on   LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:42 shkim-A320MH sh[9336]: Sending on   Socket/fallback/fallback-net
Jan 11 14:11:42 shkim-A320MH dhcpd[9336]: Sending on   LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:42 shkim-A320MH dhcpd[9336]: Sending on   Socket/fallback/fallback-net
Jan 11 14:11:42 shkim-A320MH dhcpd[9336]: Server starting service.
Jan 11 14:11:42 shkim-A320MH systemd[1]: Stopping ISC DHCP IPv4 server...
Jan 11 14:11:42 shkim-A320MH systemd[1]: Stopped ISC DHCP IPv4 server.
Jan 11 14:11:42 shkim-A320MH systemd[1]: Started ISC DHCP IPv4 server.
Jan 11 14:11:42 shkim-A320MH dhcpd[9418]: Internet Systems Consortium DHCP Server 4.3.5
Jan 11 14:11:42 shkim-A320MH dhcpd[9418]: Copyright 2004-2016 Internet Systems Consortium.
Jan 11 14:11:42 shkim-A320MH sh[9418]: Internet Systems Consortium DHCP Server 4.3.5
Jan 11 14:11:42 shkim-A320MH sh[9418]: Copyright 2004-2016 Internet Systems Consortium.
Jan 11 14:11:42 shkim-A320MH sh[9418]: All rights reserved.
Jan 11 14:11:42 shkim-A320MH sh[9418]: For info, please visit https://www.isc.org/software/dhcp/
Jan 11 14:11:42 shkim-A320MH dhcpd[9418]: All rights reserved.
Jan 11 14:11:42 shkim-A320MH dhcpd[9418]: For info, please visit https://www.isc.org/software/dhcp/
Jan 11 14:11:42 shkim-A320MH dhcpd[9418]: Config file: /etc/dhcp/dhcpd.conf
Jan 11 14:11:42 shkim-A320MH sh[9418]: Config file: /etc/dhcp/dhcpd.conf
Jan 11 14:11:42 shkim-A320MH sh[9418]: Database file: /var/lib/dhcp/dhcpd.leases
Jan 11 14:11:42 shkim-A320MH sh[9418]: PID file: /run/dhcp-server/dhcpd.pid
Jan 11 14:11:42 shkim-A320MH dhcpd[9418]: Database file: /var/lib/dhcp/dhcpd.leases
Jan 11 14:11:42 shkim-A320MH sh[9418]: Wrote 1 leases to leases file.
Jan 11 14:11:42 shkim-A320MH dhcpd[9418]: PID file: /run/dhcp-server/dhcpd.pid
Jan 11 14:11:42 shkim-A320MH dhcpd[9418]: Internet Systems Consortium DHCP Server 4.3.5
Jan 11 14:11:42 shkim-A320MH dhcpd[9418]: Copyright 2004-2016 Internet Systems Consortium.
Jan 11 14:11:42 shkim-A320MH dhcpd[9418]: All rights reserved.
Jan 11 14:11:42 shkim-A320MH dhcpd[9418]: For info, please visit https://www.isc.org/software/dhcp/
Jan 11 14:11:42 shkim-A320MH dhcpd[9418]: Wrote 1 leases to leases file.
Jan 11 14:11:42 shkim-A320MH dhcpd[9418]: Listening on LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:42 shkim-A320MH sh[9418]: Listening on LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:42 shkim-A320MH sh[9418]: Sending on   LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:42 shkim-A320MH sh[9418]: Sending on   Socket/fallback/fallback-net
Jan 11 14:11:42 shkim-A320MH dhcpd[9418]: Sending on   LPF/enp9s0f4u1/aa:88:39:f6:ff:ed/192.168.2.0/24
Jan 11 14:11:42 shkim-A320MH dhcpd[9418]: Sending on   Socket/fallback/fallback-net
Jan 11 14:11:42 shkim-A320MH dhcpd[9418]: Server starting service.
Jan 11 14:11:43 shkim-A320MH avahi-daemon[612]: Joining mDNS multicast group on interface enp9s0f4u1.IPv6 with address fe80::a888:39ff:fef6:ffed.
Jan 11 14:11:43 shkim-A320MH avahi-daemon[612]: New relevant interface enp9s0f4u1.IPv6 for mDNS.
Jan 11 14:11:43 shkim-A320MH avahi-daemon[612]: Registering new address record for fe80::a888:39ff:fef6:ffed on enp9s0f4u1.*.
Jan 11 14:11:44 shkim-A320MH ModemManager[611]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1': not supported by any plugin
Jan 11 14:11:46 shkim-A320MH atftpd[3194]: timeout: retrying...
Jan 11 14:11:47 shkim-A320MH dhcpd[9418]: reuse_lease: lease age 1741424 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.2.2
Jan 11 14:11:47 shkim-A320MH dhcpd[9418]: BOOTREQUEST from c4:be:84:cc:86:6b via enp9s0f4u1
Jan 11 14:11:47 shkim-A320MH dhcpd[9418]: BOOTREPLY on 192.168.2.2 to c4:be:84:cc:86:6b via enp9s0f4u1
Jan 11 14:11:48 shkim-A320MH kernel: [  574.146939] usb 5-1: USB disconnect, device number 20
Jan 11 14:11:48 shkim-A320MH kernel: [  574.147040] rndis_host 5-1:1.0 enp9s0f4u1: unregister 'rndis_host' usb-0000:09:00.4-1, RNDIS device
Jan 11 14:11:48 shkim-A320MH dhcpd[9418]: receive_packet failed on enp9s0f4u1: Network is down
Jan 11 14:11:48 shkim-A320MH avahi-daemon[612]: Interface enp9s0f4u1.IPv6 no longer relevant for mDNS.
Jan 11 14:11:48 shkim-A320MH avahi-daemon[612]: Leaving mDNS multicast group on interface enp9s0f4u1.IPv6 with address fe80::a888:39ff:fef6:ffed.
Jan 11 14:11:48 shkim-A320MH avahi-daemon[612]: Interface enp9s0f4u1.IPv4 no longer relevant for mDNS.
Jan 11 14:11:48 shkim-A320MH avahi-daemon[612]: Leaving mDNS multicast group on interface enp9s0f4u1.IPv4 with address 192.168.2.1.
Jan 11 14:11:48 shkim-A320MH avahi-daemon[612]: Withdrawing address record for fe80::a888:39ff:fef6:ffed on enp9s0f4u1.
Jan 11 14:11:48 shkim-A320MH avahi-daemon[612]: Withdrawing address record for 192.168.2.1 on enp9s0f4u1.
Jan 11 14:11:48 shkim-A320MH NetworkManager[3218]: <info>  [1610341908.5256] devices removed (path: /sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1/5-1:1.0/net/enp9s0f4u1,

capture_via_USB0_20210111.zip

0 Bin Liu over 3 years ago in reply to Sung Hwan Kim80

TI__Guru*** 125116 points

Hi,

The syslog shows there is atftp timeout error. I just reviewed the document "6.1.9 Ubuntu 14.04 Set Up to Network Boot an AM335x/AM437x Based Platform", and think there is an error in the dhcpd configuration.

   elsif substring (option vendor-class-identifier, 0, 10) = "AM43xx ROM"
   {
      filename "u-boot-restore.img";
   }

The filename above should be "u-boot-spl-restore.bin" instead, ROM should download the spl binary, not u-boot.img. Can you please change it on your PC and see if it works?

0 Sung Hwan Kim80 over 3 years ago in reply to Bin Liu

Prodigy 160 points

Hello,

I updated u-boot-spl-restore.bin to /etc/dhcp/dhcpd.conf as per your comment.

I attached syslog and wireshark capture via USB port (enp9s0f4u1),which was used the same USB port as previous captures, for it.

Would you advice it is operated right way and why it is paused without u-boot?

I tried to see u-boot via serial connection USB0 port of AM437x starter kit in parallel USB port(enp9s0f4u1)

as per "It is very helpful to have a serial console connection to watch the process proceed." from TI document "Ubuntu 14.04 Set Up to Network Boot an AM335x/AM437x Based Platform".

But I could not see u-boot progress and any other prompt from a serial connection USB0 port of AM437x starter kit.

I used images are provided with the SDK in the board-support/prebuilt-images directory within the SDK install. For U-Boot, simply copy the appropriate u-boot-spl.bin-am437x-evm and and u-boot-am437x-evm.img files to the /tftpboot directory and rename them to u-boot-spl-restore.bin and u-boot-restore.img, respectively and added am437x-sk-evm.dtb to the /tftpboot directory .

Thank you in advance.

wireshark_capture_20210114_am.zip

syslog for usb_20210114_am.txt

Jan 14 11:12:06 shkim-A320MH dhcpd[6332]: Server starting service.
Jan 14 11:12:08 shkim-A320MH avahi-daemon[661]: Joining mDNS multicast group on interface enp9s0f4u1.IPv6 with address fe80::a888:39ff:fef6:ffed.
Jan 14 11:12:08 shkim-A320MH avahi-daemon[661]: New relevant interface enp9s0f4u1.IPv6 for mDNS.
Jan 14 11:12:08 shkim-A320MH avahi-daemon[661]: Registering new address record for fe80::a888:39ff:fef6:ffed on enp9s0f4u1.*.
Jan 14 11:12:09 shkim-A320MH ModemManager[663]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:08.1/0000:09:00.4/usb5/5-1': not supported by any plugin
Jan 14 11:12:10 shkim-A320MH kernel: [ 6579.588643] device enp9s0f4u1 entered promiscuous mode
Jan 14 11:12:11 shkim-A320MH dhcpd[6332]: reuse_lease: lease age 1989848 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.2.2
Jan 14 11:12:11 shkim-A320MH dhcpd[6332]: BOOTREQUEST from c4:be:84:cc:86:6b via enp9s0f4u1
Jan 14 11:12:11 shkim-A320MH dhcpd[6332]: BOOTREPLY on 192.168.2.2 to c4:be:84:cc:86:6b via enp9s0f4u1
Jan 14 11:12:11 shkim-A320MH atftpd[5083]: Serving u-boot-spl-restore.bin to 192.168.2.2:1234
Jan 14 11:12:54 shkim-A320MH org.gnome.Shell.desktop[2243]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00084 (syslog [Re)
Jan 14 11:13:13 shkim-A320MH kernel: [ 6642.327717] device enp9s0f4u1 left promiscuous mode

0 Bin Liu over 3 years ago in reply to Sung Hwan Kim80

TI__Guru*** 125116 points

Hi,

The wireshark log shows u-boot-spl-restore.bin is transferred to the evm, but doesn't have further action from the evm. We are expecting the BOOTP request coming from u-boot-spl-restore.bin to download u-boot-restore.img. So it seems either the execution doesn't transition to u-boot-spl, or the u-boot-spl image has some issue for usb-ethernet boot mode.

I am currently working from home and don't have the setup for reproducing the issue. I will go to office next Tuesday to test this and get you back.

0 Sung Hwan Kim80 over 3 years ago in reply to Bin Liu

Prodigy 160 points

Hello,

I add below sysboot[4:0] setting for reference.

I was modified sysboot[4:0] from 11000 to 11101. Because the AM437x TRM for USB0 show sysboot[4:0] 11101 of AM437x starter kit board should be configured to boot from USB_CL(USB0).

So, sysboot[4:0] 11101 of AM437x starter kit board were applied to the previous test results, which were attached as syslogs and wireshark captures.

I also used the pre-built images of SDK 06.03.00.106 for u-boot-spl-restore.bin, u-boot-restore.img and am437x-sk-evm.dtb.

I reviewed the last post and corrected the USB port designation(red colored) for AM437x starter kit as below.

-----------------------------------------------------------------------------------------

I updated u-boot-spl-restore.bin to /etc/dhcp/dhcpd.conf as per your comment.

I attached syslog and wireshark capture via USB0 port (enp9s0f4u1),which was used the same USB port as previous captures, for it.

Would you advice it is operated right way and why it is paused without u-boot?

I tried to see u-boot via serial connection USB JTAG(J25) port of AM437x starter kit in parallel USB port(enp9s0f4u1)

as per "It is very helpful to have a serial console connection to watch the process proceed." from TI document "Ubuntu 14.04 Set Up to Network Boot an AM335x/AM437x Based Platform".

But I could not see u-boot progress and any other prompt from a serial connection USB JTAG(J25) port of AM437x starter kit.

-------------------------------------------------------------------------------------------------------------------------------------

Thank you for your support.

0 Bin Liu over 3 years ago in reply to Sung Hwan Kim80

TI__Guru*** 125116 points

Hi,

I tested this on my AM437x EVM with Ubuntu 18.04, and don't see any issue.

Here is the uart console log:

U-Boot SPL 2019.01-g8b90adfb16 (Jul 07 2019 - 10:12:46 +0000)
Trying to boot from USB eth
Loading Environment from FAT... Card did not respond to voltage select!

Warning: ethernet@4a100000 using MAC address from ROM
eth0: ethernet@4a100000
Warning: usb_ether using MAC address from ROM
, eth1: usb_ether
using dwc3-gadget, OUT ep2out IN ep1in STATUS ep3in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
USB RNDIS network up!
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
DHCP client bound to address 192.168.3.103 (1258 ms)
Using usb_ether device
TFTP from server 192.168.3.10; our IP address is 192.168.3.103
Filename 'u-boot-am437x-evm.img'.
Load address: 0x82000000
Loading: ##################################################
         8.9 MiB/s
done
Bytes transferred = 722360 (b05b8 hex)


U-Boot 2019.01-g8b90adfb16 (Jul 07 2019 - 10:12:46 +0000)

CPU  : AM437X-GP rev 1.2
Model: TI AM437x GP EVM
DRAM:  2 GiB
PMIC:  TPS65218
NAND:  512 MiB
MMC:   OMAP SD/MMC: 0
Loading Environment from FAT... MMC: no card present
Net:
Warning: ethernet@4a100000 using MAC address from ROM
eth0: ethernet@4a100000
Hit any key to stop autoboot:  0

And here is the wireshark capture.

am437x-usbboot-spl.pcapng.zip

0 Sung Hwan Kim80 over 3 years ago in reply to Bin Liu

Prodigy 160 points

Hello,

I saw your trial result well for AM437X-GP evm. In my view, you used UART port(J9) of AM437X-GP evm.

I used AM437X-STARTER-KIT for USB0 network boot. So, I used USB-to-UART port(USB JTAG) of AM437X-STARTER-KIT to see U-BOOT prompt via minicom ttyUSB0/1.

But I could not find any U-BOOT prompt. So, I have questions for it.

- Could I use USB-to-UART port(USB JTAG J25) of AM437X-STARTER-KIT to see U-BOOT prompt?

- How could I see U-BOOT prompt of AM437X-STARTER-KIT if USB-to-UART port(USB JTAG J25) could not be used?

Because the AM437X-STARTER-KIT for USB0 network boot seems to be worked via USB0 port as your Wireshark capture trial for AM437X-GP evm.

Thank you in advance.

Processors

Processors forum

TMDXSK437X: Request technical advice to set up Network Boot via USB0 of AM437x STARTER KIT