Search results

Subject line pretty much says it all. I'm thinking about trying to hook a couple of USB devices, to a Teensy 4.1 using the Host connector. Can I put a USB hub in there to allow me to attach both devices?

Yeah, the 4k is the default stack for single threaded setup() / loop() code. I read a fairly sizeable thread on the ESP forums about this. They were also proposing a task as a way to overcome the default 4K stack limit. In my case, that would have been massive overkill, since I only have one...

The output for a sketch build I'm working on looks something like this: Memory Usage on Teensy 4.1: FLASH: code:358444, data:48696, headers:8600 free for files:7710724 RAM1: variables:53952, code:279296, padding:15616 free for local variables:175424 RAM2: variables:91424 free for...

It's worth noting that the vast overwhelming majority of my git experience was working in a corporate environment, so I'm not as familiar as all that with working on open source projects. So it's best to view my caution as just being polite, and thinking I need to check with the repo owner...

The change is to add a config entry for the Fujitsu 4Mb FRAM. This is a link to the commit on github in my fork of LittleFS. https://github.com/dgnuff/LittleFS/commit/2e5fb4e89cd1f81e4d4d53d8627062c635976c25 BTW, I forked Paul's repo rather than mjs513's since mjs513's is itself a fork of...

I'm looking at setting up a LittleFS filesystem on the current project, and the local LittleFS package seems like the obvious way to go. However, I'm using an Adafruit breakout with the 4Mb Fujitsu FRAM chip on it, which isn't currently supported by LittleFS. It's a one line change (yeah...

Finally got it done, and it turned out not to be worth the effort. Removing MDNS and IGMP only saved 7k of code. Worse yet, I had to do a bit of hacking in the source itself, since the removal of IGMP caused a couple of undefined references. While I was able to get a successful build by...

Probably not an option. Among other things, this project has code to determine the time of civil sunrise and sunset on any given day at (almost) any point on Earth. That code is very highly dependent on floating point being available, I'm fairly certain it could not be reliably implemented...

The footprint estimate is very crude. Starting from the build that produced the numbers in the first message I posted, I simply stubbed out the socket layer so all functions were empty, removed QNEthernet.h from all files where it appears and then fixed the few errors that showed up as a...

I'll take another peek at what's going on by throwing Sysinternals ProcMon at the problem. That will capture the whole command line, and let me save to a file for later analysis. I need to take a break from this for a day or so, so I'll drop back in a while when I've figured what's going on...

1>------ Build started: Project: SmartHome, Configuration: Release x64 ------ 1>Memory Usage on Teensy 4.1: 1> FLASH: code:195256, data:55244, headers:8568 free for files:7867396 1> RAM1: variables:59456, code:172008, padding:24600 free for local variables:268224 1> RAM2...

I did as suggested, found a sym file, and gave it a good look over. Filtering out everything in section .text.itcm and then doing a column block sum on the sizes came up with almost exactly the count of bytes in RAM1, so that looks like I'm headed in the correct direction. I then did a deep...

1>------ Build started: Project: SmartHome, Configuration: Release x64 ------ 1>Memory Usage on Teensy 4.1: 1> FLASH: code:468856, data:78796, headers:8376 free for files:7570436 1> RAM1: variables:88160, code:434672, padding:24080 free for local variables:-22624 1> RAM2...

Yes it did. I'd seen the difference when looking at the code on my original analysis. Given that connected() requires both the connection to be closed and the remaining buffer to be empty, that's the one I'm finding works better for me. operator bool() will return false as soon as the...

From the perspective of my application, switching from new/delete to use of a preallocated pool doesn't change much of anything. When a connection is established, I have to get an EthernetClient from somewhere, and assign it to the class instance in my code that's handling this connection...

Agreed. Trying to combine those two sockets doesn't change anything in QNEthernet. The complexity gets added in the application itself, and without a very long essay on exactly what it's doing and how it's doing it, that's not so easy to explain.

I wrote: I can't now eedit the post, but what I should have said was "I can't be certain that it won't start returning false early in the process ..." That should make a lot more sense, and correctly describe the question I have.

This code reproduces the problem: #include <QNEthernet.h> using namespace qindesign::network; EthernetClient client; bool connected = false; void PrintString(char const *s) { Serial.print(s); } // the setup routine runs once when you press reset: void setup() {...

The documentation for QNEthernet::EthernetClient::close() notes that it closes the connection, but does so in a non-blocking fashion. Overall, I really like QNEthernet, because just about everything can be made non-blocking, which is something I find essential for the overall architecture of...

I'd thought about doing that on the Wiznet 5500 chip, and indeed I do agree it's possible. However I decided against it, because it significantly increased the complexity of dealing with inbound data. If it's from a "known" address, it goes back to the appropriate sender, but what to do with...

Thanks for the replies. In practice, I should be able to comfortably fit in 32 total sockets. If I read the source from the Github repo correctly, the default is 8 each UDP, TCP listening and TCP connected. I can easily get by with 16 TCP connections, leaving the other two at 8 each, giving...

I'm currently working on a project, and I'm using a Wiznet 5500 for ethernet connectivity. I'm becoming increasingly unhappy by the constraint imposed by that chip where it only allows 8 sockets open at once. For a number of reasons, not the least of which is the additional CPU horsepower, I'm...

It took a couple of iterations, the first case I made was a 1mm wall thickness, and it just felt too flimsy. For V2, I rebuilt it with a 2mm wall thickness, and it works like a charm. The one downside to the design I created is you have to glue it closed which means if you ever want to get the...

I've recently created a couple of 3d printable models on Tinkercad, over at https://www.tinkercad.com/ that are cases for the Teensy 2. They might be editable to work with the Teensy 3, however I'm not that motivated to do so at the moment. That will probably only change if I design something...

Thanks for the information. I've got a first pass at the model complete, and have one on order from Shapeways. If it works out correctly, I'll create another thread with a link to the model, so that other people can work with it.

Apologies for the thread necromancy, since this is over 4 years old, but is the Teensy 2 also a 1.6 m PCB? I'm in the process of modeling a 3d printable case for the Teensy 2 over on Tinkercad, and need to know the PCB thickness for that. For now, I'm going to proceed assuming it is 1.6 mm, I...