rauc install does not work with barebox and the bootloader spec about rauc

[ejoerns]

Booting with bootspec is definitely the preferred way we use, too, if possible! You will not have to give it up.

Well, you actually have to set the bootchooser boot target as the bootname in order to get this working, not what in root= is.
The bootname enables RAUC to interact with the boot selection logic, the barebox bootchooser in this case. Thus it must know about the names bootchooser and state use, not from which ubi volume we are booting.
Telling where we are booted from will then be done by additional kernel commandline parameters passed by bootchooser.

The Barebox Integration chapter in the documentation tells you a bit more about how to configure bootchooser with RAUC.

[mischelebuha]

Thanks for the help the problem has been solved.

In Germany one would say "I stood on the hose". :-D

I manually started the boot process in all attempts (boot nand0.root.ubi.system0). Therefore, the variable "bootchooser.active=" was not generated. And the resulting "error messages" did not help me either. Maybe the missing variable "bootchooser.active" should be mentioned in the error message.

Is it possible to start the bootchooser manually with a specific target (without changing the priority)?
For example, boot bootchooser -t system0 ?

[ejoerns]

Auf dem Schlauch stehen wir alle mal ;)

Well, the missing variable is sufficient but not necessary. RAUC also accepts bootstate.active= (for compatibility reasons), the generic rauc.slot= an is also able to handle simple root= options matching the 'bootname'. Thus it is not that easy to emit a helpful error messages.

No, manually selecting a boot target without modifying prios is not possible at the moment.

For both points mentioned, patches improving the current situation are always welcome ;)