I have ssh locally to my Raspberry Pi 3 running latest BalenaOS 2.46.1+rev1 development version.
I have deleted the config.txt file from /mnt/boot/ directory.
After rebbot I can see the config.txt file has been recreated in the same directory and the configuration looks ok and match the fleet wide settings applied using BalenaCloud Dashboard.
The App looks running but the LCD now does not work properly ( before the accidental deletion of config.txt the LCD was perfectly working).
What can could have happened that messed up the LCD?
Hi @rlev, could you please clarify if you have done any edits to /mnt/boot/config.txt earlier? What about after it is recreated?
I have ssh locally to my Raspberry Pi 3
Next, do you mean that you were running this RPi3 locally?
balena supervisor is going re-create /mnt/boot/config.txt and keep it in sync with the version in cloud as long as the device is connected to balenaCloud and not running in local mode. Here is our relevant doc about modifying config,txt: Advanced boot settings - Balena Documentation
I will suggest restarting the device to make sure that the device got the latest synced version of config.txt. It’d be good to check and compare its content with the default one in case you expect modifications here. As documented, we suggest to update the variables here via the dashboard interface.
If things are not running fine after restart, let’s take a further look. It’d be good if you could send us the device UUID (the dashboard link of device) and enable support access. So we could check the supervisor logs and see if there are any errors.
I using 2 devices with BalenaOS development version.
In one of them “lively-wildflower” was working ok but we noted the screen was setup via the initial config.txt to 640x480. We saw this setting using the balena cloud Dashboard. The device at this point was working ok, lcd working fine but with the mentioned resolution.
We decided to modify the 640x480 to 800x600 which is the max. resolution supported by our device’s LCD.
We used the device configuration menu in the balena cloud Dashboard.
After the modifications were done the device LCD show correct booting splash screen but then goes black and show black screen with some random lines.
The device still connect to balena cloud. using the Dashboard ssh terminal we can see in the Host that the /mnt/boot/config.txt is ok and match the parameters changed but the screen does not work properly anymore :(.
# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details
# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
disable_overscan=1
# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16
# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=800
#framebuffer_height=480
# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1
# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=1
hdmi_mode=31
#lcd 1,31
#HDMI 2,82
# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2
# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4
# uncomment for composite PAL
#sdtv_mode=2
#uncomment to overclock the arm. 700 MHz is the default.
arm_freq=1200
dtparam=i2c_arm=on
dtparam=spi=off
#display dpi24
ignore_lcd=1
lcd_rotate=2
dtoverlay=dpi24
overscan_left=0
overscan_right=0
overscan_top=0
overscan_bottom=0
framebuffer_width=800
framebuffer_height=480
enable_dpi_lcd=1
display_default_lcd=1
dpi_group=2
dpi_mode=87
dpi_output_format=0xfff007
dpi_timings=800 0 40 48 88 480 0 13 3 32 0 0 0 60 0 32000000 3
#I2C FOR TOUCH
#gpio=0,1=ip
gpio=28,29=a0
#DPI
gpio=0,1=a2
gpio=4-27=a2
#UART1 FOR BT
gpio=40-41=a5
#SDIO FOR WIFI
gpio=34-39=a3
#UART0 FOR MCU
gpio=32-33=a3
gpio=30,31=op
#PWM FOR ADJ
#gpio=45=a0
#fix
gpio=45=ip
#Touch INT/RST
gpio=2,3=ip
# Uncomment some or all of these to enable the optional hardware interfaces
dtoverlay=midi-uart1
dtoverlay=uart1,txd1_pin=40
dtoverlay=uart1,rxd1_pin=41
dtoverlay=i2c0-bcm2708,pins_28_29
dtparam=i2c_vc=on
dtparam=uart0_arm=on
dtparam=uart1_arm=on
dtparam=sdio1_arm=on
dtparam=pwm1_arm=on
#dtparam=i2s=on
#dtparam=spi=on
# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi
# Additional overlays and parameters are documented /boot/overlays/README
# Enable audio (loads snd_bcm2835)
dtparam=audio=on
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
[all]
#dtoverlay=vc4-fkms-v3d
#scaling_kernel=8
start_x=0
gpu_mem=256
##disable_camera_led=1
enable_uart=1
Is the screen connected via hdmi ?
According to https://www.raspberrypi.org/documentation/configuration/config-txt/video.mdhdmi_group should be 2 and hdmi_mode should be 8, 9, 10, 11, 12 or 13 depending on the refresh rate for a 800x600 resolution.
Your config.txt sets the screen for 1080p@50Hz framebuffer_width and framebuffer_height control the framebuffer size, not the screen resolution.
The screen was working ok.
My guess is that somehow after we did the modification using the Dashboard the supervisor did something unexpected and we end up with a non working lcd although the config.txt in the device match the settings in the balena cloud Dashboard.
We tried that. Did not help.
I guess the only solution would be to reflash the device with a new BalenaOS and assign a new device ID.
But we were hoping there was a easier solution.
