LTIB FAQs

Document created by jesseg Employee on Aug 8, 2012Last modified by Jodi Paul on Apr 16, 2013
Version 3Show Document
  • View in full screen mode

FAQ

Question:

I receive the following error message when compiling GTK2 using LTIB"

Making all in demos
make[2]: Entering directory `/home/ltib/rpm/BUILD/gtk+-2.14.3/demos'
no --raw --build-list \
        apple_red  ./apple-red.png \
                gnome_foot ./gnome-foot.png \
        > test-inline-pixbufs.h \
|| (rm -f test-inline-pixbufs.h && false)
/bin/sh: no: command not found
make[2]: *** [test-inline-pixbufs.h] Error 1
make[2]: Leaving directory `/home/ltib/rpm/BUILD/gtk+-2.14.3/demos'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/ltib/rpm/BUILD/gtk+-2.14.3'
make: *** [all] Error 2
error: Bad exit status from /home/ltib/tmp/rpm-tmp.69212 (%build)


Answer:

Some packages on your host are missing, install the following packages:

For deb distributions:

sudo apt-get install libgtk2.0-dev

or

For Fedora distributions:

sudo yum install gtk2-devel

IMPORTANT: After install the package above, be sure to remove the installed GTK package on your ltib:

On your LTIB directory:

rm -rf rpm/BUILD/gtk+-2.14.3/

Question:

I receive the following error message when booting through NFS: "Root-NFS: Server returned error -13 while mounting /tftpboot/ltib"

Answer:

Probabilty you remake your rootfs and forgot to restart NFS server. To solve this issue the command: "service nfs restart"


Question:

I am receiving "error: cannot open Name index using db3" when installing LTIB on new Ubuntu 9.10

Answer:

Edit the file "ltib" and modify line 2428 to:

$cf->{rpm}           = "rpm --force-debian";

Question:

I receive the error message "Cannot create lockfile. Sorry." when I try to open minicom.

Answer:

This error message is generated because your user doesn't have permission to create a lock file in /var/lock. Change /var/lock permission:

# chmod 777 /var/lock

 


Question:

I receive the error message "cannot open /dev/ttyS0: Permission denied" when I try to open minicom.

Answer:

This error message is generated because your user doesn't have permission to open /dev/ttyUSB0. Change /dev/ttyUSB0 permission:

# chmod 777 /dev/ttyS0

 


Question:

Compilation of e2fsprogs package or others packages with dependencies like Qtopia using LTIB in Debian derived linux system like Ubuntu makes an error like:

make[1]: Leaving directory `/home/daiane/LTIB/L2.6.24_1.2.1_SDK_042008/rpm/BUILD/e2fsprogs-1.34/tests/progs'
making all in po
make[1]: Entering directory `/home/daiane/LTIB/L2.6.24_1.2.1_SDK_042008/rpm/BUILD/e2fsprogs-1.34/po'
: --update cs.po e2fsprogs.pot
rm -f cs.gmo && : -c --statistics -o cs.gmo cs.po
mv: cannot stat `t-cs.gmo': No such file or directory
make[1]: *** [cs.gmo] Error 1
make[1]: Leaving directory `/home/daiane/LTIB/L2.6.24_1.2.1_SDK_042008/rpm/BUILD/e2fsprogs-1.34/po'
make: *** [all-progs-recursive] Error 1
error: Bad exit status from /home/daiane/LTIB/L2.6.24_1.2.1_SDK_042008/tmp/rpm-tmp.66904 (%build)

Answer:

This error is caused by lack of the new version of package gettext.

Install the gettext. For Ubuntu, the command line is:

sudo apt-get install gettext

But LTIB just recognize the existence of this package if it was installed before the LTIB installation. So, reinstall the LTIB.

 


Question

Compiling LTIB I got this error message:

checking for glib-genmarshal... no
configure: error: Could not find a glib-genmarshal in your PATH
error: Bad exit status from /home/alan/ltib/tmp/rpm-tmp.48168 (%build)

Answer:

This error happen when you don't have glib2.0-dev in your system. To Ubuntu execute:

sudo apt-get install libglib2.0-dev

 


Question:

How to convert an ELF binary to raw ARM binary?


Answer:

arm-none-linux-gnueabi-objcopy -O binary test.elf test.bin

 


Question:

How to inform to kernel to print all message on screen?

Answer:

echo 8 > /proc/sys/kernel/printk

 


Question:

How to disassembly an ARM binary?


Answer:

arm-none-linux-gnueabi-objdump -b binary -m arm -D test.bin

 


Question:

RedBoot returns invalid parameter:

RedBoot> load -r -b 0x100000 zImage
Using default protocol (TFTP)
Can't load 'zImage': invalid parameter

Answer:

Verify if your tftp server is running correctly. If so, then verify if RedBoot network is configured correctly. You can use ping command to verify if communication with computer is working. Insert non-formatted text here

Configure RedBoot to not use script and configure network:

RedBoot> ^C
RedBoot> fc
Run script at boot: false
Use BOOTP for network configuration: true.
Update RedBoot non-volatile configuration - continue (y/n)? y
... Read from 0x07ee0000-0x07eff000 at 0xa1fe0000: .
... Erase from 0xa1fe0000-0xa2000000: .
... Program from 0x07ee0000-0x07f00000 at 0xa1fe0000: .
RedBoot>

Reset the board and then load the image

 


Question:

How can I test GPIO using a very simple test?

Answer:

You can find a very simple test here

Attachments

    Outcomes