Integration questions on TI Arago SDK

[Howard Egan]

Hi:

My previous integration of SWUpdate used the GRUB bootloader.  That turned out great (Thanks Stefano).

I'm now working on an integration using the TI Arago distribution.  The SDK is based on Yocto Dunfell 3.1.6 (Feb 2021).  

I'm running into something odd related to libubootenv, and generally some items in this part of the documentation:
https://sbabic.github.io/swupdate/building-with-yocto.html#what-about-libubootenv

Without following any of the instructions listed, SWUpdate builds fine, and I see that libubootenv library is actually in the rootfs on completion.  Same goes for when I add the configuration fragment for my swupdate_%.bbappend.

So my configuration fragment has this (it will eventually have a lot more stuff):
CONFIG_UBOOT=y
CONFIG_UBOOT_NEWAPI=y

What isn't in rootfs is fw_setenv, and fw_printenv.  Both are in the work directory for libubootenv, but they are not being put in rootfs

When I add this line as directed in the docs:
PREFERRED_PROVIDER_u-boot-fw-utils = “libubootenv”

to my recipe or to my swupdate_%.bbappend I get an error running bitbake.

ERROR: ParseError at /home/.../recipes/tisdk-base-image.bbappend:21: unparsed line: 'PREFERRED_PROVIDER_u-boot-fw-utils = “libubootenv”'

Any ideas about why this error might occur?

Digging a little deeper, I explicitly added u-boot-fw-utils to my recipe via:
IMAGE_INSTALL += "u-boot-fw-utils"

That didn't fix the parse error, but now the built versions for fw_printenv and fw_setenv from the libubootenv work directory are being put in rootfs, and they are present on my target.  

What is not present is /etc/fw_env.config, so fw_printenv fails. Trying to figure out if I am supposed to create and install this myself via a bbappend, or I should expect it to be installed.  

Sorry a lot of stuff in here.  

Also PS, I did a grep of CONFIG_UBOOT_NEWAPI in both meta-swupdate and in the swupdate repo and it looks like it is not used anywhere.  Is that symbol no longer needed?

Many thanks
Howard

[Stefano Babic]

Hi Howard,

On 05.01.22 22:56, Howard Egan wrote:
> Hi:
>
> My previous integration of SWUpdate used the GRUB bootloader.  That
> turned out great (Thanks Stefano).
>

You're welcome.

> I'm now working on an integration using the TI Arago distribution.  The
> SDK is based on Yocto Dunfell 3.1.6 (Feb 2021).
>

Ok

> I'm running into something odd related to libubootenv, and generally
> some items in this part of the documentation:
> https://sbabic.github.io/swupdate/building-with-yocto.html#what-about-libubootenv
>

There are still issues when U-Boot is quite old - recent poky contains
changes in U-Boot recipe to add fw-env.config and u-boot-initial-env
(both required).

> Without following any of the instructions listed, SWUpdate builds fine,
> and I see that libubootenv library is actually in the rootfs on
> completion.  Same goes for when I add the configuration fragment for my
> swupdate_%.bbappend.
>
> So my configuration fragment has this (it will eventually have a lot
> more stuff):
> CONFIG_UBOOT=y
> CONFIG_UBOOT_NEWAPI=y
>
> What isn't in rootfs is fw_setenv, and fw_printenv.  Both are in the
> work directory for libubootenv, but they are not being put in rootfs
>
> When I add this line as directed in the docs:
> PREFERRED_PROVIDER_u-boot-fw-utils = “libubootenv”

Since dunfell, u-boot-fw-utils is obsolete and replaced by libubootenv.
however, the binaries (fw_printenv / fw_setenv) are in an additional
package (libubootenv-bin), that you have to add to your image
(IMAGE_INSTALL or whatever you prefer).

>
> to my recipe or to my swupdate_%.bbappend I get an error running bitbake.
>
> ERROR: ParseError at /home/.../recipes/tisdk-base-image.bbappend:21:
> unparsed line: 'PREFERRED_PROVIDER_u-boot-fw-utils = “libubootenv”'

unparsed is like a szntax error, there should be something else.

>
> Any ideas about why this error might occur?

I think you can forget it, and just add "libubootenv" package. While
libubootenv is added automatically by SWUpdate's dependency,
libubootenv-bin must be added explicitly.

>
> Digging a little deeper, I explicitly added u-boot-fw-utils to my recipe
> via:
> IMAGE_INSTALL += "u-boot-fw-utils"
>

I do not know why it fails, it is supposed to be compatible - but you
can use the new package's names.

> That didn't fix the parse error, but now the built versions for
> fw_printenv and fw_setenv from the libubootenv work directory are being
> put in rootfs, and they are present on my target.
>
> What is not present is /etc/fw_env.config, so fw_printenv fails.

It means you have an older U-Boot version - you have to add yourself
fw_env.config and u-boot-initial-env to /etc.

> Trying
> to figure out if I am supposed to create and install this myself via a
> bbappend,

Correct. Or you can check if u-boot-env (as package) can be installed,
this work with later U-Boot versions.

> or I should expect it to be installed.

Yes, with later U-Boot version, files are packaged into u-boot-env and
libubootenv-bin.

>
> Sorry a lot of stuff in here.
>
> Also PS, I did a grep of CONFIG_UBOOT_NEWAPI in both meta-swupdate and
> in the swupdate repo and it looks like it is not used anywhere.  Is that
> symbol no longer needed?

It is obsolete now - SWUpdate does not work anymore with legacy tool
from U-Boot, and it binds only with libubootenv.

Best regards,
Stefano


>
> Many thanks
> Howard
>
>
>
>
>
>
>
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to swupdate+u...@googlegroups.com
> <mailto:swupdate+u...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/swupdate/f3cd4457-f7bb-45b8-9272-a6d325ae11bcn%40googlegroups.com
> <https://groups.google.com/d/msgid/swupdate/f3cd4457-f7bb-45b8-9272-a6d325ae11bcn%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=====================================================================

[Howard Egan]

Great thanks.  

I guess the obvious question I should have asked up front, is are folks successfully integrating SWUpdate into Arago, but it sounds like that's a yes.