Andreas Jacob
Hilscher Gesellschaft fuer Systemautomation mbH
new Reset-Register Script available
Hy Folks,
since rcX V2 I got a lot of messages that the customers are getting in trouble by using IRQ's.
Here is a description about the malfunction:
...since we updated to rcX2 we have some strange behavior using Hitop as a debugger. I can run and debug to my liking, but as soon as i stop, reset and run, the system will stand in the function HalExptInitialize. The system will of course hang there.To solve the problem I can only restart Hitop. Any ideas?
Yes, I have an idea :wink:
When you are working with IRQ's in your project then the following behavior will appear:
- You start your project and it is running.[/*:m]
- Now you stop, to debug some parts of your code. (Maybe you are currently in an ISR.)[/*:m]
- Then you reset the registers and set the program counter to the start address again.[/*:m]
Why the project is running again after a complete restart is clear ?! The debugger perform a hardware reset on the CPU during the connection. In this case is also the VIC is relocated.
If you want to restart your project again by using the Reset-Registers script, you should include some commands to acknowledge all pending IRQs.
( I know, that this behavior is different from rcX V1, but not everything was made in the right way in that old version :wink: )
Here you will find now a new reset-register script, which includes the needed lines to relocate the VIC without a target rester or a new start of the HiTOP environment.
[/]