| Summary: | bitbake exits with error related to libubootenv | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Other YP Layers | Reporter: | michael <eberli> |
| Component: | layers | Assignee: | Stefano babic <sbabic> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Undecided | CC: | joshuagloe, poky.bs.watcher, poky.watcher |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
michael
2017-02-08 16:32:18 UTC
This appears to be meta-swupdate[1] not meta-swupd[2]. We don't formally track meta-swupdate bugs in this issue tracker but as Stefano (the swupdate developer) is a registered user of this bugzilla, let's try assigning the bug to him. 1. https://github.com/sbabic/meta-swupdate/ 2. http://git.yoctoproject.org/cgit/cgit.cgi/meta-swupd Resolving this issue as invalid as meta-swupdate bugs aren't tracked in Yocto Bugzilla. The layer README at https://github.com/sbabic/meta-swupdate/ suggests questions can be sent to swupdate@googlegroups.com Confirmed that this is related to SWUpdate and it has nothing to do with swupd. I report for the history my answer to SWUpdate's ML: This is a known issue that happens with u-boot < 2016.07, when the patch for the library were not yet integrated. Later versions are not affected by this problem. From log it seems you are using krogoth, and u-boot 2016.3 does not support the library. You have to ways: - you could take patches for tools/env from current u-boot (even 2017.01) and add them to your u-boot-fw-utils_%.bbappend - you could update u-boot-fw-utils to a newer version. In both cases, it is very important you set U-Boot's machine to build the library for the *right* machine (a raspi in your case). This guarantees that you do not brick the board if no environment is stored on the board and you run SWUpdate with default environment. Building u-boot-fw-utils with the correct machine lets the default environment to be stored inside the library, and SWUpdate can successful save a new environment even if nothing is stored in the flash. |