Sipeed M1W dock and ESP8285

Hi - I noticed in Sipeed M1W datasheet v1.1 on page 3 where Pin Map layout is
There are 4 additional WiFi pins:

Are they for data buffer transfers or it is interface similar to DM9051 which is SPI to WiFi ?
They told me WiFi on that module works with AT commands but UART transfer is very slow
so I am guessing those pins are used for faster transfers - but how.
Anyone could help me with the information and examples maybe?


M1w 1.1 add extra SPI wire to enable fast spi transfer.
but the program isn’t open, you need implement your self

You mean the firmware image on esp8285 doesn’t have any functionality ready to use with WiFi-SPI ?
In that case it is kind of very inconvenient

the spi interface is reserved for commercial usage, opensource usage is mostly AT command.

Recently I was able to compile and run WiFi communication esp8266 rtos sdk examples on esp8285 .
Now I am thinking what would be the best way of communicating with K210.
I am not sure if all modules have 8285 spi pins exposed but those with spi will have fastest transfers.
So assuming I am sending TCP stream from esp spi and then K210 reads them based on interrupt response. However I don’t know what function would be the best here for receiving the data.
Standalone SDK doesn’t have so many functions as RTOS so I’d go with that.
I appreciate any suggestions. Thanks!

Hi, if you use the standalone C SDK programming for Kendryte you could get up to 2.5Mpbs using UART between Kendryte K210 and ESP8285, right now i´m working with 1.5Mbps and it works fine, the only problem a have is that some times (randomly) the ESP8285 gets frezzed for 5 to 60 seconds waiting for a TCP response send by the server.

I could’t find a higher speed of data transmition between a MaixDock and a Web Server using 2.5Mbps instead of 1.5Mbps, thats why I’m working with 1.5Mbps, I think the problem is the quality and the strength of the WIFI signal sent by the WIFI Router.

The AT command specification for ESP8285 is the same as the ESP8266, beware of that documentation, is not clear and have omisions with the description of errors when sending messages via TCP.