Home of the Squeezebox™ & Transporter® network music players.
Results 1 to 9 of 9
  1. #1
    Junior Member
    Join Date
    Apr 2020
    Posts
    8

    LiFePO4wered/Pi+

    Dear people.

    Since some time I user of LMS and Picoreplayers troughout the house for sonos like experience but better.
    I recently wanted to use a headphone amp hat on a project and the only one was the Pirate Audio with screen and buttons.
    http://kiwi-electronics.nl/pim-482

    A bit of an overkill but made me think of a totally different option. A portable wifi pocket streamer. Thanks to this amazing tutorial I was able to make it work https://forums.slimdevices.com/showt...l=1#post971970

    But now the battery part. I for some time really liked the LiFePO4 idea since its more fire safe and durable.
    https://lifepo4wered.com/lifepo4wered-pi+.html

    It came in today, but in the newer version it needs a boot veryfication to stay powered for more then 5 minutes. So it really needs this driver
    "The reason is that the LiFePO4wered/Pi+™ firmware includes a timeout for the
    boot sequence with a default length of 5 minutes. If the LiFePO4wered/Pi+™ is turned on and doesn’t
    get notified by the host daemon that the system has booted within 5 minutes, the power will be turned
    off. "

    I found out the hard way and installing the driver is not so simple for a tiny linux install unfortunately...
    So installing it this way is not possible.
    https://github.com/xorbit/LiFePO4wered-Pi

    I hope someone here has experience getting it to work with a piCoreplayer setup?
    Google only tagged people who had this in their signature but no discussions I could find so fat concerning picore player or other tinylinux distro's.

    Thanks in advance!

    p.s. Im a Linux newbie, but I try hard to get there to make it work always
    Last edited by Dutch87; 2020-05-05 at 11:17.

  2. #2
    Senior Member
    Join Date
    Apr 2005
    Location
    UK/London
    Posts
    2,448
    Will need working through this to see what tricks they need
    https://github.com/xorbit/LiFePO4wered-Pi


    Edit: I had a quick look and it appears to require Python and some build tools
    Does not look straight forward to me.
    Last edited by Paul Webster; 2020-05-05 at 11:05.
    Paul Webster
    http://dabdig.blogspot.com
    Author of "Now Playing" plugins covering Radio France (FIP etc), KCRW, Supla Finland, ABC Australia, CBC/Radio-Canada and RTE Ireland

  3. #3
    Junior Member
    Join Date
    Apr 2020
    Posts
    8
    Quote Originally Posted by Paul Webster View Post
    Will need working through this to see what tricks they need
    https://github.com/xorbit/LiFePO4wered-Pi


    Edit: I had a quick look and it appears to require Python and some build tools
    Does not look straight forward to me.
    Thanks for looking and I'm afraid too...
    That why I hope maybe somebody has been before this point before but with more knowledge and understanding to make it work...

  4. #4
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Location
    Nottingham, UK
    Posts
    1,648
    Are the register settings permanently written to the device, and are the tools provided pre-built for a different OS? If so, could you use that OS to disable the boot timeout?

    From the product brief:
    PI_BOOT_TO
    1 byte, register address 0x21, read/write, saved to flash
    Default value: 30 (corresponding to 300 seconds or 5 minutes, resolution of 10 seconds per LSB)
    The LiFePO4wered/Pi+Ö will not indefinitely stay in the boot state if there is no response from the
    Raspberry Pi. Instead, power will be turned back off after the boot timeout expires. The boot timeout
    can be set in 10 second increments up to 2550 seconds or 42.5 minutes. Setting this register to 0 turns
    the boot timeout off.

    The Raspberry Pi host software package contains scaling code so the value can be read and set in
    seconds for convenience

  5. #5
    Junior Member
    Join Date
    Apr 2020
    Posts
    8
    Quote Originally Posted by chill View Post
    Are the register settings permanently written to the device, and are the tools provided pre-built for a different OS? If so, could you use that OS to disable the boot timeout?

    From the product brief:
    Indeed, it seems one can rewrite this in the firmware... but now im looking into how to get this I2C acces done and what it is...
    "The LiFePO4wered/Pi+Ö supports I2C access from the host at the standard speed of 100 kHz
    maximum"

  6. #6
    Junior Member
    Join Date
    Apr 2020
    Posts
    8
    If it turns out, nobody ever got this driver working with piCoreplayer maybe it's better for me to look for an alternative powersource... This I2C so far is too challenging withouth a manual how to edit it.
    So far I could only find this that shows how to read it https://learn.adafruit.com/adafruits...onfiguring-i2c

    Anybody have any experience with piCore player and a UPS?

    I'm looking for a lithium free/safe powered source. Anybody any thoughts on regular battery powered situatiens or this board?
    https://www.adafruit.com/product/4114
    Last edited by Dutch87; 2020-05-07 at 05:18.

  7. #7
    Junior Member
    Join Date
    Mar 2020
    Location
    Bristol, UK
    Posts
    24
    Hi,
    I am not sure to understand what you are looking for exactly. UPS?
    Could the Pi-Supply products be of interest for your project?
    https://uk.pi-supply.com/collections...-and-batteries
    I have not used them myself but from what I have gathered they are OK.
    Sorry if my answer is off-topic.

  8. #8
    Junior Member
    Join Date
    Apr 2020
    Posts
    8
    Yeah, by me its also ontopic, since I wonder if anybody here has experience using a different UPS with shutdown button on piCore player thats compatible with this OS..
    Last edited by Dutch87; 2020-05-07 at 06:00.

  9. #9
    Junior Member
    Join Date
    Apr 2020
    Posts
    8
    I got word back for the support. The auto boot shutdown protection was disabled by these commands using a raspbian lite build with the drivers installed:

    # lifepo4wered-cli set PI_BOOT_TO 0

    # lifepo4wered-cli set CFG_WRITE 70

    It now works.
    I understand it takes the work of the developers here to actually include the driver in the build.
    And yeah ofcource we don't need a clean shutdown so maybe who cares...

    If you ask me its solved.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •