[ Cubietruck ] BAD CRC on environment
Cubieboard 3 image lost the settings of the board at each boot because the config file has a bad CRC.
Output of boot:
U-Boot SPL 2017.05-00394-g22f3368 (May 22 2017 - 22:09:57)
DRAM: 2048 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1
U-Boot 2017.05-00394-g22f3368 (May 22 2017 - 22:09:57 +0200) Allwinner Technology
CPU: Allwinner A20 (SUN7I)
Model: Cubietech Cubietruck
I2C: ready
DRAM: 2 GiB
MMC: SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment
Setting up a 1024x768 vga console (overscan 0x0)
In: serial
Out: vga
Err: vga
SCSI: SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net: eth0: ethernet@01c50000
starting USB...
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
USB2: USB EHCI 1.00
USB3: USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0-
Does Devuan use sunxi tools? where is the "script.bin" file and the related tools?
Edited by Luzemario -
These images use mainline u-boot and mainline Linux where applicable. There's a boot.cmd in the first partition (/boot) where you can change the bootargs that get read by u-boot.
However, this warning is very usual and I think I saw it on every device I've tried to boot.
-
I am experiencing issues to make VGA the default output at boot... the settings are never saved. Will I need to recompile the entire DTS file to achieve this?
-
What do you mean by "not saved"? Are you able to get a tty on vga?
-
I get no VGA output at all after rebooting. The default output for current DTS is at HDMI only, as far as I can tell. After logging in with SSH, for example, I can sucessfully activate dual-head output, i.e. both HDMI and VGA.
Can you confirm the default setting for "display_output" in the DTB used in Devuan?
Edited by Luzemario -
You can get more info here:
-
@parazyd Nevermind... for some strange reason a bad block on the microSD was returning aways "0x0" to the "disp_mode" setting in the DTB image area...
I got a new fresh image from Devuan repo and all works flawlessly. I am closing this bug.
-
closed
