Skip to content

Commit f2fbd1a

Browse files
authored
Add FAQ item about random failures
1 parent 3aa6271 commit f2fbd1a

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

README.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -63,8 +63,14 @@ perform as expected. (For more on exactly what is going on here, see [Hackaday |
6363
without full optimizations can throw off your timing. Always use either `--release`
6464
flag with your `cargo <command>`, or alternatively set `[profile.dev] opt-level = "3"`
6565
To ensure timing matches what your programmed. A dead giveaway of this is when all
66-
pixels go full brightness for every color.
67-
66+
pixels go full brightness for every color.
67+
68+
- Does it mostly work, but sometimes some of the LEDs get randomly colored?
69+
70+
If your MCU does something else, besides driving the LEDs, at the same time (for example communicate via wifi)
71+
make sure you have allocated large enough DMA buffer for your SPI interface,
72+
since any CPU interrupts can mess up the signal timing and DMA fixes that.
73+
6874
When opening an issue about wrong/strange data, it would help if you include
6975
your code (of course) and a capture of MOSI & SCK from an oscilloscope/a logic
7076
analyzer.

0 commit comments

Comments
 (0)