Search results

you guys are aware of this discussion on the QNEthernet github, right? It's where I shared to story and lastest code. Hope somebody can pick it up and create a PR. https://github.com/ssilverman/QNEthernet/discussions/80 Well anyway, I'm glad we have ENET2 working on MM.

Thanks KurtE. I'm not blaming the compiler per se other than the compiler creates the issue for me and I don't have any indication on where my code could be problematic during runtime.... there are no warnings or pointers when compiling. a) This runs on my 4 layer pcb with quite good signal...

Hi again. I was involved earlier and wrote a library for the MicroMod using 8080 with Flexio & DMA & lvgl and checked with the digital analyzer of why we have too much beats and found a solution to manually load the shifters etc... see here: https://github.com/leutholl/TFT0784_mm which stems of...

While I have finished my work with great success. One last thing bugs me: I need to use: ENET2_MSCR = ENET_MSCR_MII_SPEED(0x33); // gives around 1.4 MHz while the original divider sets a clock way too high too around 7.5MHz ENET2_MSCR = ENET_MSCR_MII_SPEED(9); // gives around 7.5 MHz why...

[SOLVED SEE BELOW] Many thanks for your valuable information. I have now a solid clock and packets going in. It was a combination of ground bounce and probing (forgot to switch to 1:10). The code was fine. My lab setup was improved and yes the clock is good enough now. However, and I think I...

ok that's very helpful. Thanks a lot! I will try that tomorrow and see the clock on my scope. I'm aware of the probing, grounding etc. issues and still can improve my setup in this regard. The thing is, RXD0, RXD1, TXD0, TXD1 and the other signals look much better - it's only the clock that...

yes I know but this is out of scope for my project it has to be onboard.

yes two drivers one for each library - but I stick the QNEthernet until I get all the settings right and might only then continue with FNET. The library is not the problem nor is it my driver (I guess) - it's either a weird hardware problem or conceptually REF_CLK2 is hard to get right on ENET2...

I'd like to chime in here as I'm working on gettin ENET2 to work on a MicroMod. I wrote a driver for QNEthernet and FNET that uses ENET2 and I can get some packets in (and out?) but it's far from reliable. This is with a LAN8720A PHY. Clock is generated on ENET2_REF_CLK2 and I see a 50 MHz...

Not exactly where you want to do but seeing that this is all about 8080 with FlexIO mode, my library: https://github.com/leutholl/TFT0784_mm might be helpful - however it's using lvgl fonts

Seeing that this is all about 8080 with FlexIO mode, my library: https://github.com/leutholl/TFT0784_mm might be helpful

thanks for the quick answer. I tried to simply turn it on in fnet_user_config.h but realized that NativeEthernet itself uses the ipv4 variants of the commands. So there isn't an easy hack, right?

Is Native Ethernet IPv6 on the T4.1 supported? I have a host that has a IPv6-only stack. Played around with the underlaying FNET config but no luck. If there is support, a small example would do be very much appreciated. If not, is this planned?

ok thanks - will do. One additional questions - this time on the receiving side: What's the effect of the RX buffer when working with callbacks? Wouldn't the callback fire as soon as one frame went through the filters (of the associated MB)? What's the point to buffer on RX side? Using callbacks...

OK thank you very much. However, Can0.events does not extist and Can0.events() doesn't return an int: error: invalid operands of types 'void' and 'int' to binary 'operator&' if ( (Can0.events() & 0xFFF) > 10 ) while ( (Can0.events() & 0xFFF) && (millis - timeout < 100) );

ah - that may explain why it did run at the first stage just until I thought enhancements would be needed for something else. Well, I changed the meaning of my own protocol bytes so that's not a problem any longer. Thanks anyway - it help to understand! But man, I'm still having problem to...

I managed to read out the ESR1 register as a workaround until it'll be in the library. But I have a new problem ;-( I can send exactly one extended frame (2 bytes payload) every 50ms without a problem. I have a Metro timer in my loop(), fill up my CAN_message_t struct and send it with...

Ok! I make sure I bit shift the 0x14 in the filter criteria then. Thanks. I'll do some tests and come back about the filters should I get some surprises. I'll keep the enhanced filtering methods in mind also. I never really understood the needs for FIFO - maybe it's just my application use case...

Thanks tonton81. That's quite clear to me now. Yes I wanted to ask if custom filters/masks would help me here but now it's clear. Since this is my own protocol, I can change the meaning of the bytes. I will change the lowest byte with the next one so that I have use a "steady" right-justified...

Hello everybody. Awesome work and quite extensive features in those libraries! Very good! Thank you very much. I'm using FlexCAN_T4 on a teensy 3.2 with great success! Two teensy's 3.2. with a round trip time of 280uS on 500kBits. This is with diodes and also with CAN transceivers. I have a...

it wasn't enough to get the mdns working. I managed to send correct packages when setting the registers before opening the socket but I couldn't receive anything. I guess because the way SEND_MAC sets the HW MAC (even when not writing to the register before opening) makes it also listening on...

I know what you mean. But here's the thing: UDP implementation is fine and the hardware mac address should be the "regular" one. multicast needs a special generated hardware mac access and while it is set correctly in beginMulticast() the problem is that the SEND command is in endPacket(). To...

Here is the summary: the registers must not necessarily be written before opening the socket AS LONG AS endPacket->socketSendUDP will write the send Command (Sock_SEND_MAC). So this is all which was needed. I changed the following files to introduce an additional method name (having multicast in...

I can't believe it but I've found the problem!!!!!! ;-) in the original socket.cpp in method socketSendUDP the Sn_CR register is written with Sock_SEND (0x20) but as the custom multicast MAC address must be sent along with it the correct value is Sock_SEND_MAC (0x21). The manual says: he basic...

Here is what I'd do: 0) make sure you are non-routed/local-link and both endpoints are on wireline (sometimes wifi will not forward multicast to another segment) 1) Install the mentioned library (which claims to be T3 compatible) 2) Open the RegisteringServices example - alternatively you can...

Yes I do have a arduino (mega und uno) but no ethernet shield. And my application needs Teensy features. I really hope that somebody can help here as I'm new to all this. Would it be a good test to install a old Ethernet library together with a hopefully matching Bonjour library on the Teensy...

I don't have a T3.2 to test. Maybe somebody can run the Bonjour example on a T3.6 and confirm the issue?! After having the libraries sending mdns correctly it turned out that parsePacket on socket 0 (which is the first one and is the one opened with beginMulticast()) will never report any bytes...

Thank you very much! This should solve my "NULL" problem when using a TXT record. I doesn't help about the destination IP and destination mac. But just 5min ago I managed to get it work. Destination IP and Destination MAC is now correctly sent (I had massive impact in the socket and Udp library...

Thanks! I increased the array but obviously it doesn't solve my main problem. Destination IP address is always set to 0.0.0.0. I traced all calls from Bonjour down to the w5100 library and everywhere the correct destination ip address is set - it's lost somewhere. The payload itself looks fine...

Thanks. Which id do you refer to? the mac address array? Using a static address and some further troubleshooting I managed to see a MDNS package on Wireshark. However it is being sent to destination address 0.0.0.0 instead of the multicast address 224.0.0.251. Using DHCP I see malformed...

Hi. My T3.6 with WIZ820io using the adaptor plate works perfectly on DHCP and static ip. I want to add Bonjour support and installed this library (https://github.com/TrippyLighting/EthernetBonjour) which installs and compiles successfully. it reads the MAC address correctly and also I can ping...