Open qiaojingx opened 7 years ago
Looks like the setInterval isn't finishing before it gets called again. I'll look to make sure there isn't a problem with callbacks. It may also be that 10 is too low a timer number.
Looks like callbacks are fine, the demo timer is just going faster than the callbacks can be handled - hence the error message. #1614 will fix this.
Verified with commit cac4c3a + #1614. Error in I2CBMP280.js has been fixed. Could you change interval time in HeartRateDemo.js, too?
This seems to indicate we have a performance regression because we used to do this work in 10ms apparently and now it takes 200ms? Rather than mask the problem (:D) let's look into why. @brianjjones, could you try testing this just before and after #1542 to see if that's what caused the problem.
@brianjjones ping on this one, just note I don't think we're done here.
@cuiyanx is this still reproducible?
@jimmy-huang Yes, this issue can be reproduced on both cases. And /samples/Stepper.js case looks like this issue. Log:
Stepper Motor sample...
554:(ERROR) 1 ringbuf put errors (last rval=-122)
554:(ERROR) 15 ringbuf put errors (last rval=-122)
554:(ERROR) 47 ringbuf put errors (last rval=-122)
554:(ERROR) 110 ringbuf put errors (last rval=-122)
Description
This is an regression issue and probably caused by #1542.
ringbuf put errors
prints when running HeartRateDemo.js and I2CBMP280.js on A101.Test Code
HeartRateDemo.js; I2CBMP280.js
Steps to Reproduction
make JS=samples/I2CBMP280.js
make dfu
Actual Result
Expected Result
No error.
Test Builds
Additional Information