Oselas 2018.12.0 toolchain seems to break barebox for AM335x

[Andreas Geisenhainer <Andreas.Geisenhainer@atsonline.de>]

Hello barebox mailinglist.

While updating my local ptxdist setup I ran into the following problem.

Updating the toolchain to OSELAS_2018.12.0 and copiling barebox
it decided not to start anymore. To my surprise, compiling the
exact same source with the previous OSELAS toolchain (2018.02.0)
just works.
I installed the toolchains through the official debian repository.

We're still running an older barebox (2015.09), so i grabed a
stock, barebox 2019.06.1 and it produces the exact same behaviour.

We're running barebox an a Phytec PhyCORE AM335x platform, and the
behaviour does emerge for the default "barebox-am335x-phytec-phycore.img"
image from barebox.

* Exhibit A: barebox 2019.06.1 compiled with OSELAS_2018.12.0 (gcc 8.2.1)
----------------------------------8<-------------------------------------
barebox@sbo800:/mnt/10.0.1.6/rootbootm -vv -c barebox_2019.06.1_k1.img

Loading ARM barebox image 'barebox_2019.06.1_k1.img'
using internal devicetree
OS image not yet relocated
Passing control to OMAP barebox handler
exitcall-> devices_shutdown+0x1/0x24
exitcall-> arch_shutdown+0x1/0x1c
---------------------------------->8-------------------------------------

* Exhibit B: barebox 2019.06.1 compiled with OSELAS_2018.02.0 (gcc 7.3.1)
----------------------------------8<-------------------------------------
barebox@sbo800:/mnt/10.0.1.6/rootbootm -vv -c barebox_2019.06.1_k2.img

Loading ARM barebox image 'barebox_2019.06.1_k2.img'
using internal devicetree
OS image not yet relocated
Passing control to OMAP barebox handler
exitcall-> devices_shutdown+0x1/0x24
exitcall-> arch_shutdown+0x1/0x1c
start.c: memory at 0x80000000, size 0x20000000
start.c: found Compressed DTB in boarddata, copying to 0x9fdfd040
start.c: initializing malloc pool at 0x8fefe820 (size 0x0fefe820)
start.c: starting barebox...
----------------------------------<8-------------------------------------

What's the best course of action to debug this further?

There's a slight possibility for a barebox config option to be the culprit,
since i copied our local config into the extracted archive.
But it does not really explain why this breaks.

kind regards
Andreas Geisenhainer

-- 
        _
   __ _| |_ ___
  / _` | __/ __|
| (_| | |_\__ \
  \__,_|\__|___/
Elektronik GmbH


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox