Re: [PATCH v7 5/5] iot2050: Enable watchdog support, but do not auto-start it

Jan Kiszka
2021-09-13T07:57:57Z

On 11.09.21 02:10, Tom Rini wrote:
> On Tue, Aug 03, 2021 at 04:24:05PM +0200, Jan Kiszka wrote:
>
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> This allows to use the watchdog in custom scripts but does not enforce
>> that the OS has to support it as well.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>
> Sorry for the late reply. This causes CI to fail:
> Building current source for 1 boards (1 thread, 16 jobs per thread)
> aarch64: + iot2050
> +(iot2050) WARNING ATF file bl31.bin NOT found, resulting binary is non-functional
> +(iot2050) WARNING OPTEE file bl32.bin NOT found, resulting might be non-functional
> +(iot2050) binman: Filename 'k3-rti-wdt.fw' not found in input path (.,/home/trini/work/u-boot/u-boot,board/siemens/iot2050,arch/arm/dts) (cwd='/tmp/iot2050/.bm-work/iot2050')
> +(iot2050) make[1]: *** [all] Error 1
> +(iot2050) make: *** [sub-make] Error 2
> 0 0 1 /1 iot2050
>
> And needs to be handled like ATF/OPTEE/etc where CI can build but throw
> a "THIS WILL NOT RUN CORRECTLY" type warning to the user.
>

I was about to sent an update anyway - time passed, and now we even have
support for the next generation integrated from the beginning. But
related upstream DT changes are not yet merged.

But back to this issue: How can CI be fed with all those required
binaries? The build makes no sense in their absence.

Jan

--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux