[U-Boot] Heads-up: Compilation error with arm-none-eabi-gcc version 7.1
Hi, I just upgraded my Arch Linux system to the latest arm-none-eabi-gcc version which is "7.1.0-1" (from 6.3.1-1). After I did this I ran into two issues. First, u-boot no longer links. I get several linker errors [1]. Secondly, if I build a Linux kernel v4.10 image with this compiler it won't boot. It hangs at "Starting kernel...". Reverting back to v6.3 of gcc fixes both issues. Don't know if this is an issue with gcc or with the gcc package (from community. I did not build it myself) that is built for Arch Linux. [1] fs/built-in.o: In function `read_symbol': /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:129: undefined reference to `pull_bit' fs/built-in.o: In function `decompress_huffman': /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:159: undefined reference to `pull_bits' /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:170: undefined reference to `pull_bits' fs/built-in.o: In function `init_code_tables': /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:208: undefined reference to `cramfs_memset' /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:209: undefined reference to `cramfs_memset' /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:210: undefined reference to `cramfs_memset' fs/built-in.o: In function `decompress_block': /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:360: undefined reference to `pull_bit' /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:361: undefined reference to `pull_bits' fs/built-in.o: In function `decompress_none': /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:115: undefined reference to `pull_bits' fs/built-in.o: In function `decompress_dynamic': /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:230: undefined reference to `pull_bits' /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:231: undefined reference to `pull_bits' /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:232: undefined reference to `pull_bits' fs/built-in.o:/uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:244: more undefined references to `pull_bits' follow fs/built-in.o: In function `decompress_fixed': /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:326: undefined reference to `cramfs_memset' /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:327: undefined reference to `cramfs_memset' /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:328: undefined reference to `cramfs_memset' /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:329: undefined reference to `cramfs_memset' /uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:330: undefined reference to `cramfs_memset' fs/built-in.o:/uboot/u-boot-marvell.git/fs/jffs2/mini_inflate.c:331: more undefined references to `cramfs_memset' follow arm-none-eabi-ld.bfd: BFD (GNU Binutils) 2.28 assertion fail elf32-arm.c:9512 arm-none-eabi-ld.bfd: BFD (GNU Binutils) 2.28 assertion fail elf32-arm.c:9512 arm-none-eabi-ld.bfd: BFD (GNU Binutils) 2.28 assertion fail elf32-arm.c:9512 make: *** [Makefile:1207: u-boot] Error 1 / ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] Marvell Kirkwood Guruplug Server Standard upgrade uboot and standalone app issue
On 05/06/2017 01:18 AM, Chris Packham wrote: Hi On 6/05/2017 3:57 PM, "Kernel Hacker" <mailto:kernel.hack...@gmail.com>> wrote: On 04/25/2017 09:04 PM, Kernel Hacker wrote: I have a Guruplug server standard that I would like to upgrade with a newer version of u-boot. Serial output during boot currently shows the following: [...] Sorry I can't answer your specific questions but if you want to avoid flashing a board take a look at the kwboot tool. I've used it quite successfully on boards with similar Marvell processors test out new images and to unbrick boards. Great, that worked! Thanks! ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] Marvell Kirkwood Guruplug Server Standard upgrade uboot and standalone app issue
On 04/25/2017 09:04 PM, Kernel Hacker wrote: I have a Guruplug server standard that I would like to upgrade with a newer version of u-boot. Serial output during boot currently shows the following: cut U-Boot 2009.11-rc1-00602-g8e6db3d (Dec 24 2009 - 03:11:17) Marvell-Plug2 SoC: Kirkwood 88F6281_A0 [...] I cloned git://git.denx.de/u-boot-marvell.git and built u-boot off master branch: make mrproper make guruplug_config make CROSS_COMPILE=arm-none-eabi- u-boot.kwb No one have any idea? Can someone tell me whether this is the right repo/branch for the guruplug server standard and this uboot should work with it? Also, to do a sanity check I tried to get the standalone hello_world.bin to run in the current u-boot and I am unable to get this to work. I loaded the hellow_world.bin to 0x0c10 (tftp 0x0c10 hello_world.bin" and then I issue "go 0x0c10" and again nothing is printed after the "Starting application at ..." is printed by u-boot. Any ideas what can be wrong? Thanks! ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
[U-Boot] Marvell Kirkwood Guruplug Server Standard upgrade uboot and standalone app issue
I have a Guruplug server standard that I would like to upgrade with a newer version of u-boot. Serial output during boot currently shows the following: cut U-Boot 2009.11-rc1-00602-g8e6db3d (Dec 24 2009 - 03:11:17) Marvell-Plug2 SoC: Kirkwood 88F6281_A0 DRAM: 512 MB NAND: 512 MiB In:serial Out: serial Err: serial Net: egiga0 88E1121 Initialized on egiga0 Hit any key to stop autoboot: 0 Marvell>> cut I cloned git://git.denx.de/u-boot-marvell.git and built u-boot off master branch: make mrproper make guruplug_config make CROSS_COMPILE=arm-none-eabi- u-boot.kwb I wanted to verify that my uboot works properly on my device before committing to flash since I don't have a JTAG available at the moment. However, when I tftp the new u-boot.bin image to the device and issue a "go 0x.." command it never starts (no output after "Starting application at ...". Also, to do a sanity check I tried to get the standalone hello_world.bin to run in the current u-boot and I am unable to get this to work. I loaded the hellow_world.bin to 0x0c10 (tftp 0x0c10 hello_world.bin" and then I issue "go 0x0c10" and again nothing is printed after the "Starting application at ..." is printed by u-boot. So my questions are what am I doing wrong and am I using the right repo, branch, and configuration? Appreciate any pointers. ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
