We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hi, There's a bug running scripts in uVision 4. Scripts are aborted due to "Cannot access Memory", caused by uVision itself. It is NOT the script that failed but due to (for example) an incorrect device database used by uVision. E.g. both CAN modules have this issue (can be seen simply by opening the CAN device descriptor window and notice "Cannot access Memory" printout).
A (very annoying) short-term solution is to close tab(s) that are incorrect.
I need to fix this by updating the device database (I can do this myself). Therefore I need to understand: How do I tell which address relates to "Cannot access Memory"? Once known, I can remove this from the svd-file etc.
Any ideas are appreciated!! (Note: I'm using Kinetis K61 1MB 120Mhz)
Per, I very much appreciate your reply!
I'm sure you're correct, however that is not the case here.
By simply opening the System Viewer for CAN (Peripherals->System Viewer->CAN->CAN1) the "Cannot access memory" message is printed. Hence, it is uVision itself that has the incorrect "memory map" of CAN.
If I'm able to see what goes wrong (i.e. the address) I can fix this. //bjoern