Hi Patrice, Hi Simon, Patrice CHOTARD wrote, > Hi Waldemar > > On 9/20/22 01:12, Waldemar Brodkorb wrote: > > Hi Simon, > > Simon Glass wrote, > > > >> Hi Waldemar, > >> > >> On Mon, 19 Sept 2022 at 13:48, Waldemar Brodkorb <w...@openadk.org> wrote: > >>> > >>> Hi again, > >>> > >>> Waldemar Brodkorb wrote, > >>> > >>>> Hi, > >>>> > >>>> I am trying to run u-boot on a STM32F746G-DISCO device. > >>>> I am configuring u-boot with stm32f746-disco_spl_defconfig. > >>>> > >>>> But nothing happens on the LCD nor on the serial console. > >>>> I use screen /dev/ttyACM0 115200 under Linux to connect. > >>> > >>> It seems my USB port on my laptop was buggy, after reboot I get > >>> following output via serial console: > >>> > >>> U-Boot SPL 2022.07 (Sep 19 2022 - 13:20:08 +0200) > >>> Trying to boot from XIP > >>> > >>> > >>> U-Boot 2022.07 (Sep 19 2022 - 13:20:08 +0200) > >>> > >>> Model: STMicroelectronics STM32F746-DISCO board > >>> DRAM: 8 MiB > >>> Hard fault > >>> pc : 080087d6 lr : c05aa775 xPSR : a1000000 > >>> r12 : 00000010 r3 : 080087c1 r2 : 0805344d > >>> r1 : 08008001 r0 : c05aa000 > >>> Resetting CPU ... > >>> > >>> resetting ... > >>> > >>> I get a Hard fault. I then tried an older version of u-boot using > >>> the information from https://github.com/fdu/STM32F746G-disco_Buildroot > >>> as a hint. With U-Boot 2018.11 I get a working binary (I had to > >>> disable Falcon mode): > >>> > >>> U-Boot SPL 2018.11 (Sep 19 2022 - 13:41:50 +0200) > >>> Trying to boot from XIP > >>> > >>> > >>> U-Boot 2018.11 (Sep 19 2022 - 13:41:50 +0200) > >>> > >>> Model: STMicroelectronics STM32F746-DISCO board > >>> DRAM: 8 MiB > >>> Flash: 1 MiB > >>> MMC: sdio@40012c00: 0 > >>> In: serial > >>> Out: serial > >>> Err: serial > >>> usr button is at LOW LEVEL > >>> Net: > >>> Warning: ethernet@40028000 (eth0) using random MAC address - > >>> fe:f8:94:5f:5e:26 > >>> eth0: ethernet@40028000 > >>> Hit SPACE in 3 seconds to stop autoboot. > >>> Wrong Image Format for bootm command > >>> ERROR: can't get kernel image! > >>> U-Boot > > >>> > >>> Seems like a regression to me. > >> > >> Yes, can you use git bisect to find it? > > > > cd82f199852d88218e1f17f5ec07cdd9112a89c4 is the first bad commit. > > I remember i encountered an issue with patch in the past and by updating my > toolchain > everything goes fine. > > Which toolchain version do you use ?
I used arm-gnu-toolchain-11.3.rel1-x86_64-arm-none-eabi.tar.xz from ARM. https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads > On my side i am using this one : > https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/11.1.0/x86_64-gcc-11.1.0-nolibc-arm-linux-gnueabi.tar.xz Well it really seems to be an toolchain issue, with this one I can compile U-Boot master and it runs on the system without failure. best regards Waldemar
