https://github.com/Ebiroll/qemu_esp32
https://github.com/espressif/qemu
Most popular esp32 simulators seem to have the above.
By the way I need a physical WiFi connection.
Are there any simulators for esp32 that support WiFi?
What do you mean by "I need a physical WiFi connection"? Software running on an emulator is abstracted from the physical network connections of the host machine. If you connect your host machine to a WiFi network then the emulator will use this WiFi to communicate. There are specific instructions in the README of the project you linked.
I have a Raspberry Pi 3B+ connected to a Macbook Air via an ethernet cable into a ethernet-USB adapter on the Macbook. I am able to connect to the Pi when my Macbook's wifi is disconnected. However, as soon as I turn on wifi, I lose signal over the ethernet connection to the Pi, and I can no longer see VNC or ssh.
I have tried:
reordering the serve preferences in the network settings
disabling / enabling internet sharing
Any thoughts would be appreciated! Many thanks
I was following the Coral Dev Board get started guide - Get started with the Dev Board (https://coral.withgoogle.com/docs/dev-board/get-started/). Everything worked fine until to the step - Connect to the board's shell via MDT.
I've waited about 5 minutes until the flashing to complete, and the terminal prompt returned to me, then I tried the command:
mdt devices
The terminal returns nothing. Unlike the guide says it supposes to return my board hostname and IP address. I've checked the USB-C OTG and USB-C power cable, they are all connected well.
I've also tried this solution: https://superuser.com/questions/1452786/coral-dev-board-not-recongized-on-mdt-shell. I went to Network under System Preferences, and clicked "+" icon, but I couldn't find the mendel device.
I'm using Macbook Pro running on macOS Catalina. The fastboot and mdt commands are both working.
I just found a solution:
Just plug micro-B USB cable, then run:
screen /dev/cu.SLAB_USBtoUART 115200
If it shows blank, wait a couple seconds, then plug usb-c power cable, the system of the dev board will start loading, the login prompt will come out. After I logged in, I plugged the usb-c cable into data port(keep the micro-B USB cable in at the same time), then run:
mdt devices
or
mdt shell
This solution works for me only when I have turned on the wifi of the dev board and connect it to the same wifi network. If you want to turn on the wifi network of coral dev board, run the command on screen terminal:
nmtui
The Network Manager TUI prompt will come out then you can connect to your wifi network.
It's a problem on macOS Catalina. It doesn't "see" USB connection as a network connection and as such it is impossible to connect to Coral Dev Board.
I have the same issue, but I tried with another MAC with older macOS and it worked just fine.
Now, I don't have yet the solution, but at least we all know the problem ;-)
Regards,
Rui
First check the that the device is detected by running dmesg command.
Normally you should see something like this
$ dmesg
...
[107834.681816] usb 2-3: new high-speed USB device number 3 using xhci_hcd
[107834.845073] usb 2-3: New USB device found, idVendor=18d1, idProduct=9304, bcdDevice= 4.19
[107834.845077] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[107834.845079] usb 2-3: Product: Mendel
[107834.845081] usb 2-3: Manufacturer: Google,LLC
[107834.845083] usb 2-3: SerialNumber: bored-horse
[107834.985296] cdc_acm 2-3:1.0: ttyACM0: USB ACM device
[107834.986069] usbcore: registered new interface driver cdc_acm
[107834.986070] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[107835.005045] cdc_ether 2-3:1.2 usb0: register 'cdc_ether' at usb-0000:06:00.3-3, CDC Ethernet Device, aa:9f:04:54:dc:45
[107835.005124] usbcore: registered new interface driver cdc_ether
[107835.019787] cdc_ether 2-3:1.2 enxaa9f0454dc45: renamed from usb0
[107897.336866] IPv6: MLD: clamping QRV from 1 to 2!
[107956.344960] usb 2-3: USB disconnect, device number 3
[107956.345357] cdc_ether 2-3:1.2 enxaa9f0454dc45: unregister 'cdc_ether' usb-0000:06:00.3-3, CDC Ethernet Device
...
After that, check your network interfaces using ip command
$ ip link
Then look for the one with the one with the same MAC address as the one that appears in the logs of dmesg.
Once you find it, run this command to assign an IP address
$ sudo dhclient <name of the network interface of coral dev board>
Now you should see an IP assigned to the interface.
$ ip a
After that, run mdt devices and you should see the dev board connected.
$ mdt devices
bored-horse (192.168.100.2)
I had the same problem in Debian (Buster). I was able to follow all the steps to connect and flash the device until 'mdt shell' and I would receive a 'Unable to find any devices on your local network segment' message.
Opening the network settings and enabling 'USB' as a network interface worked for me.
After connecting to the Coral Dev Board the first time and exchanging private keys, I unplugged the USB cable. After that, my computer was offline until I re-enabled the ethernet connection. It seems that enabling the USB network disabled the ethernet. At that point, mdt shell was able to connect via the ethernet network.
So I've just spent most of the afternoon with this issue. After I downgraded the OS to Chef it seemed to work fine as the USB device (OTG port) would initialize on boot and then the SSH key could be pushed through. However, with the latest OS (Eagle) this was not the case.
The fix was simple:
Remove the USB C OTG port cable from the board
Reboot the Coral board
Wait for boot sequence to complete
Connect the USB C OTG port cable to the board
Run "mdt shell"
key is pushed through!
Now I can set up the WiFi or connect Ethernet and remove that cable once again and now I can freely call mdt shell and it connects every time.
My Raspberry Pi 3 (running Raspian) is a robot and needs to drive around.
At home, I control it using Windows 10/Putty over SSH. However, in 2 weeks I will be demonstrating it in a place where I have no control over the wifi connection, and I don't want to be reliant on a potentially heavily firewalled network.
I read that Wifi Direct would allow me to SSH into my Raspi (and thus control it) using my Windows 10 laptop, without using an existing wifi network. My laptop supports Wifi Direct. However, all tutorials appear to be concerned with connecting the Raspi with an Android app, and not windows 10/Putty.
How do I connect my windows 10 laptop to my Raspi using a Wifi Direct connection?
So what I did is use a spare router as a switch to create a local wireless network, and connect both my laptop and my pi to it. I could hence establish a ssh connection.
I am trying to write a small app which can communicate with USB device when connected to a WP7 device. Is it possible to use PTP protocol over USB from a WP7 device? Does a phone needs to support USB host controller to be able to communicate via PTP over USB?
I'm afraid it's not currently possible. The only external access currently provided by the SDK (including the beta Mango release) is via HTTP or network sockets.
While the phone is connected to the PC I believe it can access it's internal IP address, but that's as close as you're going to get for now.