Thanks for the extensive reply. I was unaware of make lst, I used cc commands that I found by running make under sh -x
Looking at the assembly unrolling the for loop would eliminate the branch at line 26. M4 has no instruction cache and no speculative execution or so, so that would help a bit.
Doing this with a gcc pragma is definitely better. I was unaware of that possibility.
DMA might not be faster. I've seen situations where the setup time exceeded the time needed for bitbanging.
And unfortunately I have no debugger. I think I didn't see that option when ordering my bangle (or should I have gotten it from somewhere else?)
Note also that I am still learning about the ecosystem and software structure.
(and the reason I asked about the flash chip I hoped that its datasheet would also give info on how to drive it).
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.
Hi Gordon,
Thanks for the extensive reply. I was unaware of make lst, I used cc commands that I found by running make under sh -x
Looking at the assembly unrolling the for loop would eliminate the branch at line 26. M4 has no instruction cache and no speculative execution or so, so that would help a bit.
Doing this with a gcc pragma is definitely better. I was unaware of that possibility.
DMA might not be faster. I've seen situations where the setup time exceeded the time needed for bitbanging.
And unfortunately I have no debugger. I think I didn't see that option when ordering my bangle (or should I have gotten it from somewhere else?)
Note also that I am still learning about the ecosystem and software structure.
(and the reason I asked about the flash chip I hoped that its datasheet would also give info on how to drive it).