Call to arms | Teensy + WiFi = true

[shawn]

I'd consider signing an NDA for this too.

@sparkfro One other detail is that I couldn't even get them to confirm that such a document existed, NDA or no. (A protocol document.)

 

[sparkfro]

Murata tech support just pointed me to the following:

User Guides ( https://community.murata.com/s/help-tab )
Forum ( https://community.murata.com/s/ )
MyMurata (https://my.murata.com/en/home)

I've got in touch with Infineon, hoping they can give me more direct info. Stay tuned!

 

[sparkfro]

We've completed our internal design review and are ready to order prototypes. Want to make sure I have allocations correct:

@shawn 2 for you
@wwatson 1 for you
@defragster 1 for you

@Dogbone06 @PaulStoffregen @KurtE @mjs513 I haven't seen requests from any of you, but you've all been active in this thread. Would you each like one?

Thanks!

Edit - Please PM me with your shipping address.

 

[wwatson]

@sparkfro - Yes, one for me. Thanks. Will send a PM with address if that is appropriate...

 

[sparkfro]

Also @Dogbone06 would you like to be attributed in our hardware design? If so, please let me know how you'd like to be attributed (eg. username, real name, etc.). Note that we typically license our designs under Creative Commons Attribution Share-Alike 4.0, is that okay with you?

 

[sparkfro]

@sparkfro - Yes, one for me. Thanks. Will send a PM with address if that is appropriate...

Yes please, thanks!

 

[shawn]

Murata tech support just pointed me to the following:

User Guides ( https://community.murata.com/s/help-tab )
Forum ( https://community.murata.com/s/ )
MyMurata (https://my.murata.com/en/home)

I've got in touch with Infineon, hoping they can give me more direct info. Stay tuned!

I went around in circles with them. Then they said it doesn't exist. But I'm not sure I believe that.

 

[sparkfro]

From Infineon:

For SDIO interface in general and with respect to our Linux ecosystem software, the following guide is available: https://www.infineon.com/assets/row...n.pdf?fileId=8ac78c8c8c3de074018c8ba3a9973619

Similar is not available with respect to M-class devices.
However, you can check the WHD SDIO bus protocol source on the initialisation and other implementations.

whd-expansion/WHD/COMPONENT_WIFI6/src/bus_protocols/whd_bus_sdio_protocol.c at 0f13160971d02e7b1d4bd569da0d5eb96f2692d9 · Infineon/whd-expansion

Support wifi chipset on 3rd party platform as IMXRT platform - Infineon/whd-expansion

github.com

FYI: WHD is the driver available for M-class RTOS based devices for communicating with the Infineon Wi-Fi chips, here, CYW43439.
WHD expansion is the library for third-party MCU integration that adds WHD flavor for third party along with other necessary middleware for applications.

 

[wwatson]

QNEthernet_WIFI_0.36.0 is available here:

GitHub - wwatson4506/QNEthernet_WIFI at QNEthernet_WIFI_0.36.0

A version of QNEthernet Adapted to USE with the CYW4343x WIFI device. - wwatson4506/QNEthernet_WIFI

github.com

Quite a few changes needed to be made to the CYW4343W driver to make it work with the new QNEthernet library. The main one was moving all of the CYW4343W init and begin code out of the CYW4343W driver file into a seperate file. So now the init and join methods are done with one call to "WIFIinit(const char *ssID, const char *passphrase, int security)".

@shawn - The changes you made to QNEthernet V0.36.0 had some very positive results for using the two QNEthernet ping sketches.

Using simplePing.ino:

Starting...
Please Wait...
MAC = 70:87:a7:10:64:b5
Waiting for local IP...
Setting link up
    Local IP    = 192.168.4.26
    Subnet mask = 255.255.252.0
    Gateway     = 192.168.4.1
    DNS         = 75.75.75.75

Pinging arduino.cc (18.238.238.4)...
1. Time = 19 ms
2. Time = 20 ms
3. Time = 16 ms
4. Time = 32 ms
5. Time = 17 ms
6. Time = 15 ms
7. Time = 16 ms
8. Time = 16 ms
9. Time = 25 ms
10. Time = 15 ms
11. Time = 16 ms
12. Time = 16 ms
13. Time = 16 ms
14. Time = 24 ms
15. Time = 20 ms
16. Time = 16 ms
17. Time = 18 ms
18. Time = 19 ms
19. Time = 22 ms

and ping.ino:

Starting...
Please Wait...
MAC = 70:87:a7:10:64:b5
Waiting for local IP...
Setting link up
    Local IP    = 192.168.4.26
    Subnet mask = 255.255.252.0
    Gateway     = 192.168.4.1
    DNS         = 75.75.75.75

Looking up "arduino.cc"...
IP = 18.238.238.12
1. 64 bytes from 18.238.238.12: seq=0 ttl=245 time=24 ms
2. 64 bytes from 18.238.238.12: seq=1 ttl=245 time=15 ms
3. 64 bytes from 18.238.238.12: seq=2 ttl=245 time=15 ms
4. 64 bytes from 18.238.238.12: seq=3 ttl=245 time=17 ms
5. 64 bytes from 18.238.238.12: seq=4 ttl=245 time=18 ms
6. 64 bytes from 18.238.238.12: seq=5 ttl=245 time=18 ms
7. 64 bytes from 18.238.238.12: seq=6 ttl=245 time=26 ms
8. 64 bytes from 18.238.238.12: seq=7 ttl=245 time=16 ms
9. 64 bytes from 18.238.238.12: seq=8 ttl=245 time=17 ms
10. 64 bytes from 18.238.238.12: seq=9 ttl=245 time=15 ms
11. 64 bytes from 18.238.238.12: seq=10 ttl=245 time=15 ms
12. 64 bytes from 18.238.238.12: seq=11 ttl=245 time=15 ms
13. 64 bytes from 18.238.238.12: seq=12 ttl=245 time=15 ms
14. 64 bytes from 18.238.238.12: seq=13 ttl=245 time=26 ms
15. 64 bytes from 18.238.238.12: seq=14 ttl=245 time=16 ms

They would not work previously. Nice fixes
Tested all of the examples. They all compile without error and most of the sketches that I could test worked (some of the sketches I have no idea yet what they are supposed to do) That will come later. MAYBE! Also tested most of the original Arduino Ethernet sketches found at:

GitHub - wwatson4506/QNEthernet_WIFI_Examples: These are some of the original Ethernet library examples modified for QNEthernet_WIFI.

These are some of the original Ethernet library examples modified for QNEthernet_WIFI. - wwatson4506/QNEthernet_WIFI_Examples

github.com

Now back to the CYW43439 research...

EDIT: Just noticed that the README.md file needs to be updated...

 

[shawn]

@sparkfro thanks for trying. Looks like the only source of information is their driver code. Either they don't know what's being asked, they can't talk about it, or it actually doesn't exist.

 

[sparkfro]

Infineon also linked me to this for Bluetooth: https://infineon.github.io/btsdk-docs/BT-SDK/AIROC-HCI-Control-Protocol.pdf

 

[shawn]

Infineon also linked me to this for Bluetooth: https://infineon.github.io/btsdk-docs/BT-SDK/AIROC-HCI-Control-Protocol.pdf

That's for their Bluetooth stuff, not the WiFi chip. (Oh, you already say that...)

 

[mjs513]

Not for nothing but this is the link for the zephy implementation for Infineon airoc control:

https://github.com/zephyrproject-rtos/zephyr/tree/main/drivers/wifi/infineon

Think I posted this before - maybe has some clues

 

[PaulStoffregen]

haven't seen requests from any of you, but you've all been active in this thread. Would you each like one?

Thanks, but I should decline. I'm currently working on another project and probably can't do much at this time.