Hi
At a first glance it looks as though the interrupt vector is jumping to the address 0 (like a null pointer) where there is emply FLASH. I assume that you are downloading to and debugging from RAM(?)
Are you sure that the Vector Base Register is set up correctly (are other interrupts working?).
mcf5xxx_wr_vbr((unsigned long)__VECTOR_RAM); // set VBR to work with vectors in RAM
If you are working with interrupt vectors in RAM then the vectors.s file will not actually be used. It is only used if working from FLASH where the vector table is fixed - in this case mcf5xxx_set_handler() will also not be of any use. Since it looks more as though the vector table has a null pointer entry I would suspect that it is somewhere in RAM but not being initialised correctly. [check the value of VBR in the debugger. Then open a memory window at that address and check the interrupt vector addresses which are there.]
Note also that you can activate I2C support in the uTasker code by activating the define IIC_INTERFACE in config.h.
It is configured by
IC_ICR_0_17 = IIC_INTERRUPT_PRIORITY; // define interrupts level and priority fnSetIntHandler(IIC_VECTOR, (unsigned char *)_IIC_Interrupt); // enter the handler routine IC_IMRL_0 &= ~(IIC_PIF_INT_L | MASK_ALL_INT);
where fnSetIntHandler is equivalent to the one you are using.
The interrupt level and priority are user configurable in app_hw_m5223x.h (in SP4) and is defined as default to (INTERRUPT_LEVEL_2 | INTERRUPT_PRIORITY_2).
If you also activate TEST_IIC in application.c the code will read and write test data from/to an IIC EEPROM - see the description:
http://www.utasker.com/docs/uTasker/uTaskerIIC.PDFRegards
Mark
www.uTasker.com