What could cause interrupts to reset the device or jump to incorrect addresses when using extended memory?
In CCE v3 interrupt code needs to be placed in lower Flash memory for interrupt to function correctly. If it is not in lower Flash memory, unexpected resets/hangs may occur. The reason for this is that interrupt vectors have only 16 bits available hence only the lower 16 bits of these addresses are saved as interrupt vector. If the interrupt routine is in upper Flash memory, only the lower 16 bits of the address is taken and the device jumps to the wrong address. The compiler tools in CCE v3 do not force the interrupt routines into low memory. So when code exceeds 64k the linker is free to allocate to upper Flash. If you are running into unexpected resets/hangs, you can confirm if this is the cause of your issue by generating a link map file and looking at whether the code (.text) sections for the interrupt functions are being placed in upper Flash memory.
Related Questions
- I understand that NTA Stealth can be operated from a USB memory device to identify past Internet leads. Is there an easy way to configure a USB memory device for use with the NTA Stealth program?
- Can the historical storage memory of 20 values in the device be erased?
- Can the historical storage memory in the device be erased?
