Looking at eeprom.c this is the line that generates that error message.
https://github.com/PaulStoffregen/cores/blob/3c442f9c67ee785ddad921ff5d0a3ebe5a9682ca/teensy4/eeprom.c#L53
Looks like you want to set it to 3824....
Right, the button shorts (to GND) the trace that the program pin is connected to, so pressing the button and shorting the program pin to GND do the same thing. A quick press will put the Teensy into programming mode...
No worries, I would hope it was just a strange accident that it was pressed between 13-17 seconds and not that something shorted the program pin for that amount of time.
The Teensy has a LED Blink restore feature if you hold the program button down between 13 and 17 seconds. Is there a chance that this happened? It would also happen if the program pin was pulled low for this time...
I have been using this library ever since our last message and everything has been pretty smooth so far. I did find one issue today when testing client reconnection, if you unplug and plug back in the ethernet cable...
I do something similar with a device that communicates over RS485. In my case the device has a model which has ethernet but we only have the RS485 model, I was able to use their software and connect to the Teensy over...
Okay so what I am seeing is by design, just call flush whenever data is time sensitive and if not, I can let the library buffer and send the data when the timer hits to be more efficient? I will try using flush and make...
I tried making the switch over to QNEthernet this week but I had a few issues/questions.
First issue I noticed was that the data that I was sending from the Teensy to the PC wasn't being received fast enough, I did...
Great! After playing around with it I am able to read the program on the flash simply by reading a variable pointed to the flash address, I thought I would need a special function to read from the flash.. does the cpu...
Thanks for the clarification and all your work on this, this should work perfectly for my needs I just need to send the file over ethernet. Assuming I verify the program with either a CRC or sending back each line, is...
No worries, in my case I am not using LittleFS, I just wanted to use the flash space between the program and EEPROM for buffering the new program. With the default offsets I was having the issues described above....
I came across the same issue as @ipaq3115 when testing this, I also use the EEPROM in my program and when trying to flash I get "buffer = 0K FLASH (601FC000 - 601FC000)". I decided to use a ram buffer instead and...