IMX6 SWUpdate Requires a Login

[MichaelBMiner]

Hello,

I have gone back and forth with @Sanket_Parekh to get my u-boot environment properly setup. Now that I have that working I started to build my image and run the SWUpdate kernel. 

I build my images with the commands

bitbake swupdate-image
bitbake mainapplication-dev
bitbake smg-image-swu

Some background, when I build my image I get a file mainapplication-dev-imx6ull14x14evk.wic.bz2. When I build SWUpdate I get the image swupdate-image-imx6ull14x14evk.ext4.gz.u-boot.

I also get a properly created .SWU file but I am not ready to use this. 

I program my sd card with 

bzcat mainapplication-dev-imx6ull14x14evk.wic.bz2 | sudo dd of=/dev/sdd bs=1M conv=fsync

Then I mount my SD card to my Linux machine and run 

sudo cp swupdate-image-imx6ull14x14evk.ext4.gz.u-boot /mnt/rootfs/

I boot my device and interrupt the boot process to enter u-boot. I then run the commands

setenv bootargs console=ttymxc0,115200 root=/dev/ram0 rootfstype=ext4 rw 
setenv swupdate_bootcmd "load mmc 1 0x82000000 swupdate-image-imx6ull14x14evk.ext4.gz.u-boot;load mmc 1 0x82a00000 imx6ull-14x14-evk.dtb;load mmc 1 0x80800000 zImage;setenv root /dev/ram0;setenv rootfstype ext4;bootz 0x80800000 0x82000000 0x82a00000"
saveenv
print swupdate_bootcmd
run swupdate_bootcmd

This successfully loads the SWUpdate kernel

Kernel image @ 0x80800000 [ 0x000000 - 0x641778 ]
## Loading init Ramdisk from Legacy Image at 82000000 ...
   Image Name:   swupdate-image-imx6ull14x14evk-2
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    8992112 Bytes = 8.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 82a00000
   Booting using the fdt blob at 0x82a00000
   Using Device Tree in place at 82a00000, end 82a0bb93

There is a lot printed after this as modules are loaded. Then I get to the end

Swupdate v2021.11.0

Licensed under GPLv2. See source distribution for detailed copyright notices.

[INFO ] : SWUPDATE running :  [print_registered_handlers] : Registered handlers:
[INFO ] : SWUPDATE running :  [print_registered_handlers] :     dummy
[INFO ] : SWUPDATE running :  [print_registered_handlers] :     archive
[INFO ] : SWUPDATE running :  [print_registered_handlers] :     tar
[INFO ] : SWUPDATE running :  [print_registered_handlers] :     flash
[INFO ] : SWUPDATE running :  [print_registered_handlers] :     lua
[INFO ] : SWUPDATE running :  [print_registered_handlers] :     raw
[INFO ] : SWUPDATE running :  [print_registered_handlers] :     rawfile
[INFO ] : SWUPDATE running :  [print_registered_handlers] :     rawcopy
[INFO ] : SWUPDATE running :  [print_registered_handlers] :     shellscript
[INFO ] : SWUPDATE running :  [print_registered_handlers] :     preinstall
[INFO ] : SWUPDATE running :  [print_registered_handlers] :     postinstall
[TRACE] : SWUPDATE running :  [listener_create] : creating socket at /tmp/swupdateprog
[TRACE] : SWUPDATE running :  [network_initializer] : Main loop daemon
[TRACE] : SWUPDATE running :  [listener_create] : creating socket at /tmp/sockinstctrl
[TRACE] : SWUPDATE running :  [start_swupdate_subprocess] : Started webserver with pid 258 and fd 8
[INFO ] : SWUPDATE running :  [start_mongoose] : Mongoose web server version 6.18 with pid 258 started on port(s) 8080 with web root [/www]
Connected to SWUpdate via /tmp/swupdateprog

NXP i.MX Release Distro 5.10-hardknott imx6ull14x14evk /dev/ttymxc0

imx6ull14x14evk login: 

Here I am asked to login. I have tried admin/admin, admin/pass and a user I created for my main application with un/pw michael/michael. For these I always get the error 

NXP i.MX Release Distro 5.10-hardknott imx6ull14x14evk /dev/ttymxc0

imx6ull14x14evk login: admin
Password:
Login incorrect
login[255]: invalid password for 'UNKNOWN' on 'ttymxc0'
imx6ull14x14evk login:

If I attempt to login as root I am not prompted for a password. 

imx6ull14x14evk login: root
Login incorrect
login[255]: invalid password for 'root' on 'ttymxc0'
imx6ull14x14evk login:

As it stands I am completely locked out of my device every time I run the SWUpdate kernel. Has anyone else experienced this? Does anyone have any ideas?

[MichaelBMiner]

I believe this has to do with my rootfs, however I have not been able to confirm this. I have built a new image core-image-full-cmdline and attempted to place SWUpdate in my SD card image. When I attempt to run my SWUpdate kernel I am told there is bad data and a CRC is failing. 

[MichaelBMiner]

Within my bitbake environment I build core-image-full-cmdline, when I load this onto my SD card. I get the same error. I cannot log into the image. 

[MichaelBMiner · Accepted solution]

I kind of figured this out. Someone can correct me if I am wrong. NXP places a limitation preventing root from logging into the system. If you enable debug configs root can login. 

The SWUpdate kernel will only be run internal to the device. To resolve my issue I create a swupdate-image.bbappend and added IMAGE_INSTALL_append += " debugconfigs".

Now the SWUpdate kernel can be logged into using root and no password.