Connect via ssh to Ultra96

Hi,

I'm not sure if you ever solved this, however I had the same issue and followed this Xilinx confluence page under the "Ethernet Gadget" section with success:

https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841729/Zynq+Ultrascale+MPSOC+Linux+USB+device+driver#ZynqUltrasc…

The confluence page looks like it was written for v2016.2 of the tools, however I used 2018.3 and the only thing different was the kernel configuration menu options have changed a bit (the changes are intuitive to figure out), and I used built in configuration <*> instead of module <M> setup.  If you build them into the image, you do not have to do all of the insmod and mount of configfs under the "Testing Procedure".  I also scripted the commands under "Testing Procedure" and set them up to autorun at boot following the methodology described under the section "Application Auto Run at Startup" in the Petalinux Tools Reference Guide https://www.xilinx.com/support/documentation/sw_manuals/xilinx2018_3/ug1144-petalinux-tools-reference-guide.pdf .  That way each time you boot the configuration of the USB ethernet and setup of the ip address is done automatically.

One thing to note; I did notice that the step:

echo "fe200000.dwc3" > UDC

Will send a console message stating that the device is busy, this did not appear to have an impact on functionality.

For the Device tree section, the entry:

  usb0: usb@fe200000 {

    #address-cells = <2>;

    #size-cells = <2>;

    status = "disabled";

    compatible = "xlnx,zynqmp-dwc3";

    clock-names = "bus_clk", "ref_clk";

    clocks = <&clk125>, <&clk125>;

    dwc3_0: dwc3@fe200000 {

        compatible = "snps,dwc3";

        status = "disabled";

        reg = <0x0 0xfe200000 0x0 0x40000>;

        interrupt-parent = <&gic>;

        interrupts = <0 65 4>;

    };

};

is automatically generated in 'zynqmp.dtsi'.

You will need to add the entries:

&usb0 {

    status = "okay";

};

&dwc3_0 {

    status = "okay";

    dr_mode = "peripheral";

};

to your 'system-user.dtsi' in your petalinux project.

Also note.  I just used a standard micro-USB cable for this, I did not require any special adapters.  I'm not sure what the discussion of the adapter is referring to though I suspect it to be errant?

Once you boot the target and you've implemented the commands under "Testing Procedure", on your host if you run "ifconfig" (under Linux, probably ipconfig under Windows), you'll see a new ethernet interface listed.  You'll need to assign it an ip address that matches whatever subnet you used for the IP address in the commands under "Testing Procedure".  So for me on my target I assigned 10.10.7.1  so on my host I assigned 10.10.7.2.  After this you can ping, ssh and scp files back and forth.

It appears as though the gadget ethernet is point to point, so host-to-target seems to be all I can get in terms of functionality.  I've not figured out how to bridge it to the rest of the network (and I'm not sure if it was intended to work that way or not).  So when you pick your subnet, choose a different subnet than the rest of your network or your host machine will not be able to communicate with the network while the gadget interface is up and running.  If anyone has a suggestion on how to bridge the network or place the gadget ethernet connection on the same subnet as the host network, I'd appreciate a follow up post.

I hope this helps.

Hi,

I'm not sure if you ever solved this, however I had the same issue and followed this Xilinx confluence page under the "Ethernet Gadget" section with success:

https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841729/Zynq+Ultrascale+MPSOC+Linux+USB+device+driver#ZynqUltrasc…

The confluence page looks like it was written for v2016.2 of the tools, however I used 2018.3 and the only thing different was the kernel configuration menu options have changed a bit (the changes are intuitive to figure out), and I used built in configuration <*> instead of module <M> setup.  If you build them into the image, you do not have to do all of the insmod and mount of configfs under the "Testing Procedure".  I also scripted the commands under "Testing Procedure" and set them up to autorun at boot following the methodology described under the section "Application Auto Run at Startup" in the Petalinux Tools Reference Guide https://www.xilinx.com/support/documentation/sw_manuals/xilinx2018_3/ug1144-petalinux-tools-reference-guide.pdf .  That way each time you boot the configuration of the USB ethernet and setup of the ip address is done automatically.

One thing to note; I did notice that the step:

echo "fe200000.dwc3" > UDC

Will send a console message stating that the device is busy, this did not appear to have an impact on functionality.

For the Device tree section, the entry:

  usb0: usb@fe200000 {

    #address-cells = <2>;

    #size-cells = <2>;

    status = "disabled";

    compatible = "xlnx,zynqmp-dwc3";

    clock-names = "bus_clk", "ref_clk";

    clocks = <&clk125>, <&clk125>;

    dwc3_0: dwc3@fe200000 {

        compatible = "snps,dwc3";

        status = "disabled";

        reg = <0x0 0xfe200000 0x0 0x40000>;

        interrupt-parent = <&gic>;

        interrupts = <0 65 4>;

    };

};

is automatically generated in 'zynqmp.dtsi'.

You will need to add the entries:

&usb0 {

    status = "okay";

};

&dwc3_0 {

    status = "okay";

    dr_mode = "peripheral";

};

to your 'system-user.dtsi' in your petalinux project.

Also note.  I just used a standard micro-USB cable for this, I did not require any special adapters.  I'm not sure what the discussion of the adapter is referring to though I suspect it to be errant?

Once you boot the target and you've implemented the commands under "Testing Procedure", on your host if you run "ifconfig" (under Linux, probably ipconfig under Windows), you'll see a new ethernet interface listed.  You'll need to assign it an ip address that matches whatever subnet you used for the IP address in the commands under "Testing Procedure".  So for me on my target I assigned 10.10.7.1  so on my host I assigned 10.10.7.2.  After this you can ping, ssh and scp files back and forth.

It appears as though the gadget ethernet is point to point, so host-to-target seems to be all I can get in terms of functionality.  I've not figured out how to bridge it to the rest of the network (and I'm not sure if it was intended to work that way or not).  So when you pick your subnet, choose a different subnet than the rest of your network or your host machine will not be able to communicate with the network while the gadget interface is up and running.  If anyone has a suggestion on how to bridge the network or place the gadget ethernet connection on the same subnet as the host network, I'd appreciate a follow up post.

I hope this helps.

How did you connect without ethernet adapter? If you issue ifconfig on your pc does the usb0 option appear? If i connect my micro-usb cable it won't appear any option on ifconfig.

I've added to etc/network/interfaces the following:

allow-hotplug usb0

auto usb0

iface usb0 inet static

    address 10.10.7.2

    netmask 255.255.255.0