[PATCH 20/45] sandbox: Add a way to specify the sandbox executable

[Simon Glass]

Hi Heinrich,

On Mon, 26 Sept 2022 at 00:49, Heinrich Schuchardt <xypron.glpk at gmx.de> wrote:
>
> On 9/25/22 17:02, Simon Glass wrote:
> > At present the sandbox executable is assumed to be arg[0] but this only
> > works for a single jump (e.g. from SPL to U-Boot). Add a new arg to solve
> > this issue, along with a detailed comment.
>
> What is the impact on os_relaunch()?
> With current origin/master it fails on SPL:
>
> $ spl/u-boot-spl -S
>
> U-Boot SPL 2022.10-rc5-00012-g435596d57f (Sep 26 2022 - 08:40:30 +0200)
> Creating new bloblist size 400 at c000
> Finished bloblist size 400 at c000
> Finished bloblist size 400 at c000
> Found existing bloblist size 400 at c000
>
>
> U-Boot 2022.10-rc5-00012-g435596d57f (Sep 26 2022 - 08:40:30 +0200)
>
> DRAM:  256 MiB
> Core:  23 devices, 11 uclasses, devicetree: board
> MMC:
> Loading Environment from nowhere... OK
> In:    serial
> Out:   serial
> Err:   serial
> Net:   No ethernet found.
> Hit any key to stop autoboot:  0
> => reset
> resetting ...
> Finished bloblist size 400 at bffd000
> Failed to read RAM buffer '/tmp/u-boot.mem.LypddQ': -1
> Expected bloblist at c000 not found (err=-2)
> Creating new bloblist size 400 at c000
>
>
> U-Boot 2022.10-rc5-00012-g435596d57f (Sep 26 2022 - 08:40:30 +0200)
>
> u-boot: error: failed while parsing option: memory
>          try running with --help for more information.

This does not change the behaviour of os_relaunch(), but I think it
would be possible to use the argument to avoid this failure.

Regards,
Simon