D
Reaction score
7

Latest activity Postings About

    • D
      DrM replied to the thread Future Teensy features & pinout.
      Yes, and therefore, even more so, it is important to decide what this platform is for, or if perhaps there should be more than one platform.
    • D
      I just updated the description on git-hub to fill in some details and explain how to use the boards - i.e., jumpers and interconnects, etc.
    • D
      The Hamamatus SPI board is up and running! The design files include the sensor board and a mating carrier for a Teensy 4.0 Here is a link to the repo. https://github.com/drmcnelson/S11639-01-Linear-CCD-PCB-and-Code This is a self contained...
    • D
      DrM replied to the thread TCD1304 with teensy 3.2.
      @Qar sorry for the delayed response. If you want something that is reproducible you need a transistor follower, or better still an opamp follower, and you need an RC (resistor in series with capacitor to ground) - because (A) you are driving an...
    • D
      DrM replied to the thread TCD1304 with teensy 3.2.
      @Huyd It sounds like you are asking for help debugging. That is okay, I think. But you need to post your code and circuit. With apologies to the moderator, I think you could start a new thread, you are not really asking about the original...
    • D
      DrM replied to the thread T4 interrupt latency and etc.
      P/S I plan to put this up on my git-hub, just havent gotten around to it. Need to find some time to generate the readme. Again the idea is "time your arduino", I tried to stay with the API as far as possible and not go to bid fiddlin'. The...
    • D
      DrM replied to the thread T4 interrupt latency and etc.
      @kd5rxt-mark I attached a complete code a few messages back. But here is the current code, which now includes the API described two messages back. This is the api I plan to use in my own work. Please see the attachment. Start the sketch...
    • D
      DrM replied to the thread T4 interrupt latency and etc.
      @PaulStoffregen Thanks for the book tip, it looks good, I ordered it. I see it has some information on ice. So that is really helpful.
    • D
      DrM replied to the thread T4 interrupt latency and etc.
      @PaulStoffregen Hi Paul, two things perhaps of interest. First, here is my API for the direct attach. I think it would be nice to have something like this available in the general API. If so, the directDetach could simplified. volatile...
    • D
      DrM replied to the thread T4 interrupt latency and etc.
      @PaulStoffregen Yes, it was the attachInterrupt() that I was concerned about. In interrupt.c, at line 89 it invokes NVIC_ENABLE_IRQ(IRQ_GPIO6789); Does that mean that interrupts become enabled again while I am still in my ISR? I thought...
    • D
      DrM replied to the thread T4 interrupt latency and etc.
      @PaulStoffregen Hi Paul, it works! Thank you. I have one question though, how do we restore the generic interrupt handler? Trying to load it with attachInterruptVector() gives an undefined reference. Another strategy, actually the one I...
    • D
      DrM replied to the thread T4 interrupt latency and etc.
      Okay, with that ado, and pending comments, I'll give it a try, on labrat hardware, and see what happens.
    • D
      DrM replied to the thread T4 interrupt latency and etc.
      @PaulStoffregen P/S - further thought on the previous. I think i need to restore the previous interrupt handler when I am done, so that external triggers will be recognized again. That would mean doing something like this before i leave the...
    • D
      DrM replied to the thread T4 interrupt latency and etc.
      @PaulStoffregen Hi Paul So looking at interrupt.c, it seems like irq_anyport() is the generic handler, and the source of the interrupt is cleared in the line gpio[ISR_INDEX] = status (the usual "write the bit to clear the bit" kind of thing)...
    • D
      @jmarsh, if you are interested, see Pauls' reply here https://forum.pjrc.com/index.php?threads/t4-interrupt-latency-and-etc.74688/post-340883 Paul confirms that there is a "generic" handler that calls the user supplier function, and provided...
  • Loading…
  • Loading…
Back
Top