ChristopherRush
commented
4 years ago Does the PiJuice work on it's own and does the eink display work on it's own?
On Tue, 31 Dec 2019, 16:09 andrewsmyname, notifications@github.com wrote:
I was told by one of your colleagues to post here, and he did his best to help out (Ryan Walmsley). He deserves a pint!
He let me know that the EEPROM of both HATs collied, so I changed the PiJuice EEPROM to 52, which seemed to improve matters as the papyrus-test command now correctly identifies the Pi as not a Pi Zero. But nothing shows up on the e-ink display (I'm using the full size HAT with the 2.0 inch display, and have checked that it is seated correctly).
Here's some outputs to help:
I was told by one of your colleagues to post here, and he did his best to help out (Ryan Walmsley). He deserves a pint!
He let me know that the EEPROM of both HATs collied, so I changed the PiJuice EEPROM to 52, which seemed to improve matters as the papyrus-test command now correctly identifies the Pi as not a Pi Zero. But nothing shows up on the e-ink display (I'm using the full size HAT with the 2.0 inch display, and have checked that it is seated correctly).
Here's some outputs to help:
pi@calipi:~ $ i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- 14 -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- 48 -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- 6f 70: -- -- -- -- -- -- -- --
As mentioned in the PiJuice docs, when changing the EEPROM from 50 to 52, i2c-rtc,ds1339 will have to be added to /boot/config.txt. I also note that i2c-bcm2708 is an entry - removing it stops me from being able to communicate with the PiJuice. dtoverlay=i2c-bcm2708,i2c-rtc,ds1339
The PaPiRus also has an RTC that I don't need to use, but to enable that I have to change that entry to: dtoverlay=i2c-rtc,mcp7940x=1
This allows that RTC to actually function and be read with sudo hwclock -r, but of course without i2c-bcm2708 I can't communicate with the PiJuice (and using dtoverlay=i2c-bcm2708,i2c-rtc,mcp7940x=1 results in the RTC not working).
RTC aside, the main issue is that the e-ink display doesn't show anything. Here's the output of papirus-test (with dtoverlay=i2c-bcm2708,i2c-rtc,ds1339 set, and sudo hwclock -r giving the Cannot access the Hardware Clock via any known method. error, it seems the PiJuice RTC isn't working for me at all - I never did check when I set the PiJuice up:
pi@calipi:~ $ papirus-test Assuming this is a PaPiRus HAT board
---- Detect temperature sensor and RTC (RTC for HAT only) ---- Other device found at: 14 NXP LM75BD detected at: 0x48 Other device found at: 68 MCP7940N detected at: 0x6f
---- Screen Information ---- Vendor: Pi Supply Product: PaPiRus ePaper HAT v1.91 Serial: 342d3938-3462-2d38-3836-62313433327b Date/Time from RTC: Tuesday 31 December 2019 - 15:07:28 Temperature from sensor: 31 degrees Celsius Panel info: EPD 2.0 200 x 96 version=4 COG=2 FILM=231
I'm sure these two boards must be able to function together, I just don't know how to get them to play nice? Thank you for your help! :D
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/PiSupply/PaPiRus/issues/212?email_source=notifications&email_token=AAOKSKSBP6Z6DTEJBMNHTHLQ3NOEJA5CNFSM4KBWEN2KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IDP7JPQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOKSKV7I3M52JR77PR3WI3Q3NOEJANCNFSM4KBWEN2A .
andrewsmyname
tvoverbeek
ryanteck
I was told by one of your colleagues to post here, and he did his best to help out (Ryan Walmsley). He deserves a pint!
He let me know that the EEPROM of both HATs collied, so I changed the PiJuice EEPROM to 52, which seemed to improve matters as the
papyrus-testcommand now correctly identifies the Pi as not a Pi Zero. But nothing shows up on the e-ink display (I'm using the full size HAT with the 2.0 inch display, and have checked that it is seated correctly).Here's some outputs to help:
I was told by one of your colleagues to post here, and he did his best to help out (Ryan Walmsley). He deserves a pint!
He let me know that the EEPROM of both HATs collied, so I changed the PiJuice EEPROM to 52, which seemed to improve matters as the
papyrus-testcommand now correctly identifies the Pi as not a Pi Zero. But nothing shows up on the e-ink display (I'm using the full size HAT with the 2.0 inch display, and have checked that it is seated correctly).Here's some outputs to help:
As mentioned in the PiJuice docs, when changing the EEPROM from 50 to 52,
i2c-rtc,ds1339will have to be added to/boot/config.txt. I also note thati2c-bcm2708is an entry - removing it stops me from being able to communicate with the PiJuice.dtoverlay=i2c-bcm2708,i2c-rtc,ds1339The PaPiRus also has an RTC that I don't need to use, but to enable that I have to change that entry to:
dtoverlay=i2c-rtc,mcp7940x=1This allows that RTC to actually function and be read with
sudo hwclock -r, but of course withouti2c-bcm2708I can't communicate with the PiJuice (and usingdtoverlay=i2c-bcm2708,i2c-rtc,mcp7940x=1results in the RTC not working).RTC aside, the main issue is that the e-ink display doesn't show anything. Here's the output of
papirus-test(withdtoverlay=i2c-bcm2708,i2c-rtc,ds1339set, andsudo hwclock -rgiving theCannot access the Hardware Clock via any known method.error, it seems the PiJuice RTC isn't working for me at all - I never did check when I set the PiJuice up:I'm sure these two boards must be able to function together, I just don't know how to get them to play nice? Thank you for your help! :D