Open-Embedded Study Yard

03/05/2012

Display Current System IP Address

arguments << "-c" << "ifconfig wlan0 | grep 'inet ' | awk '{print $2}' | sed 's/addr://'";
// or arguments << "-c" << "ifconfig eth1 | grep 'inet ' | awk '{print $2}' | sed 's/addr://'";
QProcess* process = new QProcess(this);
process->start(prog , arguments);
process->waitForFinished();
QString tmp = process->readAll();
//qDebug() << tmp;
ui->label_ip->setText(tmp);

20/04/2012

Black screen after running an application

I put my application in /etc/rc5.d/S99rmnologin to let it automatically start.
The application is running well. But the screen turns black after 1 minute. When I touched the screen, a small area, where my finger pointed, of my application GUI show up. My application GUI gradually appears if I continuously moving my finger on the screen. It looks like using a mop to wipe the screen.

Solution:

Take a look in /etc/rcS.d/S01psplash file. At the end of line, there is a "sleep 120 ..." command which caused the problem. After comment out this line, everything goes fine.

# Timetrap against hanging with splash hiding console messages.
(sleep 120; psplash-write "QUIT") &

13/04/2012

Change Gumstix Overo Booting Screen (Logo image)

By default, overo boots up with its own image with progress bar. I want to display my own picture when it boots up.

I follow the below website, but it is for Angstrom. I did some modification to suit my overo COM.

https://support.bluetechnix.at/wiki/Changing_the_splash_screen_picture

1) bitbake psplash

$ cd /build/czhang/overo-oe

$ source build/profile

$ bitbake psplash

...

2) copy make-image-header.sh file to proper place.

$ cp /build/czhang/overo-oe/tmp/work/armv7a-angstrom-linux-gnueabi/psplash-angstrom-0.0+svnr422-r33/psplash/make-image-header.sh /build/czhang/overo-oe/org.openembedded.dev/recipes/psplash/files/overo

3) create your own image file, make sure it is in right dimensions.

$ cd /build/czhang/overo-oe/org.openembedded.dev/recipes/psplash/files/overo

$ ./make-image-header.sh [your-image].png HAND

back up original image head file:

$ mv psplash-hand-img.h psplash-hand-img.h_orig

$ mv [your-imge]-img.h psplash-hand-img.h

$ cd /build/czhang/overo-oe

$ source build/profile

$ bitbake psplash

Error occurred:

| psplash.c: In function 'main':

| psplash.c:271: error: 'POKY_IMG_WIDTH' undeclared (first use in this function)

| psplash.c:271: error: (Each undeclared identifier is reported only once

| psplash.c:271: error: for each function it appears in.)

| psplash.c:272: error: 'POKY_IMG_HEIGHT' undeclared (first use in this function)

| psplash.c:275: error: 'POKY_IMG_BYTES_PER_PIXEL' undeclared (first use in this function)

| psplash.c:276: error: 'POKY_IMG_RLE_PIXEL_DATA' undeclared (first use in this function)

| make[1]: *** [psplash.o] Error 1

| make[1]: *** Waiting for unfinished jobs....

| mv -f .deps/psplash-write.Tpo .deps/psplash-write.Po

| mv -f .deps/psplash-console.Tpo .deps/psplash-console.Po

| mv -f .deps/psplash-fb.Tpo .deps/psplash-fb.Po

| make[1]: Leaving directory `/build/czhang/overo-oe/tmp/work/armv7a-angstrom-linux-gnueabi/psplash-0.0+svnr422-r33/psplash'

| make: *** [all] Error 2

| FATAL: oe_runmake failed

it took me a long time to figure it out. In

/build/czhang/overo-oe/tmp/work/armv7a-angstrom-linux-gnueabi/psplash-0.0+svnr422-r33/psplash

there are three files:
psplash-hand-img.h
psplash-poky-img.h
psplash-bar-img.h

take a look psplash-poky-img.h content where the error occurred:

$ less psplash-poky-img.h

/* GdkPixbuf RGB C-Source image dump 1-byte-run-length-encoded */

#define HAND_IMG_ROWSTRIDE (816)

#define HAND_IMG_WIDTH (272)

#define HAND_IMG_HEIGHT (363)

#define HAND_IMG_BYTES_PER_PIXEL (3) /* 3:RGB, 4:RGBA */

#define HAND_IMG_RLE_PIXEL_DATA ((uint8*) \

After I replaced the HAND with POKY, and bitbake again, error disappeared.

4) bitbake console image

$ bitbake omap3-console-image

5) remember to install psplash_0.0+svnr422-r33.6_armv7a.ipk (maybe psplash-support_0.0+svnr422-r33.6_armv7a.ipk too), this is a software which can load booting image.

Done! you will see the pretty image in the booting procedure.

Modify booting scrip for Gumstix Overo Tide COM

The Tide COM has no NAND built in. When I try to change environment parameter, such as rotate screen or change default display, it just won't work.

The solution is to create a boot command file, e.g. ubootenvcmd, and add it into a boot.scr.

Here is how I do it:

1) create a ubootenvcmd file by using gedit. The content is something like:

setenv ethaddr 00:00:00:FF:FF:FF

setenv mpurate 720

setenv vram 4M

setenv linuxmem 176M

setenv defaultdisplay lcd43

setenv dvimode 480x272MR-16@60

setenv mmcargs ${mmcargs} omapfb.rotate=1

setenv bootcmd 'mmc init; run loaduimage; run mmcboot'

boot

2) install mkimage:
$ sudo apt-get install uboot-mkimage

3) create boot.scr file:
$ mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "Overo boot script" -d ubootenvcmd boot.scr

ps. remember to put the ubootenvcmd file in current directory.

4) copy boot.scr to your FAT partition of your SD card.

Done :)

10/04/2012

Cross compile for i386 on 86_64 system

Down load qt-everywhere-opensource-src-4.7.0

"configure -help" will tell you how to do the cross compile for different OS.

1) tell machine to compile program to 32bit OS
$ ./configure -platform linux-g++-32

Error:
/usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory
make: *** [project.o] Error 1

Solution:
$ sudo apt-get install libc6-dev-i386

Error:
/usr/bin/ld: cannot find -lstdc++
collect2: ld returned 1 exit status

Solution:
$ sudo apt-get install g++-multilib

2) make all libraries
$ make

3) create a "projects" folder under "qt-everywhere-opensource-src-4.7.0". put your project folder, i.e. m4works, in "projects". and also copy relative folders, qextserialport, qwt-5.2.1, into "projects".

4) compile project relative libraries first to get 32bit libraries.
$ qmake qextserialport.pro
$ make
...

5) modify project .pro file to point libraries in right directory.

6) compile project.
$ qmake m4.pro
$ make

23/03/2012

Rotate Screen in Ubuntu

The screen rotation function in Nvidia graphics driver is normally disabled. But We can enable it by modifying xorg.conf file.

To do this, we need to back up xorg.conf file first.

$ sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf.bak

Now edit the file:

$ sudo gedit /etc/X11/xorg.conf

In the Device section that includes the line:

Driver "nvidia"

Add:
Option "RandRRotation" "on"

It will looks like:

Section "Device"
    Identifier            "Device0"
    Driver        "nvidia"
    VendorName     "NVIDIA Corporation"
    Option                "RandRRotation" "on"
EndSection

Then, we need to log out and log back in to restart X server.

To rotate screen to left, use:

$ xrandr -o left

To rotate screen to right, use:

$ xrandr -o right

To flip screen upside down, use:

$ xrandr -o inverted

To go back to normal, use:

$ xrandr -o normal

10/01/2012

还有几天就能看到妞妞了，很是期待。。。 :)

07/12/2011

Rotate Gumstix Overo Touch screen

Go to u-boot environment settings,

Overo # setenv mmcargs setenv bootargs console=${console} mpurate=${mpurate} vram=${vram} omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay} omabfp.rotate=1 root=${mmcroot} rootfstype=${mmcrootfstype}

Overo # saveenv

Overo # reset

ps: 1 --- 90° 2 --- 180° 3 --- 270°

------------------------------
Several month later when I tried to rotate my another gumstix fire + LG4.3" screen, it doesn't work!

finally, I found at this time, the default dvimode was 1024x768. I have to change it back to 4.3" screen resolution, which is 480x272.

#dvimode=480x272MR-16@60

03/11/2011

Gumstix Overo Fire Wifi setup

1. Take a look available wireless signal:

root@overo:~# iwconfig wlan0 essid any

root@overo:~# ifconfig wlan0 up

root@overo:~# iwlist wlan0 scan

2. Edit /etc/network/interfaces to include a section which looks like:

a) Unencypted wifi

Some default builds do not enable any Wifi. You may need to edit /etc/network/interfaces to include a section which looks like:

allow-hotplug wlan0                                                             
auto wlan0                                                                      
iface wlan0 inet dhcp                                                           
        pre-up /sbin/iwconfig wlan0 essid any                                   
        wireless_mode managed

The problem is this setup is not reliable! we're waiting for a solution.

b) WEP encryption

Edit /etc/network/interfaces to have only for wlan0 (don't touch the other entries):

iwconfig wlan0 essid "My Wireless Network"
iwconfig wlan0 key my-hex-key
ifdown wlan0
ifup wlan0

c) WPA encryption

Edit /etc/network/interfaces to have only for wlan0 (don't touch the other entries):

allow-hotplug wlan0
iface wlan0 inet dhcp
      pre-up wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B
      down killall wpa_supplicant

There is an error in the current /etc/network/interfaces as of 2011-09-25. The pre-up line reads:

pre-up wpa_supplicant -Dmarvell -iwlan0 -c/etc/wpa_supplicant.conf -Bw

The "-Bw" causes a usage message to be dumpted to the screen. Make sure it is just "-B". The -Dmarvell option will yield the message "Unsupported driver 'marvell'. Change it to "-Dwext" as shown above.
My /etc/network/interfaces came this way from the factory, and was also that way in my build from the latest git.

Create /etc/wpa_supplicant.conf containing:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1

network={
      ssid="add-your-ascii-ssid"
      proto=WPA2                 # try WPA RSN if you WPA2 fails
      key_mgmt=WPA-PSK
      pairwise=CCMP TKIP
      group=CCMP TKIP
      scan_ssid=1
      psk="add-your-ascii-passphrase"
      priority=10
}

3. Connect to network

To connect to the wireless network when the configuration is done, do the following:

Take down the wireless network (it might already be down, but try to be sure):

# ifdown wlan0

Then, bring it up again:

# ifup wlan0

4. Power management:

Many users have reported issues with wifi data throughput being limited to about 100kB/second. It is theorized this is due to lack of SDIO IRQ support in the OMAP3 MMC driver. A patch is being investigated which reportedly achieves 13Mbps.
Additionally, the driver does not support power management at present. The use of iwconfig power commands such as the following will fail:

iwconfig wlan0 power on

Therefore, the wifi module always consumes close to 1 Watt of power when turned on.

28/10/2011

How to Perform a Windows XP Repair Install

It is extremely important that you backup important data that is not available from other media sources. This backup should be located on a separate hard drive, CD, DVD, network storage, etc. that will not be affected by the repair install.
Please check out the warning links before attempting the Repair Install. It is to your advantage you follow the suggestions to prevent data loss and especially if you also have the capability to boot into XP, perform the steps listed in the Warning #1 , before proceeding with the repair install.
After completing [if Windows is still accessible] the steps listed to prevent data loss in warning #1 and you did not remedy the no boot situation, you can use an OEM XP Pro or Home, "retail" XP Home or Pro full or upgrade version CD of the same version Home or Pro to perform a Repair Install. OEM Restore disks or hidden restore folders on the hard drive will not work for the Repair Install. A Repair Install will replace the system files with the files on the XP CD used for the Repair Install. It will leave your applications and settings intact, but Windows updates will need to be reapplied.
A Repair Install will replace files altered by adware and malware, but will not fix an adware, malware problem.
You can use the In place upgrade option to change a Product Key in the event you entered a key that was already activated. The In Place Upgrade also produces the same result as the Repair Install.
Alternate options to Change XP Product Key #18 on the FAQ list.
Setup cannot continue because the version of Windows on your computer is newer than the version on the CD.
If you get a "Setup cannot continue because the version of Windows on your computer is newer than the version on the CD." message, if you continue, you will need to apply the SP 2 updates after the repair install completes, plus you will need to take the following steps to keep your system from being immediately infected with a virus.
1. If you connect directly to the internet without a router or hardware firewall, disconnect from the internet by physically removing the connections cable, removing a wireless card, or any other means of internet connection.
2. After the Repair install is completed, enable the XP firewall or install third party firewall software or router before connecting to the internet.
If you get the "Setup cannot continue because the version of Windows on your computer is newer than the version on the CD.". You should create a slipstreamed copy of your XP CD by using the software and step by steps supplied in the links below.
Slipstream XP
Automatic Updates
If you cannot download Automatic updates after the Repair install , follow the steps in the link below submitted by MS-MVP's Richard Harper and Ron Martell.
Automatic Updates stops working after a repair install of Windows XP

XP Repair install Please read carefully and make sure you followed the warning links before initiating the Repair Install. You can print a text version for reference. repair.txt

Boot the computer using the XP CD. You may need to change the boot order in the system BIOS so the CD boots before the hard drive. Check your system documentation for steps to access the BIOS and change the boot order.
When you see the "Welcome To Setup" screen, you will see the options below This portion of the Setup program prepares Microsoft
   Windows XP to run on your computer:

   To setup Windows XP now, press ENTER.

   To repair a Windows XP installation using Recovery Console, press R.

   To quit Setup without installing Windows XP, press F3.
Press Enter to start the Windows Setup.

do not choose "To repair a Windows XP installation using the Recovery Console, press R", (you Do Not want to load Recovery Console). I repeat, do not choose "To repair a Windows XP installation using the Recovery Console, press R".
Accept the License Agreement and Windows will search for existing Windows installations.
Select the XP installation you want to repair from the list and press R to start the repair. If Repair is not one of the options, END setup. After the reboot read Warning#2!
Setup will copy the necessary files to the hard drive and reboot. Do not press any key to boot from CD when the message appears. Setup will continue as if it were doing a clean install, but your applications and settings will remain intact. If you get files not found during the copying stage.
Blaster worm warning: Do not immediately activate over the internet when asked, enable the XP firewall before connecting to the internet. You can activate after the firewall is enabled. Control Panel - Network Connections. Right click the connection you use, Properties and there is a check box on the Advanced page.
KB 833330u Blaster removal
What You Should Know About the Sasser Worm and Its Variants
Microsoft Security Bulletin MS04-011
Reapply updates or service packs applied since initial Windows XP installation. Please note that a Repair Install using an Original pre service pack 1 or 2 XP CD used as the install media will remove SP1/SP2 respectively and service packs plus updates issued after the service packs will need to be reapplied. Windows XP Service Pack 1
Service Pack 2

An option I highly recommend; is creating a Slipstreamed XP CD with SP1, SP2, etc. .
Slipstreaming Windows XP with Service Pack 2 (SP2) Good
Another Slipstream step by step Better
AutoStreamer mirror link for AutoStreamer Best!!
Step by Step on AutoStreamer
Printable Repair Install step by step. repair.txt
XP Repair Install in PDF XPrepairinstall

Warning! #1

Should you do a repair install and is it the best choice?

A Repair Install is not foolproof and should not be considered the cure-all fix for non-boot situations. The below procedure applies only if you can still boot into Windows.
To prevent loss of data and/or program settings, perform the following before the Repair Install.
Manually delete the Undo_guimode.txt file from the Windows\System32 folder before you perform any of the actions that are listed in the "Symptoms" section of this article. To do this in Windows XP, type the following command at a command prompt:
del /a /f %windir%\system32\undo_guimode.txt

From the Start menu, click Run. See screen shot Image
In the Run dialog box, in the Open text box, type: cmd. Click OK.
Delete the undo_guimode.txt file. In the C:\Windows\System32\cmd.exe dialog box, type: del /a /f c:\windows\system32\undo_guimode.txt. Press the ENTER key. See screenshot Image

KB Q312369
Check the link below for an option for recovering from a non-boot event. Windows XP Crashed? Here's Help
A salvage mission into the depths of Windows XP, explained by a non-geek
by Charlie White

Also as a precaution the windows\system32\WPA.DBL and WPA.BAK should be copied to a floppy before doing a repair install. For more information see Alex Nichol's article on XP activation.

Additional tips to perform before initiating the Repair Install.
You should complete the basic requirements of backing up all files and folders that cannot be restored from other media. This includes passwords, applications purchased and downloaded from the internet without CD support, financial records and folders, digital images that cannot be replaced...............
Backup copies of your registry files (in the %systemroot%\Repair folder) are also replaced after the in-place upgrade is complete. Copy these registry backups to another location before you perform an in-place upgrade/Repair Install. You may need to use them after the in-place upgrade is complete.
It would also be a good idea to run the Files And Settings Transfer wizard F.A.S.T located on the XP CD.
If you made unorthodox registry changes with third party software, there is the potential of data loss from a Repair Install. Another consideration of concern would be a power failure during the repair install could render your system un bootable and result in loss of data.
The likelihood of you losing the files and folders is probably of minimal risk, but you have to expect the worst and make sure you are prepared for recovery.
If you are sure you have explored all other troubleshooting avenues, then proceed with the repair install.
If you get a warning message: "Setup cannot continue because the version of Windows on your computer is newer than the version on the CD."
You get this message when you use a pre-SP 1, SP2 XP CD on an XP installation that has been updated to SP1, SP2.
You have the options listed below.

Remove the SP 1, SP2 update if the option is available from Add/Remove.
Create a slipstreamed XP CD merging the SP1 or SP2 update.
2a Autostreamer for creating a slipstreamed CD the easy way.
Purchase an XP CD with SP2 included.

Slipstreaming Windows XP with Service Pack 1 or 2 (SP1, SP2)
Another Slipstream step by step
AutoStreamer mirror link for AutoStreamer
Step by Step on AutoStreamer

Warning!! #2

If the Repair Option is not Available

What should I do? Most important do not ignore the information below!
If the option to Repair Install is NOT available and you continue with the install; you will delete your Windows folder and the Documents and Settings folders. All applications installed that place keys in the registry will need to be re-installed and will require the original install media.
You should exit setup if the repair option is not available and consider other options. I have found if the Repair option is not available, you have a few paths I have listed below to try before XP requires a Clean install.
Another option to consider (since the cost of 100 + gig hard drives has dropped to well under $75) would be to disconnect the current hard drive and install a clean XP from retail disks or restore media to a new hard drive. You can then connect the original hard drive after configuring the jumpers to a slave drive. You can retrieve important files. One thing to remember, if a hard drive has not been formatted or written over by reinstalling, the data is accessible. The less you access a hard drive after a non-boot episode; the better your chances of retrieving your data.
Very important!!
If you still have the ability to access the Windows XP installation, backup all important files not restorable from other sources before attempting any recovery console or other trouble shooting attempts.
Possible Fix by reconfiguring boot.ini using Recovery Console.
1.Boot with XP CD or 6 floppy boot disk set.
2. Press R to load the Recovery Console.
3. Type bootcfg.
4. This should fix any boot.ini errors causing setup not to see the XP OS
install.
5. Try the repair install.

One more suggestion from MVP Alex Nichol
"Reboot, this time taking the immediate R option and if the CD letter is say K: give these commands

copy K:\i386\ntldr C:\
copy K:\i386\ntdetect.com C:\

(two other files needed - just in case)
1. Type: attrib -h -r -s C:\boot.ini del C:\boot.ini
2. Type: BootCfg /Rebuild

which will get rid of any damaged boot.ini, search the disk for systems and make a new one. This might even result in a damaged windows reappearing; but gives another chance of getting at the repair"

12/10/2011

Load Gumstix Libraries

1) Install rsync pakage:

$ scp /build/czhang/overo-oe/tmp/deploy/glibc/ipk/armv7a/rsync_3.0.6-r0.6_armv7a.ipk root@10.0.0.146://home/root/

$ opkg install rsync_3.0.6-r0.6_armv7a.ipk

2) Install Qt lib:

$ rsync -av czhang@10.0.1.202://build/czhang/qt-everywhere-opensource-src-4.7.0/lib/* /usr/lib

3) Install serial port lib:

$ rsync -av czhang@10.0.1.202://build/czhang/qt-everywhere-opensource-src-4.7.0/projects/qextserialport/build/libqextserialport* /usr/lib

4) Install qwt lib:
$ rsync -av czhang@10.0.1.202:///build/czhang/qt-everywhere-opensource-src-4.7.0/projects/qwt-5.2.1/lib/* /usr/lib

4) Install sqlit3 lib:

$ scp czhang@x.x.x.x:/build/czhang/qt-everywhere-opensource-src-4.7.0/plugins/sqldrivers/libqsqlite.so /home/m4/sqldrivers

5) Install qzip lib:

$ rsync -av czhang@10.0.1.202://build/czhang/qt-everywhere-opensource-src-4.7.0/projects/quazip-0.3/quazip/libquazip.so* /usr/lib

6) Install Analogwidget lib:
$ scp /build/czhang/qt-everywhere-opensource-src-4.7.0/projects/AnalogWidgets/analogwidgets/libanalogwidgets_plugin.so root@10.0.0.146://usr/lib

07/10/2011

Stop Bluetooth in Overo Fire

# echo 0 > /sys/class/gpio/gpio164/value

01/10/2011

Create an Application Shortcut to Open Nautilus as Root in Ubuntu

$ sudo nano /usr/share/applications/Nautilus-root.desktop

Paste the following text in the editor that comes up in Terminal:

[Desktop Entry]
Name=File Browser (Root)
Comment=Browse the filesystem with the file manager
Exec=gksudo nautilus
Icon=file-manager
Terminal=false
Type=Application
Categories=Application;System;

Hit Ctrl+X then Y

Done!

29/09/2011

User Management

Create a user:

$ useradd tech

Add password:

$ passwd tech

Enter new UNIX password:
Retype new UNIX password:

Direct user to a preferred directory when the user log on:
usermod -d /home/tempdir/ tech

25/08/2011

Gumstix touch screen problem

I re-installed file system (2Gb SD card) for my Overo gumstix. After i booted from SD, I found the touch screen did not work. So, I had a look in /dev/input directory. I can only see 'mice' in this folder, no 'touchscreen0'.

Then I tried different way to solve the problem. I tried:

$ nand erase 240000 20000
$ reset

When I booted gumstix, the back light of screen turned on, but nothing displays on the screen. I can see 'touchscreen0' in /dev/input. I tried '/usr/bin/ts_test'. This command can detect the position when i touched screen, but just no display.

I thought my screen was faulty.

After that, I took a look the u-boot environment:

# printenv

dvimode=1024x768MR-16@60

defaultdisplay=dvi

DVI? The touch screen I am using is LCD!

Ok, changed it to:

# setenv defaultdisplay lcd43
# saveenv
# boot

Haha, screen is working.

08/08/2011

Install AnalogWidget in Ubuntu / Gumstix

Install in Ubuntu:

System spec:

Ubuntu 10.04 (lucid)
2.30.2 (Ubuntu 2010-06-25)
2.6.32-33-generic (#70-Ubuntu SMP Thu Jul 7 21:13:52 UTC 2011)
4.4.3 (x86_64-linux-gnu)
AnalogWidgets_234.zip

Download from here:
http://qt-apps.org/content/show.php?content=87780&forumpage=0

unzip it.

$ cd /home/czhang/Downloads/AnalogWidgets
$ qmake AnalogWidgets.pro
$ make
$ sudo make install

$ cp /home/czhang/Downloads/AnalogWidgets/analogwidgets/libanalogwidgets_plugin.so /home/czhang/QtSDK/QtCreator/lib/qtcreator/plugins/designer/libanalogwidgets_plugin.so

In .pro file, added:

LIBS += /home/czhang/Downloads/AnalogWidgets/analogwidgets/libanalogwidgets_plugin.so

INCLUDEPATH += /home/czhang/Downloads/AnalogWidgets/analogwidgets/analogwidgets

Install in Gumstix:

unzip Analogwidget.zip under:
/build/czhang/qt-everywhere-opensource-src-4.7.0/projects

$ qmake AnalogWidgets.pro
$ make

got some error messages according to file:
/build/czhang/AnalogWidgets/analogwidgets/code/chart/channel.cpp
/build/czhang/AnalogWidgets/analogwidgets/code/scriptwidget.cpp

I edited these two files:
in channel.cpp

void Channel::setType(unsigned int i)
{
//if (i!=Line && i!=Dots)
// throw "Bledny typ";

m_type = i;

}

in scriptwidget.cpp:
void ScriptWidget::setScript(const QString & s)
{
m_script = s;
qDebug("ScriptWidget::setScript() %s",qPrintable(m_script));
try
{
QFile file(m_script);
if (file.open( QIODevice::ReadOnly ))
{
QString src = QString(file.readAll());
QScriptValue widget = m_engine->newQObject(this);
m_engine->globalObject().setProperty(objectName(),widget);
m_engine->evaluate(src);
QScriptValue v = m_engine->uncaughtException();

if (v.isValid())
qDebug("Error %s",qPrintable(v.toString()));
}
}
//catch (std::exception & e)
//{
// qDebug("Wyjatek %s",e.what());
//}
}// setScript

$ scp /build/czhang/qt-everywhere-opensource-src-4.7.0/projects/AnalogWidgets/analogwidgets/libanalogwidgets_plugin.so root@10.0.0.146://usr/lib

31/05/2011

Disable gumstix overo console login message on ttyS2

In my design, I need to use second serial port (ttyS2) on overo.

I connected SDA3 (pin 24 on chestnut43 board) to WinXP hyperterminal, and booted up Overo.

I saw all booting messages are showing in hyperterminal.

-----------------------------------------------------------

.-------.

| | .-.

| | |-----.-----.-----.| | .----..-----.-----.

| | | __ | ---'| '--.| .-'| | |

| | | | | |--- || --'| | | ' | | | |

'---'---'--'--'--. |-----''----''--' '-----'-'-'-'

-' |

'---'

The Angstrom Distribution overo ttyS2

Angstrom 2010.7-test-20101005 overo ttyS2

overo login: root

| ' | | | |

'---'---'--'--'--. |-----''----''--' '-----'-'-'-'

-' |

'---'

The Angstrom Distribution overo ttyS2

Angstrom 2010.7-test-20101005 overo ttyS2

...

--------------------------------------------------------------------

Then, I run my program (written by Qt), the hyperterminal shows as follow:

--------------------------------------------------------------------------

QIODevice::read: Called with maxSize < 0

...

-------------------------------------------------------------------------

in the meantime, the string which sent from Qt program also shows in the screen.

I only want ttyS2 send the information from my program, not other messages.

With help from Nabble forum, the following is my solution:

Those messages are from the kernel. U need to change the "console" uboot environment variable, otherwise the kernel will print messages on that serial port.

Take a look at uboot environment variable. to do this , boot gumsix, pushed any key to stop it booting from MMC. Then use "printenv" list all u-boot variables.

------------------------------------------

Overo # printenv

bootcmd=if mmc init; then if run loadbootscript; then run bootscript; else if run loaduimagei

baudrate=115200

loadaddr=0x82000000

console=ttyS2,115200n8

vram=12M

dvimode=1024x768MR-16@60

nandargs=setenv bootargs console=${console} vram=${vram} omapfb.mode=dvi:${dvimode} omapfb.d2

loadbootscript=fatload mmc 0 ${loadaddr} boot.scr

bootscript=echo Running bootscript from mmc ...; source ${loadaddr}

loaduimage=fatload mmc 0 ${loadaddr} uImage

mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}

nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} 280000 400000; boot}

dieid#=0ef000040000000004035c140d002011

ethact=smc911x-0

bootdelay=2

defaultdisplay=lcd43

i2cspeed=3,100

bootargs=console=ttyS2,115200n8 i2c_bus=${i2cspeed} vram=12M omapfb.mode=dvi:1024x768MR-16@6t

mmcargs=setenv bootargs console=${console} i2c_bus=${i2cspeed} vram=12M omapfb.mode=dvi:1024t

stdin=serial

stdout=serial

stderr=serial

Environment size: 1279/131068 bytes

---------------------------------------------

the "console=ttyS2,115200n8" means send console login messages to ttyS2.

After that, take a look at /etc/inittab in mmc system on 2G SD card.

-------------------------------------------------

# /etc/inittab: init(8) configuration.

# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# The default runlevel.

id:5:initdefault:

# Boot-time system configuration/initialization script.

# This is run first except when booting in emergency (-b) mode.

si::sysinit:/etc/init.d/rcS

# What to do in single-user mode.

~~:S:wait:/sbin/sulogin

# /etc/init.d executes the S and K scripts upon change

# of runlevel.

# Runlevel 0 is halt.

# Runlevel 1 is single-user.

# Runlevels 2-5 are multi-user.

# Runlevel 6 is reboot.

l0:0:wait:/etc/init.d/rc 0

l1:1:wait:/etc/init.d/rc 1

l2:2:wait:/etc/init.d/rc 2

l3:3:wait:/etc/init.d/rc 3

l4:4:wait:/etc/init.d/rc 4

l5:5:wait:/etc/init.d/rc 5

l6:6:wait:/etc/init.d/rc 6

# Normally not reached, but fallthrough in case of emergency.

z6:6:respawn:/sbin/sulogin

S:2345:respawn:/sbin/getty 115200 ttyS2

# /sbin/getty invocations for the runlevels.

# The "id" field MUST be the same as the last

# characters of the device (after "tty").

# Format:

# :::

1:2345:respawn:/sbin/getty 38400 tty1

-------------------------------------------------------

The last line sets up a login on tty1. If you have a keyboard (eg. USB keyboard via a powered HUB) and display connected, then you'd be able to login using those. I am using a chestnut43 board with LCD, and i can use tty1 on a couple of occasions when I messed up the networking.

the command to change console environment variable are follows:

# setenv console tty1

# saveenv

The console setting is passed to the kernel at boot time. It Only tells the kernel where to send messages; It does not have anything to do with login terminals as that is handled by inittab and getty. I can use tty1 because it allows me to see the kernel messages on the LCD during boot.

20/05/2011

Linux hints

After reinstalled Ubuntu in my laptop, I tried to ssh laptop from Fedora computer. I got following error message:

[czhang@F13-64-VM projects]$ ssh czhang@10.0.0.124

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!

Someone could be eavesdropping on you right now (man-in-the-middle attack)!

It is also possible that the RSA host key has just been changed.

The fingerprint for the RSA key sent by the remote host is

4e:b4:d9:05:e3:b3:81:3c:1a:f6:79:64:c1:23:b7:83.

Please contact your system administrator.

Add correct host key in /home/czhang/.ssh/known_hosts to get rid of this message.

Offending key in /home/czhang/.ssh/known_hosts:3

RSA host key for 10.0.0.124 has changed and you have requested strict checking.

Host key verification failed.

This is because the RSA host key has changed since reinstalled the system.
Just remove the RSA key will solve the problem.

$ rm /home/czhang/.ssh/known_hosts

18/05/2011

Summary of Installation All Necessary Libraries for Qt programming

1) Serial port communication lib:

http://oestudyard.blogspot.com/2009/09/add-serial-port-communication-lib-in-qt.html?zx=b682084f36b1c11d

2) quazip lib:

http://oestudyard.blogspot.com/2011/03/linux-library-link-configuration.html

3) qwt 2D plot lib:
ubuntu: http://oestudyard.blogspot.co.nz/2010/10/install-qwt-in-ubuntu.html
fedora: http://oestudyard.blogspot.com/2011/05/install-qwt-in-fedora-14.html
gunstix: http://oestudyard.blogspot.com/2010/11/install-qwt-for-gumstix.html

4) sqlite3 database lib:
ubuntu: apt-get install sqlite3
gunstix: http://oestudyard.blogspot.com/2011/02/install-sqlite3-library-in-gumstix-for.html

5) SVN subversion control:
http://oestudyard.blogspot.com/2010/10/subversion-control-svn.html

6) AnalogWidget lib:

http://oestudyard.blogspot.com/2011/08/install-analog-widget-in-ubuntu.html

17/05/2011

Ubuntu 10.04 Install No Machine NX

Download DEB package from here:
http://www.nomachine.com/download-package.php?Prod_Id=2573

$ sudo chmod 755 /usr/lib/cups/backend/ipp

$ sudo dpkg -i nxclient_3.4.0-7_x86_64.deb

Labels