Serial debug output - how to interpret exception message?

al12559 · Mar 15th 2011

On quitting my application on picoCOM2, Kernel V.1-16, I sometimes receive this debug output :

Code

Exception 'Data Abort' (4): Thread-Id=05aa03da(pth=8165a588), Proc-Id=00400002(pprc=81052308) 'NK.EXE', VM-active=057f049e(pprc=81502cf4) 'LowVolumeSpectrometer.exe'
PC=c09827e8(pc2_ni2c.dll+0x000027e8) RA=c098317c(pc2_ni2c.dll+0x0000317c) SP=d103fd80, BVA=d1071bea
Exception 'Raised Exception' (-1): Thread-Id=05aa03da(pth=8165a588), Proc-Id=00400002(pprc=81052308) 'NK.EXE', VM-active=057f049e(pprc=81502cf4) 'LowVolumeSpectrometer.exe'
PC=c003bb54(k.coredll.dll+0x0001bb54) RA=80130520(kernel.dll+0x00006520) SP=d103f610, BVA=ffffffff

What can I read from this message?
My application uses a driver that talks to a module on I2C bus. So it appears that something with regard to pc2_ni2c.dll may get wrong.

Thank you in advance.

fs-support_HK · Mar 16th 2011

When you quit your application, do you make sure that there are no pending I2C transmissions in progress anymore? Otherwise the transmission might try to access memory from your application that is not available anymore.

al12559 · Mar 16th 2011

Thanks for the hint. Such an improper series of actions was probably causing the exception, now it does not show up anymore

Share