I am trying to run a simple program for Raspberry Pi 3 powered by Android Things. The program will try to read and write through serial port. When I try to get the UART device list, I get:
java.lang.NoClassDefFoundError: Failed resolution of: Lcom/google/android/things/pio/PeripheralManagerService
To make it more clear:
Use latest version of Android Things which is
'com.google.android.things:androidthings:1.0'
and change PeripheralManagerService object into
PeripheralManager pioManager = PeripheralManager.getInstance()
Related
I'm trying to upload my build code to my alchitry-CU FPGA board threw apio using iceprog on windows.
apio upload
which then executes
iceprog -d i:0x0403:0x6010:0 hardware.bin
And the output is
init..
Can't find iCE FTDI USB device (device string i:0x0403:0x6010:0).
ABORT.
scons: *** [upload] Error 2
I have installed the libusbk driver and also tested uploading with the same cable on another pc with the standard drivers and the provided IDE Alchitry Labs in combination with iceCube2 but I really wanted to use the open source alternative instead.
Never mind I found the fix. The problem was that the Alchistry CU shows up as two different devices in Zodic when installing the drivers, one as Interface 0 and one as Interface 1 and I didn't see the other one and only installed the libUsbK driver on one of them.
i am trying to make an anti theft door notification IOT app. I am using nodemcu,arduino for coding and a blynk app to operate it. I have already installed a drivers from the link for nodemcu. Now I don't why I am not able to upload a code.
I am getting this as an error:
Sketch uses 281080 bytes (26%) of program storage space. Maximum is 1044464 bytes.
Global variables use 30152 bytes (36%) of dynamic memory, leaving 51768 bytes for local variables. Maximum is 81920 bytes.
error: Failed to open COM1
error: espcomm_open failed
error: espcomm_upload_mem failed
error: espcomm_upload_mem failed
You are getting
error: Failed to open COM1 error: espcomm_open failed error: espcomm_upload_mem failed error: espcomm_upload_mem failed
Because the arduino IDE was not able to upload code to the nodeMCU through COM1.
There are multiple reasons for this to happen,
If you are on linux or mac, make sure you have write permission to the port. (as the port you mention looks like a windows port this is probably not your issue.)
Make sure that you have selected proper board in the Arduino IDE board list.
Press and hold the flash on nodeMCU and plug the USB cable into the PC, once you connect the cable release the flash button. now try to upload the code.
I am trying to build OpenThread(NCP mode) and upload program to EFR32 without JLink.
EFR32 can support OTA upload method and supported format is "ebl".
My propose is：
Adding cstartup-common.c into compile script
Build to "axf" format by adding "-gdwarf-2" option on arm-none-eabi-gcc.
Using "arm-none-eabi-objcopy.exe --srec-forceS3 -O srec ot-ncp-ftd.axf ot-ncp-ftd.s37" to convert "axf" -> "s37"
Using Silabs' tool "commander.exe" to convert "s37" -> "ebl"
Using "flash_firmware" tool to upload "ebl" file from host chip to EFR32 by UART
I meet the following error log when runing "wpantund" on host chip
- "The NCP is
misbehaving: Repeatedly unable to initialize NCP. Entering fault state."
Is there any one know this?
Unless you have loaded something onto your part before, Silicon Labs chips don't come with a bootloader from the factory. The initial programming of an EFR32 must come via J-Link or the Silicon Labs WSTK.
How are you interfacing this chip? You mention UART, but via what interface?
I installed Bluez and I am trying to scan and get UUID Major, Minor and if possible mac address for nearby ibeacon. I found similar questions and they refer to a script which I found here . When I launch the script I get this error
Set scan parameters failed: Input/output error
Did someone know how to solve the problem or has another solution ?
If I start transmitting with the beacon and then I start the scan I get no result at all and I have to interrupt the script.
You should test that the BlueZ installation is working properly on your Linux machine. Try using the hcitool dev command to see if it lists attached devices properly.
You may want to refer to a BlueZ installation guide like this one for Ubuntu to verify that you have your dongle set up properly.
I made a node which contains a USRP_UHD and a GPP (and make sure the ip_address is correct for USRP_UHD). I launched the domain based on this node. However, I got the following error:
UHD Error:
Device discovery error: AssertionError: libusb_init(&_context) == 0
in libusb_session_impl::libusb_session_impl()
at /builddir/build/BUILD/uhd-release_003_005_003/host/lib/transport/libusb1_base.cpp:37
UHD Error:
Device discovery error: AssertionError: libusb_init(&_context) == 0
in libusb_session_impl::libusb_session_impl()
at /builddir/build/BUILD/uhd-release_003_005_003/host/lib/transport/libusb1_base.cpp:37
...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
UHD Warning:
Unable to set the thread priority. Performance may be negatively affected.
Please see the general application notes in the manual for instructions.
EnvironmentError: OSError: error in pthread_setschedparam
I did get two unallocated (TX/RX for each) tuners, but it is not easy to allocate these two tuners for use for any parameters.
Besides, if I just launch the domain and launch the single device USRP_UHD, or simply run the discover USRP_UHD command via the command line window, I got the same error:
UHD Error:
Device discovery error: AssertionError: libusb_init(&_context) == 0
in libusb_session_impl::libusb_session_impl()
at /builddir/build/BUILD/uhd-release_003_005_003/host/lib/transport/libusb1_base.cpp:37
2016-02-01 16:59:20 WARN USRP_UHD_i:943 - WARNING: NO UHD (USRP) DEVICES FOUND!
Could anybody figure out where this problem is? Thanks in advance!
So, first of all, the good news is that this is happening during autodetection of USB devices, so your N2xx is not inherently affected, but:
UHD 3.5.3 is not only old, it's ancient. You should really uninstall it (If you've got Debian or a derived one [Ubuntu], it'd be sudo apt-get remove uhd-host libuhd003 libuhd-dev), install a new version directly from Ettus (can help you with that, if necessary) and rebuild Redhawk against that version.
Really, really do that. There's been so much improvement in behaviour like failure handling that fixing this without updating isn't really worth it.
Now, if you explicitly specify a device address that allows you to cancel USB-based USRP detection completely, you should be fine. As device address, use type=usrp2 for USRP2, N200 and N210.
I ran into this issue trying to install UHD v3.9.3 in a CentOS 7 Docker container - the error message points to a usb issue, not related to Redhawk. The Redhawk Device, USRP_UHD, is just an abstraction layer on top of the Ettus UHD drivers, so the easiest way to tell whether the problem is Redhawk or something else is to try one of the UHD commands directly from a terminal to generate the same error, like uhd_usrp_probe.
To check if the problem is directly related to the usb drivers try the command lsusb. This should list all usb devices connected to your OS. These are good debug tips to isolate where the problem is.
If you happen to be doing this using Linux containers or Docker you have to give the proper privileges, see docker-any-way-to-give-access-to-host-usb-or-serial-device. Otherwise, assuming you built UHD from source, check the output of make test step - if all the tests passed there shouldn't be anything wrong with the UHD library.
Edit: Also if you're running this inside a VM you have to make sure your host has given network/USB/etc privileges to the hypervisor (ex. VirtualBox) during installation, or that you've attached the correct virtual hardware in the VM configuration.