Posts by HarryH

    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?

    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

    I‘m not sure if it’s a good idea to start this discussion here and not in separate thread...

    Do you have ensured that you has connected to the first HDMI 0 port? If yes, please check if the contacts at the plugs and the sockets looks good.

    Did it work with LibreELEC 11.0.3 before or just an older version?

    myshit,

    You're welcome. Nice to read that it's working for you now.

    Da Flex
    I have reviewed the python scripts again. To be technical correct I should revise my posting (#28)

    • the microcontroller supports Reboot (double-tab at power-on button) and not RESET
    • the microcontroller signals 2 different requests (Reboot, Shutdown) at PIN7 of the Pi4 board
    • during shutting down a script sends 2 messages at SMBus (i2C) back to the microcontroller
      - first message : stop fan
      - second message: initiate power off, cut when the serial pin goes 'down'
      More information about this are available here: https://github.com/Argon40Tech/Argon40case

    These things are only working if a service is running in the background to make cycling checks at PIN7 for new message from the microcontroller. The shutdown script is a hook during the LibreELEC OS shutdown: https://wiki.libreelec.tv/configuration/startup-shutdown

    Hi Da Flex ,

    I hope I can remind me right, because these information are 2 years old... ;)

    There are at least 2-3 revisions of the Argon One case. The newer ones even have an infrared receiver on board. The power-on button is not directly connected to the Pi. In between is a circuit board with a microcontroller. This is responsible for switching off the power supply to the Raspberry after shutting down. The microcontroller recognizes the signal at the power-on button and can also trigger a RESET (different PIN on the Raspberry) by pressing the power-on button twice in quick succession. If you press this button longer than 3x seconds, the Raspberry will be shut down and the power will be switched off after a delay. It may be that this behavior depends on the firmware version of the microcontroller and could be different with the first batch of the casing.

    If you shut down the Raspberry via OS, the microcontroller in the Argon One lacks the information that its allowed to cut the power supply. Therefore, after an orderly shutdown, the red LED at the front, behind the semi-transparent plastic cover, remains on. However, the microcontroller also knows a return channel via PIN on the UART interface. This PIN changes its logic level after shut down of the Pi and the microcontroller starts the process to cut the power of the Raspberry Pi. This has to be configured specifically on every OS and with every startup. It's part of the ArgonForty Device Configuration add-on, for example. Alternatively, there are some other scripts/daemons that do something similar.

    Please be aware:

    I'm not a developer of KODI Add-ons. This is only a result of someone who had the wish to get the Add-on work again with LibreELEC 10 and later.



    what it does:

    • supports LibreELEC 11 + 12 Nightly
    • supports Argon One V1/2 (RPi4)
    • supports Argon One V3 (RPi5)
    • enables IR Receiver (V2/V3, or if self added to V1 pcb)
    • enables Argon REMOTE support (rc_maps + keymap)
    • fan control
    • graceful shutdown (power button commands: Reboot , Shutdown ...)

    :!:For full support of the power button commands with a RPi5, please use LE12.



    It includes a workaround for the lgpio bug (Many thanks to HiassofT). Also thanks to Nekromantik how gaves me feedback regarding LE12 nightly and testing with the new V3 case.

    Please use the latest version of the add-on if you are using LE11 or L12 to ensure that the known bugs have been fixed.
    It might also work with LE10 (RPi4) but is untested. If someone is really using LE10 and it doesn't work, they can try version v.0.0.4. I have made the download available just for this case.

    2024/08/18 Version 1.1.2 (recommended):

    Important: The add-on download has been moved to GitHub: Download

    I have refactored something to fix some exceptions which appeared during shutdown process in the kodi.log. This speeds up the Shutdown and the Reboot time.

    Additional I have implemented a workaround for the unexpected behavior of the shutdown procedure if the power button of the remote control is used for that.

    Issue:
    :!:After the power button at remote control is pressed, KODI (OS independent) has only ~10 seconds to shutdown safety ! It can't be interrupted and is perhaps only with another case firmware correctable.

    Solution:
    To compensate that, I have optimized v0.0.10 as far I currently could to decrease the shutdown time to below 8 seconds. Depending whats currently installed and running in KODI it need sometimes longer, then the shutdown will not be graceful and data corruption is possible in the worst case.

    This behavior is only if you use the remote control power button to switch off. If the case button is in use or the power menu of KODI to shutdown, the power cut is initiated just at the end (+10 seconds).

    Another workaround for the following scenario:
    Remote control power button pressed → 10 seconds timer starts -> shutdown is initiated → red LED turns off, but it seems that it doesn't respond to the power button on the remote to get it on again.

    Please try in this situation (unsuccessful shutdown):

    • The red LED must be off
    • Press the power button on the remote control
    • Wait 10 seconds (MCU cuts off power internally)
    • Press the power button on the remote control again to boot


    Breaking change:
    :!:Additional I have switched from lircd to rc_maps/keymaps (thanks to adam.h. for providing the files). If you use a self made remote control profile for your remote control, please make a backup of your remote control configuration and/or place a lock file before installation to prevent overwriting:
    touch /storage/.config/argon40_rc.lock



    Source:

    The original sources are from there: GitHub Argon40Tech

    and here: Installation package version 0.0.1


    I have forked (26.10.2023) the Argon40 Add-on repository and pushed my changes to this repository: GitHub ArgonForty Device Configuration add-on



    Installation:
    The installation process will try to add 3 lines to the config.txt to enable the needed modules for I2C and UART. This part is not bullet proofed, because it looks only for the first line. It skips the needed modification if the line "dtparam=i2c=on" is already there. Therefore it could be better to make a backup of /flash/config.txt before to see the different.

    A few things to do (The first 3 steps in square brackets are only optional, if the dependencies can not be resolved automatically):

    • [ install RPi Tools (LibreELEC Repo -> Program Add-ons) ]
    • [ install System Tools (LibreELEC Repo -> Program Add-ons) ]
    • [ Reboot (necessary before installing the Argon Add-on so that the system tools work properly) ]
    • upload one of the attached zip files to /tmp, /storage or another place where you have access via KODI
    • Allow installation of Add-ons from external sources:
    • Enable "Settings->System->Addons->Unknown sources".
    • in the main menu within Add-ons select "Install from ZIP file", confirm the security question and switch to the folder where you uploaded the zip
    • select the ZIP file and press OK
    • after installation: Ignore the "Device Configuration Error" teaser message and reboot, so that the modules for UART and I2C are activated

    Within Add-ons list, the ArgonForty Device Configuration Add-on should be available now. There you can configure the fan settings and the shutdown should work now. Please be patient, it will take a few seconds for the LED to turn off.

    Important: The add-on download has been moved to GitHub: Download

    myshit ,

    You will need some additional scripts that are part of the Argon Pi addon. Since the add-on was no longer maintained after the initial commit on GitHub, I ported it myself to make it work with LibreElec 10+ two years ago. I haven't touched this since then, but it still works with LibreElec 11 and you can also configure the fan speed.

    I'd have to look up the git repo and installation package. If my newly created user allows this at all, I could make it available here.