nielsreijers
commented
11 years ago The VM will continue to listen to the radio is most/all the busy loops I know of in the framework. It will check inbetween processing byte code instructions, in the WKPF.select() function since we will spend a lot of time there, and in the error function (when it prints ERR:X). I added the last one for exactly this problem, that I wasn't able to upload new code anymore when the VM crashed, for instance because the code upload failed halfway through on a previous attempt.
Since the VM should be responding to radio messages in pretty much all circumstances, the problem is probably somewhere else, for instance in the zwave stack, or maybe because we're using too much memory. Actually that last one sounds like a possible candidate since the problem apparently was quite common when preparing the intel demo, but it hasn't turned up recently. A few weeks ago I ran into memory problems since we were right on the 8K edge, so I decided to reduce some of the constants like maximum group size in Penn's group.c code.
If that's wasn't the problem, then there's clearly something else going on, but for now I'm closing the issue until we see it happening again.
Can you add some comment for this item? In the demo setup, the VM often stop handling any messages. It must trapped somewhere in the VM. You can discuss with Penn. We need to fix this before the official release.