On Fri, Oct 9, 2015 at 5:24 PM, Kursad Oney <[email protected]> wrote: >> From: Otavio Salvador [mailto:[email protected]] >> On Thu, Oct 8, 2015 at 5:26 PM, Kursad Oney <[email protected]> >> wrote: >> > I ran into an issue with the 1.8 fido toolchain I installed using >> > populate_sdk task. I noticed this issue with both warpboard and the >> > mx6slevk. >> > >> > I used the fido branch to create an SDK and used the following command >> > to populate a toolchain: >> > >> > bitbake core-image-base -c populate_sdk >> > >> > When I compile u-boot with this toolchain, nothing appears on the >> > console when it is run out of eMMC. However, if I use the >> > imx_usb_loader tool to download the u-boot image to memory, it runs just >> > fine. >> > >> > I then installed the pre-built 1.6, 1.7, and 1.8 toolchains and to my >> > surprise the u-boot image I built had no issues. >> > >> > Comparing the pre-built 1.8 toolchain and the one populated by >> > populate_sdk, I noticed this in each one's environment setup scripts: >> > >> > pre-built: >> > export CC="arm-poky-linux-gnueabi-gcc [...] >> > -mfloat-abi=softfp [...] >> > populate_sdk: >> > export CC=="arm-poky-linux-gnueabi-gcc [...] >> > -mthumb-interwork -mfloat-abi=hard [...] >> >> Could you please try, before building the U-Boot, todo: >> >> unset CFLAGS >> unset LDFLAGS >> >> and rebuild? >> > I actually ran make with: > > make LDFLAGS="" CC="${CC}" > > due to libgcc path not being resolved. I even tried the USE_PRIVATE_LIBGCC > option but u-boot still wouldn't come up.
What U-Boot version? -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 -- _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
