-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New device, set up error 121 #96
Comments
Buster or Bullseye? Put this down in the console: sudo i2cdetect -y 1 |
Hi, i have Buster. It seems that i had to add in boot/config.txt dtoverlay=i2c-rtc,ds1307. Now, it is boot up and then halt. |
Did you fix the problem? I have the same problem right now. pi@raspberrypi:~ $ i2cdetect -y 1 Its a 3B+ running Buster. |
I have a RPi 4B model, bullseye x64. I've tried to write 0x00 in the address 50 in the same way OTA_firmware_upgrade.py does at the end of the script without success (bus.write_byte_data(0X18, 50, 0)): i2cset -y 1 0x18 50 0 b The only way I could get out of the firmware upgrade mode (0x18) to the operational mode (0x17) was to proceed a complete firmware upgrade running: python3 OTA_firmware_upgrade.py I removed batteries and external power source, reinstalled batteries, and the UPSPlus was working in the 0x17 operation mode, back again. |
i gave it up and order another hat from another company. I stoped using it from my last post. |
@alpapak, which one, if you don't mind to inform for a next purchase? because it is very disappointing about having no clue on miss-functions of the upsplus. |
@mmaga |
Hello,
I have one upsplus and after following the setup manual and running the install script i got error 121
Any idea?
The text was updated successfully, but these errors were encountered: