AlexT_Intel wrote:
That looks strange. Since that finding, the bug was fixed, AFAICS in the sources, so you don't need to specify the second argument unless you want to have your function called less frequently than the timer's frequency. I don't see anything there which would apparently stand out as a possible root cause for such behavior.
Which Galileo release do you have, Gen1 or Gen2?
If you have Gen1, then set the VARIANT_TRACE_LEVEL to TRACE_LEVEL_DEBUG in \arduino-1.5.3\hardware\arduino\x86\variants\galileo_fab_d\variant.h
If you have Gen2, the debug level is already set and no action is needed.
Then compile the sketch (it's better to strip it to the bare minimum to avoid excessive logging) and run it.
After that take a look at /tmp/log.txt and /tmp/log_er.txt files on the board - they will contain stdout and stderr information produced by the sketch.
Look for the following string (the placeholders will be replaced by the actual numbers): "Setting timer interrupt callback @%p hpet @ %lu Hz timer @ %lu Hz"
That should give you an idea of what are the actual parameters it uses when attaching. Feel free to post the files here if you have troubles interpreting them, I'll try to help.
Thanks for the reply. I will try to look into this as you are suggesting. But, before I go spelunking - do you get a different value when you run the sketch that I had attached? Does everyone else get the right values??