Hello Tom,

Am 07.05.2020 um 16:38 schrieb Tom Rini:

On Thu, May 07, 2020 at 02:53:49PM +0200, Heiko Schocher wrote:

...

Hello Fabio,

Am 07.05.2020 um 14:12 schrieb Heiko Schocher:

...

Hello Fabio,

I have my wandboard DL in my automated daily build setup example:

http://xeidos.ddns.net/ubtestresults/

and wondered, why my last result is from may 4th ...

(Ok, there is a bug, that I do not see not booting boards in this page,  but this is just a proof of concept page ...)

Ok, found this error, now I have one broken build in above webpage. Also, the newest commit adds > 300 bytes imge size...

http://xeidos.ddns.net/ubtestresults/stats/wandboard_defconfig/6

That's not what I see: $ (export SOURCE_DATE_EPOCH=`date +%s`; ./tools/buildman/buildman -o /tmp/wandboard3 --step 0 -SBC -b 125956..69bf66 -devl wandboard && ./tools/buildman/buildman -o /tmp/wandboard3 --step 0 -SsB -b 125956..69bf66 -devl wandboard) Building 2 commits for 1 boards (1 thread, 16 jobs per thread) 01: scripts/get_default_envs.sh: preserve order of multiple entries for same variable 15: Merge branch '2020-05-06-master-imports' 2 0 0 /2 wandboard Completed: 2 total built, duration 0:00:23 Summary of 2 commits for 1 boards (1 thread, 16 jobs per thread) 01: scripts/get_default_envs.sh: preserve order of multiple entries for same variable 15: Merge branch '2020-05-06-master-imports' arm: (for 1/1 boards) bss -16.0 text +16.0 wandboard : bss -16 text +16 u-boot: add: 0/0, grow: 3/0 bytes: 12/0 (12) function old new delta menu_create 84 88 +4 handle_pxe_menu 284 288 +4 do_dcache 92 96 +4 (no errors to report) $

What details are you recording in your setup?

I simply track the size of u-boot.img for the wandboard:

https://github.com/EmbLux-Kft/tbot-tbot2go/blob/wandboard-devel-messe/tc/wan...

...

Unfortunately I cannot automate git bisect with tbot:

http://tbot.tools/modules/tc.html#tbot.tc.git.GitRepository.bisect

as I do not know how to switch for example with an gpio and a relay bootmode on wandboard ... do you know, if this is possible?

In general, or on the wandboard? For the general side, I have a network controllable relay controller that I can use to toggle a GPIO on hardware that has a force reset exposed. I don't have any imx platforms exposed however as I wasn't able to rig up some way to boot via USB on the platforms I have here. That was a while ago tho.

Only for the wandboard. I have a collection of usbrelais and simple relais connected to gpios, my preffered setup currently:

https://www.amazon.de/gp/product/B07RNWLXJM/ref=ppx_yo_dt_b_asin_title_o06_s...

attached to a raspberry PI, so I have with the PI a complete "lab host" which runs tbot incl. wifi to connect to the rest of the world ;-)

But it seems wandboard has only sd card boot, so I need for this a sd card simulator... what I do not have yet.

Thanks!

bye, Heiko

Hello Simon,

Am 08.05.2020 um 20:33 schrieb Simon Glass:

Hi Heiko

On Thu, 7 May 2020 at 21:35, Heiko Schocher hs@denx.de wrote:

...

Hello Tom,

Am 07.05.2020 um 16:38 schrieb Tom Rini:

...

On Thu, May 07, 2020 at 02:53:49PM +0200, Heiko Schocher wrote:

...

Hello Fabio,

Am 07.05.2020 um 14:12 schrieb Heiko Schocher:

...

Hello Fabio,

I have my wandboard DL in my automated daily build setup example:

http://xeidos.ddns.net/ubtestresults/

and wondered, why my last result is from may 4th ...

(Ok, there is a bug, that I do not see not booting boards in this page, but this is just a proof of concept page ...)

Ok, found this error, now I have one broken build in above webpage. Also, the newest commit adds > 300 bytes imge size...

http://xeidos.ddns.net/ubtestresults/stats/wandboard_defconfig/6

That's not what I see: $ (export SOURCE_DATE_EPOCH=`date +%s`; ./tools/buildman/buildman -o /tmp/wandboard3 --step 0 -SBC -b 125956..69bf66 -devl wandboard && ./tools/buildman/buildman -o /tmp/wandboard3 --step 0 -SsB -b 125956..69bf66 -devl wandboard) Building 2 commits for 1 boards (1 thread, 16 jobs per thread) 01: scripts/get_default_envs.sh: preserve order of multiple entries for same variable 15: Merge branch '2020-05-06-master-imports' 2 0 0 /2 wandboard Completed: 2 total built, duration 0:00:23 Summary of 2 commits for 1 boards (1 thread, 16 jobs per thread) 01: scripts/get_default_envs.sh: preserve order of multiple entries for same variable 15: Merge branch '2020-05-06-master-imports' arm: (for 1/1 boards) bss -16.0 text +16.0 wandboard : bss -16 text +16 u-boot: add: 0/0, grow: 3/0 bytes: 12/0 (12) function old new delta menu_create 84 88 +4 handle_pxe_menu 284 288 +4 do_dcache 92 96 +4 (no errors to report) $

What details are you recording in your setup?

I simply track the size of u-boot.img for the wandboard:

https://github.com/EmbLux-Kft/tbot-tbot2go/blob/wandboard-devel-messe/tc/wan...

...

...

Unfortunately I cannot automate git bisect with tbot:

http://tbot.tools/modules/tc.html#tbot.tc.git.GitRepository.bisect

as I do not know how to switch for example with an gpio and a relay bootmode on wandboard ... do you know, if this is possible?

In general, or on the wandboard? For the general side, I have a network controllable relay controller that I can use to toggle a GPIO on hardware that has a force reset exposed. I don't have any imx platforms exposed however as I wasn't able to rig up some way to boot via USB on the platforms I have here. That was a while ago tho.

Only for the wandboard. I have a collection of usbrelais and simple relais connected to gpios, my preffered setup currently:

https://www.amazon.de/gp/product/B07RNWLXJM/ref=ppx_yo_dt_b_asin_title_o06_s...

attached to a raspberry PI, so I have with the PI a complete "lab host" which runs tbot incl. wifi to connect to the rest of the world ;-)

But it seems wandboard has only sd card boot, so I need for this a sd card simulator... what I do not have yet.

I have some SDwire units and you can buy them from the designer in Poland.

I am happy to make some more but need to know how many. I made some as a test run at about $40 each.

Marek is also working on such stuff, added Marek and Wolfgang to cc...

bye, Heiko

Hello Fabio,

Am 07.05.2020 um 23:16 schrieb Fabio Estevam:

Hi Heiko,

On Thu, May 7, 2020 at 9:12 AM Heiko Schocher hs@denx.de wrote:

...

Hello Fabio,

I have my wandboard DL in my automated daily build setup example:

http://xeidos.ddns.net/ubtestresults/

and wondered, why my last result is from may 4th ...

(Ok, there is a bug, that I do not see not booting boards in this page, but this is just a proof of concept page ...)

So, what I see is:

│ │ ├─UBOOT (wandboard-uboot) │ │ │ <> Connecting to /dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller_D-if00-port0, speed 115200 │ │ │ <> Escape character: Ctrl-\ (ASCII 28, FS): enabled │ │ │ <> Type the escape character followed by C to get back, │ │ │ <> or followed by ? to see other options. │ │ │ <> ---------------------------------------------------- │ │ │ <> │ │ │ <> U-Boot SPL 2020.07-rc1-tbot-00298-g425fefa9a3 (May 05 2020 - 04:18:47 +0200) │ │ │ <> Trying to boot from MMC1

and no more output ...

Do you have any idea, what is wrong with current mainline?

Thanks for the report.

This boot failure is caused by:

commit 20a154f95bfe0a3b5bfba90bea7f001c58217536 Author: Marek Vasut marex@denx.de Date: Fri May 1 17:40:25 2020 +0200

 mkimage: fit: Do not tail-pad fitImage with external data

 There is no reason to tail-pad fitImage with external data to 4-bytes,
 while fitImage without external data does not have any such padding and
 is often unaligned. DT spec also does not mandate any such padding.

 Moreover, the tail-pad fills the last few bytes with uninitialized data,
 which could lead to a potential information leak.

 $ echo -n xy > /tmp/data ; \
         ./tools/mkimage -E -f auto -d /tmp/data /tmp/fitImage ; \
         hexdump -vC /tmp/fitImage | tail -n 3

 before:
 00000260  61 2d 6f 66 66 73 65 74  00 64 61 74 61 2d 73 69

|a-offset.data-si| 00000270 7a 65 00 00 78 79 64 64 |ze..xydd| ^^ ^^ ^^ after: 00000260 61 2d 6f 66 66 73 65 74 00 64 61 74 61 2d 73 69 |a-offset.data-si| 00000270 7a 65 00 78 79 |ze.xy|

 Signed-off-by: Marek Vasut <marex@denx.de>
 Reviewed-by: Simon Glass <sjg@chromium.org>
 Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>
 Cc: Tom Rini <trini@konsulko.com>

which has been reverted by Tom in commit:

commit 7946a814a31989998120b4b4aa417222ba21b2fa Author: Tom Rini trini@konsulko.com Date: Wed May 6 11:05:17 2020 -0400

 Revert "mkimage: fit: Do not tail-pad fitImage with external data"

 This has been reported to break booting of U-Boot from SPL on a number
 of platforms due to a lack of alignment of the external data.  The
 issues this commit is addressing will need to be resolved another way.

 Re-introduce a data leak in the padding for now.

 This reverts commit 20a154f95bfe0a3b5bfba90bea7f001c58217536.

 Reported-by: Alex Kiernan <alex.kiernan@gmail.com>
 Reported-by: Michael Walle <michael@walle.cc>
 Tested-by: Jan Kiszka <jan.kiszka@siemens.com>
 Signed-off-by: Tom Rini <trini@konsulko.com>

Yep, thanks! Board works again, see:

http://xeidos.ddns.net/ubtestresults/result/60

BTW: since commit c693f212c5b0 size of u-boot.img has increased from 561004 bytes to 562068 bytes for the wandboard

http://xeidos.ddns.net/ubtestresults/stats/wandboard_defconfig/8

bye, Heiko

Hello Fabio,

Am 08.05.2020 um 14:23 schrieb Fabio Estevam:

Hi Heiko,

On Fri, May 8, 2020 at 12:53 AM Heiko Schocher hs@denx.de wrote:

...

BTW: since commit c693f212c5b0 size of u-boot.img has increased from 561004 bytes to 562068 bytes for the wandboard

This commit points to a merge.

Do you have a specific commit that caused the increased size?

Currently not, as I do only trigger once a day a build ...

But yes, it would be nice to do for each commit a build, and get the result for it... one more task on my ToDo list...

bye, Heiko

Hello Tom,

Am 08.05.2020 um 15:09 schrieb Tom Rini:

On Fri, May 08, 2020 at 02:39:22PM +0200, Heiko Schocher wrote:

...

Hello Fabio,

Am 08.05.2020 um 14:23 schrieb Fabio Estevam:

...

Hi Heiko,

On Fri, May 8, 2020 at 12:53 AM Heiko Schocher hs@denx.de wrote:

...

BTW: since commit c693f212c5b0 size of u-boot.img has increased from 561004 bytes to 562068 bytes for the wandboard

This commit points to a merge.

Do you have a specific commit that caused the increased size?

Currently not, as I do only trigger once a day a build ...

But yes, it would be nice to do for each commit a build, and get the result for it... one more task on my ToDo list...

And use buildman and keep the function change information too. So far this cycle the biggest imx6 growth has been related to the DDR calculation changes and everything else has been a few bytes here and there on general bugfixes, etc.

Yes this looks interesting ... but for this I have to add buildman support to tbot... my ToDo list gets longer ...

But of course feel free to send patches to tbot ML [1] ;-)

BTW: just added my beagleboneblack board to my testresults page:

http://xeidos.ddns.net/ubtestresults/result/61

So I have now the wandboard and beagleboneblack up and running, soon hopefully the mpc85xx based socrates board follow, just the board is currently none functional and I have to wait until someone in our lab in munich can take a look at it...

bye, Heiko [1] tbot@lists.denx.de