I bought a Raspberry Pi 3 Model B+ 2 weeks back, and did a small project related to weather monitoring. After that I wanted to check the led blinking with the Raspberry, and tried the connection. I want to check whether the led was working or not, so i put the led pins with 5v pin and gnd pin (for checking purpose) and suddenly, the system went off and not even booting. I suspect some hardware problem.
Can anyone help me please??
LED was about 5v (I suppose), didn't use a 1k ohm resistor (I have very little idea about electronics)
Used RPi Pin 2(5v) and 6(gnd) to check LED (directly)
No screen output (image not booting).
Image was Rasbian with April 2018 Update
I'll check the schematics.
Related
i already tried using this board and all works fine but suddenly one relay has a dimmer turn on led and the relay doesn't have a clicking sound when turning on. Then one after another all 7 relays has the same problems, i tried changing may atmega chip but nothing happened. I tried using other power supply to power the 7 relay but still the same. The digitalwrite(n, HIGH) output voltage of the atmega pins that are connected to the relays is just about 1.7v and not 5v but the other ouput pins that has nothing connected has 4.89v output when turning it high, would that be the problem? And how would i fix it? My code i use to troubleshoot is just high and low digitalwrite.
Schematic Diagram
atmega328p with built-in 7 relays
I have an AOSP tree compiled on my board. I bought a wireless keyboard and connected it to my board via usb port. I expect when the board is in the suspend state, it will wakeup by pressing a key on keyboard. But it is not so.
I tried several ways in my bootloader (uboot), kernel, etc. But no effect. Additionally I made an experiment and found out that in the sleep state, my usb port (which has a dongle in it) has just 1-5 mA. But it should be higher for the dongle to work!
Has anyone experienced this? How to enable remote wakeup for usb in android?
Thanks
More info:
The uboot supports usb host controller interface. I tweaked kernel build options. but these two actions has no effect.
EDIT : I work on p212 reference board of amlogic. Its SoC is Amlogic S905X.
EDIT 2 : I tested the board (which is a tv box actually) using my phone and its charger and I found that when the box goes to sleep, the charging is stopped!! So I can deduce that the dongle has not enough power to stay alive! (yet to send wake signal to SoC !)
Then I carried out a second experiment: I connected the phone using a USB charger which only has two pin instead of four. (Just voltage supply; differential pins (signal pins) are disconnected). The result: my phone is charging now!! It seems when the SoC is suspending, it sends a signal to USB peripherals telling them to not draw power. Am I correct? How can I configure my AOSP tree and Linux kernel and uboot bootloader to avoid happening this?
Please guide me how to fix it in kernel or other parts of stack!
EDIT 3 :
I have pasted my kernel config here. I configured these options to y but has no effect:
CONFIG_PM_RUNTIME=y
CONFIG_PM_AUTOSLEEP=y
CONFIG_PM_DEBUG=y
CONFIG_USB_OTG_WAKELOCK=y
CONFIG_USB_DEBUG=y
CONFIG_USB_OTG=y
Also this link is my device tree files. (in kernel. NOT uboot)
I have a Rasp pi 3B. I installed Things 0.7 on it and developed an app. All was good.
I installed Things 1.0 and my app, and it ran fine for a week or two, and now the pi won't boot. I'm stuck on the rainbow screen. The red led is on, and the green flashes for a moment on powering up.
There was a thunderstorm which made the power supply flicker. I thought maybe this had caused some damage. I've tried reinstalling Things. No change. I tried installing Raspian, and the pi booted up just fine, so I'm thinking both the card and the pi are actually good. When I put Things 1.0 back on the card, it doesn't boot again.
Any clues?
My app is designed to control an irrigation system. So the GPIO pins are connected to relays which operate some valves.
I tried disconnecting all the pins and rebooting, and it now works. So it was something to do with the pins being wired up. I don't know why the connections would make a difference as there is no voltage on any of the wires. I'll look into it further, but I really don't want to have to disconnect and reconnect all the wires every time I reboot (there are 16 relays). If anyone can suggest why I am seeing this behaviour I'd be grateful.
I have just finished a project using an Arduino Micro dev board and want to move to a standalone ATmega32.
I need to run this at 3.3V and I dont want to go down the overclocking road so I have an 8MHz crystal to put on it.
I still want to be able to upload sketches via USB and the Arduino compiler so I gather I need to burn a different bootloader.
For this purpose I have purchased a USBASP programmer.
I am slightly unsure of what to do next - everything I can find on the topic either relates to the ATmega328 or to burning bootloaders using another Arduino.
I have worked out that I need to modify boards.txt to point to the correct bootloader....but which is the correct bootloader for ATmega32 at 8Mhz?
Also do I need to change any fuses?
Thanks
I think you're a bit out of luck.
The ATmega doesn't have hardware USB, so I assume the bootloader is using V-USB to implement USB. That stack, being a software implementation of USB's high-speed signalling, requires at least a 12 MHz clock (higher is better).
I don't think you can run V-USB using only the internal 8 MHz oscillator.
According to the OP comments the micro is indeed an Atmega32u4, not an Atmega32 (#OP: please fix the question to match this).
Since it has onboard USB, you can use a pre-existing bootloader like the sparkfun one:
https://www.sparkfun.com/products/12587
Here you have the link to one of their products, the Arduino pro micro 3.3V (which runs at 8MHz). You can add the sparkfun arduino boards repository to your IDE and then just use the board specification for their pro micro 3.3V do upload the correct bootloader and to program it through the USB just like the usual Arduino Micro.
I have an arduino uno R3. I am able to upload the programs with no connectivity issues. But there is a problem while executing the program and I don't know what that is. The 13th pin led is not blinking as the default bootloader program comes with preloaded blink program. I am not able to reset the board too. What might be causing the problem?
I even tried to reload the bootloader program. But the same think happens yet again.
Thanks in advance and Regards,
Rishi.
Have you tried to blink one led with pin 2 or 3 ( any of the digital pins ). You might have a working Arduino uno but your led on the board can be broken.
Otherwise,you should try to flash the bootloader with a secondary arduino and check if you get the same issue.