Community
cancel
Showing results for 
Search instead for 
Did you mean: 
mkawa8
Novice
2,407 Views

update to Node 0.12.7 and xdk-daemon not working...

Jump to solution

Hello

I tried upgrade to Node 0.12.7 by below command

```

root@edison~:opkg upgrade nodejs

```

and restart Edison. However xdk-daemon 0.0.35 not working

may be the daemon repeat restart process. and Not found Edison from XDK

Did not work xdk-daemon with Node 0.12.7 ?

1 Solution
mkawa8
Novice
187 Views

Now I installed xdk-daemon 0.0.37 from http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-iot-middleware/commit/recipes-devtools/xdk-daem... meta-intel-iot-middleware - Shared middleware recipes for Intel IoT platforms

When this version upload to opkg repository...?

View solution in original post

11 Replies
mkawa8
Novice
187 Views

In addition my software stack is...

Yacto OS Release2.1(weekly159)

node: v0.12.07

mraa: v0.8.0

xdk: v2170

mkawa8
Novice
188 Views

Now I installed xdk-daemon 0.0.37 from http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-iot-middleware/commit/recipes-devtools/xdk-daem... meta-intel-iot-middleware - Shared middleware recipes for Intel IoT platforms

When this version upload to opkg repository...?

View solution in original post

Carlos_M_Intel
Employee
187 Views

Hi masato-ka,

If you are talking about this repository: http://repo.opkg.net/edison/repo/ Index of /edison/repo it is managed by AlexT.

If this is the case maybe AlexT_Intel could help us with this.

Regards,

Charlie

mkawa8
Novice
187 Views

Hi CMata_Intel

Thank you.

OK, I send request to AlexT_Intel.

However, This release is intel official release?…Or Test?, 3rd Party?

If you know that, please tell me.

Regards,

masato-ka

Carlos_M_Intel
Employee
187 Views

Hi masato-ka,

About the repository: http://alextgalileo.altervista.org/edison-package-repo-configuration-instructions.html Edison Package Repo Configuration Instructions

As you can in there:

This is not any kind of an official or Intel-endorsed repo. Packages are compiled with the latest official BSP as the base and I'm doing some basic tests, but as with everything in the Makers world you use that on your own risk :-) ...

This repo works really well and it is being updated very often

Regards,

Charlie

AT9
Honored Contributor II
187 Views

Well, if node.js works and xdk-daemon is not, then maybe it's simply not compatible with this newer version of the node.js?

mhahn, any idea who could know more about xdk-daemon and Node.js version compatibility?

AT9
Honored Contributor II
187 Views

Ok, never mind, masato-ka told me in a private message that updating to xdk-daemon 0.0.37 fixed this for him, so I'll add this newer version to my repo, added this to my packaging ToDo list.

mkawa8
Novice
187 Views

AlexT_Intel

Thank you for message.

I'm waiting update your repository :-)

Dan_Y_Intel
Employee
187 Views

The daemon that is bundled with the IoTDevKit contains a node module (mdns) that is pre-compiles against node 0.10.x headers. In order for the daemon to work on a machine running node 0.12.x the module needs to be compiled against the node 0.12.x headers.

One way to do this is by upgrading the the mdns node module.

cd /opt/xdk-daemon/current/node_modules/

npm update mdns@2.2.10

systemctl restart xdk-daemon

Note: The mdns node module is needed for automatic device detection to function properly

 

Edit # 1: As masato-ka mentioned extractiing the contents of http://download.xdk.intel.com/iot/xdk-daemon-0.0.37.tar.bz2 http://download.xdk.intel.com/iot/xdk-daemon-0.0.37.tar.bz2 and running setup.sh will also install the daemon (and compile the nessicary node modules in the process)

 

mkawa8
Novice
187 Views

@intel_dan

Thank you dan.

Ok, I will try update mdns with xdk-daemon 0.0.35.

mkawa8
Novice
187 Views

@intel_dan

I tried your recommend commands.

After, xdk-daemon started.

However, npm update mdns@2.2.10 therefor , I run below command.

root@edison~:npm install mdns

started rebuild mans after the command.

Regards.

Reply