Flash upgrade seems to work, but 2 error messages makes one a bit nervous

[frater]

Below is the text shown during a flash upgrade.
I know most of the warning and error messages in general can be ignored, but this is a bad habit really.....

Could this be addressed?

install: have Kernel 2.6.28.10 - set kversion '2.6.28' and FlashUpdateTool '/lib/modules/2.6.28.10/kernel/drivers/char/flash_update/flash_update.ko'
install: check and install new firmware ...
sh: write error: Invalid argument
OEM=
ANNEX=A
testing acceptance for device Fritz_Box_7390 ...
korrekt install type: iks_16MB_xilinx_4eth_2ab_isdn_nt_te_pots_wlan_usb_host_dect_64415
device has installtype iks_16MB_xilinx_4eth_2ab_isdn_nt_te_pots_wlan_usb_host_dect_64415
OK - accept this update for device Fritz_Box_7390 ...
testing acceptance for device Fritz_Box_7390 done
curr: 84.05.51 new: xx.05.51
debug: curr: 84.05.51
debug: new: "XX.05.51"
major_currFWver=84
middle_currFWver=5
minor_currFWver=51
middle_newFWver=5
minor_newFWver=51
check Firmware Version: xx.05.51
DEBUG: 5 >= 5
DEBUG: 51 >= 51
Accept Firmware Version: xx.05.51
install: 2.6.28 check files...
File doesn't contain the checksum, adding
Calculated checksum is C33003
Adding failed
chksum for file /var/tmp/kernel.image ok
size for file /var/tmp/kernel.image ok
install: 2.6.28 getting mtd to install...

 

[gismotro]

I think all your messages are normal. Look at my updatelog:

install: have Kernel 2.6.32.41 - set kversion '2.6.32' and FlashUpdateTool '/lib/modules/2.6.32.41/kernel/drivers/char/flash_update/flash_update.ko'
install: check and install new firmware ...
[COLOR="#FF0000"][B]sh: write error: Invalid argument[/B][/COLOR]
OEM=
ANNEX=B
testing acceptance for device Fritz_Box_HW188 ...
korrekt install type: mips34_16MB_dect441_1eth_1geth_1ab_2usb_host_wlan11n_01118
device has installtype mips34_16MB_dect441_1eth_1geth_1ab_2usb_host_wlan11n_01118
OK - accept this update for device Fritz_Box_HW188 ...
testing acceptance for device Fritz_Box_HW188 done
curr: 116.01.01  new: xx.05.50
debug: curr: 116.01.01
debug: new: "XX.05.50"
major_currFWver=116
middle_currFWver=1
minor_currFWver=1
middle_newFWver=5
minor_newFWver=50
check Firmware Version: xx.05.50
DEBUG: 5 >= 1
DEBUG: 5 > 1
Accept Firmware Version: xx.05.50
install: 2.6.32 check files...
[COLOR="#FF0000"][B]File doesn't contain the checksum, adding
Calculated checksum is 24C7224
Adding failed[/B][/COLOR]
chksum for file /var/tmp/kernel.image ok
size for file /var/tmp/kernel.image ok
install: 2.6.32 getting mtd to install...
install: -----------------------------------------------------
flash_startadress 268435456
kernel_update_start 268566528
bootloader_size 0x00020000
jffs2_size 0x00100000
Kernel_without_jffs2_size 15073280
kernel_image_size 14739208
kernel_mtd_size 16121856
Kernel_Start_Add = 268566528
Kernel_End_Addr = 268566528 + 14739208
Kernel_without_jffs2_End_Addr = 268566528 + 15073280
install: -----------------------------------------------------
install: kernel_size=16121856
install: kernel_update_start=268566528
install: kernel_update_len=16121856
install: 2.6.32 setting files to install...
install: /var/tmp/kernel.image to start(268566528) size(16121856)
install: check for old settings ...
set INFO led to blink (modul=7, state=4)
sh: write error: Invalid argument

I think this messages depense on this point: * bei Downgrade auf ältere Version zulassen

 

[frater]

Maybe I should have used a different "subject title", but what I meant to say is that there shouldn't be any failure messages if there is no failure...
Especially in user interaction.

Otherwise an attitude is developed that one can ignore these messages....
When there is really something wrong it will not get noticed.

 

[olistudent]

These scripts are written by AVM. As the user normally doesn't read this messages they don't care about errors...

We don't mind to fix broken AVM scripts as long as there is no problem.

Regards
Oliver

 

[frater]

Thanks for your clarification. I wasn't aware that those were AVM scripts. I fully agree with your policy.