How to upgrade to php-5.3.0?

[JM K]

Hi,

I think the default version of php in the openembedded/recipes is php-5.2.11. I would like to know how to upgrade to php-5.3.0. The problem I am facing is that sqlite3 is compatible with only php-5.3.0 and not any of the php 5.2.x versions. I have checked the php.inc file and also the .bb files but did not find a DEFAULT_PREFERENCE statement anywhere. Any quick advice/suggestions on how to fix this one would be greatly appreciated. Thank you and have a great day.

Best Regards,

JM

[Jesse Gilles]

CoreCDP 2.0.2 was just released and includes php 5.3.6. You could give that a try if you wish, but it is a major new release and you’ll have to rebuild everything in a new directory.

[Jesse Gilles]

Also, php isn’t compiled with sqlite support by default — the recipe would need to be modified to change that and see if it builds.

[JM K]

Hi Jesse,

thank you for your response. I don’t think I can upgrade to Corecdp 2.0.2 due to some time constraints. Isn’t there a compatible bitbake recipe for php-5.3.0? In case this (bitbake recipe) is included in the new version of Corecdp, can you please post it in the forum. Would the recipe included with the latest version of Corecdp have any compatibility problems with the Corecdp 1.0.0? (the one I am using presently) Any idea what to change in the recipe such that php compiles with sqlite? I tried searching for a recipe in git.openembedded.org but could not find a good one. I would be very much thankful if you could help me out with this one.

Best Regards,

JM

[Jesse Gilles]

The php recipe is on git.multitech.net. There may be some compatibility issues with using that recipe with CoreCDP 1.x, yes — this is due to changes in OpenEmbedded and Bitbake. You are free to try it out and see what happens.

To try compiling with sqlite, you would have to add sqlite to the DEPENDS variable and edit the EXTRA_OECONF to build with sqlite instead of without. This might take some research and you’ll need to be familiar with configuring and compiling php to get it working.

I may try to expand the recipe to add sqlite support in the future if I have time, but this would only get tested against CoreCDP 2.x.

[JM K]

Dear Jesse,

Thank you for the response. I have decided to upgrade to the latest CoreCDP 2.0.2. As for installing CoreCDP 2.0.2, would all these steps have to be followed along with setting up TFTP server again?

http://www.multitech.net/developer/products/multiconnect-ocg/getting-started/

I am worried about the part of setting up and configuring the TFTP server as I ran into some problems last time. I would appreciate it if you could advice/suggest me on this one.

Thank you and have a great day.

Best Regards,

JM

[Bryan Tran]

Hi JM,

1. You should not have to worry about the TFTP server.

2. Here is how to flash upgrade your device with CoreCDP-2.0.2

Procedure for how to flash them to your CDP device:

a. Create a /flash-upgrade folder on your SD card.

b. Copy the rootfs.jffs2 and uImage.bin to /flash-upgrade folder.

c. Insert the SD card into the CDP device.

d. Do: cd /media/card/flash-upgrade and then ls to make sure the rootfs.jffs2, uImage.bin files are there.

e. Do: touch /var/volatile/do_flash_upgrade

f. Do: reboot.

Regards,

BT

[JM K]

Dear Bryan,

Good to hear from you. Thank you for the response. I just started downloading the latest CoreCDP 2.0.2, looks like that is going to take a while. The first step where I copy the rootfs.jffs2 to the SD card is after I extract the build system and build the cross compilation tool chain, sample kernel and filesystem image, yes? I would appreciate it if you could answer my question.

Best Regards,

JM

[JM K]

Dear Jesse,

I would very much appreciate it, in case you find the time if you modify the php recipe to accommodate sqlite3. That would solve a lot of potential problems in my application development. Thank you and have a great day.

Best Regards,

JM

[Bryan Tran]

Hi JM,

After you have downloaded the source code: you then cd into the folder: corecdp-2.0.2 and do as follow:

a. source env-oe.sh

b. bitbake corecdp-base-image or bitbake corecdp-full-image

The result file will be in:

/corecdp-2.0.2/build/tmp/deploy/eglibc/images/mtcdp/corecdp-full-image-mtcdp.jffs2

Note: Rename this file to: rootfs.jffs2

and:

/corecdp-2.0.2/build/tmp/deploy/eglibc/images/mtcdp/uImage-mtcdp.bin

Note: Rename this file to: uImage.bin

From the Development machine, you ssh into your CDP device with the SD card plugged in. Then do: cd /media/card.

a. Create a /flash-upgrade folder on your SD card.

b. Copy the rootfs.jffs2 and uImage.bin from your Development machine to /flash-upgrade folder on your SD card.

c. Do: cd /media/card/flash-upgrade and then ls to make sure the rootfs.jffs2, uImage.bin files are there.

d. Do: touch /var/volatile/do_flash_upgrade

e. Do: reboot.

When the CDP is rebooting back up, it will upgrade your CDP to the newest firmware CoreCDP-2.0.2.

Regards,

BT

[JM K]

Hi Bryan,

I renamed both files somehow they both had a black arrow on their respective icons. I created a folder flash-upgrade on the SD card and when I tried copying these files I was faced with an error: Filesystem does not support symbolic links. Then I checked the properties of both rootfs.jffs2 and the uImage.bin and their type was listed as: Link to unknown. (application/octet-stream). I did a corecdp-base-image from the prompt after a source-env-oe.sh. Please do let me know how to fix this one. Thank you and have a great day.

Best Regards,

JM

[Bryan Tran]

Hi JM,

So you go into this folder on your development machine:

/corecdp-2.0.2/build/tmp/deploy/eglibc/images/mtcdp/corecdp-full-image-mtcdp.jffs2

and rename the file above to the rootfs.jffs2 ?

And this folder:

/corecdp-2.0.2/build/tmp/deploy/eglibc/images/mtcdp/uImage-mtcdp.bin

to uImage.bin and it is giving you a sym link ?

Can you go into the above folder do a command: ls -l and paste the output to this post so that I can see what they are.

Regards,

BT

[JM K]

Dear Bryan,

thanks for your response. Here is the output you requested:

jm@jm-desktop:~/Desktop/corecdp-2.0.2/build/tmp/deploy/eglibc/images/mtcdp$ ls -l

total 285156

lrwxrwxrwx 1 jm jm 48 2011-12-02 10:26 at91bootstrap.bin -> at91sam9g20nf-nandflashboot-2.13-r1.corecdp3.bin

-rwxr-xr-x 1 jm jm 5220 2011-12-02 10:26 at91sam9g20nf-nandflashboot-2.13-r1.corecdp3.bin

lrwxrwxrwx 1 jm jm 62 2011-12-02 16:34 corecdp-base-image-mtcdp.jffs2 -> CoreCDP-corecdp-base-image-eglibc-ipk-2.0.2-mtcdp.rootfs.jffs2

lrwxrwxrwx 1 jm jm 60 2011-12-02 16:34 corecdp-base-image-mtcdp.tar -> CoreCDP-corecdp-base-image-eglibc-ipk-2.0.2-mtcdp.rootfs.tar

-rw-r–r– 1 jm jm 16252928 2011-12-02 16:34 CoreCDP-corecdp-base-image-eglibc-ipk-2.0.2-mtcdp.rootfs.jffs2

-rw-r–r– 1 jm jm 33914880 2011-12-02 16:34 CoreCDP-corecdp-base-image-eglibc-ipk-2.0.2-mtcdp.rootfs.tar

drwxr-xr-x 2 jm jm 4096 2011-12-02 10:28 CoreCDP-corecdp-base-image-eglibc-ipk-2.0.2-mtcdp-testlab

-rw-r–r– 1 jm jm 78118912 2011-12-02 16:29 CoreCDP-corecdp-full-image-eglibc-ipk-2.0.2-mtcdp.rootfs.jffs2

-rw-r–r– 1 jm jm 159641600 2011-12-02 16:29 CoreCDP-corecdp-full-image-eglibc-ipk-2.0.2-mtcdp.rootfs.tar

drwxr-xr-x 2 jm jm 4096 2011-12-02 16:30 CoreCDP-corecdp-full-image-eglibc-ipk-2.0.2-mtcdp-testlab

lrwxrwxrwx 1 jm jm 62 2011-12-02 16:29 corecdp-full-image-mtcdp.jffs2 -> CoreCDP-corecdp-full-image-eglibc-ipk-2.0.2-mtcdp.rootfs.jffs2

lrwxrwxrwx 1 jm jm 60 2011-12-02 16:29 corecdp-full-image-mtcdp.tar -> CoreCDP-corecdp-full-image-eglibc-ipk-2.0.2-mtcdp.rootfs.tar

-rw-r–r– 1 jm jm 1929751 2011-12-02 09:59 modules-2.6.35-r4.corecdp5-mtcdp.tgz

lrwxrwxrwx 1 jm jm 62 2011-12-02 10:27 rootfs.jffs2 -> CoreCDP-corecdp-base-image-eglibc-ipk-2.0.2-mtcdp.rootfs.jffs2

-rwxr-xr-x 1 jm jm 159244 2011-12-02 10:12 u-boot-mtcdp-1.3.4-r9.bin

lrwxrwxrwx 1 jm jm 25 2011-12-02 10:12 u-boot-mtcdp.bin -> u-boot-mtcdp-1.3.4-r9.bin

-rw-r–r– 1 jm jm 1936596 2011-12-02 09:59 uImage-2.6.35-r4.corecdp5-mtcdp.bin

lrwxrwxrwx 1 jm jm 35 2011-12-02 09:59 uImage.bin -> uImage-2.6.35-r4.corecdp5-mtcdp.bin

drwxr-xr-x 2 jm jm 4096 2011-12-02 10:26 Utilities

After doing a corecdp-base-image, renaming the files and having failed to copy them, I did a corecdp-full-image from the command prompt.

Best Regards,

JM

[Bryan Tran]

Hi JM,

1. -rw-r–r– 1 jm jm 78118912 2011-12-02 16:29 CoreCDP-corecdp-full-image-eglibc-ipk-2.0.2-mtcdp.rootfs.jffs2

*Rename this file to: rootfs.jffs2 by typing:

mv CoreCDP-corecdp-full-image-eglibc-ipk-2.0.2-mtcdp.rootfs.jffs2 rootfs.jffs2.

2. -rw-r–r– 1 jm jm 1936596 2011-12-02 09:59 uImage-2.6.35-r4.corecdp5-mtcdp.bin

*Rename this file to: uImage.bin by typing:

mv Image-2.6.35-r4.corecdp5-mtcdp.bin uImage.bin

3. Then copy these two files to your SD card under the folder /flash-upgrade. Do the ls command on your SD card

to verify that:

a. uImage.bin is about roughly 1.85MB

b. rootfs.jffs2 is about roughly 74.5MB

Regards,

BT

[Bryan Tran]

Hi JM,

BTW, When you are issuing the mv command, make sure you separate the source and the destination file with a space. For example,

mv source destination.

Note: There is a space between the source and destination.

Regards,

BT

[JM K]

Dear Bryan,

I copied the said files to the SD card and inserted the SD card in to the CDP Device and then issued the command that you have posted. Here is the log:

# cd flash-upgrade

# ls

rootfs.jffs2 uImage.bin

# touch /var/volatile/do_flash_upgrade

# reboot

Broadcast message from root (pts/0) (Mon Dec 5 11:15:54 2011):

The system is going down for reboot NOW!

# Connection to 192.168.2.1 closed by remote host.

Connection to 192.168.2.1 closed.

jm@jm-desktop:~$ ssh root@192.168.2.1

ssh: connect to host 192.168.2.1 port 22: No route to host

jm@jm-desktop:~$ ssh root@192.168.2.1

ssh: connect to host 192.168.2.1 port 22: No route to host

jm@jm-desktop:~$ ssh root@192.168.2.1

ssh: connect to host 192.168.2.1 port 22: No route to host

jm@jm-desktop:~$ ssh root@192.168.2.1

ssh: connect to host 192.168.2.1 port 22: No route to host

jm@jm-desktop:~$ ssh root@192.168.2.1

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

@ 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

ab:e7:36:a3:e5:a5:da:e5:06:c8:a7:70:66:a4:35:2b.

Please contact your system administrator.

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

Offending key in /home/jm/.ssh/known_hosts:1

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

Host key verification failed.

Looks like there is some kind of verification issue. Please do let me know how to solve this one. Thank you.

Best Regards,

JM

[Bryan Tran]

JM,

Issue the following command on your development machine:

sudo rm /home/jm/.ssh/known_hosts

Then try to ssh back into your device again. It should work.

Regards,

BT

[JM K]

Dear Bryan,

It worked. I could log in to the CDP. I have another question. I used to put all my programs in the recipes folder in a directory called user-collection and there is not a user-collection folder in the corecdp-2.0.2 instead there is a folder called user-layer. Are user-collection (corecdp-1.1.1) and user-layer (corecdp-2.0.2) the same? Thank you.

Best Regards,

JM

[Bryan Tran]

Hi JM,

Yes, it is.

http://www.multitech.net/developer/products/multiconnect-ocg/development/development-examples/

Regards,

BT

[JM K]

Hi Bryan,

Thanks for your response. I ran in to this error when I tried bitbaking one of my old recipes on the new corecdp-2.0.2. The recipe bitbaked fine on the old version. Error is:

ERROR: LexToken(Rbace,’}’,0,0)

followed by

LexToken(NEWLINE,’n’,0,0)

LexToken(NEWLINE,’n’,0,0)

LexToken(TOKEN,’do_install’,0,0)

LexToken(LPARENS,'(‘,0,0)

LexToken(RPARENS,’)’,0,0)

Please do let me know how to fix this one.

Best Regards,

JM

[JM K]

Dear Bryan,

please disregard my question. Think there’s a problem with the recipe. Thanks for your help installing the new corecdp.

Best Regards,

JM

[Author]

Posts