I wanted to update the list with the latest findings from the Sunxi Linux
community regarding the data abort when loading the kernel. Although early
testing implicated recent GCC, more focused testing has identified binutils
2.31 as the culprit and a specific commit causing the u-boot regression.
Apologies! I just realized I had my SD cards mixed up. 2018.05 compiled
with GCC 8.2.0 isn't working either, although I just see a 'resetting'
message rather than the full dump. The 2018.05 installation I saw booting
successfully was compiled using earlier GCC.
On Tue, Aug 21, 2018 at 3:17 PM
I tested another configuration to further isolate the issue:
u-boot 2018.05 / nanopi_neo_defconfig / GCC 8.2.0 + Linux 4.17.14 / GCC
8.2.0 = works
So something introduced between 2018.05 GA and 2018.07 GA associated with
Sunxi H3 configs is rubbing GCC 8.2.0 the wrong way.
On Tue, Aug 21, 2018
Greetings,
As others have reported (
https://lists.denx.de/pipermail/u-boot/2018-July/334126.html), a 'data
abort' occurs when attempting to load the kernel with recent u-boot
compiled with recent GCC on Allwinner (Sunxi) H3 boards. I ran into this
issue when performing a bootstrap of Shedbuilt
CC: ARM SUNXI maintainers
On 08/22/2018 01:31 AM, Heinrich Schuchardt wrote:
> On 08/22/2018 01:05 AM, Auston Stewart wrote:
>> Greetings,
>>
>> As others have reported
>> (https://lists.denx.de/pipermail/u-boot/2018-July/334126.html), a 'data
>> abort' occurs when attempting to load the kernel
On 08/22/2018 01:05 AM, Auston Stewart wrote:
> Greetings,
>
> As others have reported
> (https://lists.denx.de/pipermail/u-boot/2018-July/334126.html), a 'data
> abort' occurs when attempting to load the kernel with recent u-boot
> compiled with recent GCC on Allwinner (Sunxi) H3 boards. I ran
6 matches
Mail list logo
