I have a PSoC with debugging functionality ( I am sure other MCUs have similar functionality) which allows you to place the system in debug mode and you are then able to step through program execution, view register values, etc.. When in this configuration does the entire system halt and wait for you to "step through" the code? or are there more processes running in the background?
Electronic – When a microcontroller is in debug mode, does it freeze the entire MCU
debuggingmicrocontroller
Related Solutions
Recently, I deployed a few units of a new embedded product for a friendly trial. I was trying to discover how well the IP stack performed out in the real world, so using the on-board ethernet for debug wasn't an option.
I bought several serial dataloggers from Sparkfun (many similar devices are available) and attached one to each unit over TTL serial. When I got the units back, I retrieved the logs from the SD cards.
In the case of a system crash, dumping registers out to the serial port will let you find the offending code via the map file later.
I used an assembly template located here from Bill Howl on this website and wrapped your delay routine around it.
I payed particular attention to the port initialization routine example given on the microchip datasheet pg 124 Example 12-1 Initializing port A. The BANKSEL PORTA just before the delay routine and port toggling kicks off is crucial! Doesn't appear to have the problem your are experiencing with the program counter. Simulated for 806 seconds... And no issues. Sometimes it helps to clean the project code up by clicking project, clean.
Your second piece of code is causing stack overflow errors
CORE-E0001: Stack over flow error occurred from instruction at 0x000037
CORE-E0001: Stack over flow error occurred from instruction at 0x000037
CORE-E0001: Stack over flow error occurred from instruction at 0x000037
CORE-E0001: Stack over flow error occurred from instruction at 0x000038
This is because you are missing the return statement in the AUXHELLOWORLD block.
When your code starts it would cause an infinite never-ending loop of these two calls (initialise and auxhelloworld) each time adding to the stack and never getting popped back.
Eventually the stack will be overwhelmed and lose track of where it is supposed to return causing strange code behaviour and program counter to jump about.
START
CALL INITIALISE
CALL AUXHELLOWORLD
Try the template!
Really you should learn c code and download the microchip or Hitech c compiler. It will make your life much easier... You won't go back to assembly!
Furthermore you can also incorporate assembly in c code, if you really needed the specialised code.
Related Topic
- Electronic – Power cycle error when trying to program/debug HCS08 MCU
- Electronic – Altera Cyclone IV FPGA and jtag debugging
- Electronic – STM32 Sleep Mode: Interrupt gets executed but the CPU stays in WFI
- Electronic – OpenOCD child process termination: Wrong device detected
- Electronic – Am I using ARM 7 LPC21xx ADC register correctly
- Electronic – STM32F7 device freeze: cannot access registers
- Electronic – STM32F407 Clock Configuration Order
Best Answer
It depends on the MCU. Some (like TI's C2000 line) have a debug mode that allows the CPU to take interrupts while stepping through non-interrupt code. Timing and communication peripherals may have an option to continue working while the CPU is halted. But unless the documentation says otherwise or you've done some special configuration, you should assume that all peripheral activity will halt along with the CPU.