After upgrading the XDK, did you receive a message with a notification to upgrade the daemon in the board?
Are you receiving an error message in the log when you upload and run the code? Or is it just that it’s not working as it should?
Is the only thing that have happened the upgrade of the XDK?
After the XDK update, you shouldn’t need to re-flash your board.
I did receive the message to upgrade the daemon, which I did. It didn't help.
I don't get any kind of code or syntax error. When I run it, I do not get any runtime error. It's coded such that if the pin goes hi/lo, then my callback should be called and I get a console message. When I press my (grove) button, my function is not called because I never see my console message.
The XDK upgrade was the only thing I did.
BTW, I'm on a MacBook Pro (running 10.10.5). I have also been using my Ubuntu box which I *did not yet update* XDK. I'll give it a try on there when I get some time.
Again, I didn't have any problems before the upgrade on my Mac. But now I do. I wonder if I have to reboot the Mac? Worth a shot, I guess.
Since I posted this message I decided to re-flash. I used the Mac all-in-one tool that on the Intel downloads page. MRAA and UPM versions look good. The XDK is the same. But my simple code still doesn't work. Very odd.
Hi gwfong ,
Do you have updates in this? Have you been able to test this in your Ubuntu machine?
Have you tried to run another example like the Blink example?
Let’s try running:
systemctl enable xdk-daemon
systemctl restart xdk-daemon
Also, in the XDK go to the Manage your daemon/IoT device icon and select Sync PC time w/ clock on target board. Let me know if you get improvements after this.
Sorry. Been too busy. Now I'm back working on this.
Running XDK IOT 2170 on Ubuntu, I'm having the same problem. I synced the time and that didn't help. I noticed that the reason why the ISR callback isn't firing is because the node app is immediately exiting. I registered a callback for the process 'exit' event and it is fired immediately.
I have been able to successfully run other templates. I have even been able to run simple Johnny Five apps (very simplistic apps). My guess with all of these, however, is that there is a setInterval() or setTimeout() loop that's running. This keeps node from exiting. Again, with the basic Grove button example template there is no loop that keeps node running. And when I add a callback handler for the 'exit' event, it is called. It would seems reasonable to conclude that the reason the ISR callback isn't getting called is because node exited before I got a chance to push the button.
Does that seem reasonable to you (or to anyone else reading this post)?