Search results

  1. R

    EncoderTool wrong value on first anti-clockwise adjustment after power up

    Thanks for the follow up. It turned out that the particular encoder I was testing was worse than most others that I tried (of the same model). But it would be nice to have my design more immune to sample variation. I'll give the polled version a try.
  2. R

    EncoderTool wrong value on first anti-clockwise adjustment after power up

    On a somewhat related note, I find with the encoder I'm using that I don't always get changes when clicking to a next detent. Switching to full mode shows more or less than the expected 4 pulse changes. Is there a way of dealing with this in software so I can ensure single increments/decrements...
  3. R

    EncoderTool wrong value on first anti-clockwise adjustment after power up

    Tested now with the 1us delay added after setting pinmodes in encoder.h, and can confirm it fixes the issue for me too. Thanks very much, it's greatly appreciated.
  4. R

    EncoderTool wrong value on first anti-clockwise adjustment after power up

    Do you mean in EncoderTool.h? I'm having a bit of trouble locating where that lives (but see the stock encoder.h lib no problems). Will report back when I can find it! ...OK I see you probably mean encoder.h in the src/single directory?
  5. R

    EncoderTool wrong value on first anti-clockwise adjustment after power up

    No, as I showed above the encoder gives 4 outputs per detent. Also, it works exactly as expected apart from that very specific first anticlockwise detent click after power up. Seems more like some sort of initialization issue to me.
  6. R

    EncoderTool wrong value on first anti-clockwise adjustment after power up

    >Looks like it doesn't read the pinlevels at startup correctly. How did you connect the encoder? >I tested your code with a directly connected encoder (common GND) without any additional stuff. It works without issue here. My encoder is directly connected too, with A/B to pins 17/16 on T4.1 and...
  7. R

    EncoderTool wrong value on first anti-clockwise adjustment after power up

    I'm using EncoderTool.h (version 3.2.0 + Teensyduino 1.59) on T4.1 with a Bourns 24 detent encoder (PEC11R-4215F-S0024) and getting an error for the very first anti-clockwise adjustment after power up. The error arises between the initial and next (anti-clockwise) detent, as soon as the encoder...
  8. R

    Teensy 4.1: flashing fails every other time

    As it turns out the display presence/absence was a red herring. Instead, as I anecdotally noted in the other thread where I wrote about this issue, there is variation across my T4.1 boards where some have the timeout error on the erase cycle and others don't. This is when they're plugged into...
  9. R

    Teensy 4.1: flashing fails every other time

    Teensy 4.1, lockable (I'm just about to test to see if I get any different behaviors for hex and ehex files) (with no ethernet in case it makes a difference)
  10. R

    Teensy 4.1: flashing fails every other time

    It's interesting that without the display the erase time seems (probably just) short enough for the unextended version of teensy loader to work reliably. Whereas with the display connected I get a download error the first time, and success every second time because (I assume ) the erase is...
  11. R

    Teensy 4.1: flashing fails every other time

    Thanks. For the macos build, I was told the Teensy loader times were noticeably slower than for the windows version. Is it possible to extend the macos version timeout even further for test purposes, e.g. to 2 minutes?
  12. R

    Teensy 4.1: flashing fails every other time

    Thanks Paul, I appreciate the added comments. However, the Teensy in my circuit board has a well bypassed linear LM7805 T0-220 regulator all to itself so it can optionally drive a MIDI controller on the USB host port. And the touch display is powered by a separate LM7805 SOT223. I'll put a...
  13. R

    Teensy 4.1: flashing fails every other time

    Thanks, but my board has multiple regulators driven from a 9V plug pack, and doesn't use the USB 5V supply (track is cut). The Teensy, display, codec and analog circuits all have their own regulators.
  14. R

    Teensy 4.1: flashing fails every other time

    After further investigation (back on my own windows system), I found that if I program the T4.1 with it removed from my custom circuit board I can get it to work every time even without the extended delay. I subsequently put together a circuit board that contains everything except the ILI1394...
  15. R

    Teensy 4.1: flashing fails every other time

    Thanks very much Paul, that's greatly appreciated. I won't be testing it myself as I know virtually nothing about MAC OS, but have someone else who is testing it for me. I'll pass on your comment about the notarization. Regarding the next beta, do you have any idea what sort of time scale we're...
  16. R

    Teensy 4.1: flashing fails every other time

    Hi Paul, are you able to make available a GUI version of Teensy loader with extended timeout for MAC OS (like the experimental version you did for Windows recently) ? It would be a great help to me. Thanks very much.
  17. R

    Help with Teensy Loader

    Yes, what I'm after is a simple standalone GUI program that can upload ehex files to T4.1 without pressing the button on the board, and can run on Windows or MacOS. I sent a message to Koromix last year asking whether there were plans to incorporate ehex abilities into TyUploader, but didn't...
  18. R

    Help with Teensy Loader

    p.s. note that I'm referring here to stand-alone Teensy Loader use, without Arduino running. When called from within Arduino (after compiling), Teensy Loader starts the uplaod automatically, and with the extended 45 sec time-out I get no errors that way now too.
  19. R

    Help with Teensy Loader

    Yes, after I load an ehex file into Teensy loader, it doesn't automatically start the upload to the Teensy. It shows the notice to press the physical button on the Teensy, and disables both Program and Reboot options (regardless of whether Auto is on or off). But my end users won't have access...
  20. R

    Help with Teensy Loader

    Excellent, thanks very much Paul! 45 seconds seems to do the trick for me. No errors so far with any of the T4.1 boards I've been testing, and the program auto-boots after upload every time. Do you happen to also have a MAC/OS version that I could try sometime? Will you make this publicly...
  21. R

    Help with Teensy Loader

    Sure, understood. I'll see what I can do, but so far the modifications I've made to allow me to share the hex have also alleviated the problem.
  22. R

    Help with Teensy Loader

    I opened two new Teensy 4.1 boards and tested those today, as well as retesting two of the boards that I've been developing with, which both showed the problem I've mentioned in this thread. For the new boards, I cut the VCC/USB trace and soldered pins onto one so it could go into my custom PCB...
  23. R

    Help with Teensy Loader

    Thanks Defragster. Maybe I misunderstand your example, but the problem I'm seeing relates to how much FLASH is taken up (mostly) by my large constant data arrays stored there, rather than the RAM2 use for the delay line. And it also needs to be very high usage for me to see the issue. For...
  24. R

    Help with Teensy Loader

    Thanks for the response Paul. Unfortunately I can't share the problem hex file as it stands, as it's commercially sensitive. But maybe I can modify it so it isn't functional but still produces the loader problem. If so, should I send you a dropbox link (as it will be very large)? The system...
  25. R

    Help with Teensy Loader

    Also, I'm not sure who authored the GUI version of the loader (presumably Paul?), but it would be ideal if the timeout value for that could be changed.
  26. R

    Help with Teensy Loader

    Thanks very much - definitely sounds like it's worth a try. Is the Windows version available for download? Another plus might be that it could be an alternative for my end users having to use both Teensy Loader and TyCommander - the latter to force the bootloader to start when using ehex...
  27. R

    Help with Teensy Loader

    I have a large synth project (much too large to post code) that stores many constant arrays containing raw drum samples in FLASH: FLASH: code:361728, data:7052072, headers:9172 free for files:703492 RAM1: variables:94496, code:358152, padding:2296 free for local variables:69344...
  28. R

    Headphone vs Lineout - and grounding issue and change to touchRead()

    With the virtual ground approach there's likely a considerable risk of damaging the HP output if there's any other ground connection between the synth chip and the audio equipment you are connecting to the HP out. If you must use HP out, a better approach is to pass the L and R headphone...
  29. R

    Teensy 4.0 audioEffectDelay - incorrect maximum limit?

    Thanks very much for this. I ran into the same problem about a week ago on a T4.1 where I assumed I could get a stereo delay time of 2 seconds, but could only make it work up to about 1.2 sec until I changed the AudioStream.cpp define value for MAX_AUDIO_MEMORY as you suggested. As long as you...
  30. R

    PT8211 with irregular clocking signals (non I2S) from T4

    I didn't think you would need to do that if you use the code I posted in #27. I don't have time at the moment to double check that but perhaps you could? I recall the (sparse) data sheet does claim the two DAC outputs are synchronously updated, but it doesn't state whether that's done on L or...
  31. R

    SGTL5000 32-PIN QFN exchangeable by 20-PIN QFN?

    In case anyone else is using this chip with separate ground planes, I contacted NXP technical support about this. They advised me that the analog bypass and VAG capacitors need to connect to the ground pad close to the chip to be effective. So that leaves me inclined to connect the ground pad...
  32. R

    SGTL5000 32-PIN QFN exchangeable by 20-PIN QFN?

    The SGTL5000 QFN-20 seems to have just a single ground via the pad on the underside of the chip. I have a layout I'm working on with separate analog and digital ground planes, that join together a long way from my SGTL5000. In that situation, which would be the better ground plane to connect the...
  33. R

    T4.1 large/many data arrays in PROGMEM

    Thanks for that, it looks like the compiler is pretty extensive in its optimization, even looking at the values of the initialized arrays it seems. When I did a max search and print for each of the three arrays it still only reported 100k instead of 300k data, until I changed the initialized...
  34. R

    T4.1 large/many data arrays in PROGMEM

    I'm hoping to store (audio) sample data in flash memory for accompanying playback in a large synth project, but when I load too many files using the progmem declaration for the arrays e.g. using PROGMEM const uint8_t wav1[] = { 0x15, 0x00, 0x15, 0x00, ... } for each array, the compiler hangs...
  35. R

    USBhost_t36 MIDI losing midi note on / off events (Teensy 3.6) during modwheel change

    Thanks again for looking at this Paul. If it's not a buffer number/size effect, is it possible the reason the problem doesn't arise when connecting the Arturia to a PC (and then back out to the Teensy non-host MIDI port) is due to the the same changes that occur when using a hub between the...
  36. R

    USBhost_t36 MIDI losing midi note on / off events (Teensy 3.6) during modwheel change

    A hanging note on a synth means too few note off messages rather than too many. Remember also that the issue only arises when using the host port, and then is remedied by inserting a hub. I don't think the Arturia is at fault.
  37. R

    USBhost_t36 MIDI losing midi note on / off events (Teensy 3.6) during modwheel change

    To localize the problem may require feedback from the receiving teensy back to the host teensy to tell it to stop transmititng when an error occurs (using e.g. known note sequences where the number of notes left on should be zero at the end of the run). I can't see how else you can know whether...
  38. R

    USBhost_t36 MIDI losing midi note on / off events (Teensy 3.6) during modwheel change

    Thanks Paul. Even with this many messages, the code above only produces 'stuck notes' on my T4.1 synth on something like 60-70% of trials.
  39. R

    USBhost_t36 MIDI losing midi note on / off events (Teensy 3.6) during modwheel change

    Also, the Arturia Minilab only causes missing midi events on the Teensy when using the USB MIDI host port. I have never seen the Teensy lose data when going into the serial or non-host USB MIDI port.
  40. R

    USBhost_t36 MIDI losing midi note on / off events (Teensy 3.6) during modwheel change

    Yes it fails with the appropriate message if I put in a syntax error. Hopefully PaulS will be able to try the file with his minilab too and let us know if he sees the same result.
  41. R

    USBhost_t36 MIDI losing midi note on / off events (Teensy 3.6) during modwheel change

    Thanks Paul. I tried the new midi.cpp file, but unfortunately the behavior with my Arturia Minilab seems unchanged. Still seems to work reliably only via the hub.
  42. R

    T4.1 using USB Audio - resource drain?

    I have a large synth project near complete now, which includes a T4.1 and the audio shield (via the Audio library block structure), has 3 way midi connectivity including USB and HOST USB, and has lots of other devices and sensors. So there's quite a lot going on already, with multiple timers and...
  43. R

    USBhost_t36 MIDI losing midi note on / off events (Teensy 3.6) during modwheel change

    Thanks in advance for any time you can spend on this Paul. Would be really excellent to have the USB MIDI host working well for keyboards like the miniLab that have fast midi bursts without needing a hub.
  44. R

    USBhost_t36 MIDI losing midi note on / off events (Teensy 3.6) during modwheel change

    It's very small and cheap "SAMVOL" SY-H20. I'm using the host port on a synth that will be sold to others, so I need a simple/cheap solution for anyone that runs into this problem. Or hopefully when possible, we'll get revised host USB code that avoids the issue.
  45. R

    USBhost_t36 MIDI losing midi note on / off events (Teensy 3.6) during modwheel change

    Thanks for the added info. In my synth code I indeed use a 'while' rather than an 'if' to read the midi stream, but in the test program #13 the loop is so short I can't imagine it matters.
  46. R

    USBhost_t36 MIDI losing midi note on / off events (Teensy 3.6) during modwheel change

    Unfortunately forcing 12Mbit by uncommenting line 267 in ehci.cpp doesn't fix it for me, and I still get 'hanging notes'. In fact it's worse because adding the (unpowered) USB hub then doesn't resolve the issue anymore. So for now, I'm still stuck with having to use a hub to make it work.
  47. R

    USBhost_t36 MIDI losing midi note on / off events (Teensy 3.6) during modwheel change

    So when I use your code AND go via the unpowered hub, the issue seems to be resolved. Thanks very much! This is a tentative solution for me. What is the likely reason it doesn't work if I don't go via the (unpowered) hub? Is the T4.1 talking to the hub at a different rate than when it is...
  48. R

    USBhost_t36 MIDI losing midi note on / off events (Teensy 3.6) during modwheel change

    Thanks for the suggestion, but it doesn't seem to change anything. I have been experimenting with the values of MAX_PACKET_SIZE and RX_QUEUE_SIZE in the MIDIDevice_BigBuffer class in USBHost_t36.h. If I set them both to very large values (4000) the issue is substantially improved, but not...
  49. R

    USBhost_t36 MIDI losing midi note on / off events (Teensy 3.6) during modwheel change

    The only hub I have atm is a small unpowered one, which doesn't work at all when inserted between the T4.1 and the midi controller.
Back
Top