Yes - it sounds nuts but I have tested both hardware SPI and memory mapped QSPI. At least for the read patterns we do, it's still fastest to bit-bang using 2 bits for data, so that's what we do.
Pretokenising complete strings is an interesting idea, and could help in a lot of areas. Right now all we do is turn tokens into single bytes. I guess we could store strings like: TOKEN_STR,LEN_HI,LEN_LO,raw string bytes and could handle that pretty easily. If we spotted atob(...) we could just decode that and store the raw data as well.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Yes - it sounds nuts but I have tested both hardware SPI and memory mapped QSPI. At least for the read patterns we do, it's still fastest to bit-bang using 2 bits for data, so that's what we do.
Pretokenising complete strings is an interesting idea, and could help in a lot of areas. Right now all we do is turn tokens into single bytes. I guess we could store strings like:
TOKEN_STR,LEN_HI,LEN_LO,raw string bytes
and could handle that pretty easily. If we spottedatob(...)
we could just decode that and store the raw data as well.