I'm working on the project and use neo-6m, raspberry pi 3. I follow these steps but I get an error. Please help me.
Neo 6M VCC -----> Raspberry pi 5v Neo 6M GND -----> Raspberry pi GND
Neo 6M RX -----> Raspberry pi TX (gpio 14) Neo 6M TX ----->
Raspberry pi RX (gpio 15)
sudo nano /boot/config.txt
At the end of the file add the follwing lines:
dtparam=spi=on
dtoverlay=pi3-disable-bt
core_freq=250
enable_uart=1
force_turbo=1
sudo nano /boot/cmdline.txt Replace the content with the follwing line (delete everything in it and write down the following content):
dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
sudo reboot
sudo cat /dev/ttyAMA0
and this error:error
Related
Hello I am using a Raspbarry 4 8Gb system
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
$ lsusb
Bus 001 Device 004: ID 1ff7:0013 CVT Electronics.Co.,Ltd CVT Touch Screen (HID)
For some reason after a few hours the touch with infrared frame stops working. If you restart the machine it will work again.
I'm even using a program to reset the USB made in C
usbreset.c that works perfectly I left it in crontab every 10 min.
I noticed that this problem only started in the new version 11 of Raspbian, in version 10 I never had this problem.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 10 (buster)
Release: 10
Codename: buster
Has anyone experienced this, know how to fix it?
I am running the following command line to capture an image:
raspistill -o image.jpg
and I am getting this error message:
mmal: No data received from sensor.
Check all connections, including the Sunny one on the camera board
I have tried the following steps:
Installed the camera in the port next to the DVI socket and made sure that both ends of the ribbon cable are seated.
Enabled the camera through a terminal on the PI via "sudo raspi-config"
Updated the Raspberry PI firmware through a terminal with "sudo rpi-update"
Increased the GPU memory available from the default of 128 to 144
Used "sudo vcgencmd get_camera" to make sure that the camera is detected. (output from this command is: supported=1 detected=1)
Checked that there is no other process accessing the camera: "sudo ps aux|grep raspi" the output was: pi 1097 0.0 0.0 4372 540 pts/0 S+ 09:09 0:00 grep --color=auto raspi
I have been working on this errors and I am not sure what the problem is.
Trying to connect a Redbear Blend Micro Arduino board over BLE from a Rasperry Pi B+
Raspbian Jessie kernel 4.1.13+ (also tried on wheezy w identical issue)
Bluez 5.37
Tried several different ways of installing Bluez but in essence followed this http://www.elinux.org/RPi_Bluetooth_LE.
pi#raspberrypi:~ $ sudo hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 5C:F3:70:75:A3:EA ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:1722 acl:0 sco:0 events:85 errors:0
TX bytes:788 acl:0 sco:0 commands:70 errors:0
pi#raspberrypi:~ $ sudo hcitool lescan
LE Scan ...
EC:EA:FA:D8:F9:77 BlendMicro
EC:EA:FA:D8:F9:77 BlendMicro
pi#raspberrypi:~ $ sudo gatttool -b EC:EA:FA:D8:F9:77 -t random -I
[EC:EA:FA:D8:F9:77][LE]> connect
Attempting to connect to EC:EA:FA:D8:F9:77
Error: connect: Connection refused (111)
[EC:EA:FA:D8:F9:77][LE]>
The same procedure on my Ubuntu:
ubuntu:~$ sudo gatttool -b EC:EA:FA:D8:F9:77 -t random -I
[ ][EC:EA:FA:D8:F9:77][LE]> connect
[CON][EC:EA:FA:D8:F9:77][LE]> primary
[CON][EC:EA:FA:D8:F9:77][LE]>
attr handle: 0x0001, end grp handle: 0x0007 uuid: 00001800-0000-1000-8000-00805f9b34fb
attr handle: 0x0008, end grp handle: 0x000b uuid: 00001801-0000-1000-8000-00805f9b34fb
attr handle: 0x000c, end grp handle: 0x0011 uuid: 713d0000-503e-4c75-ba94-3148f18d941e
attr handle: 0x0012, end grp handle: 0xffff uuid: 0000180a-0000-1000-8000-00805f9b34fb
[CON][EC:EA:FA:D8:F9:77][LE]>
What I tried:
Different versions of Bluez5 installation and don't think that is the issue.
I read that the Raspberian kernel version didn't support Bluez 5 and downgraded to 3.10.25+ which resulted in the Raspberry's USB ports being disconnected
https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=120539&p=819468
Tried three different bluetooth dongles (including a plugable and a CSR) and they all give the same error on the RBi and works fine on the Ubuntu.
I'm aware of this stack posting.Cannot connect to BLE device on Raspberry Pi
This is solved.
Bluez 5 is not compatible with the default Kernel version 4.1.13 for Raspbian Jessie or Wheezy.
The solution is to step back to an earlier Kernel. In my case I first tried Kernel 3.10.25+ which killed all USB port on my RBi B+. Then downgraded to Kernel 3.12.36+ and that solved the issue and I can now connect from gatttool.
Downgrading is easy. Just do:
sudo rpi-update f74b92120e0d469fc5c2dc85b2b5718d877e1cbb
sudo reboot
And the connection below
pi#raspberrypi:~ $ sudo gatttool -b EC:EA:FA:D8:F9:77 -t random -I
[EC:EA:FA:D8:F9:77][LE]> connect
Attempting to connect to EC:EA:FA:D8:F9:77
Connection successful
[EC:EA:FA:D8:F9:77][LE]> primary
attr handle: 0x0001, end grp handle: 0x0007 uuid: 00001800-0000-1000-8000-00805f9b34fb
attr handle: 0x0008, end grp handle: 0x000b uuid: 00001801-0000-1000-8000-00805f9b34fb
attr handle: 0x000c, end grp handle: 0x0011 uuid: 713d0000-503e-4c75-ba94-3148f18d941e
attr handle: 0x0012, end grp handle: 0xffff uuid: 0000180a-0000-1000-8000-00805f9b34fb
I am running a RaspberryPi with raspbian-wheezy:
uname -a
Linux raspberrypi 3.18.5+ #744 PREEMPT Fri Jan 30 18:19:07 GMT 2015 armv6l GNU/Linux
How i want to use a NetGear N150 Wireless USB stick as a wlan interface:
dmesg
[ 3.401856] usb 1-1.2: new high-speed USB device number 4 using dwc_otg
[ 3.523552] usb 1-1.2: New USB device found, idVendor=0846, idProduct=9043
[ 3.532493] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.541771] usb 1-1.2: Product: WNA1000Mv2
[ 3.547744] usb 1-1.2: Manufacturer: Realtek
[ 3.553858] usb 1-1.2: SerialNumber: 00e04c000001
The device is not automatically detected. After plugging in the stick into a windows machine, it seems as the stick uses a Realtek rtl8192cu chip. Loading the 8192cu kernel module does not seem to work, there is still no wlan0 device.
Any ideas?
Never mind, I found a solution:
The usb id is not detected by the 8192cu kernel module as a supported device. After tweaking a bit and adding the following code to the rc.local file, everything works as expected:
modprobe 8192cu
echo "0846 9043" > /sys/bus/usb/drivers/rtl8192cu/new_id
ifdown wlan0
ifup wlan0
To have this handled automatically on module insertion, put the following line in /etc/modprobe.d/netgear_n150.conf:
install 8192cu /sbin/modprobe --ignore-install 8192cu; echo "0846 9043" > /sys/bus/usb/drivers/rtl8192cu/new_id
Going the extra mile: having it load automatically is more system specific, but on Arch Linux, adding a file in /etc/modules.load.d containing the module name is sufficient.
I have built the very latest u-boot release and placed the image on a Raspberry PI. After boot, I get this error message:
U-Boot 2013.10 (Oct 24 2013 - 09:35:44)
DRAM: 448 MiB
WARNING: Caches not enabled
MMC: bcm2835_sdhci: 0
Using default environment
In: serial
Out: lcd
Err: lcd
Hit any key to stop autoboot: 0
mmc0 is current device
** No partition table - mmc 0 **
U-Boot>
Obviously, u-boot failed to mount the file system.
Can this be related to some mmc related setting as access speed?
Thanks in advance