NanoPi M1 Plus doesn't load after change boot.scr

[Gerasim]

My device (NanoPi M1 Plus) is working by Ubuntu 16, and loading from eMMC (i'm connecting to device by SSH)
I was just gonna to change the HDMI display resolution from 1024x600 to 800x600 DPI.

The boot.cmd include a string

Code: Select all

#setenv hdmi_res drm_kms_helper.edid_firmware=HDMI-A-1:edid/1280x720.bin video=HDMI-A-1:1280x720@60

it is commented by default.
I uncommented this line with new options:

Code: Select all

setenv hdmi_res drm_kms_helper.edid_firmware=HDMI-A-1:edid/800x600.bin video=HDMI-A-1:800x600@60

After that, I had rebooted the device, but after the reboot, the new display setting had no effect (the resolution have not change from 1024x600 to 800x600)
Next to the boot.cmd is a boot.scr file with same data.
I uncommented the string "setenv hdmi_res..." with 800x600 option in boot.scr file, and after reboot, the device did not starting
How i can get back?
I have not connected by UART0 yet, to see boot log.

[Gerasim]

Debug UART output:

Code: Select all

U-Boot SPL 2017.11 (Jun 15 2021 - 10:49:36)
DRAM: 1024 MiB(408MHz)
CPU Freq: 408MHz
memory test: 1
Pattern 55aa  Writing...Reading...OK
Trying to boot from MMC2
Boot device: emmc


U-Boot 2017.11 (Jun 15 2021 - 10:49:36 +0800) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyElec NanoPi H3
DRAM:  1 GiB
CPU Freq: 1008MHz
MMC:   SUNXI SD/MMC: 1, SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
BOARD: nanopi-m1-plus
starting USB...
No controllers found
Hit any key to stop autoboot:  0
reading boot.scr
1575 bytes read in 18 ms (85 KiB/s)
## Executing script at 43100000
Bad data crc
=>

[Gerasim]

How did i repare the boot.scr
1) connect to device by Debug-UART
2) Based by article https://blog.csdn.net/qlexcel/article/details/122377077 i performed all strings of boot.cmd almost line-by-line like a picture. Yes device had starded!
3) Knocked to devise by WinSCP with root rights, and entered to boot folder.
4)

Code: Select all

mkimage -C none -A arm -T script -d boot.cmd boot.scr

created new boot.scr from boot.cmd
After reboot, the device has started normally.