Posts by HarryH

  • [RPi4] Argon One Case Shutdown

    Version 0.0.11d released

    Original this version should only be a debug release, but I corrected many things under the hood so I don't hide.

    • “Handle power button events” is honored without reboot
    • remote control shutdown exception fixed
    • fan settings now adjustable in 1 degree steps
    • added debug messages
    • freeing of power button detection GPIO pin forced
    • code cleanup

    Edit:
    Known issues:

    • LibreELEC 12 -> gpiozero makes some trouble in combination with lgpio
      If the add-on was disabled and enabled again, the GPIO pin for power button monitoring can't be freed. To workaround a reboot is needed, to work again.
      It's a general issue, not specific for this version. It affects all versions until now. I'm currently investigating to find a solution for that.

  • [RPi4] Argon One Case Shutdown

    Version 0.0.11b released

    • explicit firmware detection during power off procedure to reduce this call to one
    • attempt to fix the permission issue for lgpio workaround
      The problem must have existed from version 0.0.7 to 0.0.10, but unfortunately no one here reported that the add-on does not work properly in combination with LE12. In such cases, I would be happy to receive feedback and, if necessary, a kodi.log.:
      https://wiki.libreelec.tv/support/log-files

  • RPi-Tools, gpiozero and a rPi5

    You need to force gpiozero to initialize lgpio with the correct chip. For this you need LE12 nightly, because lgpio is only part of the RPi tools from LibreELEC 12. This combination is currently the only one that supports RPi5 out of the box.

    To initialize the RP1 at the RPi5:

    Python
    from gpiozero.pins.lgpio import LGPIOFactory
from gpiozero import Device, PWMLED
Device.pin_factory = LGPIOFactory(chip=4)

    Additionally you have to circumstand this lgpio bug:

  • [RPi4] Argon One Case Shutdown

    Quote

    Can the addon be configured so it doesn't override /storage/.config/rc_maps.cfg on boot? I've changed it to support the remote I'm using but after a reboot its back to the argon40 remote.

    Before I look deeper into the code, does this "touch /storage/.config/argon40_rc.lock" don't work for you?

    Regarding the range. I have seen your post in Argon40 forum. I can only report from a buddy of me, who is owner of a Argon One V1 and has added the IR Receiver manually. He reported a bad response to the IR signal until he has made a slot/hole in the transluent red plastic cover. Before made such irreversible changes you should check without the bottom assembled.

    Edit:
    In a short test with my universal remote control, I got a distance of about 4m/13 feet when I pointed the remote control frontal to the argon case. The further you go away, it seems more important to keep the remote control at the same heights as the case/IR sensor.

  • [RPi4] Argon One Case Shutdown

    Version 0.0.9a released

    • includes the fix for power button recognition with RPi5 + LE12
      (double tab) -> Reboot
      (hold > 3 seconds) -> graceful shutdown
      (hold > 5 seconds) -> enforced shutdown with power cut Pi

    :!:A fix for the power button recognition with RPi5 + LE11 is currently not possible, because lgpio is only available with RPi-Tools Add-on for LE12. The LE11 RPi-Tools Add-on provides the backend RPi.GPIO which doesn't support the RPi5.

  • [RPi4] Argon One Case Shutdown

    The hopefully fixed version 0.0.8 is available. Please report if it's working now without fan fluctuation with the Argon One V3 case.

    Can someone with a Argon One V3 case check if a "Double Tap" at the power button triggers Reboot like with Argon One V2 case?
    If not, I need some information if it works after changing these lines in /flash/config.txt from:

    Code
    dtoverlay=gpio-ir,gpio_pin=23
dtparam=i2c=on
enable_uart=1

    to

    Code
    dtoverlay=gpio-ir,gpio_pin=23
dtparam=i2c=on
dtparam=uart0=on

    Followed by a reboot.

  • [RPi4] Argon One Case Shutdown

    PANiCnz ,

    your are the second which reports this behavior with Argon One V3 in combination with 0.0.7. So there seems really to be an issue within the current code.
    Currently I can't reproduce with my V2 case... it could takes longer to find the root cause.

    As long the CPU temperatur is below the first threshold, the fan should be off. Pulsing is possible if the current temperature is around the threshold. 42c is far away from the 55c default value. I fear I have possibly insert this bug as I switched over to the Argon Register Helper methods, which has a mechanism included to differentiate the firmware versions.

    From the testing with Argon V3 case exists a version 0.0.6d, but this version should only be used with LE12 + Argon One V3 cases, because the commands were changed for the new firmware. I don't know if there are also V2 cases with this type of firmware in the wild.

    Edit: This bug was fixed beginning with v.0.0.8. Please update to a current version of the add-on.

  • TSV video format

    @Guis,

    If blueribb's hint doesn't work and the files aren't encrypted (unlike petediscrete feared), you might want to try TS-Doctor. This tool is not free, but you have a trial period. The files are only remuxed and not converted. The time required is not that great and the quality of the video and audio stream remains unaffected.

  • [RPi4B] A/V Problems

    myshit,

    I am in the lucky situation that the combination Argon One + Pi4 worked flawless out-of-the box. According to the PiHut documentation it seems to make a difference which HDMI port is in use.

    https://support.thepihut.com/hc/en-us/articles/360008687257-No-HDMI-output-on-my-Raspberry-Pi-4

    With LibreELEC 11.0.3., I get vc4-hdmi-0 as primary audio device, but my cable chain is (Pi4)Argon One M2 -> AVR-> TV (1920x1080). I don't know if it's only because the auto-detection of your displays EDID is currently not working right, but it looks to me that your HDMI cable is connected to the second HDMI port.

    HDMI can be erroneous, because of many pitfalls. VLouis and Da Flex comments are directing to the most well-known root causes of issues with EDID, handshake, maximum transfer speed (4K related) and so on.

    - bad cabling (cheap manufactured cables, not certified, not 4K ready ...)

    - buggy software/hardware at display device or AVR (TV, monitor, projector)

    - production issue of circuit board in the Argon One case

    - driver issue

    - high frequency emitting devices in the near like USB3, WLAN

    ...

    Additional I had made the experience that a powerless device which is connected at the same time to the AVR via HDMI can disturb CEC, because it seems to pulls down the +5V or the signal level at HDMI.

    The Argon One casing seems not free of additional issues, some users had to force the EDID information. Do you have tested yet the 4 lines at the same time in your config.txt?

    Thread

    RPI4 No HDMI Sound using Argon One Case

    Just got my RPI 8GB today and flashed LibreELEC on it and installed Argon One script on it. I have already set hdmi_drive=2 and there is still no sound. When I switch to Analogue and plug in a headphones and switch the Audio Output Device to HDMI / HDMI + Analog, I get sound only on the headphones . When I disassembled and used the RPI4 without the case, the audio seemed to work fine. This only happens when it is connected to the Argon One Case. Really appreciate any help

    Kodi Log: …
    prispither
    June 1, 2020 at 4:22 PM
    Raspberry Pi Documentation - The config.txt file
    The official documentation for Raspberry Pi computers and microcontrollers
    www.raspberrypi.com
    Code: config.txt
    hdmi_drive=2
hdmi_ignore_edid=0xa5000080
hdmi_mode=16
hdmi_group=1