Search results

  1. S

    Teensy 4.1 QNethernet requests and SD problems

    After a bit more tweaking, the performance has been improved quite a lot: Threshold of available space before write dropped to 1460, delay(2); after write changed to yield(); while (f.available()) { // Check Connection if (!client->connected()) { success = false; break; }...
  2. S

    Teensy 4.1 QNethernet requests and SD problems

    Example debug dump for a jpg Client connected: 192.168.2.100 Client count: zu GET /website/media/posts/2/homepage_2.43.jpg HTTP/1.1 requestline: GET /website/media/posts/2/homepage_2.43.jpg HTTP/1.1 Host: 192.168.2.177 header: Host: 192.168.2.177 Connection: keep-alive header: Connection...
  3. S

    Teensy 4.1 QNethernet requests and SD problems

    Hi nieuwemaker, I am having very similar issues serving multiple files, no just from SD card but also from flash. I have created the following minimalist webserver using the ServerWithListeners example by Shawn as the starting point. It is working reliably for me, however in the much more...
  4. S

    EHEX has EOF twice in the file - Confuses FlasherX

    In the end, I only needed to remove the check for the flash ID, since this will not work with encrypted hex. Working nicely now with ehex files from SD card and web-based GUI and filemanager.
  5. S

    EHEX has EOF twice in the file - Confuses FlasherX

    @Dogbone06 did you have any issues with FlasherX aborting due to bad hex lines or invalid hex code? (removed a chunk of verbage here after reading Paul's document relating to ehex files) Did you need to comment out any of the hex integrity checking in the update firmware function? ie in...
  6. S

    EHEX has EOF twice in the file - Confuses FlasherX

    Thanks all for your work on this. I intend to implement flasherX into my application to perform remote updates with a locked T4. A question for @joepasquariello : I already have a webserver that allows the upload of files to the SD card over ethernet. Would you recommend implenting flasherX to...
  7. S

    TyTools / TyUploader or similar for lockable Teensy ?

    Hey RVH, I have the same issue as you but get around this by using TyCommander to trigger the bootloader and then the Teensyloader does it's thing. Have a look at page 17, section 6 on this user manual I have for a product using the T4.1...
  8. S

    Recommended method to trigger programming without access to prog button, with ehex on locked T4.1

    I have a product design that uses a locked T4.1 and no easy access to the prog pushbutton. Therefore I am looking for a method to trigger the bootloader and programming with an ehex via the usb port. Current idea is to use TyCommander to trigger the programming which Teensy loader. It seems...
  9. S

    Cutting VUSB to 5V jumper trace too deep?

    Looking at the board again, the cut made is quite shallow so I suspect something else has gone wrong with this board.
  10. S

    Cutting VUSB to 5V jumper trace too deep?

    I use teensy 4.1s in a prodct of mine and need to cut the VUSB to 5V jumper. This has worked fine for a couple of boards so far but the last one I just cut I fear may have damaged something. How deep can one cut into the surface before the likelyhood of damage?
  11. S

    Dead editor

    Considered using Platform IO? I'm using it with Teensyduino 1.59 very happily and with VS Code quite a nice editing environment etc.
  12. S

    Configuration of I2C buses - issue of multiple start bits on IC2 in single message

    Capture of writing 255 to port with readback of 255
  13. S

    Configuration of I2C buses - issue of multiple start bits on IC2 in single message

    So I've been discussing this issue with a person from Microchip and decided to look for any other transmissions on the bus that might somehow get the device into an odd state. There was a burst of data being sent to address 0x62 (the MCP23008 is at address 0x20) for a graphics LCD library. Going...
  14. S

    Ever had a week where nothing works? Mine has to do with the ADC MCP3564 chip

    Maybe it's worth hooking up the IRQ to confirm that conversions are being completed?
  15. S

    Configuration of I2C buses - issue of multiple start bits on IC2 in single message

    Capture below shows the result of writing 255 to the port when configured as output, then immediately reading back the port value. Bit 2 does NOT get set but all others are.
  16. S

    Configuration of I2C buses - issue of multiple start bits on IC2 in single message

    Checking that all bits are configured as outputs during initialisation by reading back register 0x00 ie IO direction register. It confirms that this has been set to 0x00 ie all bits as output. This is on I2C bus 2 which is showing the issue with bit 2.
  17. S

    Configuration of I2C buses - issue of multiple start bits on IC2 in single message

    Another data point that makes it a bit weirder I think, turning them all on in a single message ie 0xFF still results in gpio2 not being set, only on I2C2. Reading back the port value I get 251, so bit2 is not set. Will look more into the bit directions register setting, as it really looks...
  18. S

    Configuration of I2C buses - issue of multiple start bits on IC2 in single message

    Hi MarkT, yes that would be the most plausible if it didn't work just fine when I put it back onto I2C1. Issue repeats for multiple boards of that type and another board design. Also with MCP23008 of different production batches/years.
  19. S

    Configuration of I2C buses - issue of multiple start bits on IC2 in single message

    Ok good point. However the problem I have is this is the only difference I can see between the two buses and this is the bus that gio2 on the expansion chip cannot be activated. The traces look identical otherwise I believe.
  20. S

    Configuration of I2C buses - issue of multiple start bits on IC2 in single message

    UhClem, thanks for making me take a closer look, you are definitely correct..... and this may help me find the root cause of the issue. Those blips in the SDA2 line are not actually a start or a stop and maybe I have something else in the system driving that line. Will look into that further...
  21. S

    Configuration of I2C buses - issue of multiple start bits on IC2 in single message

    I have a support request in with Microchip, lets see what they say. Missing from the initial submission, I am using the Adafruit library: https://github.com/adafruit/Adafruit-MCP23008-library Thinking of changing over to this one as it is still being maintained...
  22. S

    Configuration of I2C buses - issue of multiple start bits on IC2 in single message

    Hi All, I have a project with a number of MCP23008 digital io expanders on both the I2C bus 1 and bus 2. This is on a Teensy 4.1, running teensyduino 1.59 and being built in Platform IO. Curiously I am not able to set the GIO2 output on when the devices are on bus2, bus 1 is fine. The only...
  23. S

    Multi-channel Fast Analogue Capture and Stream

    The block diagram above shows an ADC chip by TI that has 4x internal ADCs which therefore allows it to sample all channels at the same time, eliminating and phase/time shift between samples. This may be beyond what you are trying to do, I'm not sure. The reason I suggest you inject a different...
  24. S

    Multi-channel Fast Analogue Capture and Stream

    Hi Roni, we will need a bit more information to be able to assist you. Directly connecting piezo sensors to the Teensy ADC inputs is not a great idea since Piezo devices can produce quite high voltages without suitable clamping/limiting circuitry in place. So it is possible you have damaged the...
  25. S

    Multi-channel Fast Analogue Capture and Stream

    Yes Rezo, good point (I'm using this for a large RAM buffer at the moment) Might need to go to a full custom Teensy4.1 board to get access to the FlexIO for some really high performance ADC.
  26. S

    Multi-channel Fast Analogue Capture and Stream

    Sounds like you might need a QSPI or parallel data interface to the ADCs. I have a system sampling 4 channels at 128ksps and 16bit with a 50MHz SPI interface, and this bus would not be able to support 200ksps. If a QSPI port can be made available on the Teensy 4/4.1 this would be very helpful to...
  27. S

    Thoughts on allowing T4.1 lockable to run ehex but not permanently locking

    Thanks guys, fully locked it will be.
  28. S

    Thoughts on allowing T4.1 lockable to run ehex but not permanently locking

    hi defragster, just to confirm, the key is written to within memory (fuses?) in the main processor prior to locking, so is there any way without going to extreme lengths that the key could be extracted? I understand JTAG is still enabled until the final lock process is undertaken. Is there...
  29. S

    Thoughts on allowing T4.1 lockable to run ehex but not permanently locking

    Hi jmarsh, is that because the key is kept in the location that is locked off? If so this is of course a big oversight on my part.... :-(
  30. S

    Thoughts on allowing T4.1 lockable to run ehex but not permanently locking

    I have a product I want to sell commercially soon andafter some discussion here previously I will distribute the firmware as an ehex. All seems well and I have the product running an ehex just fine, but I realise that if I do not perform the final locking process it can still run a normal...
  31. S

    length of filename extensions for sdfat

    confirming I can read *.json files with this library no problem
  32. S

    length of filename extensions for sdfat

    I'm developing using Teensyduino on Platform IO for a T4.1 and using sdfat file system. I know that it supports long filenames but does it also support more than 3char filename extensions? Reason I would like this to be true is for json, yaml etc files for configuration etc
  33. S

    100 +/- inputs and outputs (analog?)

    Hi Gef Those expansion devices over I2C will not be much good at all for analog signals. They are really suitable for low speed digital IO. There are SPI versions of these devices available that can obviously increase the update bandwidth however this still would be poor. It looks like you are...
  34. S

    SPI frequency too low for real-time data acquisition

    Hi bigdlin, For a data point, my board has no issue running the SPI clock at 50MHz for the ADC I'm using with a Teensy 4.1.
  35. S

    SPI frequency too low for real-time data acquisition

    This seems very curious and not the norm: Typically the SPI bus is shared and additional CS lines are used to select the chip you want to talk to. Why are they doing it this way? bigDlin do you have them wired this way? Is it working? Also I meant to ask previously, have you tried running...
  36. S

    SPI frequency too low for real-time data acquisition

    That chip produces 16 bit results ie 16bit multiplexed ADC.
  37. S

    SPI frequency too low for real-time data acquisition

    Is the data actually 32bits? or is it a 24bit converter sending a 4byte result? Depending on the converter, some will allow the result (eg ADC) to be sent as 3 bytes (24bits) instead of the 32 saying you 25% throughput.
  38. S

    Need advice on PCB manufacturers

    I had been using PCBWay for everything up until recently when they dramatically increased their pricing on 4 layer boards. A 100mm x 100mm 4 layer board from PCB Way is about 4 to 5 times the price of the same design from JLCPCB which I found incredible. Quality from both has been great so...
  39. S

    Writing Data to Teensy 4.1 microSD

    Looking at your loop, it seems that you will keep opening and writing to your file indefinitely. Is that why you have append as an option/mode?
  40. S

    [no Teensy?] +/-5V power from USB

    Hi DrM My ADC input full range is only +-1.2V hence the +-4V is plenty of room. I am using these as my front end buffer amplifiers. They are working very well in my current application...
  41. S

    [no Teensy?] +/-5V power from USB

    Hi DrM Looking good. How much current and at what voltage ripple are you getting out of your design? I have now used a charge pump device to do something similar but with 5V input and +-4V outputs. I have a DAQ board which requires a bipolar supply for some front end op-amps...
  42. S

    Interfacing ADS7828 to Teensy 4.0 via I2C

    One thing to think over is that the Teensy 4.1 is not 5V tolerant so if at some time you have accidentally pulled up to 5V maybe you have damaged the I2C bus IO on the Teensy? Do you have an DSO or logic analyser to look at the signals?
  43. S

    Interfacing ADS7828 to Teensy 4.0 via I2C

    That looks correct. However one issue you need to be very careful of is ensuring that SDA and SCL are not pulled up to or being driven to 5V. Is your ADC running off 3.3 or 5V?
  44. S

    Interfacing ADS7828 to Teensy 4.0 via I2C

    In my working system I used the address 0x48, 0x49 etc
  45. S

    Thoughts on importance/need for encrypted firmware ie locked Teensy

    Hi Paul, I don't have any issue with the process you have created at all. My question for the forum is how important people feel it is to use this for a product that is going out to consumers. One thing that does weigh into this a little is the availability of the lockable boards vs the std...
  46. S

    Interfacing ADS7828 to Teensy 4.0 via I2C

    Hi Smuscat, Recommend you look at the pullup resistors as well (not sure if you have done so?) Are your connections made to the SDA0 and SCL0 pins? This is important as you have not defined pins other than default in your code. I also not that in your wait for data, you are triggering once a...
  47. S

    Thoughts on importance/need for encrypted firmware ie locked Teensy

    Hey Mark, Thanks for your considered response. Your product sounds very nice! I can see for products that have actuators or potential safety issues then preventing other versions of firmware from being loaded is a very good reason to enable the locked/encrypted mode. I am happy for users to...
  48. S

    Thoughts on importance/need for encrypted firmware ie locked Teensy

    I have a product I've developed for which I use the Teensy 4.1, it is a data acquisition and related product. I was initially planning to provide these with the locked version of the Teensy 4.1 so I could prevent people from copying the firmware onto other teensy boards but this seems a bit...
  49. S

    Interfacing ADS7828 to Teensy 4.0 via I2C

    Hi smuscat, I have done this exact thing recently and managed to have it working well now. I would check that you have appropriate pull up resistors on the I2C lines. I had 4k7 resistors and was running a clock freq of 400kHz and with the length of my cables and number of devices on the bus...
Back
Top