DEY 3.2 bugs, format update partition with error, failed to update firmware using the firmware update package

Embedded Devices Linux
, , ,
1

I try the newly release DEY 3.2 but found some bugs. I use the ccimx6ul starter kit and build the project without any modification.

  1. When I format the update partition, the console prints the follwoing lines

ubi: mtd6 is already attached to ubi2
ERROR: Could not mount ‘update’ partition, volume not found
rmdir: ‘/mnt/update’: Device or resource busy
imx_busfreq soc:busfreq: Skip setting low bus freq
imx_busfreq soc:busfreq: Skip setting low bus freq
imx_busfreq soc:busfreq: Skip setting low bus freq
Error opening /dev/fb0
[RECOVERY] Starting recovery…
[RECOVERY] Wipe ‘update’ partition requested
[RECOVERY] Formatting ‘update’ ubi volume
[RECOVERY] Partition ‘update’ successfully erased!

There is maybe something wrong, but somehow the update partition is formated finally

  1. When I update firmware using the update firmware package (.swu), the console prints lots of errors

Update started !
Interface: UNKNOWN

[TRACE] : SWUPDATE running : [extract_files] : Found file
[TRACE] : SWUPDATE running : [extract_files] : filename core-image-base-ccimx6ulstarter.boot.ubifs
[TRACE] : SWUPDATE running : [extract_files] : size 8634368 required
[TRACE] : SWUPDATE running : [extract_files] : Installing STREAM core-image-base-ccimx6ulstarter.boot.ubifs, 8634368 bytes
Error opening /dev/fb0
[TRACE] : SWUPDATE running : [install_single_image] : Found installer for stream core-image-base-ccimx6ulstarter.boot.ubifs ubivol
[INFO ] : SWUPDATE running : Installing image core-image-base-ccimx6ulstarter.boot.ubifs into volume /dev/ubi0_0(linux)
[TRACE] : SWUPDATE running : [update_volume] : Updating UBI : core-image-base-ccimx6ulstarter.boot.ubifs 8634368
Error opening /dev/fb0
Error opening /dev/fb0
Error opening /dev/fb0---------------------------------------- ] 1 of 2 0% (core-image-base-ccimx6ulstarter.boot.ubifs), dwl 0% of 0 bytes
Error opening /dev/fb0---------------------------------------- ] 1 of 2 1% (core-image-base-ccimx6ulstarter.boot.ubifs), dwl 0% of 0 bytes
*** SOME LINES are REMOVED TO MAKE THE POST SHORT ***
Error opening /dev/fb0==================---------------------- ] 1 of 2 64% (core-image-base-ccimx6ulstarter.boot.ubifs), dwl 0% of 0 bytes
Error opening /dev/fb0===================--------------------- ] 1 of 2 65% (core-image-base-ccimx6ulstarter.boot.ubifs), dwl 0% of 0 bytes
[TRACE] : SWUPDATE running : [extract_files] : END INSTALLING STREAMING
[TRACE] : SWUPDATE running : [extract_files] : Found file
[TRACE] : SWUPDATE running : [extract_files] : filename core-image-base-ccimx6ulstarter.ubifs
[TRACE] : SWUPDATE running : [extract_files] : size 80248832 required
[TRACE] : SWUPDATE running : [extract_files] : Installing STREAM core-image-base-ccimx6ulstarter.ubifs, 80248832 bytes
[TRACE] : SWUPDATE running : [install_single_image] : Found installer for stream core-image-base-ccimx6ulstarter.ubifs ubivol
[INFO ] : SWUPDATE running : Installing image core-image-base-ccimx6ulstarter.ubifs into volume /dev/ubi1_0(rootfs)
[TRACE] : SWUPDATE running : [update_volume] : Updating UBI : core-image-base-ccimx6ulstarter.ubifs 80248832
Error opening /dev/fb0===================--------------------- ] 1 of 2 66% (core-image-base-ccimx6ulstarter.boot.ubifs), dwl 0% of 0 bytes
Error opening /dev/fb0====================-------------------- ] 1 of 2 67% (core-image-base-ccimx6ulstarter.boot.ubifs), dwl 0% of 0 bytes
*** SOME LINES are REMOVED TO MAKE THE POST SHORT ***
Error opening /dev/fb0=======================================- ] 1 of 2 99% (core-image-base-ccimx6ulstarter.boot.ubifs), dwl 0% of 0 bytes
Error opening /dev/fb0======================================== ] 1 of 2 100% (core-image-base-ccimx6ulstarter.boot.ubifs), dwl 0% of 0 bytes

Error opening /dev/fb0---------------------------------------- ] 2 of 2 0% (core-image-base-ccimx6ulstarter.ubifs), dwl 0% of 0 bytes
Error opening /dev/fb0---------------------------------------- ] 2 of 2 1% (core-image-base-ccimx6ulstarter.ubifs), dwl 0% of 0 bytes
*** SOME LINES are REMOVED TO MAKE THE POST SHORT ***
Error opening /dev/fb0===================--------------------- ] 2 of 2 65% (core-image-base-ccimx6ulstarter.ubifs), dwl 0% of 0 bytes
Error opening /dev/fb0===================--------------------- ] 2 of 2 66% (core-image-base-ccimx6ulstarter.ubifs), dwl 0% of 0 bytes
[TRACE] : SWUPDATE running : [extract_files] : END INSTALLING STREAMING
[TRACE] : SWUPDATE running : [extract_padding] : Expecting 388 padding bytes at end-of-file
[TRACE] : SWUPDATE running : [network_initializer] : Valid image found: copying to FLASH
[INFO ] : SWUPDATE running : Installation in progress
[INFO ] : SWUPDATE successful ! SWUPDATE successful !
[TRACE] : SWUPDATE running : [network_initializer] : Main thread sleep again !
[INFO ] : No SWUPDATE running : Waiting for requests…
Error opening /dev/fb0====================-------------------- ] 2 of 2 67% (core-image-base-ccimx6ulstarter.ubifs), dwl 0% of 0 bytes
[INFO ] : SWUPDATE running : [endupdate] : Swupdate was successful !

[RECOVERY] Firmware update process succeed!

Please check for me, thanks.

2

DEY-3.2 no longer uses the update partition software update mechanism. Instead, it switches to a dual boot system.
https://www.digi.com/resources/documentation/digidocs/embedded/dey/3.2/cc6ul/yocto_t_dualboot
you can still create and use update partition but some porting will be required

https://www.digi.com/resources/documentation/digidocs/embedded/dey/3.2/cc6ul/yocto_t_program-firmware-from-linux

3

Those Error opening /dev/fb0 error messages are not important, but they are annoying.
Removing the psplash package from the recovery image seems to fix most of it.

However, updates are MUCH slower since DEY 3.2, I don’t know why.

Dual boot is an optional feature, which doesn’t seem to be enabled by default.