Community
cancel
Showing results for 
Search instead for 
Did you mean: 
mgiun
New Contributor I
1,626 Views

Edison BSP (1.0 ... 2.1 ... 3.0 .. 3.5) and Nodejs, the never ending story.... AKA Where in the World Is Carmen Sandiego?

Jump to solution
Intel Edison from node 0.10.38 to 0.12 ... aiming to 4.x .. a long story passed... but finally in Jun 6 , 2016 ..https://software.intel.com/en-us/user/1141904 Wai Lun Poon (Intel)

in the Release note of INTEL® IOT DEVELOPER KIT 3.5 RELEASE ANNOUNCEMENT ( https://software.intel.com/en-us/blogs/2016/06/06/intel-iot-dev-kit-35-release-announcement https://software.intel.com/en-us/blogs/2016/06/06/intel-iot-dev-kit-35-release-announcement ) announce the presence of nodejs 4.4.3 in Intel BSP.

but, taking a deep look : in the main page of BS ( https://software.intel.com/en-us/iot/hardware/edison/downloads https://software.intel.com/en-us/iot/hardware/edison/downloads ) the binary image release ( https://software.intel.com/edison-image/latest https://software.intel.com/edison-image/latest ) contais nodejs 4.4.3....

BUT.....

the source code ( http://iotdk.intel.com/src/3.5/edison/ ) that developers MUST use to rebuild image without Library, develop kit, usefull for remote upgrade etc etc ... ) misses the nodejs 4.4.3 and... after years.. sadly contains ... nodejs 0.10.38 ( .. )

# -------------------------------------------------------------------------------------------

./build/tmp/work/x86_64-linux/nodejs-native

./build/tmp/work/x86_64-linux/nodejs-native/0.10.38-r0/sysroot-destdir/home/mgiuncato/e/i3.5/poky/out/linux64/build/tmp/sysroots/x86_64-linux/sysroot-providers/nodejs-native

./build/tmp/work/x86_64-linux/nodejs-native/0.10.38-r0/license-destdir/nodejs-native

./build/tmp/work/x86_64-linux/nodejs-native/0.10.38-r0/node-v0.10.38/out/Release/.deps/home/mgiuncato/e/i3.5/poky/out/linux64/build/tmp/work/x86_64-linux/nodejs-native

./build/tmp/buildstats/edison-image-edison/Custom Edison build by mgiuncato@ubu14v 2016-07-22 10:08:50 CEST/nodejs-native-0.10.38-r0

./build/tmp/buildstats/edison-image-edison/Custom Edison build by mgiuncato@ubu14v 2016-07-22 10:08:50 CEST/nodejs-0.10.38-r0

mgiuncato@ubu14v:~/e/i3.5/poky/out/linux64$ bitbake -s | grep nodejs

# -----------------------------------------------------------------------------------------------

anyone in Intel may correct ?

( or indicate how to do it :-) )

to be continue...

Tags (1)
0 Kudos
1 Solution
mgiun
New Contributor I
109 Views

Diego,

I have not time to try 3.5 in the way indicated, because we arrive to the first release date of our product based on Edison.

I still use the only good image I produced with BSP 3.0, with size reduced cutting off develop components.

With the indications of Peter I reach a workaround (supplying where can be found node 4,4,3) , so I include the module .ipk in image and applied a "postinstall" install of node's modules (opkg install xxxx.ipk) .

it works fine and the final installation contains nodejs 4.4.3, & npm

our application now works !.

this is not the perfect way...but still works for 1.0 release.

so I can go on Summer Holydays ! :-)

at the end of august I will restart working with BSP 3.5 image and notify the result.

thank of support

Marco

View solution in original post

10 Replies
idata
Community Manager
109 Views

Hello mgiuncato,

 

 

The BSP indeed includes Node.js 4.4.3. What happens is that it includes several versions of Node and if the recipes are modified, the version that is built might end up not being 4.4.3.

 

 

In fact if you check the BSP in the directory poky/meta-intel-iot-devkit/recipes-devtools/nodejs/, you will indeed find Node's recipe for the 4.4.3 version (nodejs_v4.4.3.bb). The following is a screenshot of our PC, you will be able to see that on our build the package that was created was version 4.4.3:

 

 

Peter.
mgiun
New Contributor I
109 Views

thank for fast answer.

Let me explain, after reading the rRlease Note of BSP 3.5 , I took the source indicated ( http://iotdk.intel.com/src/3.5/edison/iot-devkit-yp-poky-edison-20160606.zip http://iotdk.intel.com/src/3.5/edison/iot-devkit-yp-poky-edison-20160606.zip ) bitbaked it following the instructions, sure to find (finally) node 4.x.

it took a lot of time, you know (3-5 hours ).

After that, I flashed the new image in prototypes we are finalizing for mass production.

I installed our nodejs application (>= 4.x ) and it crash, I found node in the old version 0.10.x .

so

Why the package 4.4.3 is not considered as the default to be installed also in bitbaked images, as reported in Press Release and in the same way of the binary pre compiled image ?

I did not verify the presence of .ipk, I believe you of course and will look, but why there is not information about find it, it seems important, so important to refer several times the the Press Release ( indeed developers wait for it ;-) ) ?

And last, If not preinstalled ( as all of us hope for ) I appreciate if you almost indicate HOW install, DURING bitbake, for automating large production of embedded systems.

Happy to find this qualified support....

surely, al last, we will find Carmen Sandiego ... and node 4.x :-D

idata
Community Manager
109 Views

In my experience the image is indeed built with version 4.4.3 of Node.js by default, as you can see in the screenshot bellow. Could you please verify that you are not making any modifications that could be affecting the Node version on your board?

 

 

In the screenshot it is appreciated the date when I built the image, the version of Node (this is a default build, there's no modifications made to it) and the kernel information.

 

 

-Peter
mgiun
New Contributor I
109 Views

Hi Peter,

I start from the source published : http://iotdk.intel.com/src/3.5/edison/iot-devkit-yp-poky-edison-20160606.zip http://iotdk.intel.com/src/3.5/edison/iot-devkit-yp-poky-edison-20160606.zip

bitbake it without any change, only bitbake, postinstall, & flash, as the instruction said.

((unfortunately now I'm outside office, tomorrow morning I send you the screenshots with same your information ))

in the meantime, can you send the size of your image ( after bitbake and postBuild, directly in toFlash dir ) or size or md5 of ....poky-edison-20160606.zip ?

I noticed that the image obtained was very little , this beacuse a little image is a good starting point for remote update..

I suspect that it was a "core only" image, not the full-size (1,4gb) of the binary-build distribution.

Marco

mgiun
New Contributor I
109 Views

Peter,

last, could you send the EXACT instruction followed after download the zip file (http://iotdk.intel.com/src/3.5/edison/iot-devkit-yp-poky-edison-20160606.zip http://iotdk.intel.com/src/3.5/edison/iot-devkit-yp-poky-edison-20160606.zip)

I really appreciate this.

Marco

idata
Community Manager
109 Views

As you can see in the screenshot bellow the size of toFlash.zip is 283MB and the unzipped image is 1.1GB.

I followed the steps provided in the BSP, precisely, in the README.edison file:

# Building the edison image

 

unzip iot-devkit-yp-poky-edison-20160606.zip

 

cd iot-devkit-yp-poky-edison-20160606/poky/

 

source oe-init-build-env ../build_edison/

 

bitbake edison-image u-boot

 

../poky/meta-intel-edison/utils/flash/postBuild.sh .

 

zip -r toFlash.zip toFlash

-Peter.

mgiun
New Contributor I
109 Views

Well Peter,

I'm using BSP since 3 months ago,compiling Lot of times in various way, starting from 2.1 , to 3.0 and now with 3.5...so it should be that I make mistake.

I will do again with that directories , to be sure .

But In this moment I remember one directory , with the same structure, but located deeply. In the tree below poky/..something like ..out/Linux64.

Is late in the evening now, tomorrow I verify and report here.

Thanks

Marco

idata
Community Manager
109 Views

We'll wait for your update, please let us know how it goes.

 

 

-Peter.
idata
Community Manager
109 Views

Hi Marco,

 

 

I'd like to know if you have any updates about this. Were you able to run additional tests? Please let us know if you still need help.

 

 

Regards,

 

-Diego

 

mgiun
New Contributor I
110 Views

Diego,

I have not time to try 3.5 in the way indicated, because we arrive to the first release date of our product based on Edison.

I still use the only good image I produced with BSP 3.0, with size reduced cutting off develop components.

With the indications of Peter I reach a workaround (supplying where can be found node 4,4,3) , so I include the module .ipk in image and applied a "postinstall" install of node's modules (opkg install xxxx.ipk) .

it works fine and the final installation contains nodejs 4.4.3, & npm

our application now works !.

this is not the perfect way...but still works for 1.0 release.

so I can go on Summer Holydays ! :-)

at the end of august I will restart working with BSP 3.5 image and notify the result.

thank of support

Marco

View solution in original post

Reply