In my case a pointer was corrupted which was causing a read to out of bounds area... ARM is downplaying the significance of this bug I believe... from the sounds of it though you may be encountering something else entirely... after we fixed the ca...
Do you just need the erreta?to anyone wondering it basically just says there is an issue with the cache and that random data corruption can occour at any time dependent on some internal timing issue... there is no workaround and to disable all caches...
More importantly, there probably isn't some other horrible memory corruption going on elsewhere for the same reason, which isn't going to come back and bite me eventually.I hate to break it too you but we have experienced memory corruption going on e...
Just for the record we experience the same issues with ethernet, slow usability before finally locking and being reset by the WDT. Both CycloneTCP and LWIP experience the same issue...If anyone has a workaround please share...Kind Regards,Jon Mundall
