Way to know which path is my usb port

[alvin0319]

I have connected a USB-A male to USB-A male to my desktop and raspberry pi

so when I run lsusb in my raspberry pi, it output follows:

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 534d:2109 MacroSilicon USB Video
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

So, it seems /dev/bus/usb/001/002 is the correct path for my USB output, so I modified app_settings.cfg file to point that file

but the following error output:

Jun 25 23:32:49 raspberrypi python[6644]: Traceback (most recent call last):
Jun 25 23:32:49 raspberrypi python[6644]:   File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
Jun 25 23:32:49 raspberrypi python[6644]:     self.run()
Jun 25 23:32:49 raspberrypi python[6644]:   File "/usr/lib/python3.9/threading.py", line 892, in run
Jun 25 23:32:49 raspberrypi python[6644]:     self._target(*self._args, **self._kwargs)
Jun 25 23:32:49 raspberrypi python[6644]:   File "/home/minjae/tinypilot/venv/lib/python3.9/site-packages/socketio/server.py", line 733, in _handle_event_internal
Jun 25 23:32:49 raspberrypi python[6644]:     r = server._trigger_event(data[0], namespace, sid, *data[1:])
Jun 25 23:32:49 raspberrypi python[6644]:   File "/home/minjae/tinypilot/venv/lib/python3.9/site-packages/socketio/server.py", line 758, in _trigger_event
Jun 25 23:32:49 raspberrypi python[6644]:     return self.handlers[namespace][event](*args)
Jun 25 23:32:49 raspberrypi python[6644]:   File "/home/minjae/tinypilot/venv/lib/python3.9/site-packages/flask_socketio/__init__.py", line 282, in _handler
Jun 25 23:32:49 raspberrypi python[6644]:     return self._handle_event(handler, message, namespace, sid,
Jun 25 23:32:49 raspberrypi python[6644]:   File "/home/minjae/tinypilot/venv/lib/python3.9/site-packages/flask_socketio/__init__.py", line 828, in _handle_event
Jun 25 23:32:49 raspberrypi python[6644]:     ret = handler(*args)
Jun 25 23:32:49 raspberrypi python[6644]:   File "/home/minjae/tinypilot/app/socket_api.py", line 68, in on_key_release
Jun 25 23:32:49 raspberrypi python[6644]:     fake_keyboard.release_keys(keyboard_path)
Jun 25 23:32:49 raspberrypi python[6644]:   File "/home/minjae/tinypilot/app/hid/keyboard.py", line 22, in release_keys
Jun 25 23:32:49 raspberrypi python[6644]:     hid_write.write_to_hid_interface(keyboard_path, [0] * 8)
Jun 25 23:32:49 raspberrypi python[6644]:   File "/home/minjae/tinypilot/app/hid/write.py", line 36, in write_to_hid_interface
Jun 25 23:32:49 raspberrypi python[6644]:     execute.with_timeout(_write_to_hid_interface_immediately,
Jun 25 23:32:49 raspberrypi python[6644]:   File "/home/minjae/tinypilot/app/execute.py", line 86, in with_timeout
Jun 25 23:32:49 raspberrypi python[6644]:     raise result.exception
Jun 25 23:32:49 raspberrypi python[6644]: OSError: [Errno 22] Invalid argument

I have modified tinypilot's socket server a bit, but I didn't modify anything related to serial input/output but I only modified socket options. so I don't think that would be a problem

Helps would be very appriciated!

[cghague]

Hi @alvin0319, thanks for your question about identifying the path to your USB port.

Unfortunately, only the USB-C port on your Raspberry Pi can emulate a USB device, so you won't be able to use a USB-A to USB-A cable. You'd instead need to use a USB-C to USB-A cable. Depending on how you power your Raspberry Pi, you may also need to purchase a TinyPilot Power Connector.

We preconfigure TinyPilot with the correct device paths, but for reference, keyboard output goes to /dev/hidg0, and mouse output to /dev/hidg1.

I hope this is helpful!

[alvin0319]

Oh, it's sad to hear that. Thank you for fast reply!