Jukka Laitinen

> @jlaitine As I mentioned, the H7 was the only platform that interpreted getpage as the index of writable units instead of erasable units. Can you explain why this was...

> @jlaitine can you please check if this works for you? Hi sorry for the very long response time, I have been busy with some other things. I see that...

1. Hi, here are the most relevant PR:s #17672 #17814 #18387 #18761 #19093 #19158 #19932 #20103 2. Yes, this was my intention, please assing the task to me. I finally...

I didn't check the latest master, my own branch is from March 2021. There doesn't seem to be much differencies, however, so it should be fine with the master. Please...

Any update on this? We have to do ugly workarounds around the issue, exactly for HIL_GPS message handling. It is also theoretically possible to get a crash due to this...

I actually never tested whether this is reproducible in qemu; that would depend on the timer accuracy in qemu/linux. It is really easy to reproduce in real hw within approx...

issue re-produces also in qemu, at least with this simple test. ``` #include #include #include #define read_sysreg(reg) \ ({ \ uint64_t __val; \ __asm__ volatile ("mrs %0, " STRINGIFY(reg) \...

I added a minimal test code above, which can be used in both real target and qemu; it shows the major issue typically within 1 minute.

@Fix-Point Were you able to re-produce the issue with the code I pasted above?

Is the difference just init value or polynomial itself? Maybe keep the default crc32, there is some reason why exactly that variant has selected (I don't know what), but blindly...