I am trying to use the Google Coral Dev Board. I am following the tutorial Get Started with the Dev Board and I am stucked at the Flash the board part and precisely at the step :
dmesg | grep ttyUSB
This request returns me nothing, in fact there are no usb using the cp210x listed converter after doing dmesg.
I have verified the content of /etc/udev/rules.d/65-edgetpu-board.rules and it is good.
And lsusb gives me :
Bus 001 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 005: ID 0424:7800 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
My user account is in the dialout and plugdev groups. And the cp210x driver is running.
I have this problem on a fresh install of Ubuntu 18.04 LTS and on a Raspberry Pi 3B+.
I have been in touch with Google-Coral re this. I have had the same problem. Linux must have a driver for the particular USB used. The driver is cp210x. Just sorted this out yesterday.
Doing a lsmod should show is cp210x is on your machine.
Link shows how to do the install.
http://headstation.com/archives/instructions-installing-cp210x-serial-bridge-driver/
The driver is available from Silicon Labs and the instructions have the details.
I am still working on this. It is evidently a known issue. It is worth a shot. I am also suspicious of a board problem on mine as Windows cp210x drivers will not id the board. Widows drivers are a very rapid install, That is not a definitive test and will do a Linux make tonight.
Google-Coral has been very helpful on this. I believe they are in Bangalore so there is a 12 hour delay in response. I told them about your posting.
I am not sure it is related or not. Flashing the SD via serial drove me crazy and I finally got a solution from Google support. They send me the link
https://coral.withgoogle.com/docs/dev-board/reflash/#flash-from-u-boot-on-an-sd-card
But the name of system image is different from the one working with serial. I don't know the difference
Related
I tried working with my RPi Pico today and my computer doesn't recognize the usb I triple checked the cable is power and data. And yes I'm holding the button
I've also had this annoying issue. Seems to happen even more often on the Pi Pico W.
Use my laptop USB-C port to connect via a USB-C to USB 3.0 hub and this happens every so often.
Bought a powered hub from Amazon: "UGREEN USB C Hub 4 Ports, USB C to USB Hub 3.0". It has a separate USB-C power input in addition to the laptop USB-C connection and it works fine when no other USB devices are connected to the hub. Seems to be an issue similar to what Foibled2 mentioned where the underlying issue may be power related.
I'm struggling with the same thing. Other than uninstalling in Device Manager and rebooting (sometimes several times) I can get it to recover.
There must be a better way.
I've seen references to Zadig, etc. But finally figured out the issue in my circumstance.
I disabled all of my other USB serial devices (Prolific USB for GPS tracker; and CH340 USB for Android Nano).
After that, I could plug / unplug my R Pi Pico between application and USB drive mode without rebooting.
Works now as advertised. Hope this helps short cut a few hours for someone else!
I would like to pair my Bluetooth Low Energy Sport Watch (Suunto Ambit 3) to my Raspberry PI 3 B V1.2
I am using the RaspianOS Version 10 buster with kernel Version 5.4.79-v7+
This OS contains the bluez stack in version 5.50 which was installed from a predefined package via apt-get.
Usually the ble pairing is done with smartphones under android and IOS. When doing the pairing process the watch offers a pincode which has to be entered by the smartphone.
With nRFConnect app under android the pairing works fine.
When I am running the hcitool on my raspberry and the watch is in pairing mode it appears.
sudo hcitool -i hci0 lescan
but when i try to run the sudo bluetoothctl command with scan on my device does not appear and pairing with the correct mac address does not work either.
Other devices still appear in bluetoothctl
I also had a look into https://github.com/raspberrypi/linux/issues/3689 but this seems that this is only related to newer raspberry pi models.
Do have any idea what hinders my device from being found in the bluetoothctl scan mode or what can I do to pair my device with pin code enabled?
I found a solution by myself.
inside bluetoothctl calling the following sequence
menu scan
transport le
back
scan on
finally enables bluetoothctl to find my watch.
The connect command is then also working.
I'm using a raspberry pi running on Window IoT Core, and connects to Azure IoT hub. When I initially wanted to provision the device I just used a TPM simulator (via the Windows Device Portal). Now I've chucked in a real TPM chip to the pi, and I want to provision the device using that chip.
But I'm not seeing an option to do that on the device portal - TPM Configuration section.
How it looks now on the device portal now.
Maybe I'm missing something obvious. Any help is greatly appreciated.
Firmware TPM (fTPM) requires special Processor/SoC support that is not currently implemented on Raspberry Pi 2 or 3. You can use MinnowBoard or DragonBoard410c instead.MinnowBoard Max needs firmware version 0.80 or higher. DragonBoard410c provides fTPM capabilities out of the box enabled by default.
I'd like to use Raspberry Pi 4 to collect data from several BLE mesh supported devices (beacons) that uses a chip like nRF52832, nRF52833 or nRF52840.
I know that Pi 4 comes with bluetooth 5.0.
My question is, can I use Pi 4 as it is without any hat, cape etc. connected to collect data from the beacons that uses those chips and communicates by using the BLE mesh technology.
Yes, you should be able to use the Raspberry Pi for mesh functionality depending on the version of BlueZ that is available there. Mesh functionality was initially added in BlueZ v5.47 (September 2017) and subsequent versions of BlueZ have had bug fixes and additions to this feature. You can find more information here:-
http://www.bluez.org/
You can check the version of BlueZ that is on your Raspberry Pi through the following command:-
bluetoothctl --version
I hope this helps.
I made an WinCE 6.0 R2 image and load it into VMWare Player 3.1.3. The host operating system is a Windows XP Sp3. I followed this article and all worked fine (the article uses VMWare Workstation, but it worked fine also with VMWare Player).
My final goal is from the virtual machine WinCE to use the Bluetooth USB dongle attached to the Windows XP host computer. In the WinCE image I had added support for Bluetooth USB like in this Mike Hall's post. Also I want to mention that I had included support for USB Host when I created the BSP, and also USB drivers are checked.
When I go in WinCE -> Control Panel -> Bluetooth Device Properties, Bluetooth Manager is launched. But if I try to make a "Scan device" I am getting the following error:
Bluetooth hardware error 10050 (controller not present)
But the dongle is attached to the VMWare Player and disconnected from the host, so theoretically the transport layer is controlled by the virtual machine and WinCE can talk with EHCI of the USB.
Can anyone give me a hint to follow? Any suggestions are welcome.
I have no idea whether the stuff described at http://www.codeproject.com/KB/windows/bth4devemul.aspx is required in your case...
There the FreeBT.NET stack is installed on the host PC to enable the WM emulator to use a host-attached Bluetooth dongle...