I have just got the new Raspberry Pi model a+ and was very excited. Removed the old model a, and replaced it with the new model a+'s 26 compatible pins. I started fine, and I can see it runs the code as it should. However, I have already run into two problems.
The HDMI port does not show anything on the screen anymore. This has never been an issue before. I use the LINDY hdmi to vga adaptor.
I was very excited to see how much the powerconsumption would decrease. But was very disapointed to see the powerconsumption actually increased by 50%, whitch was a bit of a blow.
I have just replaced the old model a with the new model a+ and copied a raspian image to a 16gb micro sd. I know there is not a lot of experence yet on the subject, but maybe some of you also will have simular problemems?
Best Regards Allan
Try running a
sudo apt-get update
and
sudo apt-get upgrade
on another Pi with the same SD card inserted. There might be some necessary software updates required for the A+.
Related
I since a few months, I have been using a Hyperpixel 4.0 Touchscreen with my Raspberry 3B+ without any problems. Since a few weeks i use my touchscreen with the Raspberry Pi 4 Compute module and mounted both on my own designed PCB. Unfortunately, I’m facing some difficulties with the Touch function of my Hyperpixel 4.0. I have no clue how to solve these problems because the circumstances, which cause the fault don’t make sense to me.
Which System do I use?
Hyperpixel 4.0 in combination with Raspberry ComputeModule 4 with 2GB RAM and 8GB onBoard eMMC. Both is mounted on my custom PCB, which is supplied with 24V, stepped down by an «APP63300WU-7» Step down converter, which provides 3A # 5.1V continuous output. The measured Voltage over 2 Days of measurement is a maximum of 5.2V and a minimum of 5.05V. The software ist the latest Raspbian.
What error is caused?
I have been running a GUI on my Raspberry Pi. I have one Page on which i have three sliders for changing brightness of my room light, colortemperature and one slide is to regulate the speed of some fans. Everything works fine in darkmode, but if I change to lightmode and touch the screen for about 1.5 seconds, the touch- function hangs up. My GUI doesn’t move anymore and I have a still image. I know that it’s only the touch function beacause if I plug in a keyboard and mouse, I can open for example chromium or other stuff without problems. With «i2cdetect »-command I can detect the Goodix GT911 driver on Address 0x14. Even if the touch has hung up, i can detect the Goodix GT911. I know that the address should probably be 0x5D but I thought it isn’t necessary to care about this problem as long as it works. After a reboot, the touchscreen works fine again until i use the lightmode of my GUI. Interesting to mention is, that i can click a thousand times for around 0,25seconds and no problems occur. But if I touch the screen permanently for around 1,5seconds, I instantly get my above described problems. Generally considered, this problems seems very strange to me and it doesn’t behave like any physical law i know…
On the first view, the error seems like a software issue ? Hear this!
If i use the official «Compute Module 4 IO-Board » to mount my Compute Module and Touchscreen, I don’t get the issue at all… My actual designed PCB ist the 2nd version. On the 1st version It also worked fine without any problems. The only differnce between version 1 and 2 is the wiring, which I tried to improve on the 2nd version and viewer parts which I only put on my 1st version to evaluate some functionalities like ethernet or 2nd I2C-Bus, which I’m not using on my 2nd version. The wiring did not change between these two versions, i only tried to increase the distance between the GPIO-traces to improve signal integrity.
So it seems like a hardware problem? But why does the GUI work fine in darkmode? I don’t have any explanation to that.
What did I do to narrow down the error?
I flashed a new image on my Compute Module and also used another Compute Module, Custom PCB and touchscreen as well, but without any success. As far as I experienced, the issue is only caused on my GUI and not on any other websites or images, etc. An interesting thing was the interrupt line, which is typically only drawn to 0Volts if the touchscreen gets touched. After the touchscreen hung up, I measured 0,084V on that line and as long as I touched the screen, this voltage rised to about 0,2V, which for me seems also like a strange behaviour. I also checked the «dmseg» file and got some entries for failed i2c tests of the GoodixGT911. I also tried the github fix for the swapped i2c address, but without success. I used the command «git clone GitHub - pimoroni/hyperpixel4: Driver for the Pimoroni HyperPixel 4.0" Touchscreen Display -b pi4-i2c-fix » for that.
What do I try next?
I dont have any clue what to do next. My only solution in mind, is to undo the «improved» wiring of my 2nd PCB to get as close as possible my first PCB version.
Conclusion :
I really need help and hope, someone can do me this favour. I’ve never found my described error behaviour in any forum. Are there any other usable forums for problems with the Hyperpixel 4.0? Let me please know.
Update:
I tried to reproduce the errors and specify the error source. As above mentioned, the touchdriver hangs up on lightmode (nearly every pixel on rgb(255,255,255)). If i change the color in lightmode to around rgb(245,245,245) the error does not occur. I also noticed that there are two flatband cables on the Hyperpixel 4.0: One for displaying the image and another for the whole I2C-Communication to the touch driver. I plugged out the one for displaying the image and got no problems at all. Even if was theoretically in lightmode(if display would have been on). The touchscreen worked fine and transmitted everyting flawless:
Conclusion on my Update: It seems as the rgb(666) datalines for displaying the image on the screen cause some problems on the I2C bus. I also checked the bus and the power supply with an oscilloscope but I haven't seen any unusual behaviour in any case. Voltage ripple was around 200mV Peak to Peak and the I2C-Datalines rised and fell really sharp
I still need help from you!
Thanks, Manuel
There is a Raspberry Pi 3 B+ which was already used.
I need to bring it to the default settings, i.e. to the state which you get it from the store (so that I can start using from scratch again, I want raspberry to forget all the previous actions, like it is new. Or simply cancel all the previous actions one has done).
What I did:
I tried to search "how to reset" or bring to the default, I could not find anything. Everything is about factory default and reinstalling some image.
Among useful commands I didn't find: https://raspberrytips.com/raspberry-pi-commands/
Isn't it not simple like resetting a smartphone? I may google differently.
The only way I could find to reset my raspberry pi is to rewrite (reflash) an SD card of it.
https://www.youtube.com/watch?v=ntaXWS8Lk34
I am new here but I hope you can help me to find a solution to my problem.
I have four PIGRRL Kit from Adafruit and I need to install in it Raspbian (Operating System), the PiTFT and the gamepad as shown here (https://learn.adafruit.com/pigrrl-2/software).
But, when I try to install the gamepad, the OS goes in loop and the only way to exit it is to restart everything. I have checked if there were some problems with the soldering, but the voltage machine is not showing me any problem of the kind. The problem is just on the gamepad, because at the PITFT installation step everything goes fine and works.
But when I install the gamepad it goes in loop.
I used these commands:
cd
curl -O https://raw.githubusercontent.com/adafruit/Raspberry-Pi-Installer-Scripts/master/retrogame.sh
sudo bash retrogame.sh
And then I follow the instructions for PIGRRL 2.0. But when I reboot, the OS loops.
Any idea or suggestion?
Thanks anyway!
I didn't tried retrogame, but I'm trying to use PiTFT 28 capacitive.
What I can say is that have some troubles with the display :).
In the first time I follow exactly they procedure and made my software work perfectly. But at some point in time it started to reboot after starting the software.
So I tried to start all over again, but this time I used Diet Pi and follow an alternative solution. I follow the procedure on this page: http://www.0xf8.org/2016/01/complete-rotation-support-for-the-adafruit-pitft-2-8-capacitive-touchscreen-display/
The display works, but:
1. If I use other console font, it starting immediately the font is going active.
2. The mouse don't work so well, it seems to start all the time in the left corner. So I didn't manage this part. :).
Maybe my answer can be useful in the combination of your experience.
Bafta
I found a solution. The problem for me was solved by charging the batteries. Basically, when it first reboots the OS needs more energy and with no charged batteries it went in loop.
All the best!
I have a 8gb sd card and when i install the raspian on it the file manager inside raspian shows the disk space about 700 mb. Is that normal cuz the raspian requires about 3.5gb. Please help me . .
so most likely you haven't resized your SD-Card, maybe look into this site. Make sure you do an backup, as he tells you on the answer. Was a 1 min google lookup. Maybe try to search by your self the next time.
Edit: I also found out there is a even easier way given by raspberry, just enter sudo rasps-config and use expand_rootfs
What you really need to do is Resize Flash Partitions
The article may be long to read but it's very useful because you can apply it for many Linux based operating systems.
I am trying to over clock my rasbian raspberry pi, but when I change any files beyond /sys/devices/system/cpu and restart, the changes are not saved. I tried echoing to the files and nano and cat. Nothing will work.
SysFS (mounted on /sys) is not a regular filesystem, the elements in this FS represent different aspects and options exposed by the kernel and modules, as such, those parameters are not persisted on secondary memory.
Is normal that changes under that directory are not saved (the only ones I recall to be saved are some settings about power saving in some notebooks, those settings were saved in the BIOS), in order to have the changes on every reboot you should create a init script or modify /etc/rc.local (on Debian based systems as Raspbian).
My SDcard was doing the same thing.
I tried to re-burn the image to the card, but it still had the same problem.
I burnt the image to another SD card, and it worked right away.
More than likely the card was corrupted or damaged