![]() ![]() # Use `install_packages` for dependencies RESIN_HOST_CONFIG_dtoverlay: “vc4-fkms-v3d”ĭockerfile.template # Force Raspberry Pi 3 for 32-bit X. ![]() Define DT parameters: “i2c_arm=on”,“spi=on”,“audio=on”.Define device GPU memory in megabytes: 512.If anyone has any ideas how to debug further that’d be great! Are there any Device Variables we should be setting differently?.Could you check over our Dockerfile.template & start script for obvious errors?.Do you have any ideas how we can debug this?.Have you noticed this behaviour before in other Balena apps?.Checking the supervisor logs journalctl -f -a -u resin-supervisor shows that it thinks it’s healthy.Attempting to restart the media player container via the Balena Cloud Services tab results in the Host reporting it has Killed the service but it doesn’t ever restart it.We can still interact with the Host and app container running the media player via the Balena Cloud Terminal, but free -m reports 288MB free ram, and top shows nothing using any significant CPU.The Balena Cloud Reboot/Restart buttons don’t reboot or restart the device.Running the identical software on a BalenaOS balenalib/raspberrypi3:buster image works for n loops of the playlist before hanging at the end of a video, and providing no error logs, warnings, or anything that we’ve been able to find. Running our software on a Raspbian Buster with desktop image, it’s able to run solidly for a week+. We were hoping to use Balena to deploy hundreds of these players but have run into a problem. We’re using the VLC bindings for Python module to download/cache a playlist of 1080p movies, and post playback stats to a RabbitMQ message broker. My team and I are working on a VLC based Raspberry Pi 4 media player. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |