Hi John,
Welcome to the Bascom Forum!
I'm still sitting at the airport. Mechanical failure delay for our plane. 6.5+ Hrs delay :(
I was about to drive home and get my chip to take on the trip, now that I have two new tasks to perform, (rechecking/changing the Interrupt Vector Address, and seeing if I can do Xmega debugging over the PDI interface with Studio, as I don't have a JTAG programmer).
Darn, I could have made it home and back to the airport several times!
Anyway, I am glad you noticed the Interrupt Vector is incorrect, that means the problem is easily correctable!
I had prior discussions with Mark about the def.dat table, and I believe I correctly located the TCC4 addresses, formatted them appropriately, and entered them into the def.dat file correctly; but apparently I made a mistake somewhere within that process.
Question: Did you check the Vector Interrupt Table via JTAG, or just by looking at the def.dat file? The reason being, IIRC, the entries were an Index, the Interrupt Name used for linking from the Bascom program for the given interrupt, the Interrupt's address, the bases address of the interrupt priority flags, (0, 1 = lo, ...), and finally a flag address for the simulator. In the Intr Vector Table in the def.dat file I did not bother changing the last item, as I don't use the simulator, I run and debug everything on real hardware. Bottom line: Igone the last entry for the added interrupts in the def.dat file.
Your analysis matches my findings. The TCC4 is running, and is rolling over at the CCA designated TOP. I also noted that the Main Loop LED flasher slows down when one of the interrupts is enabled, indicative of something actually running, albeit not my ISR.
Oh well, no hardware to play with for a while...
Take Care,
JC
↧