fredizzimo
fredizzimo
@bremoran, yes you are right. I believe the trace port would be quite useful for debugging this problem though. But it's connected to tx0, which is used for the UART...
Thanks a lot, There's some seriously dangerous code there in the transport protocol, mostly because I'm used to relying on C++ and type safety. I also wanted to keep the...
I'm not able to look into the issue properly right now, since I'm at work. One thing that might help, is the map file in the build folder, which should...
The pointer might not be exactly the same as the object pointer, since as the name implies, there's three different buffers, triple_buffer_begin_write_internal, is supposed to return a valid pointer to...
I have now manually verified that the pointer appears to be calculated correctly. However for some reason the size is 20, while it should be 17. The object in question...
Yes, I will add that sanity check in any case, even if I fix the bug. But I will probably just ignore the data if the size is wrong. The...
I was able to confirm the bug on the left hand size. The size suddenly went from 18 to 39. But just for one packet. So there's either some other...
It's certainly possible, the crc32 check is not a very strong one, but still the expected error rate is 2.3E-10. And add that we should expect very few errors on...
One thing that I noticed, is that it always gets corrupted to the same 39 value. So it's probably something else writing it there, rather than a problem with the...
Yes, the left hand side (or the master), receives the keyboard_matrix object.