Tiny Core Base > Raspberry Pi

USB gadget kernel module with RPi zero

<< < (14/18) > >>

creitzel:
You were definitely on the right track Rich.  I was just going to post that I figured out how to get the dwc2 module to load.

After I posted this, I found another post that was having the same problem with dwc2 on 13.x, and the missing module was "roles.ko", so I included that in my tcz as well, and now it seems to be loading fine.  As for the "udc_core.ko", I'm pretty sure I already have that one, because I copied the entire "gadgets" sub folder into my tcz, and it is in there.  I found the need for "roles.ko" using your "modinfo dwc2" command.   :)

So, now it appears to load the modules correctly on boot, and it creates the usb0 device, and the ifconfig statement works to assign the ip, and bring the interface up. 

Now I'm stuck where I can't seem to ping it or ssh into it, from my windows 10 machine.  I've tried scanning for new hardware on the Win10 box, but that doesn't seem to do anything.  Do I have to somehow point ssh to the usb ip or something?  Although, the fact that ping doesn't work either, is kinda telling me that the problem may be on the Win10 side.

Sorry, for my lack of knowledge, I'm fairly new to this part of linux/piCore.

Thanks for any help you can give in advance,

Chris

Rich:
Hi creitzel
I think the way to connect to the pi remotely goes something like:

--- Code: ---ssh tc@aaa.bbb.ccc.ddd
--- End code ---
where  aaa.bbb.ccc.ddd  is the IP address of your pi.

creitzel:
yeah, that would be the way I would ssh from a command line in win10.  I also have putty installed, which allows ssh connections as well. 

The problem I have right now, is the win10 box doesn't seem to recognize the fixed ip that I gave to the pi, it just keeps timing out whenever I try to access it. 

I think I'll give it a go from my linux laptop, and see if that can recognize it.

Thanks for all you help, it's much appreciated. 

Rich:
Hi creitzel
Are both machines on the same subnet? i.e. Are they both  192.168.1.xxx  or 10.10.1.xxx.

creitzel:
Just for completeness, I've tried both with it on my subnet, and with it on a different subnet.  Either way, if I try to ping to the ip that I've assigned to it, it times out, like it would if there was no machine at that ip.

It is also connecting via wifi on my lan's subnet, which is currently how I'm able to work on it, because once I enabled dwc2, my usb hub HAT that is connected via the gpio pins has stopped working, so my usb keyboard isn't working right now.

I also now have tried it with my linux laptop, with the same results.  i.e. ping times out when I try to ping the ip assigned to the pi.

I'm not sure what else to check on the win10/linux box side.  There must be something I'm still missing on the pi side.

Navigation

[0] Message Index

[#] Next page

[*] Previous page