[U-Boot] u-boot compile error: Source object has EABI version 5, but target has EABI version 0
When I try to compile u-boot I get the following error: The error is explained in this link: http://www.denx.de/wiki/DULG/SourceObjectHasEABIVersion4ButTargetHasEABIVersion0 It works for another toolchain. However, I want to learn that if there is a way to compile it with the current toolchain as explained in the link above. abdullah___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] u-boot - timestamp
I have a custom board which uses u-boot-1.3.3. I want to add timestamp information during booting. Do I have to use a patch for this? abdullah___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] u-boot - timestamp
Sorry for the missing detail. I want to measure how long a specific process takes. For example, [3814526.197336] message-1 [3814527.234145] message-2 abdullah On Monday, February 10, 2014 2:08 PM, Albert ARIBAUD wrote: Hi Abdullah, > >On Mon, 10 Feb 2014 03:25:51 -0800 (PST), Abdullah YILDIZ > wrote: > >> I have a custom board which uses u-boot-1.3.3. I want to add timestamp >> information during booting. Do I have to use a patch for this? > >Note sure what exactly you mean by "timestamp information", but AFAIR, >each build of U-Boot includes the build date and time. > > >> abdullah > >Amicalement, >-- >Albert. > >___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] show_boot_progress
I use u-boot version 1.3.3. The function call __show_boot_progress is
defined in common/main.c as
void inline __show_boot_progress (int val) {}
There are many calls to this function in particular locations with
specific parameters. But it does nothing. What is the purpose of this?
Since I'm not a very good programmer, I also wonder the meaning of
void inline show_boot_progress (int val) __attribute__((weak,
alias("__show_boot_progress")));
Is it a directive to the compiler?
abdullah
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] show_boot_progress
Hi Albert, > On Wed, Feb 19, 2014 at 12:32 PM, Albert ARIBAUD > wrote: > > Hi Abdullah, > > > I use u-boot version 1.3.3. > > Any reason to use a five-years-old release? > The development board I use supports u-boot version 1.3.3 and I couldn't manage to port the functions to newer releases of u-boot. abdullah ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] show_boot_progress
Hi Albert, > > What board is that? > The board is DevKit3250 from Embest. Actually, there is limited support of the board in the latest version of u-boot. There is no NAND or ethernet support, for example. abdullah On Wed, Feb 19, 2014 at 4:16 PM, Albert ARIBAUD wrote: > Hi Abdullah, > > On Wed, 19 Feb 2014 15:14:42 +0200, Abdullah YILDIZ > wrote: > >> Hi Albert, >> >> > On Wed, Feb 19, 2014 at 12:32 PM, Albert ARIBAUD >> > wrote: >> > >> > Hi Abdullah, >> > >> > > I use u-boot version 1.3.3. >> > >> > Any reason to use a five-years-old release? >> > >> >> The development board I use supports u-boot version 1.3.3 and I >> couldn't manage to port the functions to newer releases of u-boot. > > What board is that? > >> abdullah > > Amicalement, > -- > Albert. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Loading uImage into RAM
I'm trying to understand how u-boot loads zImage into RAM. mkimage is called as mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008040 -d arch/arm/boot/zImage /bootImage/uImage Here, 'a' stands for load address and 'e' stands for entry point (64 bytes are used for wrapping?). However, when loading uImage from u-boot, boot operation starts at address 0x8010. Furthermore, u-boot recognizes the load address and entry point as 0x80008000. Loading from NAND 128MiB 3,3V 8-bit, offset 0x1c Image Name: Linux-2.6.27.8 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1735148 Bytes = 1.7 MB Load Address: 80008000 Entry Point: 80008000 ## Booting kernel from Legacy Image at 8010 ... Image Name: Linux-2.6.27.8 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1735148 Bytes = 1.7 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Could you help me with this? abdullah ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Loading uImage into RAM
Hi Belisko, On Tue, May 6, 2014 at 12:34 PM, Belisko Marek wrote: > Hi Abdullah, > > On Tue, May 6, 2014 at 10:55 AM, Abdullah YILDIZ > wrote: >> I'm trying to understand how u-boot loads zImage into RAM. >> >> mkimage is called as >> >> mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008040 >> -d arch/arm/boot/zImage /bootImage/uImage >> Why is entry point different from load address of uImage? >> Here, 'a' stands for load address and 'e' stands for entry point (64 >> bytes are used for wrapping?). However, when loading uImage from >> u-boot, boot operation starts at address 0x8010. Furthermore, >> u-boot recognizes the load address and entry point as 0x80008000. > Kernel uImage is loaded from NAND to ram at address which $loadaddr > points to (check print $loadaddr) > or env command which loading kerenl image from NAND. > Then by bootm command is copied to address which is specified in > mkimage (e.g. 0x80008000). Hope this helps. Kind regards. abdullah ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
