This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ARM TOOLS QUIRKINESS

I'm evaluating the Demo version of the ARM7 tools from Keil and notice a lot of unusual quirkiness when dealing with the Flash erase procedure called out in Philips' IAP section. Many times I've had to power down the eval MCB2100 board, constantly re-enter Debug mode, do the hokey-pokey, etc. to re-establish the code and get it to run.

On one occasion, I had put into the Memory Window address 0xFFFFF030 (or any other address from the Vectored Interrupt Controller (VIC)) and my target just froze up.

Anyone else experiencing strange stuff with this eval board and ARM7 tools?
Thanks.

Parents
  • I know about the issues you raised.

    The flash download process works okay and the code works. But like I said, I press the run button and sometimes the target (LED's lite) runs okay and sometimes the target does nothing at all. I set break points and it appear to go into the ether during the flash erase/programming stuff in the IAP.

Reply
  • I know about the issues you raised.

    The flash download process works okay and the code works. But like I said, I press the run button and sometimes the target (LED's lite) runs okay and sometimes the target does nothing at all. I set break points and it appear to go into the ether during the flash erase/programming stuff in the IAP.

Children