You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My PiJuice is no longer at i2c-address 0x14 but reports at i2c-address 0x41
I guess this occurred after updating pijuice firmware from V1.5 to V1.6 (not sure however).
I was preparing a new system with a new pijuice delivered with 1.5 firmware.
Tried to recover from this situation by (again) updating the firmware to 1.6.
The update itself is done using pijuiceboot and is executed without any error but doesn't solve the problem.
I also used the option no_start but this doesn't help either.
Any suggestions on how to recover from this situation and get the pijuice accessible again?
The text was updated successfully, but these errors were encountered:
fjpdevries
changed the title
PiJuice does not repond and reports at 0x41
PiJuice does not respond to i2c-commands and reports at 0x41
Nov 24, 2023
The PiJuice reporting I2C address 0x41 means it is in the MCU bootloader.
From the documentation:
Holding pressed SW3 while powering up PiJuice HAT will initiate the bootloader.
This is used only in cases when ordinary initiation through I2C does not work
because of damaged firmware.
Note that you have to use the pijuiceboot version from the 1.6 firmware if you
install the latest packages since the 1.6 firmware is larger than 80k.
From the firmware 1.6 changelog:
* pijuiceboot
- Support loading firmwares larger than 80k. Needed for loading V1.6
My PiJuice is no longer at i2c-address 0x14 but reports at i2c-address 0x41
I guess this occurred after updating pijuice firmware from V1.5 to V1.6 (not sure however).
I was preparing a new system with a new pijuice delivered with 1.5 firmware.
Tried to recover from this situation by (again) updating the firmware to 1.6.
The update itself is done using pijuiceboot and is executed without any error but doesn't solve the problem.
I also used the option no_start but this doesn't help either.
Any suggestions on how to recover from this situation and get the pijuice accessible again?
The text was updated successfully, but these errors were encountered: