EmbLogic » Amit Gemini https://www.emblogic.com/blog Embedded System and ARM Training Tue, 03 Mar 2020 13:00:06 +0000 en-US hourly 1 http://wordpress.org/?v=3.9.1 Facing Problem : CROSS_COMPILE Diet libc https://www.emblogic.com/blog/12/facing-problem-cross_compile-diet-libc/ https://www.emblogic.com/blog/12/facing-problem-cross_compile-diet-libc/#comments Sun, 12 Dec 2010 09:12:16 +0000 http://emblogic.org/blog/?p=305 $make

Error :

In file included from contrib/elftrunc.c:5:
/home/Amit/control-project/daq-module/build-tools/dietlibc-0.21/include/stdio.h:18: warning: ‘malloc’ attribute ignored
contrib/elftrunc.c: In function ‘main’:
contrib/elftrunc.c:141: warning: implicit declaration of function ‘memcmp’
contrib/elftrunc.c:145: warning: implicit declaration of function ‘strncpy’
contrib/elftrunc.c:145: warning: incompatible implicit declaration of built-in function ‘strncpy’

]]> https://www.emblogic.com/blog/12/facing-problem-cross_compile-diet-libc/feed/ 0 Facing Problem : CROSS_COMPILE uclibc https://www.emblogic.com/blog/12/facing-problem-cross_compile-uclibc/ https://www.emblogic.com/blog/12/facing-problem-cross_compile-uclibc/#comments Sat, 11 Dec 2010 08:49:57 +0000 http://emblogic.org/blog/?p=298 Continue reading →]]> $ make CROSS_COMPILE=arm-uclibc-

Error : Help me out

ld: ldso.o: Relocations in generic ELF (EM: 40)
ld: ldso.o: Relocations in generic ELF (EM: 40)
ldso.o: could not read symbols: File in wrong format
make[2]: *** [lib] Error 1
make[2]: Leaving directory `/home/Amit/control-project/daq-module/build-tools/uClibc-0.9.16/ldso/ldso’
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/Amit/control-project/daq-module/build-tools/uClibc-0.9.16/ldso’
make: *** [_dir_ldso] Error 2

]]> https://www.emblogic.com/blog/12/facing-problem-cross_compile-uclibc/feed/ 0 Building A Cross Compilation Toolchain for ARM from Linux i386 platform https://www.emblogic.com/blog/12/building-a-cross-compilation-toolchain-for-arm-from-linux-i386-platform/ https://www.emblogic.com/blog/12/building-a-cross-compilation-toolchain-for-arm-from-linux-i386-platform/#comments Wed, 08 Dec 2010 11:10:52 +0000 http://emblogic.org/blog/?p=265 Continue reading →]]> The toolchains were build from the following sources:

- binutils-2.11.2.tar.gz
- gcc-2.95.3.tar.gz
- gcc-2.95.3.diff.bz2 (a re-diffed version of Phil Blundell’s diff)
- glibc-2.2.3.tar.gz
- glibc-linuxthreads-2.2.3.tar.gz
- linux-2.4.6.tar.gz
- patch-2.4.6-rmk2.gz
- diff-2.4.6-rmk2-np1.gz

Sources :

linux-2.4.6.tar.gz

http://www.kernel.org/pub/linux/kernel/v2.4/

patch-2.4.6-rmk2.gz

http://ftp.linux.org.uk/pub/linux/arm/kernel/v2.4/

diff-2.4.6-rmk2-np1.gz
ftp://ftp.arm.linux.org.uk/pub/armlinux/people/nico/v2.4/

gcc-2.95.3.diff.bz2

http://ftp.arm.linux.org.uk/pub/armlinux/toolchain/src-2.95.3/

binutils-2.11.2.tar.gz

http://ftp.gnu.org/gnu/binutils/

gcc-2.95.3.tar.gz

http://ftp.gnu.org/gnu/gcc/

glibc-2.2.3.tar.gz
glibc-linuxthreads-2.2.3.tar.gz

http://ftp.gnu.org/gnu/glibc/?

]]> https://www.emblogic.com/blog/12/building-a-cross-compilation-toolchain-for-arm-from-linux-i386-platform/feed/ 0 gcc 2.95.3 building problem https://www.emblogic.com/blog/12/gcc-2-95-3-building-problem/ https://www.emblogic.com/blog/12/gcc-2-95-3-building-problem/#comments Wed, 01 Dec 2010 15:57:43 +0000 http://emblogic.org/blog/?p=257 decl.c: In function 'start_struct':
decl.c:4451: error: argument 'code' doesn't match prototype
ch-tree.h:736: error: prototype declaration
make[2]: *** [decl.o] Error 1
make[2]: Leaving directory `/home/cihan/gcc-2.95.3/gcc/ch'
make[1]: *** [cc1chill] Error 2
make[1]: Leaving directory `/home/cihan/gcc-2.95.3/gcc'
make: *** [all-gcc] Error 2

]]> https://www.emblogic.com/blog/12/gcc-2-95-3-building-problem/feed/ 1 The seq_file interface https://www.emblogic.com/blog/11/the-seq_file-interface/ https://www.emblogic.com/blog/11/the-seq_file-interface/#comments Mon, 08 Nov 2010 14:13:59 +0000 http://emblogic.org/blog/?p=246 why the implementation of large files under /proc is a little awkward ?

what is benefits of using seq_file interface over /pro file systems ?

]]> https://www.emblogic.com/blog/11/the-seq_file-interface/feed/ 0 Facing Problem in Write() https://www.emblogic.com/blog/09/facing-problem-in-write/ https://www.emblogic.com/blog/09/facing-problem-in-write/#comments Tue, 28 Sep 2010 10:26:13 +0000 http://emblogic.org/blog/?p=175 Continue reading →]]> I’m trying to update the struct file -> f_pos with count number of bytes in my write function,

but everytime i call write(), it will display the value of f_pos = 0.

and i call 5 times write() in my user application at a time.

I am not able to update the f_pos value………..

]]> https://www.emblogic.com/blog/09/facing-problem-in-write/feed/ 1 Device Driver : Initial Stage https://www.emblogic.com/blog/09/device-driver-initial-stage/ https://www.emblogic.com/blog/09/device-driver-initial-stage/#comments Tue, 21 Sep 2010 08:54:40 +0000 http://emblogic.org/blog/?p=113 Continue reading →]]> We just used two command “insmod” and “rmmod” to insert and remove the module from the Kernel.

And We also make some Pseudo programs for 2.4 and 2.6 compatible kernels.

What is the benefit of making some program using 2.6 version over 2.4 version and Vice Versa ?

And why we have to study 2.4v program while 2.6v program are more efficient in terms of memory management ???

]]> https://www.emblogic.com/blog/09/device-driver-initial-stage/feed/ 6 Atten : Device Driver https://www.emblogic.com/blog/09/atten-device-driver/ https://www.emblogic.com/blog/09/atten-device-driver/#comments Wed, 15 Sep 2010 06:07:04 +0000 http://emblogic.org/blog/?p=110 Classes of Device Driver will be start on Thursday onwards,

so be there at right time and be regular ….

]]> https://www.emblogic.com/blog/09/atten-device-driver/feed/ 0 Signals https://www.emblogic.com/blog/08/signals/ https://www.emblogic.com/blog/08/signals/#comments Tue, 03 Aug 2010 16:04:24 +0000 http://emblogic.org/blog/?p=57 Continue reading →]]> Signal handlers usually execute on the current stack of the process. This lets the signal handler return to the point that execution was interrupted in the process. This can be changed on a per-signal basis so that a signal handler executes on a special stack. If a process must resume in a different context than the interrupted one, it must restore the previous context itself.

What it means ?????

]]> https://www.emblogic.com/blog/08/signals/feed/ 0