Forum Rule: Always post complete source code & details to reproduce any issue!

Search:

Type: Posts; User: petesoper

Search: Search took 0.00 seconds.

  1. Thanks for sharing that. If my circumstances make...

    Thanks for sharing that. If my circumstances make a more efficient solution necessary I'll keep this in mind. I went with the four IntervalTimers for convenience. Using a Teensy 4.0 is extreme...
  2. TLDR; I can use update and the test case above is...

    TLDR; I can use update and the test case above is flawed, failing every time the interval parameter passed to begin() is zero.

    @mborgerson I can use update, should use update, and update is the...
  3. I appreciate that, Paul, believe me. But you'll...

    I appreciate that, Paul, believe me. But you'll understand that my priorities are not all of my choosing. I just (hopefully) got to the end of an adventure with IntervalTimer that cost me a ton of...
  4. Here is the test case. It had some surprises in...

    Here is the test case. It had some surprises in store for me, starting with the fact that this has nothing to do with the private IntervalTimer::channel field. My workaround is trivial: if begin...
  5. OK, submitted the report at the top based purely...

    OK, submitted the report at the top based purely on the behavior of the implementation, before looking at the source code for the library. Now clear there should be no reason why begin can't be...
  6. In a hobby context you have a point. In a...

    In a hobby context you have a point. In a professional context your assertion to "always post the complete source code" is a nice goal but sometimes not possible (e.g. one can't always post...
  7. IntervalTimer::update and begin documentation improvement

    The current doc says "To immediately begin a new interval, without completion of the current interval as scheduled, use begin()." I suggest it say one more thing after this sentence: something like...
  8. Dear mborgerson, Thank you for the effort you...

    Dear mborgerson,
    Thank you for the effort you put into this explanation. I hope to be able to offer you and the others help some day to show my gratitude.
    But I am still not communicating...
  9. The test program I submitted is perfectly bogus....

    The test program I submitted is perfectly bogus. It does not demonstrate the failure I observed, which was failure to escape from an empty loop like this: wihle(!Serial2.available()) {} that was...
  10. Yes, this test case is flawed. The original code...

    Yes, this test case is flawed. The original code has while(!Serial2.available()) {} and control never got past the while loop, somehow because of operations with Serial. I'll try again.
  11. Yes, though, no matter what the Serial baud rate...

    Yes, though, no matter what the Serial baud rate is, will be constantly overrunning the transmit buffer. But the nature of the bug is that something about Serial operations hosing the behavior of...
  12. If Serial.begin(19200) is substituted on either...

    If Serial.begin(19200) is substituted on either or both sides the receiver program fails just the same.
  13. Serial.print interferes with Serial2.available on Teensy 4.0

    Attached find two sketches that when run together with the "sender" Teensy writing to the "receiver" Teensy using Serial2 on both sides, shows Serial2.available never returning a nonzero result if...
  14. Robin, You wrote: "As far as I know, SWD...

    Robin,
    You wrote:

    "As far as I know, SWD with a debug probe / adapter such as the LPC-Link2 is the only way to program and debug the RT1062 MCU with GCC and GDB."

    Segger J-Link comes with...
  15. Better than "fine enamel wire" is 30 gauge kynar...

    Better than "fine enamel wire" is 30 gauge kynar insulated wire designed for wire wrapping (an ancient ritual almost forgotten). It can be stripped to expose a very short length of wire and with good...
Results 1 to 15 of 15